Boox Note 3 bricked

aaron42195 · 09-15-2024, 08:54 PM

My Boox Note 3 bricked. Please check the vedio below
https://drive.google.com/file/d/1oKl...ew?usp=sharing
only fastboot mode I can enter.
Any suggesion for me to fix this issue?

Renate · 09-16-2024, 11:12 PM

You can always fix a Poke3 from software problems.
The worst case is if you lose some calibration data, MACs or serial number if you haven't backed up.

With EDL and the Firehose you can make a full, raw backup that will return your specific device exactly to a certain time point.

You can also use EDL to get to recovery and from there do a "factory reset".

I'm not sure how you use your device, but I've got nothing "precious" on mine.
From a fresh device it would take under 30 minutes to make it like before.

Your video is not public.

aaron42195 · 09-17-2024, 09:33 AM

Quote:

Originally Posted by Renate

You can always fix a Poke3 from software problems.
...
From a fresh device it would take under 30 minutes to make it like before.

Your video is not public.

Hi Renate,

Thank you for your reply! It has given me some hope.
Could you please suggest any instructions or guides on how to proceed with the steps (such as using EDL mode and the Firehose tool)?
Also, I have now made the video public, so you should be able to view it.

Thanks again for your help!

Renate · 09-18-2024, 12:06 AM

That's the boot animation.
It runs when the Android subsystem is mostly running but it hasn't started looking for a launcher application yet.

If you had previously enabled ADB you should be able to connect and ask it what it thinks it's doing.
But I guess that you haven't?
With ADB you could just:

Code:

adb reboot recovery

Getting into EDL mode is easy if you have ADB:

Code:

adb reboot edl

Internal test points always work but can be difficult to access and locate.
EDL test cables should work on most recent Onyx.

aaron42195 · 09-18-2024, 01:57 AM

Click image for larger version

Name: 螢幕擷取畫面 2024-04-30 074904.png
Views: 26
Size: 312.2 KB
ID: 210866

Click image for larger version

Name: 螢幕擷取畫面 2024-09-18 135548.png
Views: 19
Size: 94.3 KB
ID: 210867

Is this edl mode?

aaron42195 · 09-18-2024, 02:58 AM

Is this edl mode?[/QUOTE]

Renate · 09-18-2024, 03:58 AM

Quote:

Originally Posted by aaron42195

Is this edl mode?

Yes, but I don't like QFIL and virtual com ports (or Python).

aaron42195 · 09-18-2024, 09:17 AM

Quote:

Originally Posted by Renate

Yes, but I don't like QFIL and virtual com ports (or Python).

I can use edl.exe.
What is my next step?
Sorry, I don’t know much about this part.

aaron42195 · 09-18-2024, 10:24 AM

Quote:

Originally Posted by Renate

Yes, but I don't like QFIL and virtual com ports (or Python).

I use edl/l command. Get the result below.

C:\Temp>edl /l
Found EDL 9008, handshaking... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)

Renate · 09-18-2024, 03:02 PM

Quote:

Originally Posted by aaron42195

I use edl/l command. Get the result below.

Code:

C:\Temp>edl /l
Found EDL 9008, handshaking... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)

That's all good. You need to load the correct loader. That's in the instructions.
You can rename it poke3.bin as it's shorter and more succinct.
You may need to start a fresh EDL session as it's easily confused.

Code:

C:\>edl /lpoke3.bin
C:\>edl /g

That will dump the GPT so we know everything is working ok.

I get confused. Didn't somebody post after you? Did it disappear?

aaron42195 · 09-18-2024, 04:43 PM

I find the loader by hash code and ...

C:\Temp>edl /labc.bin
Found EDL 9008, handshaking... nope, resetting... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)
Sending abc.bin 100% ok, starting... ok, waiting for Firehose... ok

C:\Temp>edl /g
Found EDL 9008, configuring... nope, configuring... ok
Requesting info on LUN 0...
<log value="ERROR: Failed to open the SDCC Device slot 0 partition 0"/>
<log value="ERROR: Failed to open the device 1 slot 0 partition 0"/>
<log value="ERROR: Failed to get device info slot:0artition:0"/>
<log value="ERROR 14: Line 1270: HANDLE_STORAGE_INFO_FAILURE"/>
Nope

is this correct?

aaron42195 · 09-18-2024, 05:32 PM

The result.
C:\Temp>edl /labc.bin
Found EDL 9008, handshaking... nope, resetting... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)
Sending abc.bin 100% ok, starting... ok, waiting for Firehose... ok

C:\Temp>edl /g
Found EDL 9008, configuring... nope, configuring... ok
Requesting info on LUN 0...
<log value="ERROR: Failed to open the SDCC Device slot 0 partition 0"/>
<log value="ERROR: Failed to open the device 1 slot 0 partition 0"/>
<log value="ERROR: Failed to get device info slot:0artition:0"/>
<log value="ERROR 14: Line 1270: HANDLE_STORAGE_INFO_FAILURE"/>
Nope

Renate · 09-18-2024, 09:29 PM

Sorry, you're UFS.

Code:

C:\>edl /lpoke3.bin
C:\>edl /u /g

After using /l you need to always add a /u.

aaron42195 · 09-19-2024, 05:31 PM

I found another thread (EDL on a Boox Note3) mation
sdm660/3006000000010000_7e425bcb25364725_fhprg_peek.bin worked on Note3
but in my machine got the error below

C:\Temp>edl /l
Found EDL 9008, handshaking... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)

C:\Temp>edl /lbkerler\qualcomm\factory\sdm660\3006000000010000_ 7e425bcb25364725_fhprg_peek.bin
Found EDL 9008, handshaking... nope, resetting... version 2.1
HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3)
Sending 3006000000010000_7e425bcb25364725_fhprg_peek.bin 100% ok, starting... ok, waiting for Firehose... no response, poking...
Could not write device

I can load other .bin such as
bkerler\qualcomm\factory\sdm636\000cc0e100000000_7 be49b72f9e43372_fhprg_bqx2_peek.bin

What's the problem?

another I don't know why my post always dispear after reply

Renate · 09-19-2024, 08:15 PM

For most devices you have to pay attention to the PK hash and it must match.
That's because it's the security mechanism for Secure Boot.

But if you don't have Secure Boot enabled the universe of loaders to check is much larger.

A single loader can support multiple different processors.

In the final analysis the loader you need is the one that works.

The loader you mentioned in #12 seemed to work fine, but you need that /u flag.
Why are you talking about a different loader in #14?

09-18-2024, 12:06 AM	#4
Renate Wizard Posts: 2,931 Karma: 12021497 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	That's the boot animation. It runs when the Android subsystem is mostly running but it hasn't started looking for a launcher application yet. If you had previously enabled ADB you should be able to connect and ask it what it thinks it's doing. But I guess that you haven't? With ADB you could just: Code: adb reboot recovery Getting into EDL mode is easy if you have ADB: Code: adb reboot edl Internal test points always work but can be difficult to access and locate. EDL test cables should work on most recent Onyx.

09-18-2024, 02:58 AM	#6
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	Is this edl mode?[/QUOTE] Attached Thumbnails

09-18-2024, 09:29 PM	#13
Renate Wizard Posts: 2,931 Karma: 12021497 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Sorry, you're UFS. Code: C:\>edl /lpoke3.bin C:\>edl /u /g After using /l you need to always add a /u.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Possible to recover a bricked Boox Note Plus?	noteplususer	Onyx Boox	3	04-19-2022 02:57 PM
Bricked Boox Note 5	xenoscr	Onyx Boox	1	02-05-2022 02:04 PM
Clarify tech specs: Screen on Onyx Boox Note Pro vs Onyx Boox Note 3.	Sm0och	Onyx Boox	12	08-10-2021 03:14 PM
Boox Note and Boox Note pro: unreliable screen!	tokapi	Onyx Boox	10	06-14-2020 06:20 PM
Boox Note Bricked?	jdog609	Onyx Boox	11	08-08-2018 09:16 AM

09-15-2024, 08:54 PM	#1
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	Boox Note 3 bricked My Boox Note 3 bricked. Please check the vedio below https://drive.google.com/file/d/1oKl...ew?usp=sharing only fastboot mode I can enter. Any suggesion for me to fix this issue?

09-16-2024, 11:12 PM	#2
Renate Wizard Posts: 2,931 Karma: 12021497 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	You can always fix a Poke3 from software problems. The worst case is if you lose some calibration data, MACs or serial number if you haven't backed up. With EDL and the Firehose you can make a full, raw backup that will return your specific device exactly to a certain time point. You can also use EDL to get to recovery and from there do a "factory reset". I'm not sure how you use your device, but I've got nothing "precious" on mine. From a fresh device it would take under 30 minutes to make it like before. Your video is not public.

09-18-2024, 01:57 AM	#5
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	Is this edl mode?

09-18-2024, 04:43 PM	#11
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	I find the loader by hash code and ... C:\Temp>edl /labc.bin Found EDL 9008, handshaking... nope, resetting... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) Sending abc.bin 100% ok, starting... ok, waiting for Firehose... ok C:\Temp>edl /g Found EDL 9008, configuring... nope, configuring... ok Requesting info on LUN 0... <log value="ERROR: Failed to open the SDCC Device slot 0 partition 0"/> <log value="ERROR: Failed to open the device 1 slot 0 partition 0"/> <log value="ERROR: Failed to get device info slot:0artition:0"/> <log value="ERROR 14: Line 1270: HANDLE_STORAGE_INFO_FAILURE"/> Nope is this correct?

09-18-2024, 05:32 PM	#12
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	The result. C:\Temp>edl /labc.bin Found EDL 9008, handshaking... nope, resetting... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) Sending abc.bin 100% ok, starting... ok, waiting for Firehose... ok C:\Temp>edl /g Found EDL 9008, configuring... nope, configuring... ok Requesting info on LUN 0... <log value="ERROR: Failed to open the SDCC Device slot 0 partition 0"/> <log value="ERROR: Failed to open the device 1 slot 0 partition 0"/> <log value="ERROR: Failed to get device info slot:0artition:0"/> <log value="ERROR 14: Line 1270: HANDLE_STORAGE_INFO_FAILURE"/> Nope

09-19-2024, 05:31 PM	#14
aaron42195 Enthusiast Posts: 32 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	I found another thread (EDL on a Boox Note3) mation sdm660/3006000000010000_7e425bcb25364725_fhprg_peek.bin worked on Note3 but in my machine got the error below C:\Temp>edl /l Found EDL 9008, handshaking... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) C:\Temp>edl /lbkerler\qualcomm\factory\sdm660\3006000000010000_ 7e425bcb25364725_fhprg_peek.bin Found EDL 9008, handshaking... nope, resetting... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) Sending 3006000000010000_7e425bcb25364725_fhprg_peek.bin 100% ok, starting... ok, waiting for Firehose... no response, poking... Could not write device I can load other .bin such as bkerler\qualcomm\factory\sdm636\000cc0e100000000_7 be49b72f9e43372_fhprg_bqx2_peek.bin What's the problem? another I don't know why my post always dispear after reply Attached Thumbnails

09-19-2024, 08:15 PM	#15
Renate Wizard Posts: 2,931 Karma: 12021497 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	For most devices you have to pay attention to the PK hash and it must match. That's because it's the security mechanism for Secure Boot. But if you don't have Secure Boot enabled the universe of loaders to check is much larger. A single loader can support multiple different processors. In the final analysis the loader you need is the one that works. The loader you mentioned in #12 seemed to work fine, but you need that /u flag. Why are you talking about a different loader in #14?

Advert

Advert