View Single Post
Old 09-23-2024, 10:46 AM   #28
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,086
Karma: 18218153
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Ok, so Note3

I looked at the update.
I had to write a DeBooxUpx in C because I was so sick of the broken Python.
Dependencies from hell.

There's no recovery in that update.
It's hard to tell why that misc patch wouldn't send it to recovery.
It's hard to tell why it's bootlooping.

Since you're Magisk'ed I can try to make an overlay so that ADB starts up.
But I tried that with somebody else's something-or-other and it didn't work.
Doing this stuff at a distance is very difficult.

We can try making a custom recovery.
That's still going to take some cooperation.
Use EDL and pull recovery:
Code:
edl /lwhatever.bin
edl /u4 /r /precovery rec.img
Renate is online now   Reply With Quote