View Single Post
Old 01-15-2023, 08:18 AM   #4
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: 3,989
Karma: 18026955
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
There are probably a lot of interdependencies.
Your original system may be older or even incompatible.

Did you have ADB enabled before this all happened.
When a "bootloop" occurs the Linux-ish part of Android could be running fine.
It could be that the trivial Android/screen part is broken.
You can't tell without looking.

I had a recovery that I made for the NA2 some months ago. I just updated it.
Could you try this with just fastboot boot recmod?
I usually don't have much luck with fastboot boot image (vs. fastboot flash partition image).

This will show a white screen. Just try to access ADB.
Code:
C:\>adb shell
# getenforce
0
# ls
No, you don't have to quote it, just did it get ADB, did it get #, did it not complain about timezones?

I sent you a link in PM.
Renate is offline   Reply With Quote