Let's root the Max Lumi 2 - Page 5

Machinus · 04-08-2022, 09:55 AM

Code:

MaxLumi2:/ $ ls -l /sbin
ls: /sbin: No such file or directory

MaxLumi2:/ $ mount|grep magisk
...

MaxLumi2:/ $ which su
/system/bin/su

MaxLumi2:/ $ ls -lZ /system/bin/su
lrwxrwxrwx 1 root root u:object_r:system_file:s0 8 1970-01-01 02:39 /system/bin/su -> ./magisk

MaxLumi2:/ $ dmesg|grep denied.*su
dmesg: klogctl: Permission denied
MaxLumi2:/ $

Renate · 04-08-2022, 10:27 AM

Well, it's clearly running a Magisk-ed image. Is all the normal stuff running normally? What version Magisk did you use to convert your boot file?

Code:

$ ls -lZ /.magisk

Does the Magisk app tell you anything about the status?

Edit: Please post the magisk file.

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

Quote:

Originally Posted by Renate

Well, it's clearly running a Magisk-ed image. Is all the normal stuff running normally? What version Magisk did you use to convert your boot file?

Code:

$ ls -lZ /.magisk

Does the Magisk app tell you anything about the status?

Edit: Please post the magisk file.

Magisk 24.3

Code:

1|MaxLumi2:/ $ ls -lZ /.magisk
ls: /.magisk: No such file or directory

I made a dumb mistake. I forgot to enable SU in the app.

Code:

1|MaxLumi2:/ $ su
MaxLumi2:/ #

Renate · 04-08-2022, 11:09 AM

Success!

Thank you for your patience. We managed to stumble through this one.

Machinus · 04-08-2022, 11:20 AM

Quote:

Originally Posted by Renate

Success!

Thank you for your patience. We managed to stumble through this one.

I should be thanking you. I am a total noob.

Noctuelles · 05-15-2022, 05:03 PM

Incredible.
Thanks for your replies Renate !
Yeah i used a custom loader that i found on the web, on a strange looking website but it did the trick.

brianting · 05-24-2022, 05:14 AM

Quote:

Originally Posted by Renate

Hi @amghwk - sorry that I didn't notice your earlier post.
Edit: Your problem may be different, but you might try my way anyway.
There are also mysterious cases where "fastboot boot" does not work but "fastboot flash" and then regular boot does work. If you have backups you should be able to play safely.

Hi @Machinus

If you have access to a (real, not virtual) Windows box, I can probably help you. I have an EDL utility for Windows. What you are trying to do is very simple, and it should be simple.

Go to the website in my signature and navigate to the EDL page. It's a bit of a beta, but I'm willing to work with anybody that is having problems.

Step 0: Download edl.exe, it's 132kB with no dependencies.
Step 1: Get into EDL (05c6/9008) mode
Step 2: Got a driver for it? If not download "Zadig" and give it one.
Step 3: Got a loader for it? If not download this, it should be the correct one if you have the same model as the OP:
https://github.com/bkerler/Loaders/r...4665_FHPRG.bin
Oh, you were looking forward to downloading 100 Megs of loaders that you will never use. Sorry to disappoint you.
Step 4: Rename the file something sensible.
Step5:

Code:

C:\>edl.exe /lsomething-sensible

He, he, I was only kidding about something sensible, don't forget the "/l" before it.
Step 6: Since you're running A/B you have to know which boot_x is the right one:

Code:

C:\>edl.exe /u /g

Step 7: One of them is inactive, choose the other one:

Code:

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

And the result should be the (correct) ~20Megs and not 20Megs + 80Megs of zeroes.
Step 8: If you are in doubt what you have just downloaded, get my ImgUtil.exe and do:

Code:

C:\>imgutil.exe /v boot.img
Header:           596 (00000254)
Kernel:    12,937,496 (00C56918) @ 00008000
  Payload: 12,636,840 (00C0D2A8)
  DTB:        300,656 (00049670)
Ramdisk:            0 (00000000) @ 01000000
Second:             0 (00000000) @ 00F00000

(Or something similar, the numbers will be different for you.)

Good luck!

my problem is after the sahara protocol, the firehose one came out with this error

C:\Users\Administrator\Desktop\edl thing>edl.exe /lprog_ufs_firehose_sdm855_ddr.elf /u /g
Found EDL 9008
Serial: e3fc032c
HWID: 000a50e100290025, QC: 000a50e1, OEM: 0029, Model: 0025
Hash: 7e5acfff90370967-edd2bdf205a9ebc9-035abca140b3ab9b-b7771bd7c27057cb
Sending prog_ufs_firehose_sdm855_ddr.elf 100% Ok
Waiting for Firehose... Ok
Configuring... Ok
Requesting GPT 0 header...
<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:0 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 344384084" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3" />
Nope

Renate · 05-24-2022, 10:10 AM

Quote:

Originally Posted by brianting

C:\Users\Administrator\Desktop\edl thing>edl.exe /lprog_ufs_firehose_sdm855_ddr.elf /u /g

What is your device? Is it a "Asus Wingtech"??? Are you sure that it is using UFS? Try without the /u flag.
You might try the loader: https://github.com/bkerler/Loaders/b...rg_zs660kl.bin

brianting · 05-26-2022, 06:11 AM

Quote:

Originally Posted by Renate

What is your device? Is it a "Asus Wingtech"??? Are you sure that it is using UFS? Try without the /u flag.
You might try the loader: https://github.com/bkerler/Loaders/b...rg_zs660kl.bin

hello
my device is rog phone 2, and the internet does say that is is using ufs and i did try using without the /u, no luck. Do you have any ideas?

BR

Renate · 05-26-2022, 12:23 PM

Did you try the other loader that I mentioned? The device numbers on your loader could be off. What is the MD5 / size of your loader?

If nothing works, try some small (0-9) numbers:

Code:

C:\>edl.exe /u0 /g
C:\>edl.exe /u1 /g
...

brianting · 05-27-2022, 04:26 AM

Quote:

Originally Posted by Renate

Did you try the other loader that I mentioned? The device numbers on your loader could be off. What is the MD5 / size of your loader?

If nothing works, try some small (0-9) numbers:

Code:

C:\>edl.exe /u0 /g
C:\>edl.exe /u1 /g
...

sorry to ask but how do can i install .bin file for my loader

Renate · 05-27-2022, 06:22 AM

Huh? You don't "install" any files, you just copy them.
An EDL "loader" file is a kind of ELF executable file although it could end in .bin or anything.
In my sig you can find elfview.exe which can be used to check ELF files:

Code:

C:\>elfview.exe /v /p /l poke3.bin
Type:   executable
CPU:    ARM 64-bit architecture (AARCH64)
Linker: none
Libs:   none

 #  Type     Flags     Size  Offset  Address
--  -------  -----  -------  ------  --------
 0  null                792  000000  00000000
 1  null               6856  001000  85e28000
 2  load     RX      356508  003000  14015000
 3  load     RWZ          0  05A0A0  14077000
 4  load     RW       40704  05A0A0  1407a000
 5  load     RWX      39176  063FA0  14084800
 6  load     RWZ          0  06D8B0  85e10000
 7  load     RX        7804  06D8B0  146ae000
 8  load     RWZ          0  06F730  146b1000
 9  load     RWX     100568  06F730  14098000
10  load     RWZ          0  088010  146b2000
11  load     RWZ          0  088010  14680000
12  load     RX       77248  088010  14699000

 #  Name                      Type       Flags     Size  Offset  Address
--  ------------------------  ---------  -----  -------  ------  --------
    program header table                            728  000040
    end of file

So, just download that loader that I linked and try that.
And while you're at it, please give me the info on what you were using as a loader.

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

The Lumi2 un-rooted itself after the latest firmware update. I'm not sure how to prevent this.

This time, I could not find a way to force Windows to install the google *.inf driver, meaning that it is impossible to get fastboot to execute. I spent much longer trying to get this to work this time, but was not successful. The conditions for getting fastboot to execute on Windows 10 seem to be difficult. I followed the procedure I figured out before, but no matter what I tried, I always got the error "The folder you specified doesn't contain a compatible driver for your device."

However, after several attempts, "fastbogus" was able to load a patched *.boot file after the firmware update, so it is rooted that way.

Renate · 05-30-2022, 05:26 PM

Quote:

Originally Posted by Machinus

The Lumi2 un-rooted itself after the latest firmware update. I'm not sure how to prevent this.

Code:

# pm disable com.onyx.android.onyxotaservice

Yes, it does start getting complicated with updates.

I like using my custom recovery + flash drive method to update. Ok, it is a bit silly, but you can do that when you can't boot to normal system.

turtle_san · 11-19-2022, 08:09 PM

Hello, I wasn't able to get the instructions here working originally, but I figured it out reading a similar guide: https://blog.tho.ms/hacks/2021/03/27...-note-air.html

The problem was from

Quote:

Step 11

To get into the bootloader I did

Quote:

adb reboot fastboot

And from the menu it gave me, selected to start bootloader

This is instead of the command that didn't work:

Quote:

adb reboot bootloader

Only this way did the next command work

Quote:

fastboot boot <file_name>

04-08-2022, 10:27 AM	#62
Renate Onyx-maniac Posts: 3,544 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Well, it's clearly running a Magisk-ed image. Is all the normal stuff running normally? What version Magisk did you use to convert your boot file? Code: $ ls -lZ /.magisk Does the Magisk app tell you anything about the status? Edit: Please post the magisk file. Last edited by Renate; 04-08-2022 at 10:31 AM.

05-26-2022, 12:23 PM	#70
Renate Onyx-maniac Posts: 3,544 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Did you try the other loader that I mentioned? The device numbers on your loader could be off. What is the MD5 / size of your loader? If nothing works, try some small (0-9) numbers: Code: C:\>edl.exe /u0 /g C:\>edl.exe /u1 /g ...

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

04-08-2022, 11:09 AM	#64
Renate Onyx-maniac Posts: 3,544 Karma: 14705253 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Success! Thank you for your patience. We managed to stumble through this one.

05-15-2022, 05:03 PM	#66
Noctuelles Junior Member Posts: 2 Karma: 10 Join Date: Jan 2022 Device: Onyx Boox Max Lumi 2	Incredible. Thanks for your replies Renate ! Yeah i used a custom loader that i found on the web, on a strange looking website but it did the trick.

05-30-2022, 04:07 PM	#73
Machinus Enthusiast Posts: 42 Karma: 10 Join Date: Sep 2017 Device: Kindle	The Lumi2 un-rooted itself after the latest firmware update. I'm not sure how to prevent this. This time, I could not find a way to force Windows to install the google .inf driver, meaning that it is impossible to get fastboot to execute. I spent much longer trying to get this to work this time, but was not successful. The conditions for getting fastboot to execute on Windows 10 seem to be difficult. I followed the procedure I figured out before, but no matter what I tried, I always got the error "The folder you specified doesn't contain a compatible driver for your device." However, after several attempts, "fastbogus" was able to load a patched .boot file after the firmware update, so it is rooted that way.

Advert

Advert