Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Onyx Boox

Notices

Reply
 
Thread Tools Search this Thread
Old Yesterday, 08:32 AM   #31
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
Tried with stock recovery:
Code:
> .\adb.exe sideload ..\update.zip
serving: '..\update.zip'  (~47%)    adb: failed to read command: No error
Logs in boox recovery:
Code:
Supported API: 3
Finding update package...
Verifying update package
E:failed to verify whole-file signature
Update package verification took 79.3 s (result 1).
E:Signature verification failed
E:error: 21

Install from ADB completed with status 2.
Installation aborted.
gleboss is online now   Reply With Quote
Old Yesterday, 08:35 AM   #32
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
Quote:
If stock recovery doesn't work you'll have to manually flash a few partitions then we can get to work on manually putting together a super for you.
So looks like this is the only way to fix my poor onyx...
But I wonder how to do it properly, I have all the partitions generated by payload_dumper, what are my next steps?
gleboss is online now   Reply With Quote
Old Yesterday, 09:31 AM   #33
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
You can certainly flash the xbl, abl, boot, dtbo, vbmeta, modem, recovery without a problem.
The other five, system, systen_ext, product, vendor, odm, plus vbmeta_system have to be done later.

Last edited by Renate; Yesterday at 11:24 AM.
Renate is offline   Reply With Quote
Old Yesterday, 09:46 AM   #34
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
What do you mean by later? Should I flash xbl, abl, boot, dtbo, modem, recovery and try sideload again?
gleboss is online now   Reply With Quote
Old Yesterday, 11:01 AM   #35
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
I tried to flash some paritions and got the same verification err:
Code:
> .\edl.exe /w /pxbl_a .\output\xbl.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write xbl.img... ok, writing 100% ok
> .\edl.exe /w /pxbl_b .\output\xbl.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write xbl.img... ok, writing 100% ok
> .\edl.exe /w /pabl_a .\output\abl.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write abl.img... ok, writing 100% ok
> .\edl.exe /w /pabl_b .\output\abl.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write abl.img... ok, writing 100% ok
> .\edl.exe /w /pboot_a .\output\boot.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write boot.img... ok, writing 100% ok
> .\edl.exe /w /pboot_b .\output\boot.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write boot.img... ok, writing 100% ok
P> .\edl.exe /w /pdtbo_a .\output\dtbo.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write dtbo.img... ok, writing 100% ok
> .\edl.exe /w /pdtbo_b .\output\dtbo.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write dtbo.img... ok, writing 100% ok
> .\edl.exe /w /pmodem_a .\output\modem.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write modem.img... ok, writing 100% ok
> .\edl.exe /w /pmodem_b .\output\modem.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write modem.img... ok, writing 100% ok
> .\edl.exe /w /precovery_a .\output\recovery.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write recovery.img... ok, writing 100% ok
> .\edl.exe /w /precovery_b .\output\recovery.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write recovery.img... ok, writing 100% ok
> .\edl.exe /z
Found EDL 9008, requesting reboot... ok
> .\adb.exe sideload ..\update.zip
serving: '..\update.zip'  (~47%)    adb: failed to read command: No error
gleboss is online now   Reply With Quote
Old Yesterday, 12:25 PM   #36
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Ok, here you go. Cross your fingers.

First, flash the vbmeta and the vbmeta_system.
You should have flashed everything now except the five super things, right?

Check that you're still on _a

Make sure that the files that you have are the same size as mine:
Code:
    1,048,576 odm.img
  630,923,264 product.img
3,102,502,912 system.img
  483,250,176 system_ext.img
  595,722,240 vendor.img
Unzip and flash the new manmod.img and the five things, clear misc, reboot:
Code:
edl /w /psuper manmod.img
edl /w /psuper /s2048 odm.img
edl /w /psuper /s4096 product.img
edl /w /psuper /s1236368 system.img
edl /w /psuper /s7295944 system_ext.img
edl /w /psuper /s8239792 vendor.img
edl /f /pmisc
edl /z
We're hoping for it to boot normally.
Attached Files
File Type: zip manmod.zip (2.9 KB, 1 views)
Renate is offline   Reply With Quote
Old Yesterday, 01:47 PM   #37
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
I've flashed everything except stock recovery and it doesnt boot normally(

I see that LED is blue and it stucks on Boox logo, not even flickering.

Quote:
Make sure that the files that you have are the same size as mine
100% the same.

What I did step by step:
Code:
> .\edl.exe /w /s0 /c0 .\big64gfile.img
> .\edl.exe /w /s0 /c34 ..\both\main.img
> .\edl.exe /w /s-33 /c33 ..\both\backup.img
> .\edl.exe /w /pxbl_a .\output\xbl.img
> .\edl.exe /w /pxbl_b .\output\xbl.img
> .\edl.exe /w /pabl_a .\output\abl.img
> .\edl.exe /w /pabl_b .\output\abl.img
> .\edl.exe /w /pboot_a .\output\boot.img
> .\edl.exe /w /pboot_b .\output\boot.img
> .\edl.exe /w /pdtbo_a .\output\dtbo.img
> .\edl.exe /w /pdtbo_b .\output\dtbo.img
> .\edl.exe /w /pmodem_a .\output\modem.img
> .\edl.exe /w /pmodem_b .\output\modem.img
> .\edl.exe /w /pvbmeta_a .\output\vbmeta.img
> .\edl.exe /w /pvbmeta_b .\output\vbmeta.img
> .\edl.exe /w /pvbmeta_system_a .\output\vbmeta_system.img
> .\edl.exe /w /pvbmeta_system_b .\output\vbmeta_system.img
> .\edl.exe /w /psuper manmod.img
> .\edl.exe /w /psuper /s2048 .\output\odm.img
> .\edl.exe /w /psuper /s4096 .\output\product.img
> .\edl.exe /w /psuper /s1236368 .\output\system.img
> .\edl.exe /w /psuper /s7295944 .\output\system_ext.img
> .\edl.exe /w /psuper /s8239792 .\output\vendor.img
> .\edl.exe /f /pmisc
> .\edl.exe /z

Last edited by gleboss; Yesterday at 02:13 PM.
gleboss is online now   Reply With Quote
Old Yesterday, 01:57 PM   #38
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
And you were still on _a?

Try custom recovery and autoupdate

Try stock recovery and sideload
Renate is offline   Reply With Quote
Old Yesterday, 02:23 PM   #39
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
Yep, Im still on _a

Tried custom rec with autoupdate
Attached Files
File Type: txt autolog.txt (7.8 KB, 2 views)
gleboss is online now   Reply With Quote
Old Yesterday, 02:29 PM   #40
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Actually, that's more promising.

Hold off doing anything.

I'll give you a new manmod and reflasing info.
Renate is offline   Reply With Quote
Old Yesterday, 03:06 PM   #41
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Ok, I've got both fingers crossed this time.
See if it will boot normally.
If not autoupdate.
Use these different numbers:
Code:
edl /w /psuper manmod.img
edl /w /psuper /s2048 odm.img
edl /w /psuper /s4096 product.img
edl /w /psuper /s1236992 system.img
edl /w /psuper /s7297024 system_ext.img
edl /w /psuper /s8241152 vendor.img
Use this different manmod.img
Attached Files
File Type: zip manmod.zip (2.8 KB, 1 views)
Renate is offline   Reply With Quote
Old Yesterday, 03:24 PM   #42
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
Unfortunately the autoupdate process is stuck on 11% again.. (>10mins)
gleboss is online now   Reply With Quote
Old Yesterday, 04:27 PM   #43
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
I found smth suspicious:
Code:
> .\edl.exe /r /psuper super_current.img
> .\lpunpack.exe .\super_current.img
> ls
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        16.03.2026     23:00         131072 odm_a.img
-a----        16.03.2026     23:00      387842048 product_a.img
-a----        16.03.2026     23:00      387842048 system_a.img
-a----        16.03.2026     23:00       60424192 system_ext_a.img
-a----        16.03.2026     22:54     6442450944 super_current.img
-a----        16.03.2026     23:00       74579968 vendor_a.img
Then I tried the following:
Code:
> .\lpmake.exe --metadata-size 65536 --metadata-slots 2 --device super:6442450944 --group main:6442450944 --partition system_a:readonly:3102502912:main --image system_a=system.img --partition vendor_a:readonly:595722240:main --image vendor_a=vendor.img --partition product_a:readonly:630923264:main --image product_a=product.img --partition system_ext_a:readonly:483250176:main --image system_ext_a=system_ext.img --partition odm_a:readonly:1048576:main --image odm_a=odm.img --output super_fixed.img
> .\edl.exe /w /psuper .\super_fixed.img
> .\edl.exe /f /pmetadata
> .\edl.exe /f /pmisc
> .\edl.exe /z
After that my device is loading into adb immediately, I tried autoupdate, but it was failed. Don't know if I'm on the right track
Attached Files
File Type: txt autolog.txt (13.0 KB, 0 views)

Last edited by gleboss; Yesterday at 04:31 PM.
gleboss is online now   Reply With Quote
Old Today, 12:24 AM   #44
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,350
Karma: 20878213
Join Date: Feb 2012
Location: Germany
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Oops, sorry, a typo snuck in.

Hold off, let me fix this....
Attached Files
File Type: zip manmod.zip (2.9 KB, 1 views)

Last edited by Renate; Today at 01:34 AM.
Renate is offline   Reply With Quote
Old Today, 01:30 AM   #45
gleboss
Enthusiast
gleboss began at the beginning.
 
Posts: 38
Karma: 10
Join Date: Mar 2026
Device: Onyx Boox Go 7
Same issue with 11%
Attached Files
File Type: zip meta_current.zip (20.9 KB, 0 views)
gleboss is online now   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Troubleshooting PW5 bootloop Mars95 Amazon Kindle 5 08-19-2023 11:40 AM
PW5 PW stuck in a bootloop......... kdusr Kindle Developer's Corner 6 11-26-2022 01:58 AM
PRS-T1 bootloop charmees Sony Reader 9 11-23-2018 03:13 PM
PRS-T1 bootloop klaasvaak42 Sony Reader 0 10-20-2018 04:45 AM
My Kobo goes into a bootloop! alabrand Kobo Reader 4 06-03-2016 02:44 PM


All times are GMT -4. The time now is 04:18 PM.


MobileRead.com is a privately owned, operated and funded community.