Boox Note 3 bricked

[aaron42195]

I think I made a mistake.
I referred to other threads and accidentally flashed the wrong image to the machine.
Does this mean we need to get the original recovery image from a functioning machine?

[Renate]

I guess that you didn't backup the recovery before you flashed the custom recovery?

Do you know where you got that custom recovery? I'll delete it.

[aaron42195]

Originally Posted by Renate

I guess that you didn't backup the recovery before you flashed the custom recovery?

Do you know where you got that custom recovery? I'll delete it.

Should be here.https://www.mobileread.com/forums/sh....php?p=4280033

[Renate]

Yeah, but that was the Poke3 thread.
I never said that that was even possibly good for the Note3.

I do remember working with somebody on the Note3 a long time ago on a different thread.
I don't think it worked and it was never released.

[aaron42195]

Does this mean my Note 3 is beyond saving? Or do we have other solutions?

[Renate]

There are a few solutions:

• Get a copy of stock recovery and use factory reset
• Get a copy of stock recovery, mod it for my autoupdate and update the latest
• Add an overlay to your Magisk'ed boot image to enable ADB
• Brotli expand the the individual partitions in the update and flash them with EDL

You already did fastboot -w (erases all data)?

[aaron42195]

Originally Posted by Renate

There are a few solutions:

• Get a copy of stock recovery and use factory reset
• Get a copy of stock recovery, mod it for my autoupdate and update the latest

You already did fastboot -w (erases all data)?

Okay, I will try to get the copy of stock recovery.
[*]Add an overlay to your Magisk'ed boot image to enable ADB[*]Brotli expand the the individual partitions in the update and flash them with EDL
No idea about these 2 solutions.



Yes, I already did fastboot -w..

[Renate]

Post me your Magisk'ed boot image.
I'll take a shot at it.

[aaron42195]

Originally Posted by Renate

Post me your Magisk'ed boot image.
I'll take a shot at it.

Here is the file.

[Renate]

Just as a sanity check, flash this to the boot partition.
It should boot loop the same as before but not totally fail.

[aaron42195]

Flash into boot partition and reboot.
It is still stuck on the startup animation.

[Renate]

Ok, try this:
Look for ADB.

[aaron42195]

Originally Posted by Renate

Ok, try this:
Look for ADB.

C:\temp\platform-tools-latest-windows\platform-tools>fastboot flash boot C:\temp\bootmod\bootmod.img
Sending 'boot' (13612 KB) OKAY [ 0.043s]
Writing 'boot' OKAY [ 0.056s]
Finished. Total time: 0.130s

C:\temp\platform-tools-latest-windows\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s

C:\temp\platform-tools-latest-windows\platform-tools>adb devices
List of devices attached
7AE7E622 unauthorized

Is this correct?

[Renate]

Originally Posted by aaron42195

7AE7E622 unauthorized

Well, that's progress, Isn't it? You didn't have that before?

Let's try with your public Android key. That's not secret.
If somebody steals it, it means that you can ADB to their device.
It's called C:\Users\Whoever\.android\adbkey.pub
Just double check it. It's about six lines long, starts with QAA and ends with a fake email address.
If you like remove the email address at the end.
It's not the one that says PRIVATE KEY all over it.

[aaron42195]

Originally Posted by Renate

Well, that's progress, Isn't it? You didn't have that before?

Let's try with your public Android key. That's not secret.

This one?