Onyx 3.2.1 release screwed with buttons

[Djezpur]

So now I've noticed that even a factory reset (through com.android.settings/.Settings) reboots into the existing system, it seems like the real issue with my Poke3 is that it can't enter recovery mode anymore (which it could before rooting it with Magisk).

adb reboot recovery just reboots into system too.
Trying to get to recovery through fastboot, I get the error message "unknown reboot target recovery".

Any advice on this, Renate?

[Renate]

It's easy, just hold the volume up button... Just kidding.

adb reboot recovery works fine for me, maybe you killed recovery?
Usually, hopefully if you try to boot to a bad image it will go to fastboot.
The /misc partition is used to signal to go to recovery. You can write to that.

I've been working on stuff and bopping between EDL, recovery and normal.
I've probably got a bigger safety margin than you because I can always get into EDL easily.
Do you have EDL working at all? You could use EDL and pull a copy of recovery to check against stock.
Of course you can do that with dd too.

# dd if=/dev/block/mmcblk0p9 of=/sdcard/p9 count=37552
# md5sum /sdcard/p9
4f9373bdba1dae632ff0f80ec40e96a8

If it looks good, you can force it to recovery with /misc.
You could also just fastboot boot what you just copied.
Use EDL to pull a block off /misc or just dd /dev/zero to get 512 zeroes

dd if=/dev/zero of=/sdcard/misc-rec count=1

Then text/hex edit it to be "boot-recovery" for the first 13 chars.

# dd if=/sdcard/misc-rec of=/dev/block/by-name/misc
# reboot

Or you can edl /w it (if you're in edl).
This will keep on bringing you back to recovery, so you'll need to:

# dd if=/dev/zero of=/dev/block/by-name/misc
# reboot

(You'll get an error that it can't write more or something.)

The reason my head is so stuck in edl right now is that I'm bopping between enforcing and permissive on a Magisk-less system and edl is the only way to get out.

I was trying to draw a diagram to make things clearer. Mmm, not sure that it did.

[Djezpur]

Thanks for your elaborate response and the diagram (it looks crystal clear ).
I'm afraid EDL is new territory for me, so I would need some time to figure that out.

I expected the decrypted update.upx to contain a stock recovery.img but that does not seem to be the case.

Anyway, thanks again for your time. Maybe I should stop spending mine into this minor firmware upgrade, because the device itself works just fine for me.

[Renate]

The recovery image is not going to do you much good because the stock recovery does not enable ADB or allow you to install updates.

[Djezpur]

No, but since factory reset is not working from a normal boot, I was only thinking of trying a factory reset from stock recovery (and then install the updated firmware the official way). And that's under the assumption that my device not being able to boot into recovery is somehow the cause of not being able to update the firmware or doing a factory reset.
There's no custom recovery available for the Poke3, is there? I tried to fastboot TWRP for Onyx but that did not work.

[Renate]

I'm very wary of factory updates because who knows exactly what version it's updating to.
It also gets too confusing for my brain when somebody has problems and they say, "well, I rooted that with King Root, then factory restored, then restored a backup from somebody else, then installed a patch which bootlooped it so I had to...

I've got a half-baked recovery for the Poke3 which is sort of pre Alpha.

[Djezpur]

Originally Posted by Renate

I've got a half-baked recovery for the Poke3 which is sort of pre Alpha.

As in not ready for the general public (or an ex-flashoholic)?

[Renate]

Mmm, ready for people who can PM me.
I think that you have to have 10 posts or ask here:
https://www.mobileread.com/forums/sh...319819&page=56

[Renate]

Ok, is this any clearer?