[GUIDE] Recovering from a bootloop without TWRP or KDZ/TOT

user787

Senior Member
Apr 1, 2012
124
15
0
San Juan
every time I run the command while in bootloop it says "Device not found"
This happened to me a week ago. Got bootloop trying to enable FM radio on device. Had made this before:

Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop
But device not authorized / not found (previously used the same computer to gain root). Long story short, had to factory reset / reinstall fw then restore device to previous state with TB. Then reauthorize su on boot, authorize adb shell to run root permission and be sure that the computer is authorized for USB debbuging.

Hope this extra steps let me recover from another bootloop
 
Last edited:

tabp0le

Inactive Recognized Developer
Oct 4, 2013
1,824
3,560
113
Phoenix
www.spryservers.net
This happened to me a week ago. Got bootloop trying to enable FM radio on device. Had made this before:



But device not authorized / not found (previously used the same computer to gain root). Long story short, had to factory reset / reinstall fw then restore device to previous state with TB. Then reauthorize su on boot, authorize adb shell to run root permission and be sure that the computer is authorized for USB debbuging.

Hope this extra steps let me recover from another bootloop
That should work. Give it a test. Plug your computer into usb, reboot. Right when you see the device recognized while its still booting do this:
Code:
adb shell stop
adb shell
$su
 

Noksucow1

Senior Member
Jul 19, 2016
62
13
0
Is there any way to enable the SU during boot option via ADB? I have a device stuck on LG logo without download/recovery, but it has access to ADB. However SU does nothing so I don't have the permissions needed to replace the system.img and/or change the recovery & laf to working versions.