Loader for Onyx Boox Note 2 - Qualcomm Bengal (aka Snapdragon 662) #200
Comments
|
PS - the title is incorrect. Should be Onyx Boox Note Air 2... |
|
Please try b30f7c9 and make sure you do a submodule init and update to get the latest Loaders directory as well. |
|
Thanks for your response! I'm still learning my way around edl. When you speak of the submodule init and update, do you mean running the git submodule update line in the installation instructions? Thanks again!! |
|
The loader doesn't appear to be working, but I may have installed it incorrectly. How would I install this manually? Thanks! |
|
can you share the log to see why it doesn't work ? |
|
UbuntuTerminal.txt Thanks for your assistance. |
|
I thought that my Onyx Boox Note Air 2 had a Snapdragon 662 chip. I found out that the code name “bengal” covers more than one chip. I installed the CPU-Z app. It tells me that I have a Snapdragon 665. |
|
Hey guys, I have the same problem cannot make it work with Qualcomm Bengal, please let me know if I can help somehow with logs or testing. I have tried 662 loader, doesn't work for me either. Debug log with loader: In both cases I was using libusb1.2.6 |
|
please use linux, windows is currently broken due to usbdk issues. |
|
I am using OpenSuse Linux and I have the problem, that I loose the connection to the device (onyx boox note air 2) as soon as the message |
|
According to the log the programmer doesn't seem to fit your device |
|
So, how can I find the correct programmer? |
|
One reason for our difficulties may be, as I have said before, the CPU in the Note Air 2 is a Snapdragon 665, not 662, as I previously thought. The loader and programmer(s) we use need to be compatible with the 665. |
|
A little context, @baqlias I believe the CPU-Z app has a bug in it. I installed it and confirmed it said 665, however, DevCheck shows 662. All I can find in documentation points to 662 which is code named "BENGAL". I found this with I believe the one you mention is 665 "Trinket" Just wanted to verify this for my own sanity and share with others |
|
I wonder why it says unknown cpu, will have a look at the msm id |
|
Thanks for clarifying this. I installed CPU Identifier Pro and it tells me I have a Qualcomm Snapdragon Bengal, but does not give a number such as 662 or 665. The adb shell command does likewise. Everything else I've seen points to 662, as you said. |
|
Similar experience with the new BOOX Note 5, with the same CPU. I know next to nothing but am willing to learn and test. |
|
I'm also willing to test, as long as there's a way to back things up first, just in case! |
|
I had a PM from someone for whom bkerler's 662 loader worked. This person says that memory in the Note Air 2 is UFS mode, not eMMC mode. Once this person posts on Mobileread, you can all check it out. I'll post a link to that post here. It still didn't work for me, but this person was kind enough to upload the boot.img. |
|
If that's the case, just use --memory=ufs as option |
|
Using --memory=ufs didn't work for me for some reason! It worked for someone else, whose post appeared on Mobileread today! |
|
Does not work for the Note 5 either. Tried a few variations without luck. |
|
Still unable to pull the boot image from the BOOX Note 5 using --memory=ufs. I can open a new issue since it's a different device. I've tried from a couple different machines and keep getting this: I know very little (nothing) about loaders or how they're obtained, or how edl works. I would love to be more helpful but I will need to wait until there is a solution or Onyx releases a new firmware that I can pull the image from. Until then I have a workaround to keep my device from calling back to Onyx and Tencent. |
|
My best guess is that there are different chip revisions or hardware configurations and the edl loader will then fail. |
|
Ok, so: onyx boox note air2 has 0x0014d0e100000000, which is SDM662. What msmid does boox note 5 show ? The msmid is the only reliable source for cpu identification. |
|
So, onyx boox note air2 seems to work fine with 0014d0e100000000_d40eee56f3194665_FHPRG.bin and option --memory=ufs. |
@bkerler, the value according to edl's output is: 0x0014d0e1 (The output above is from my BOOX Note 5) |
|
Same problem with Boox Max Lumi2. Device disconnected after 0014d0e100000000_d40eee56f3194665_FHPRG.bin uploaded. |
Onyx Boox Note X failed, stucked at Trying to read first storage sector |
|
I've ordered one ... so I will try to figure out what the problem is |
|
@bkerler Hey Bjoern, I have a Note Air 2 and just tried @MlgmXyysd command |
|
Most (all?) of the Onyx with UFS have 6 LUNs, LUN 0 - LUN 5. You'll get an error querying LUN 6. This is to be expected. |
|
Ok, my Onxy Boox Note Air 2 (new HW Variant) also didn't work. But it seems I've found a fix now :) I've added the fix to the latest commit onxy_boox_air_2_variant2.zip |
Loader.txt
I've attached a copy of what came up on Terminal with my device in EDL mode when I ran the command edl printgpt --memory=emmc
It was unable to find a suitable loader for my device and encouraged me to pass this on. So here it is! If you need additional info, please let me know. My main purpose in doing this is to get the boot.img from my device so I can root it with Magisk.
The text was updated successfully, but these errors were encountered: