Let's root the Max Lumi 2 - Page 2

Renate · 04-07-2022, 10:50 AM

Ok, that's all correct except for these silly panicky errors.

The 70% is wrong. You may have flakey USB. Try it again. Try another cable. Try:

Code:

C:\>edl.exe /u /r /pboot_a long.img
C:\>edl.exe /u /r /pboot_a short.img /c4025

Machinus · 04-07-2022, 10:53 AM

Quote:

Originally Posted by Renate

Ok, that's all correct except for these silly panicky errors.

The 70% is wrong. You may have flakey USB. Try it again. Try another cable. Try:

Code:

C:\>edl.exe /u /r /pboot_a long.img
C:\>edl.exe /u /r /pboot_a short.img /c4025

I switched cables and port.

Code:

C:\>edl.exe /u /r /pboot_a boot.img /t
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 1 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 2 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 3 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 4 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 5 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting header... Ok, receiving... Ok
Android: 4025 / 24576 = 16.4%
Requesting read boot.img... Ok, receiving 100% Ok

C:\>edl.exe /u /r /pboot_a long.img
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 1 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 2 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 3 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 4 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 5 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting read long.img... Ok, receiving 100% Ok

C:\>edl.exe /u /r /pboot_a short.img /c4025
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 1 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 2 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 3 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 4 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 5 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting read short.img... Ok, receiving 100% Ok

Renate · 04-07-2022, 10:57 AM

So, everything works fine.
You should have two 16 Meg files that are exactly the same and one 100 Meg file that is the same as the 16 with 80 Megs of zeroes on the end.
Any of them are acceptable to Magisk for patching. Just follow the rest of the OP instructions.

Machinus · 04-07-2022, 11:23 AM

Quote:

Originally Posted by Renate

So, everything works fine.
You should have two 16 Meg files that are exactly the same and one 100 Meg file that is the same as the 16 with 80 Megs of zeroes on the end.
Any of them are acceptable to Magisk for patching. Just follow the rest of the OP instructions.

I was able to patch with Magisk.

The short img file is 16,486,400 bytes.
The patched img file is 17,321,984 bytes.

But, it looks like the device disconnects at the fastboot command:

Code:

C:\>adb devices
List of devices attached
16E91C12        device

C:\adb reboot bootloader

C:\>fastboot boot magisk_patched-24300_I3L2y.img
< waiting for any device >

The device freezes, disappears from Windows, and your usb logger shows a red event. What else am I doing wrong?

Renate · 04-07-2022, 11:42 AM

Hmm.. Just as a reality check, do a fastboot boot short.img

There are times (still to be investigated) where fastboot boot does not work, but fastboot flash, then reboot does.

You've got long.img, which, no matter how we screwed up is the entire boot partition.

On my Android page get imgutil.exe and check your images, see post #6

If everything still looks sane, just try flashing.

Machinus · 04-07-2022, 12:06 PM

Quote:

Originally Posted by Renate

Hmm.. Just as a reality check, do a fastboot boot short.img

There are times (still to be investigated) where fastboot boot does not work, but fastboot flash, then reboot does.

Both of those commands lead to hanging.

Code:

C:\>adb devices
List of devices attached
16E91C12        device

C:\>fastboot boot short.img
< waiting for any device >

C:\>fastboot flash
< waiting for any device >

Renate · 04-07-2022, 12:16 PM

Something is screwy.

Code:

C:\>fastboot getvar all

Is UsbLog showing a green device? Maybe with "d00d" in it?
Do you have a driver for fastboot? Zadig is your friend here too.

If you really want and can get back to EDL, you could:

Code:

C:\>edl.exe /lwhatever.bin
C:\>edl.exe /u /w /pboot_a magisk_whatever
C:\>edl.exe /z

Machinus · 04-07-2022, 12:29 PM

Quote:

Originally Posted by Renate

Something is screwy.

Code:

C:\>fastboot getvar all

Is UsbLog showing a green device? Maybe with "d00d" in it?
Do you have a driver for fastboot? Zadig is your friend here too.

If you really want and can get back to EDL, you could:

Code:

C:\>edl.exe /lwhatever.bin
C:\>edl.exe /u /w /pboot_a magisk_whatever
C:\>edl.exe /z

USBlog shows green. No flag message.

No "fastboot" appears in the drivers list of Zadig.

Code:

C:\>fastboot getvar all
< waiting for any device >

Code:

C:\>edl.exe /lQualcomm_662_loader.elf
Found EDL 9008
Serial: a2c376a9
HWID: 0014d0e100000000, QC: 0014d0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955
Sending Qualcomm_662_loader.elf 100% Ok
Waiting for Firehose... Ok

C:\>edl.exe /u /w /pboot_a magisk_patched-24300_I3L2y.img
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 1 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 2 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 3 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 4 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 5 header... Ok, receiving... Ok, requesting entries... Ok, receiving... Ok
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting write magisk_patched-24300_I3L2y.img... Ok, sending   0% Ok

C:\>edl.exe /z
Found EDL 9008
Requesting reboot... Ok

The device does not reboot.

Renate · 04-07-2022, 12:38 PM

More and more screwiness.
I don't understand that 0% Ok, that makes no sense. Did it actually go to 100% but it's not showing that?

Late in the day for asking this, but the Max Lumi 2 has buttons so that you can always get to fastboot?

Go to fastboot. Plug, unplug the cable a few times. UsbLog should probably show 18d1/d00d in green when it's plugged in and Windows should not complain.
If UsbLog is not changing all pretty, go to Zadig, Options, List all devices and look for 18d1/d00d, install driver.

Edit: Once again I'm guilty of bad/misleading messages from edl.exe, but (probably?) not of the actual problem. Thanks for helping me clear them up!

I think that you're still having flakey USB problems

Sheesh: There's a new edl.exe up at 131,584 bytes.

In my own defense, I'll just say that I've been using edl.exe on something else and have been slinging partitions around for hours without any problems.

Machinus · 04-07-2022, 01:18 PM

Quote:

Originally Posted by Renate

Late in the day for asking this, but the Max Lumi 2 has buttons so that you can always get to fastboot?

The Lumi 2 has a power button on top, which can hard reset after 15 seconds, and a "back" button on the front. By go to fastboot, do you mean hard reset?

I have it plugged directly into the motherboard root hub in the back of my PC, with a brand new short cable.

I have not been able to see a fastboot device or a d00d in the Zadig list.

Renate · 04-07-2022, 01:35 PM

Ok, it's time to dive in. Do you know UsbView.exe? It's here: https://www.ftdichip.com/Support/Uti...crosoftUSBView
Figure out which location on the left side of the screen which is your port.
Just plug/unplug whatever and look for changes.
Make your Lumi go to fastboot.
Look in the right side of the screen for Class/Subclass/Protocol of ff/42/03 that's fastboot.

Code:

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0xFF
bInterfaceSubClass:   0x42
bInterfaceProtocol:   0x03

Then look up at the top:

Code:

Device Descriptor:
bcdUSB:             0x0310
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x09 (9)
idVendor:           0x18D1
idProduct:          0xD00D

Edit: And it should also say this:

Code:

Open Pipes:              2

Check the VID/PID (idVendor/idProduct). Do they show up in UsbLog nice in green?
If not, find it in Zadig and load a new driver.
Does fastboot getvar all work? (It should spit out 100 lines).

SleepWithMachine · 04-07-2022, 03:33 PM

That should also work on the Nova Air C, right? Same CPU, same OS. I'll try it right away, thanks for the tutorial

Machinus · 04-07-2022, 04:33 PM

Quote:

Originally Posted by Renate

Ok, it's time to dive in. Do you know UsbView.exe? It's here: https://www.ftdichip.com/Support/Uti...crosoftUSBView
Figure out which location on the left side of the screen which is your port.
Just plug/unplug whatever and look for changes.
Make your Lumi go to fastboot.
Look in the right side of the screen for Class/Subclass/Protocol of ff/42/03 that's fastboot.

Code:

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0xFF
bInterfaceSubClass:   0x42
bInterfaceProtocol:   0x03

Then look up at the top:

Code:

Device Descriptor:
bcdUSB:             0x0310
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x09 (9)
idVendor:           0x18D1
idProduct:          0xD00D

Edit: And it should also say this:

Code:

Open Pipes:              2

Check the VID/PID (idVendor/idProduct). Do they show up in UsbLog nice in green?
If not, find it in Zadig and load a new driver.
Does fastboot getvar all work? (It should spit out 100 lines).

I was delayed by other work, but I am back now.

I have found the Lumi2 in USBview.

Code:

Device Descriptor:
bcdUSB:             0x0320
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x09 (9)
idVendor:           0x18D1
idProduct:          0x4EE2
bcdDevice:          0x0419
iManufacturer:        0x01
0x0409: "QUALCOMM"
iProduct:             0x02
0x0409: "BENGAL-IDP _SN:A2C376A9"

Code:

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x03
bInterfaceClass:      0xFF
bInterfaceSubClass:   0xFF
bInterfaceProtocol:   0x00
iInterface:           0x05
0x0409: "MTP"
iSerialNumber:        0x03
0x0409: "16E91C12"
bNumConfigurations:   0x01

The utilty Usblog shows the "Location/ID" as 16E91C12.
VID: 18d1 (also 0000, 05c6)
PID: 4ee2 (also 4ee7, 0004, 9008)

Under "Name," there are multiple events from today, some of which have the following two IDs:

Code:

BENGAL-IDP _SN:A2C376A9

Code:

QUSB_BULK_CID:041C_SN:A2C376A9

However, I still am not able to issue any command "fastboot" in the ADB folder:

Code:

C:\>fastboot getvar
< waiting for any device >

Renate · 04-07-2022, 04:48 PM

Quote:

Originally Posted by SleepWithMachine

That should also work on the Nova Air C, right?

Probably. Onyx keeps a lot of commonality. Some of the kernels (but not the DTBs) are bit exact between different models. Please give it a try.

@Machinus 18d1/4ee2 is just the normal MTP,ADB when you're running a regular system. Can't you put it in fastboot mode? On devices with lots of buttons it's just hold VolUp as you do a full reset. You don't have that. From ADB either "adb reboot bootloader" or "adb reboot fastboot" normally gets you there no problem.

Maybe you should practice with your phone to check what the problem is? You can "fastboot getvar all" and "fastboot continue" without risking anything.

Edit: Did you try going back and try to flash it with EDL? At least the newest edl.exe should report the error better. Also, 0000/0004 (and similar) is some uninitialized USB interface.

Machinus · 04-07-2022, 05:42 PM

Quote:

Originally Posted by Renate

@Machinus 18d1/4ee2 is just the normal MTP,ADB when you're running a regular system. Can't you put it in fastboot mode? On devices with lots of buttons it's just hold VolUp as you do a full reset. You don't have that. From ADB either "adb reboot bootloader" or "adb reboot fastboot" normally gets you there no problem.

There is no volume button, so I have to do it from command line:

Code:

C:\>adb reboot bootloader

C:\>fastboot getvar
< waiting for any device >

Once I did this, I looked at the options in Zadig, and the new entry was "Android." I installed WinUSB for that. Once I did that, it showed up in usblog as PID "d00d", VID 18d1, and Name "Android."

This did not help fastboot work:

Code:

C:\>fastboot getvar
< waiting for any device >

I cannot get out of fastboot from command line. How do you do that?
I can hard reset, though.

Quote:

Originally Posted by Renate

Edit: Did you try going back and try to flash it with EDL? AT least the newest edl.exe should report the error better. Also, 0000/0004 (and similar) is some uninitialized USB interface.

I attempted the same commands you wrote, but the output did not change. It does not reboot.

Quote:

Originally Posted by Renate

Maybe you should practice with your phone to check what the problem is? You can "fastboot getvar all" and "fastboot continue" without risking anything.

I attempted to use my Blackberry. It showed up in adb devices, but also hangs on fastboot. Maybe I have a usb driver problem. What should I install?

04-07-2022, 10:50 AM	#16
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Ok, that's all correct except for these silly panicky errors. The 70% is wrong. You may have flakey USB. Try it again. Try another cable. Try: Code: C:\>edl.exe /u /r /pboot_a long.img C:\>edl.exe /u /r /pboot_a short.img /c4025

04-07-2022, 10:57 AM	#18
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	So, everything works fine. You should have two 16 Meg files that are exactly the same and one 100 Meg file that is the same as the 16 with 80 Megs of zeroes on the end. Any of them are acceptable to Magisk for patching. Just follow the rest of the OP instructions. Last edited by Renate; 04-07-2022 at 11:06 AM.

04-07-2022, 12:16 PM	#22
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Something is screwy. Code: C:\>fastboot getvar all Is UsbLog showing a green device? Maybe with "d00d" in it? Do you have a driver for fastboot? Zadig is your friend here too. If you really want and can get back to EDL, you could: Code: C:\>edl.exe /lwhatever.bin C:\>edl.exe /u /w /pboot_a magisk_whatever C:\>edl.exe /z

04-07-2022, 12:38 PM	#24
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	More and more screwiness. I don't understand that 0% Ok, that makes no sense. Did it actually go to 100% but it's not showing that? Late in the day for asking this, but the Max Lumi 2 has buttons so that you can always get to fastboot? Go to fastboot. Plug, unplug the cable a few times. UsbLog should probably show 18d1/d00d in green when it's plugged in and Windows should not complain. If UsbLog is not changing all pretty, go to Zadig, Options, List all devices and look for 18d1/d00d, install driver. Edit: Once again I'm guilty of bad/misleading messages from edl.exe, but (probably?) not of the actual problem. Thanks for helping me clear them up! I think that you're still having flakey USB problems Sheesh: There's a new edl.exe up at 131,584 bytes. In my own defense, I'll just say that I've been using edl.exe on something else and have been slinging partitions around for hours without any problems. Attached Thumbnails Last edited by Renate; 04-07-2022 at 01:16 PM.

04-07-2022, 01:35 PM	#26
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Ok, it's time to dive in. Do you know UsbView.exe? It's here: https://www.ftdichip.com/Support/Uti...crosoftUSBView Figure out which location on the left side of the screen which is your port. Just plug/unplug whatever and look for changes. Make your Lumi go to fastboot. Look in the right side of the screen for Class/Subclass/Protocol of ff/42/03 that's fastboot. Code: Interface Descriptor: bInterfaceNumber: 0x00 bAlternateSetting: 0x00 bNumEndpoints: 0x02 bInterfaceClass: 0xFF bInterfaceSubClass: 0x42 bInterfaceProtocol: 0x03 Then look up at the top: Code: Device Descriptor: bcdUSB: 0x0310 bDeviceClass: 0x00 bDeviceSubClass: 0x00 bDeviceProtocol: 0x00 bMaxPacketSize0: 0x09 (9) idVendor: 0x18D1 idProduct: 0xD00D Edit: And it should also say this: Code: Open Pipes: 2 Check the VID/PID (idVendor/idProduct). Do they show up in UsbLog nice in green? If not, find it in Zadig and load a new driver. Does fastboot getvar all work? (It should spit out 100 lines). Last edited by Renate; 04-07-2022 at 01:38 PM.

04-07-2022, 11:42 AM	#20
Renate Onyx-maniac Posts: 3,552 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Hmm.. Just as a reality check, do a fastboot boot short.img There are times (still to be investigated) where fastboot boot does not work, but fastboot flash, then reboot does. You've got long.img, which, no matter how we screwed up is the entire boot partition. On my Android page get imgutil.exe and check your images, see post #6 If everything still looks sane, just try flashing.

04-07-2022, 03:33 PM	#27
SleepWithMachine Zealot Posts: 109 Karma: 1924 Join Date: Dec 2019 Location: Puddingtown Device: some ..	That should also work on the Nova Air C, right? Same CPU, same OS. I'll try it right away, thanks for the tutorial

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Let's root our Max Lumi	yokos	Onyx Boox	116	12-02-2024 06:01 PM
Max Lumi - Is it possible to buy one yet anywhere?	Papered Over	Onyx Boox	15	03-12-2021 02:26 AM
Max 3 / Max Lumi: lack of physical buttons annoying?	mr_sm1th	Onyx Boox	6	12-19-2020 10:45 AM

Advert

Advert