Anyone willing to "repair" an Onyx Note 2?

[Renate]

Normally you should be able to get to recovery after flashing misc and then edl /z.
But misc gets overwritten by recovery normally.
So you need to flash it (misc) again.

[tatteredscroll]

Originally Posted by Renate

Normally you should be able to get to recovery after flashing misc and then edl /z.
But misc gets overwritten by recovery normally.
So you need to flash it (misc) again.

Should I do the flash steps again with firehose and misc prc then edl/z?

[Renate]

I'm just saying that when/if 5xbutton is required then flashing misc should do the same.

That the stock recovery doesn't work is a problem.
Normally it should be fairly self contained.
But it might rely on other partitions.
Maybe even partitions that are not in the update.

I think you need to look closer at the stock recovery log to see where the problem is.

[tatteredscroll]

Originally Posted by Renate

I'm just saying that when/if 5xbutton is required then flashing misc should do the same.

That the stock recovery doesn't work is a problem.
Normally it should be fairly self contained.
But it might rely on other partitions.
Maybe even partitions that are not in the update.

I think you need to look closer at the stock recovery log to see where the problem is.

Copy that. I'll firehose flash files from update.upx again with edl /z and get a clean boot log and see what I can see.

Edit: link to output from Onyx Boox Note2 firehose load to recovery boot console log output

https://justpaste.it/7z13f

[tatteredscroll]

Google AI says--

The fb_blank(): END! message on a Qualcomm Snapdragon 625 device (MSM8953) indicates that the display driver has been initialized and then turned off. When this happens while trying to boot into recovery, it suggests a software issue, such as a corrupted recovery partition or a problem with the bootloader.

[Renate]

Was that paste from the stock recovery or from my recovery?
It seems that it was running all happy but nothing was happening.

[tatteredscroll]

Feel like I've hit a dead end. Thanks to @Renate I now have the tools to troubleshoot and have learned a lot about what makes these things tick. I've tried many ways to revive the device and it's not responding as expected. If the Google AI response is accurate, it's unable to load and draw the recovery menu to the screen as a result of faulty recovery partition and/or problem with the bootloader.

A factory reset when done against a root-patched image with Magisk (this was back in 2023) could have corrupted an area or partition unexpectedly...Onyx factory reset going against a root-patched device.

Q: Is it possible the firehose file is not the correct one? Or would we have seen an error immediately if it wasn't compatible?

Q: Would an update.gpx at version 3.3.1 or 3.3.2 make any difference?

[tatteredscroll]

Originally Posted by Renate

Was that paste from the stock recovery or from my recovery?
It seems that it was running all happy but nothing was happening.

Stock Recovery and misc prv from this thread. I agree, most of the boot log seems normal/happy until the end. I mean, there are occasional error here and there, and can't find a file or can't do this or that, but none of those seem to stop the flow and even though Google point out a possible cause of the END! statement there are two lines after the END! statement.

Maybe (as the google AI suggests) it's expecting something, can't find it, then sort of stalls. It see button input from top button and front-panel button. Doesn't register touch input. As stated before, it just loads the Onyx splash image and sits there never seen by windows device manager, usblog, adb.

[tatteredscroll]

This may be obvious to others (not to me), but after some digging, this section of the startup log tells us that it's skipping the normal boot process and is entering recovery mode. So I think everything after this is recovery mode starting.

[ 8.311300] init: init first stage started!
[ 8.314465] init: First stage mount skipped (recovery mode)
[ 8.320134] init: Using Android DT directory /proc/device-tree/firmware/android/
[ 8.327485] init: Skipped setting INIT_AVB_VERSION (not vbmeta compatible)
[ 8.334336] init: Loading SELinux policy
[ 8.445781] audit: type=1403 audit(86706.729:2): policy loaded auid=4294967295 ses=4294967295
[ 8.453579] selinux: SELinux: Loaded policy from /sepolicy
[ 8.453579]
[ 8.460505] init: kernel_enforcing: 0, is_enforcing: 0, is_recovery_mode: 1

[Renate]

Yes, it is the recovery image booting, but apparently it's not running the recovery init service.
It should also be showing ADB even if it's "unauthorized".