Max 3 Rooted

[mouth]

Originally Posted by Galunid

That's actually not 100% correct. Nova3 isn't supported by decryptor afaik. You need to first root the device to get the decryption keys, so someone has to do the honors with EDL

This has been my experience. I attempted to decrypt the downloaded update.upx file via the following URL:

http://firmware-us.boox.com/865e7836a4d6da883e52ed2822f60b9c/update.upx

Which was derived from:

http://data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user","deviceMAC":"","lang":"en_US","model":"Nova3","submodel":"","fingerprint":""}

And it failed to decrypt after updating the DeBooxUpx.py file in the cloned Hagb / decryptBooxUpdateUpx Git repository with the following boox_strings variable sub-object, which was acquired after following the instructions How to get the strings:

'Nova3': {
	"MODEL": "Nova3",
	"STRING_7F00500": "VUkFew9KjsE54uQMSZI+S2tT1RRckT/vKkfiFFqImxi7",  # settings
	"STRING_7F00501": "VEsMcHw88MpwOByhT7zqNhRFTQcruVMqhdllIlY6T+6f",  # upgrade
	"STRING_7F00502": "TGlcNi8npJe4EHxzOKbCXakJKDssoRldHueY5OGl"       # local
}

I am more than happy to assist with rooting my Nova 3, but I lack the experience and knowhow to do so. What is the appropriate programmer file to use when attempting to backup the boot/recovery images for the Qualcomm® Snapdragon™ 636?

Thanks in advance!

[yokos]

Dear mouth, did you get a python error message running your edited DeBooxUpx.py?
In your code snippet your last line should be "},"

We don't need this edl stuff, if your Nova 3 strings are right.

[yokos]

I got my boot.img using DeBooxUpdate.py for Max Lumi. But I can't test it, because it is hard to buy a Max Lumi right now.

[mouth]

Originally Posted by yokos

Dear mouth, did you get a python error message running your edited DeBooxUpx.py?
In your code snippet your last line should be "},"

We don't need this edl stuff, if your Nova 3 strings are right.

No error; In the Python file, I did have a comma after the curly bracket, and it does export a zip file, but that archive is not readable by any archive software I have tried.

[Galunid]

Originally Posted by mouth

No error; In the Python file, I did have a comma after the curly bracket, and it does export a zip file, but that archive is not readable by any archive software I have tried.

Actually I managed to decrypt the update with your strings without any problem. I attach decrypted boot.img partition. I zipped it, because mobileread doesn't take .img files

Maybe the reason for your problem is malformed update.upx file?
Hope it helps you.

EDIT: Use this file at your own risk of course. There shouldn't be any problems with it, but who knows.

[diabl0w]

Originally Posted by Galunid

That's actually not 100% correct. Nova3 isn't supported by decryptor afaik. You need to first root the device to get the decryption keys, so someone has to do the honors with EDL

it is 100% correct... you don't need root to get the decryption keys, the /system is world readable

[Galunid]

Originally Posted by diabl0w

it is 100% correct... you don't need root to get the decryption keys, the /system is world readable

Yes, my bad, I edited the message not to spread confusion. I guess I was thinking of some other app I needed root to extract.

[mePy2]

Hi guys, can you help me in understanding what root can be useful at? And also to understand what the tools you listed do?
I am a Max2 Pro owner and I really would like to personalise my Boox more.

Cheers

[diabl0w]

updated TWRP to include resetprop binary for easier OTA's

[M4H35H]

Originally Posted by mePy2

Hi guys, can you help me in understanding what root can be useful at? And also to understand what the tools you listed do?
I am a Max2 Pro owner and I really would like to personalise my Boox more.

Cheers

I imagine there's no real answer to that. The question was asked by someone else and there was no reply.

[orebmur]

Originally Posted by mePy2

can you help me in understanding what root can be useful at?

Take ownership of the device and ensure it actually becomes your property, empowering yourself to make practical use of the full potential of the device capabilities.

If the manufacturer is the only one who can decide what can be done and not be done on a given device, the buyer of the computer/phone/e-reader doesn't really own it and is not free to use it on his/her own terms.

This is at the same time a question of liberty and of technical flexibility.

Unfortunately, most people are only consumer minded and simply don't care, with all the negative consequences this includes, and that's what the manufacturers in the end cater to, effectively limiting and even prohibiting to use the inherent potential of the sold devices for everyone.

Recommended fuel for thought: www.gnu.org/philosophy/free-hardware-designs.en.html

We live in very strange times indeed.

[mouth]

Originally Posted by Galunid

Actually I managed to decrypt the update with your strings without any problem. I attach decrypted boot.img partition. I zipped it, because mobileread doesn't take .img files

Maybe the reason for your problem is malformed update.upx file?
Hope it helps you.

EDIT: Use this file at your own risk of course. There shouldn't be any problems with it, but who knows.

Thanks!

[mouth]

For those of you interested, I was able to pull the following strings for the BOOX Note Air:

'NoteAir': {
	"MODEL": "NoteAir",
	"STRING_7F00500": "U04vqHYo0LFoJQAvP3Rs1aBxySs7z4T1B+asamimEoAf",  # settings
	"STRING_7F00501": "VD1ZqgIl08305CVeftRI7qGBtq9bCMrJ3a1VkpkzjOu2",  # upgrade
	"STRING_7F00502": "PW8K6VI//Zt6iqjYQWN0LIwRTVYyDHJvHNEXFwWV"       # local
},

The current firmware URL is:

http://firmware-us.boox.com/3df6fad536d71c6e8fa2df5a7fc710fe/update.upx

Which was derived via the following URL:

http://data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user","deviceMAC":"","lang":"en_US","model":"NoteAir","submodel":"","fingerprint":""}

I will post an update once I successfully decrypt the file.

[qls0519]

note2 flash your twrp.img. , following your guide.
reboot to recovery , stuck at a black screen
max3 should have the same chip as note2.
what should i do?

[yokos]

Originally Posted by qls0519

note2 flash your twrp.img. , following your guide.
reboot to recovery , stuck at a black screen
max3 should have the same chip as note2.
what should i do?

Flash an original Note 2 recovery of course.
If you don't have it, you will need to extract it via phyton from Note 2 upx file.