View Single Post
Old 11-10-2026, 11:33 AM   #82
tatteredscroll
Zealot
tatteredscroll will become famous soon enoughtatteredscroll will become famous soon enoughtatteredscroll will become famous soon enoughtatteredscroll will become famous soon enoughtatteredscroll will become famous soon enoughtatteredscroll will become famous soon enough
 
tatteredscroll's Avatar
 
Posts: 105
Karma: 510
Join Date: Sep 2012
Device: Kindle Paperwhite Kids 2022 11th Gen (PW5)
Quote:
Originally Posted by Renate View Post
So you're saying that when it was broken neither the stock recovery or my custom recovery worked?
Have you gone back and checked both?
Yes. Both were flashed while this was still the 3.3.1 system with the Magisk boot. System and vendor were not flashed, so vendor was still the old one. Stock was note2-rec.img, extracted from the 3.5 update.upx. Yours was the static-linked custom recovery you PM'd, flashed on 6 Oct 2025 as note2-rec2.img. Both writes reported 100%. misc-recovery.prc put it into recovery, and neither one reached a menu or adb.

The UART log showed is_recovery_mode: 1. The Onyx logo came up and it sat there. USB never enumerated, so there was no adb device and Windows made no USB sound. Swapping the recovery file did not change that. Magisk was on the boot partition, not in recovery.

During the fix, recovery was overwritten with the official 3.5 recovery.img from that same update.upx, and vendor was replaced with the matching 3.5 vendor. Recovery has not been booted since, so I have not retested your idea that stock recovery needed the matching vendor.

Last edited by tatteredscroll; 11-10-2026 at 11:35 AM.
tatteredscroll is offline   Reply With Quote