Recover hard-bricked Max Lumi 2

[Renate]

Originally Posted by richard.black

Hey, here is my recovery:

If it's a challenge for me to download 16 MB on my internet, what am I supposed to do with 1.7 GB? (Also, I could download that directly myself.) I just wanted the recovery image, zipped.

[richard.black]

If it's a challenge for me to download 16 MB on my internet, what am I supposed to do with 1.7 GB?

Sorry, my bad

Here's the recovery:
https://send.vis.ee/download/c2c7fb2...yUjj98Hb09V93w

Also,

Originally Posted by Renate

The recovery looks ok. If we run into problems we can fine tune it. But it needs to run first.

[Renate]

Originally Posted by richard.black

Here's the recovery:

Thank you for the file. I noticed that it's actually not zipped. I noticed that 50 MB (over half) of it is zeroes. A zipped file would not have included that. But it's all for the good. As a programmer I often write:

x=0;

So where do you think those zeores come from? Certainly not out of thin air. I rely on public spirited people to ship me those zeroes.

[richard.black]

I noticed that it's actually not zipped. I noticed that 50 MB (over half) of it is zeroes. A zipped file would not have included that.

Again, my bad

So where do you think those zeores come from? Certainly not out of thin air. I rely on public spirited people to ship me those zeroes.

Wow! then you must have a lot of zeroes...

[Renate]

So, read your PM, download a file.

Proceed slowly.

Install and run UsbLog.exe from my sig in Windows page

In EDL flash recovery and misc (with misc-recovery) and edl /z

You will get a white screen (hopefully)

Does UsbLog say 18d1 4ee7?

adb devices - does it say device 12345678?

adb shell - does it give # ?

id - does it give 0 and su ?

getenforce - does it give permissive?

start recovery - does it get you text menu after a few seconds?

type "reboot recovery"

adb shell

start ttyscreen - what does the screen do?

[richard.black]

You will get a white screen (hopefully)

Yes, but I don't think its the right one, still 900E system crash.

Does UsbLog say 18d1 4ee7?

I tried a lot, but the only ones I get are 18d1 d001 & 18d1 d00d

adb devices - does it say device 12345678?

adb shell - does it give # ?

id - does it give 0 and su ?

getenforce - does it give permissive?

start recovery - does it get you text menu after a few seconds?

type "reboot recovery"

adb shell

start ttyscreen - what does the screen do?

I can't get to it.

[richard.black]

Now, with misc-recovery flashed, I can't boot to Recovery.
When not booting to recovery, it's still a 900E system crash.

[Renate]

Once again I'm confused.
18d1 d001 is ADB sideload, indicating the original recovery.
18d1 d00d is fastboot (running from abl)
05c6 900e could be my recovery, but are you sure that it's not the (broken) regular system?

And you say, "Now with misc-recovery flashed". Was it not flashed before?

Check which slot you are on with edl /g. If in doubt flash both recovery slots with the test recovery. Always flash misc-recovery.

STOP THE PRESSES!

Download a new version, proceed from the start.

[richard.black]

I'm sorry

18d1 d001 is ADB sideload, indicating the original recovery.

It does? It does! When adb shell didn't work after flashing your recovery, I flashed all the partitions from payload.bin to device and made sure super is correct. I'm sorry if that confused you.

18d1 d00d is fastboot (running from abl)

Yes. I used edl.exe /zf for that one. I was checking every command to see if anything worked. I shouldn't have mentioned that.

05c6 900e could be my recovery, but are you sure that it's not the (broken) regular system?

I'll get to that in a bit.

And you say, "Now with misc-recovery flashed". Was it not flashed before?

There's something you got to understand: On my device, when I flash /misc with misc-recovery (boot-recovery), it will boot to Android Recovery. And when it is zeroed, it will boot normally and crash. I'm sorry I cannot flash /misc and expect it to boot normally to check if my changes made any effect, I have to clear /misc every time.

Check which slot you are on with edl /g. If in doubt flash both recovery slots with the test recovery.

I'm on slot a and both are now flashed correctly.

Always flash misc-recovery.

Just tell me if you want to boot normally or to Android Recovery. I'll do it.

Here's the thing, when I flash /misc, the device doesn't even connect to my laptop in any manner (normal, recovery, plugged in, connect after booting up).
When I zeroes /misc, the device system crashed every time (normal, recovery, plugged in, connect after booting up).

[Renate]

I'm giving you a custom recovery to flash to recovery and I want you to flash misc so it goes to recovery.

Is that clear enough?

Now, since I just posted a new one with the last message, instead of telling me all the stuff that I didn't ask you to do that you did do, why don't you you tell me how the new one reacted differently from the old one.

I don't care about the normal system, I don't care about super, I don't care about fastboot.

[richard.black]

why don't you you tell me how the new one reacted differently from the old one.

It doesn't even connect to my laptop through USB. I've carefully monitored Device Manager and UsbLog (also usbview). No status code.

Again, Sorry

[Renate]

Ok, there's a new version up, flash it, flash misc, /z

1) Does the frontlight of the screen flash 10 times?
2) Does anything appear on the screen? Either "ttyscreen" or confused slanting lines.

If either of these happened go to EDL afterwards and

edl /u /r /psplash splash.img

Then zip and post it.

Obviously if ADB appeared too, do the checklist from the previous post.

[richard.black]

1) Does the frontlight of the screen flash 10 times?

It did!

2) Does anything appear on the screen? Either "ttyscreen" or confused slanting lines.

It said "ttyscreen has started"

Obviously if ADB appeared too, do the checklist from the previous post.

adb didn't work.
Here's the zip file (zipped correctly, 33MB to 66KB):

[richard.black]

Okay, adb works, too.

Does UsbLog say 18d1 4ee7?

Yes!

adb devices - does it say device 12345678?

Yes!

adb shell - does it give # ?

Yes!

id - does it give 0 and su ?

# id
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0

getenforce - does it give permissive?

Yes! Permissive.

start recovery - does it get you text menu after a few seconds?

Yes!

type "reboot recovery"

# reboot recovery
Could not open BCB on misc

start ttyscreen - what does the screen do?

Nothing. No error. Android recovery menu works.

[Renate]

Originally Posted by richard.black

Okay, adb works, too.

Why did you say initially that it didn't work? What happened?

It looks like your recovery (as unmodified) is broken.
Go to ADB in my recovery.

ls -l /dev/block
ls -l /dev/block/by-name
ls -l /cache

Just post it as a text file.