Onyx Boox Poke 3 (Soft) Brick by deleting Email App

[Renate]

Looks good.
Take your update.zip (are you sure that you have the right one?) and extract META-INF/com/google/android/updater-script. Just post the first couple of lines right here in [code][/code]

[toryr]

I'm pretty sure, downloaded it from their website.

(!less_than_int(1638273121, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Nov 30 19:52:01 CST 2021) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "NovaAir" || abort("E3004: This package is for \"NovaAir\" devices; this is a \"" + getprop("ro.product.device") + "\".");

[Renate]

Oh, my bad. You've got the build props from the Poke3 in there.

Same link, different file.

Edit: Just out of curiousity, are you eMMC or UFS?
Does ls -l /dev/block show lots of mmcblk0p?? or lots of sd??

[toryr]

I see a bunch of mmcblk0p files.

start autoboot now runs However, its been stuck like this for a while, is that normal? https://we.tl/t-elCHknSDH7

[Renate]

My verbosity may be slowing it down, as long as it's still moving...

Do a ps -e and check if ttyscreen and autoupdate are still working.
Do a "echo Hello there >/dev/ttyscreen" to see if that crashed.

[toryr]

It hasn't moved in a while now, stuck at 0.9864

[Renate]

Yeah, but it wrapped around to the top and the last progress is 1.0
Check the processes. Also look for update-binary in ps -e

Also, as long as you're connected, do this:

# dd if=/dev/block/by-name/recovery of=/dev/block/sda1/recovery.img

It could be some deadlock in the pipes. Don't reset or do anything rash until we figure out what is going on.

[toryr]

Ah. You're right. I tried flashing by pushing update-binary via adb and running it that way, and it works. dd gives:

dd: /dev/block/sda1/recovery.img: No such file or directory

I tried rebooting and now I see the startup screen (hurray!), but it won't go past the "starting up" stage.

[Renate]

Originally Posted by toryr

Ah. You're right. I tried flashing by pushing update-binary via adb and running it that way, and it works.

Huh? How are you typing to ADB and have the update.zip still installed on the flash?

Ok, do you have ADB working on your (partially booted) normal system?

[toryr]

I pushed the update.zip and update-binary to /data and ran ./update-binary 2 1 update.zip. Tried rebooting, didnt work (also no adb), so i went back to recovery.

[Renate]

So your /data wasn't encrypted? And it was mounted already? Or did you mount it?
Was ADB enabled before on the regular system?

[toryr]

I honestly dont know, i just did adb push to data and it all kinda worked.

I did root my device and enabled adb in that process, before bricking it, is that what you mean?

[Renate]

So update-binary printed out the log? Did it end at the same set_progress 1.0000?

[toryr]

Yup! ()

[Renate]

Well, if you have /data in recovery then just check:
/data/system/users/0/settings_global.xml that it has

settings_global.xml:  <setting id="5236" name="adb_enabled" value="1" package="android" defaultValue="1" defaultSysSet="true" />

Don't copy mine! Just change value="1" if value is zero.