Let's root the Max Lumi 2

[Machinus]

Now it won't go past the boot screen, even with the original img file. How do I undo that?

[Renate]

I just timed mine, 60 seconds total, but it sits on the original boot command for 30 seconds. And yes, I used fastbogus and not fastboot.

Is yours Android 11? Maybe they changed things.
But your reboot command just tells it to boot what is already in the flash.
Did anyone ever take a peek at their images using imgutil.exe /v just for sanity?

You can try "fastboot boot mag..." then "fastboot continue"
That may just boot up what's in flash too.

Why don't you zip up the magisk image and post it here or elsewhere.

[Machinus]

Originally Posted by Renate

I just timed mine, 60 seconds total, but it sits on the original boot command for 30 seconds. And yes, I used fastbogus and not fastboot.

Is yours Android 11? Maybe they changed things.
But your reboot command just tells it to boot what is already in the flash.
Did anyone ever take a peek at their images using imgutil.exe /v just for sanity?

You can try "fastboot boot mag..." then "fastboot continue"
That may just boot up what's in flash too.

Why don't you zip up the magisk image and post it here or elsewhere.

Lumi2 uses Android 11.

No "fastboot" commands work on my system. I have only been able to use "fastbogus" that you wrote. It won't leave the loading screen now.

C:\>fastbogus continue
Resuming boot                                      FAILED (remote: 'Failed to load image from partition: Load Error')
fastboot: error: Command failed

[Renate]

Right, fastboot, fastbogus.

It's the time of day when my internet goes to nothing, it's saying 30 minutes to download that file. No, it just said that it failed. Now it's saying an hour and a half.

A full reset doesn't get you back? You didn't even flash anything, right?

[Machinus]

Originally Posted by Renate

Right, fastboot, fastbogus.

It's the time of day when my internet goes to nothing, it's saying 30 minutes to download that file. No, it just said that it failed. Now it's saying an hour and a half.

A full reset doesn't get you back? You didn't even flash anything, right?

Hard reset is stuck on the "ONYX" boot screen.

If I reload the original img file, and reboot, it still is stuck on the loading screen.

I cannot get into normal adb mode, or edl mode. Both hard reset and "fastbogus reboot" only go back to fastboot mode. What do I need to do to get back to a normal boot sequence?

[Renate]

It doesn't sound good. Normally, since you didn't flash anything you should be fine.

Did you try a reset and then just "fastbogus continue"?

You need to check the images that you have. imgutil.exe /v
Did you make the 100 Meg backup too?

[Machinus]

Originally Posted by Renate

It doesn't sound good. Normally, since you didn't flash anything you should be fine.

What can I do with fastbogus to restore the previous settings?

Originally Posted by Renate

Did you try a reset and then just "fastbogus continue"?

C:\>fastbogus continue
Resuming boot                                      FAILED (remote: 'Failed to load image from partition: Load Error')
fastboot: error: Command failed

Originally Posted by Renate

You need to check the images that you have. imgutil.exe /v

I can do this, but I don't know anything about what to fix. This is above my knowledge.

Originally Posted by Renate

Did you make the 100 Meg backup too?

I have the long, short, and patched *.img files. How do I use them to restore the original boot?

https://easyupload.io/rwg3lu

[Renate]

Just to confirm:
You used edl.exe to get your boot files, long and short.
Things were working fine still after the last time you touched edl.exe
You could still get to normal Android.
After juggling problems with drivers and fastboot is when you stopped being able to get to Android (and ADB).

There is the other set of slots, but we don't know what's in there and it would be risky to just switch over.
Has this device already had one normal update to it?

You can do a "fastbogus getvar all" and compare it to the first one you got.

You might be able to "fastbogus boot long.img". Try it.

I finally got your Magisk'ed file.
It looks normal, but I'm not sure if the DTB is missing and it's using dtbo or what.
I'll have to look at the long.img tomorrow when my internet speed comes back up.
How about uploading it somewhere and PM me the link, please?
As long as you hold onto those files and we still have fastboot we haven't dug too deep a hole.

That's it for me for the night. My apologies.

[Machinus]

Originally Posted by Renate

Just to confirm:
You used edl.exe to get your boot files, long and short.

Yes, they are linked in the previous post.

Originally Posted by Renate

Things were working fine still after the last time you touched edl.exe
You could still get to normal Android.
After juggling problems with drivers and fastboot is when you stopped being able to get to Android (and ADB).

The device worked until I did this the second time:

C:\>fastbogus boot magisk_patched-24300_I3L2y.img
C:\>fastbogus reboot

Originally Posted by Renate

Has this device already had one normal update to it?

It is Android 11 with one Boox update.

Originally Posted by Renate

You can do a "fastbogus getvar all" and compare it to the first one you got.

Originally Posted by getvar #1

(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes

Originally Posted by getvar #2

(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no

[Machinus]

The getvar indicated the issue. I was able to get back to Android this way:

C:\>fastbogus --set-active=b
Setting current slot to 'b'                        OKAY [  0.048s]
Finished. Total time: 0.049s

C:\>fastbogus boot long.img
Sending 'boot.img' (98304 KB)                      OKAY [  2.265s]
Booting                                            OKAY [  0.093s]
Finished. Total time: 2.414s

Maybe I should not try to root this device since my fastboot is broken.

[Machinus]

I disabled signed driver requirement on Windows 10 and forced installation of ADB USB driver. This enables fastboot execution.

I repeated all steps that worked previously.

adb reboot edl

edl.exe /lQualcomm_662_loader.elf

edl.exe /u /r /pboot_a long.img

edl.exe /u /r /pboot_a short.img /c4025

--Magisk patch short.img--

adb reboot bootloader

fastboot boot magisk_patched-*.img

At this point, the device hangs and does not complete the boot.

Forcing a restart through hard-reset or "reboot" does not lead to su privileges in adb shell.

Magisk claimed the img was successfully patched, but it does not root. Flashing without root leads to frozen boot sequence.

[Renate]

Well, I'm glad that you're not disheartened, we're almost there.

Your boot image is in Android image header format #2.
Not being aware of this I lopped off the DTB and Magisk didn't notice.
Give me a couple of hours to write some new code and then write a test.

Until then, don't bother doing anything.
Except a copy of that long.img would be appreciated. Thanks, got them.

Also, if originally B was active, was the edl.exe /g indicating it the other way around?
Did the relabelling of the partitions not occur when there was a swap?
Another mystery.

[Renate]

Ok, we're ready. Download the latest edl.exe, it is 132,096 bytes

Try to figure out which is really the latest, _a or _b

C:\>edl.exe /lwhatever
C:\>edl.exe /u /r /pboot_a boot.img /t

You should get a nice file exactly 16,822,272 bytes.
Magisk it, fastboot boot it.

[Machinus]

Originally Posted by Renate

C:\>edl.exe /lwhatever
C:\>edl.exe /u /pboot_a boot.img /t

This does not work without /r flag.

04/08/2022  08:37 AM        16,822,272 boot.img

C:\>fastboot boot magisk_patched-24300_nNAMf.img
Sending 'boot.img' (16916 KB)                      OKAY [  0.388s]
Booting                                            OKAY [  0.097s]
Finished. Total time: 0.495s
C:\>adb shell
MaxLumi2:/ $ su
Permission denied

C:\>adb reboot bootloader
C:\>fastboot flash boot magisk_patched-24300_nNAMf.img
< waiting for any device >
Sending 'boot_b' (16916 KB)                        OKAY [  0.399s]
Writing 'boot_b'                                   OKAY [  0.104s]
Finished. Total time: 0.564s
C:\>fastboot reboot

C:\>adb shell
MaxLumi2:/ $ su
Permission denied

New long.img attached.

[Renate]

Originally Posted by Machinus

This does not work without /r flag.

Good point.

Since "su" is not part of stock and you're getting "Permission denied" and not "Not found"...

Have you actually got a Magisk image?

$ ls -l /sbin
magisk32.xz ...
magisk64.xz ...

$ mount|grep magisk
magisk ...

$ which su
<somepath>
$ ls -lZ <somepath>/su

$ dmesg|grep denied.*su