Register Guidelines E-Books Search Today's Posts Mark Forums Read

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

Notices

Reply
 
Thread Tools Search this Thread
Old 01-03-2022, 08:41 PM   #1
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
Onyx Nova 3 bricked

I managed to get my Nova3 into a state where I can't fastboot, or get into recovery. I think I, stupidly, replaced boot or recovery incorrectly.

I'm trying to enter EDL mode by holding down the Home button as per a different thread, while attaching it to the computer, and while the power button turns purple initially, it then turns blue, instead of going out, and the edl tool doesn't detect it.

Has anyone encountered this before?

Thank you.

EDIT: The device is stuck on the ONYX logo. Trying to connect with adb gives "error: device unauthorized."

Last edited by LinuxReaderer; 01-03-2022 at 08:45 PM. Reason: add more info
LinuxReaderer is offline   Reply With Quote
Old 01-04-2022, 01:20 PM   #2
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
Per a discussion with a very helpful member, I'm going to try an EDL cable. I'll update this thread after trying that.
LinuxReaderer is offline   Reply With Quote
Advert
Old 01-04-2022, 02:29 PM   #3
Renate
Wizard
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: 2,239
Karma: 9391749
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Onyx logo means that it's not totally dead. That is, if it actually refreshes it. If you had ADB authorized you'd be set. Was it authorized before? What do you have for images that are available? boot? recovery?

I'm not familiar with how many buttons a Nova3 has. Can't you get to bootloader with some silly combination?
Renate is offline   Reply With Quote
Old 01-06-2022, 04:32 PM   #4
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
I unfortunately had wiped it, trying to load a GSI on it, including boot and recovery.

I tried the EDL cable with no luck, as well as some combo of home button and power button (the only two buttons it has).

Any idea which of these contacts would need to be connected to trigger EDL mode? https://imgur.com/AV2ucJk
LinuxReaderer is offline   Reply With Quote
Old 01-06-2022, 06:03 PM   #5
Renate
Wizard
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: 2,239
Karma: 9391749
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
That *could* be it on the left edge near the screw. Is there nothing else on the board?
Do you have a resistor between 100 ohms and 10k? Do you have a voltmeter?
Chances are you probably can't do damage shorting those two points, but I prefer to act conservatively and short things with a resistor when I'm not sure.
Renate is offline   Reply With Quote
Advert
Old 01-06-2022, 06:18 PM   #6
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
Here are a few more images of the internals:
https://imgur.com/LrkZWeP
https://imgur.com/gNFO4gj
https://imgur.com/N2wU1N0

Let me see what I have around.

But, with more playing around, I think I managed to get into EDL mode by holding down buttons. If I hold down home and power, let power blink once, then twice, then let go of power while holding home, then press power once, the power button light turns off and I can load the programmer with edl --loader=Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin

The problem now is when I try to run printgpt I get: edl printgpt
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
firehose - Nop succeeded.
firehose - Chip serial num: 0 (0x0)
firehose -
firehose
firehose - [LIB]: GetStorageInfo command isn't supported.
firehose_client
firehose_client - [LIB]: No --memory option set, we assume "eMMC" as default ..., if it fails, try using "--memory" with "UFS","NAND" or "spinor" instead !
firehose - TargetName=
firehose - MemoryName=eMMC
firehose - Version=
firehose_client - Supported functions:
-----------------
configure,program,firmwarewrite,patch,setbootables toragedrive,ufs,emmc,power,benchmark,read,getstora geinfo,getcrc16digest,getsha256digest,erase,peek,p oke,nop,xml

I have the update.upx -> update.zip with boot.img, etc, but is there anything I can do if GetStorageInfo is not supported?
LinuxReaderer is offline   Reply With Quote
Old 01-06-2022, 06:19 PM   #7
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
I got some more photos of the interior, but I think I managed to get it into EDL mode playing around more with home and power!

Except I'm getting an error now: edl printgpt
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
firehose - Nop succeeded.
firehose - Chip serial num: 0 (0x0)
firehose -
firehose
firehose - [LIB]: GetStorageInfo command isn't supported.
firehose_client
firehose_client - [LIB]: No --memory option set, we assume "eMMC" as default ..., if it fails, try using "--memory" with "UFS","NAND" or "spinor" instead !
firehose - TargetName=
firehose - MemoryName=eMMC
firehose - Version=
firehose_client - Supported functions:
-----------------
configure,program,firmwarewrite,patch,setbootables toragedrive,ufs,emmc,power,benchmark,read,getstora geinfo,getcrc16digest,getsha256digest,erase,peek,p oke,nop,xml

I have the update.upx file -> update.zip and unzipped, how can I get the device re-imaged from this mode, with the files from the zip?
LinuxReaderer is offline   Reply With Quote
Old 01-06-2022, 06:26 PM   #8
Renate
Wizard
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: 2,239
Karma: 9391749
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Well, how did you get it into EDL mode, huh?

A update.zip will only help once you get this thing into a recovery.
If printgpt didn't work then you don't really have the loader working.
Do you know what Qualcomm processor you have?
Have you tried:
Code:
edl.py --loader=something-or-other.bin --memory=emmc printgpt
Edit: Oops, I missed the first of your double posts...

Last edited by Renate; 01-06-2022 at 07:21 PM.
Renate is offline   Reply With Quote
Old 01-06-2022, 06:59 PM   #9
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
I got it into EDL mode by a combination of power button/home button manipulations. But it's tough, most of the time, I run: edl --loader=Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin
and the output ends with
sahara - Uploading loader Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin ...
Error, couldn't find suitable enprg/nprg loader

But if I let go at a certain time, I manage to get into a mode where it does load successfully, and then I get what I put in #6, but its tough to get the timing right. I'm trying to recreate and video-recording while doing it to try to figure out what combination works.

Maybe I should try the hardware method, let me try posting the photos again. Actually, looks like my post #6 came through with them, the spam filter must not have liked the URLs.
LinuxReaderer is offline   Reply With Quote
Old 01-06-2022, 07:23 PM   #10
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
Quote:
Originally Posted by Renate View Post
Well, how did you get it into EDL mode, huh?

A update.zip will only help once you get this thing into a recovery.
If printgpt didn't work then you don't really have the loader working.
Do you know what Qualcomm processor you have?
Have you tried:
Code:
edl.py --loader=something-or-other.bin --memory=emmc printgpt
Edit: Oops, I missed the first of your double posts...
My fault, I thought for some reason it didn't go through... not sure what I am doing wrong!
LinuxReaderer is offline   Reply With Quote
Old 01-07-2022, 01:55 PM   #11
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
I managed to get it into EDL mode using the two contacts! But it seems like no functions are supported:

$edl --loader=Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin --memory=eMMC
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Using loader Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin ...
main - Waiting for the device
main - Device detected
main - Mode detected: sahara
Device is in EDL mode .. continuing.
sahara -
------------------------
HWID: 0x000cc0e100000000 (MSM_ID:0x000cc0e1,OEM_ID:0x0000,MODEL_ID:0x0000)
CPU detected: "SDM636"
PK_HASH: 0x
Serial: 0x

sahara - Uploading loader Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin ...
Successfully uploaded programmer
firehose_client - Target detected: SDM636
firehose - TargetName=
firehose - MemoryName=emmc
firehose - Version=
firehose_client - Supported functions:
-----------------

$ edl --loader=Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin --memory=eMMC printgpt
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Using loader Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
firehose - TargetName=
firehose - MemoryName=emmc
firehose - Version=
firehose_client - Supported functions:
-----------------
LinuxReaderer is offline   Reply With Quote
Old 01-07-2022, 02:18 PM   #12
Renate
Wizard
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: 2,239
Karma: 9391749
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Step one: Verify the VID/PID of what you've got. Is it 05c6/9008 or 05c6/900e? You want 9008.
The Poke3 has a Snapdragon 636 too and I use the "factory" loader, so this should all work.
I'm using:
05/06/2021 13:59 634,384 sdm636.bin (just my renaming)
MD5 0f159e0b43ad95974e4ce507ee362aec
Renate is offline   Reply With Quote
Old 01-07-2022, 02:37 PM   #13
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
The VID/PID is 05c6:9008

I tried to follow your "Onyx Boox Kon-Tiki 2 (Nova3 platform) - apps" thread as best I could to get going. The md5sum of the loader is:
0f159e0b43ad95974e4ce507ee362aec
I also tried a loader with md5sum of:
206f007e7a247b5a4e64419aa4cb403a

If I turn on debug mode I do see:
UsbClass - [LIB]: TX:<?xml version="1.0" ?><data><read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="2" physical_partition_number="0" start_sector="0"/>

UsbClass - [LIB]: RX:<log value="Attribute 'SECTOR_SIZE_IN_BYTES'=512 must be equal to disk sector size 0"/>

UsbClass - [LIB]: RX:<log value="ERROR 4: Line 2226: STORAGE_READ_FAILURE"/>

but I haven't investigated further yet.
LinuxReaderer is offline   Reply With Quote
Old 01-07-2022, 02:46 PM   #14
Renate
Wizard
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: 2,239
Karma: 9391749
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Edit: Oops, sorry, my bad.

Does printgpt give results or just an error?

Last edited by Renate; 01-07-2022 at 02:51 PM.
Renate is offline   Reply With Quote
Old 01-07-2022, 02:52 PM   #15
LinuxReaderer
Member
LinuxReaderer began at the beginning.
 
Posts: 20
Karma: 10
Join Date: Dec 2021
Device: None
VID/PID looks like 05c6:9008:
Bus 003 Device 127: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

I'm able to use commands like edl peekhex successfully, is it possible that in the process of trying to reflash it using adb (including boot/recovery/etc), I messed up the partition table? Is there a way to restore it completely using the update file?
LinuxReaderer is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ended Onyx Boox Nova 2 downeaster59 Flea Market 6 02-14-2022 11:19 PM
Sell Onyx Nova 2 mtreader Flea Market 4 12-18-2020 02:38 PM
Onyx nova 2 and chrome La Mergouille Onyx Boox 0 05-05-2020 09:37 PM
Onyx Nova Pro Like_to_read Onyx Boox 6 09-03-2019 08:21 AM


All times are GMT -4. The time now is 07:48 PM.


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