Boox Note 3 bricked - Page 2

aaron42195 · 09-19-2024, 09:06 PM

#12
Result as below. But still can not boot. Screen keep in startup animation.

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

C:\Temp>edl /u
Found EDL 9008

C:\Temp>edl /u /g
Found EDL 9008, configuring... nope, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok

LUN # Name Start Count Type
─── ── ──────────────── ────────── ────────── ────────────────────
0 1 ssd 6 2 Secure SW download
0 2 persist 8 8192 Persist
0 3 misc 8200 256 Misc
0 4 keystore 8456 128 Key store
0 5 frp 8584 128 FRP
0 6 system 8712 786432 System
0 7 cache 795144 65536 Cache
0 8 logdump 860680 16384 Log dump
0 9 onyxconfig 877064 8192 System
0 10 userdata 885256 13260275 User data

1 1 xbl 6 896 Bootloader
1 2 last_parti 902 117 Empty

2 1 xblbak 6 896 Bootloader
2 2 last_parti 902 117 Empty

3 1 cdt 6 1 CDT
3 2 ddr 7 256 DDR
3 3 last_parti 263 32500 Empty

4 1 rpm 6 128 Resource/power mgmt
4 2 tz 134 1024 TrustZone
4 3 hyp 1158 128 Hypervisor
4 4 pmic 1286 128 PMIC
4 5 modem 1414 28160 FAT32
4 6 bluetooth 29574 256 Bluetooth
4 7 dsp 29830 4096 DSP
4 8 abl 33926 256 Android bootloader
4 9 keymaster 34182 256 Key master
4 10 mdtpsecapp 34438 1024 MDTP secure
4 11 mdtp 35462 8192 MDTP
4 12 boot 43654 16384 Boot
4 13 cmnlib 60038 256 Common lib
4 14 cmnlib64 60294 256 Common lib64
4 15 devcfg 60550 256 Device config
4 16 vbmeta 60806 16 VB meta
4 17 vendor 60822 204800 System
4 18 recovery 265622 16384 Recovery
4 19 fsg 282006 512 Modem storage
4 20 sec 282518 4 Sec
4 21 dip 282522 256 DIP
4 22 devinfo 282778 1 Device info
4 23 apdp 282779 64 APDP
4 24 msadp 282843 64 MSADP
4 25 dpo 282907 1 DPO
4 26 splash 282908 8356 Splash
4 27 limits 291264 1 Limits
4 28 toolsfv 291265 256 Tools FV
4 29 logfs 291521 2048 Log FS
4 30 sti 293569 512 STI
4 31 storsec 294081 32 Store secure
4 32 rawdump 294113 32768 RAM dump
4 33 last_parti 326881 721690 Empty

5 1 modemst1 6 512 Modem ST1
5 2 modemst2 518 512 Modem ST2
5 3 fsc 1030 1 FSC
5 4 last_parti 1031 392180 Empty

C:\Temp>edl /z
Found EDL 9008, requesting reboot... ok

C:\Temp>

Renate · 09-20-2024, 01:40 AM

Edl is a tool. It's working fine.
If you do not use it to actively change anything then things will remain the same.

The question is: What is the problem and what action(s) should you take?

Do you want to do a "factory reset"? You will lose all data on it.

If you had enabled ADB before this happened it would be much easier to figure it out.

aaron42195 · 09-20-2024, 02:25 AM

Quote:

Originally Posted by Renate

Edl is a tool. It's working fine.
If you do not use it to actively change anything then things will remain the same.

The question is: What is the problem and what action(s) should you take?

Do you want to do a "factory reset"? You will lose all data on it.

If you had enabled ADB before this happened it would be much easier to figure it out.

I did not enabled ADB. Could I do "factory reset" by edl.exe?

Renate · 09-20-2024, 12:13 PM

Quote:

Originally Posted by aaron42195

Could I do "factory reset" by edl.exe?

Yes. Go to EDL.

Code:

edl /lwhatever.bin
edl /u /w /pmisc misc-recovery.img
edl /z

Rename the attached file .img

aaron42195 · 09-20-2024, 04:27 PM

Quote:

Originally Posted by Renate

Yes. Go to EDL.

Code:

edl /lwhatever.bin
edl /u /w /pmisc misc-recovery.img
edl /z

Rename the attached file .img

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

C:\Temp>edl /lbkerler\qualcomm\factory\sdm636\000cc0e100000000_ 7be49b72f9e43372_fhprg_bqx2_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 000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin 100% ok, starting... ok, waiting for Firehose... ok

C:\Temp>edl /u /w /pmisc misc-recovery.img
Found EDL 9008, configuring... nope, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Could not open misc-recovery.img

C:\Temp>edl /z
Found EDL 9008, requesting reboot... ok

The result is the same;
I still cannot boot into the system. By the way, I installed Magisk to root the device in the beginning.

Renate · 09-20-2024, 10:05 PM

Quote:

Originally Posted by aaron42195

Code:

Could not open misc-recovery.img

We're talking Computer 101 here.
Did you download misc-recovery.prc ?
Did you rename it misc-recovery.img ?
Is the file in the right directory?

aaron42195 · 09-21-2024, 02:16 AM

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

C:\Temp>edl /u /w /pmisc misc-recovery.img
Found EDL 9008, configuring... nope, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write misc-recovery.img... ok, writing 100% ok

C:\Temp>edl /z
Found EDL 9008, requesting reboot... ok

C:\Temp>

Sorry, My mistake. I just post the incorrect sequence.

(The result is the same)

Renate · 09-21-2024, 01:21 PM

You mean that that doesn't get you to recovery?

aaron42195 · 09-21-2024, 08:18 PM

Quote:

Originally Posted by Renate

You mean that that doesn't get you to recovery?

Yes, I cannot boot into the system. It is still stuck on the startup animation.

Renate · 09-22-2024, 02:21 AM

Hmm, you must have broken recovery?

I was looking to check out the Poke3 update but my Python on this computer is broken.
More later.

aaron42195 · 09-22-2024, 05:34 AM

Quote:

Originally Posted by Renate

Hmm, you must have broken recovery?

I was looking to check out the Poke3 update but my Python on this computer is broken.
More later.

Thanks. Waiting for your instruction.

Renate · 09-23-2024, 01:41 AM

ARG!!! Stop the presses! I thought that we were talking Poke3, not Note3.

Renate · 09-23-2024, 10:46 AM

Ok, so Note3

I looked at the update.
I had to write a DeBooxUpx in C because I was so sick of the broken Python.
Dependencies from hell.

There's no recovery in that update.
It's hard to tell why that misc patch wouldn't send it to recovery.
It's hard to tell why it's bootlooping.

Since you're Magisk'ed I can try to make an overlay so that ADB starts up.
But I tried that with somebody else's something-or-other and it didn't work.
Doing this stuff at a distance is very difficult.

We can try making a custom recovery.
That's still going to take some cooperation.
Use EDL and pull recovery:

Code:

edl /lwhatever.bin
edl /u4 /r /precovery rec.img

aaron42195 · 09-23-2024, 05:06 PM

Quote:

Originally Posted by Renate

Ok, so Note3

Use EDL and pull recovery:

Code:

edl /lwhatever.bin
edl /u4 /r /precovery rec.img

Here is rec.img

Renate · 09-24-2024, 01:31 AM

Oh, you got me all confused.
That recovery is one that I already patched two years ago???
That was a half-hearted attempt at the time to Frankinstein a recovery from the Poke3.

I'm much better at this now but we need the original recovery from a Note3.

09-23-2024, 01:41 AM	#27
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	ARG!!! Stop the presses! I thought that we were talking Poke3, not Note3. Last edited by Renate; 09-23-2024 at 02:06 AM.

09-23-2024, 10:46 AM	#28
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Ok, so Note3 I looked at the update. I had to write a DeBooxUpx in C because I was so sick of the broken Python. Dependencies from hell. There's no recovery in that update. It's hard to tell why that misc patch wouldn't send it to recovery. It's hard to tell why it's bootlooping. Since you're Magisk'ed I can try to make an overlay so that ADB starts up. But I tried that with somebody else's something-or-other and it didn't work. Doing this stuff at a distance is very difficult. We can try making a custom recovery. That's still going to take some cooperation. Use EDL and pull recovery: Code: edl /lwhatever.bin edl /u4 /r /precovery rec.img

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-19-2024, 09:06 PM	#16
aaron42195 Enthusiast Posts: 39 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	#12 Result as below. But still can not boot. Screen keep in startup animation. C:\Temp>edl /lbkerler\qualcomm\factory\sdm636\000cc0e100000000_ 7be49b72f9e43372_fhprg_bqx2_peek.bin Found EDL 9008, handshaking... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) Sending 636.bin 100% ok, starting... ok, waiting for Firehose... ok C:\Temp>edl /u Found EDL 9008 C:\Temp>edl /u /g Found EDL 9008, configuring... nope, configuring... ok Requesting info on LUN 0... ok Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok LUN # Name Start Count Type ─── ── ──────────────── ────────── ────────── ──────────────────── 0 1 ssd 6 2 Secure SW download 0 2 persist 8 8192 Persist 0 3 misc 8200 256 Misc 0 4 keystore 8456 128 Key store 0 5 frp 8584 128 FRP 0 6 system 8712 786432 System 0 7 cache 795144 65536 Cache 0 8 logdump 860680 16384 Log dump 0 9 onyxconfig 877064 8192 System 0 10 userdata 885256 13260275 User data 1 1 xbl 6 896 Bootloader 1 2 last_parti 902 117 Empty 2 1 xblbak 6 896 Bootloader 2 2 last_parti 902 117 Empty 3 1 cdt 6 1 CDT 3 2 ddr 7 256 DDR 3 3 last_parti 263 32500 Empty 4 1 rpm 6 128 Resource/power mgmt 4 2 tz 134 1024 TrustZone 4 3 hyp 1158 128 Hypervisor 4 4 pmic 1286 128 PMIC 4 5 modem 1414 28160 FAT32 4 6 bluetooth 29574 256 Bluetooth 4 7 dsp 29830 4096 DSP 4 8 abl 33926 256 Android bootloader 4 9 keymaster 34182 256 Key master 4 10 mdtpsecapp 34438 1024 MDTP secure 4 11 mdtp 35462 8192 MDTP 4 12 boot 43654 16384 Boot 4 13 cmnlib 60038 256 Common lib 4 14 cmnlib64 60294 256 Common lib64 4 15 devcfg 60550 256 Device config 4 16 vbmeta 60806 16 VB meta 4 17 vendor 60822 204800 System 4 18 recovery 265622 16384 Recovery 4 19 fsg 282006 512 Modem storage 4 20 sec 282518 4 Sec 4 21 dip 282522 256 DIP 4 22 devinfo 282778 1 Device info 4 23 apdp 282779 64 APDP 4 24 msadp 282843 64 MSADP 4 25 dpo 282907 1 DPO 4 26 splash 282908 8356 Splash 4 27 limits 291264 1 Limits 4 28 toolsfv 291265 256 Tools FV 4 29 logfs 291521 2048 Log FS 4 30 sti 293569 512 STI 4 31 storsec 294081 32 Store secure 4 32 rawdump 294113 32768 RAM dump 4 33 last_parti 326881 721690 Empty 5 1 modemst1 6 512 Modem ST1 5 2 modemst2 518 512 Modem ST2 5 3 fsc 1030 1 FSC 5 4 last_parti 1031 392180 Empty C:\Temp>edl /z Found EDL 9008, requesting reboot... ok C:\Temp>

09-20-2024, 01:40 AM	#17
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Edl is a tool. It's working fine. If you do not use it to actively change anything then things will remain the same. The question is: What is the problem and what action(s) should you take? Do you want to do a "factory reset"? You will lose all data on it. If you had enabled ADB before this happened it would be much easier to figure it out.

09-21-2024, 02:16 AM	#22
aaron42195 Enthusiast Posts: 39 Karma: 10 Join Date: Sep 2024 Device: Boox Note 3	C:\Temp>edl /lbkerler\qualcomm\factory\sdm636\000cc0e100000000_ 7be49b72f9e43372_fhprg_bqx2_peek.bin Found EDL 9008, handshaking... version 2.1 HWID: 000cc0e100000000, JTAG: 000cc0e1, OEM: 0000, Model: 0000 Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09 (x3) Sending 000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek. bin 100% ok, starting... ok, waiting for Firehose... ok C:\Temp>edl /u /w /pmisc misc-recovery.img Found EDL 9008, configuring... nope, configuring... ok Requesting info on LUN 0... ok Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok Requesting write misc-recovery.img... ok, writing 100% ok C:\Temp>edl /z Found EDL 9008, requesting reboot... ok C:\Temp> Sorry, My mistake. I just post the incorrect sequence. (The result is the same)

09-21-2024, 01:21 PM	#23
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	You mean that that doesn't get you to recovery?

09-22-2024, 02:21 AM	#25
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Hmm, you must have broken recovery? I was looking to check out the Poke3 update but my Python on this computer is broken. More later.

09-24-2024, 01:31 AM	#30
Renate Onyx-maniac Posts: 3,026 Karma: 12345837 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Oh, you got me all confused. That recovery is one that I already patched two years ago??? That was a half-hearted attempt at the time to Frankinstein a recovery from the Poke3. I'm much better at this now but we need the original recovery from a Note3.