• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Fix bootloop after updating SuperSU on 5.0 Nexus 5 without data loss

Z

Zachary Matson

Lurker
On my Nexus 5 running Android 5.0 (not 5.0.1) I selected to update SuperSU using the TWRP/CWM option in the SuperSU app (I have CWM). The update installed fine and after CWM asked if I would like to fix root I selected no. Boot was taking several minutes so I assumed I was dealing with a bootloop. I turned off the device mid-boot and wiped /cache and dalvik-cache. The device still will not boot. I have not yet tried anything else. I really do not want to lose my data, mainly music, settings, pictures/videos, and text messages. Any ideas?
 
How was the charge level have you tried to boot into recovery with / without it plugged into a electrical wall outlet
 
BRAINZ2013 said:
How was the charge level have you tried to boot into recovery with / without it plugged into a electrical wall outlet
Click to expand...
Around 70-80%. I have plugged it into the wall now and it is running through the bootloop. It was not plugged in when I did the wipes, and booting into recovery worked fine.
 
Zachary Matson said:
Around 70-80%. I have plugged it into the wall now and it is running through the bootloop. It was not plugged in when I did the wipes, and booting into recovery worked fine.
Click to expand...
If it boots into the recovery I say just do a fix perm. It should fix I reflashed the ROM . but I think the data is good but I had problems with play store apps
 
BRAINZ2013 said:
If it boots into the recovery I say just do a fix perm. It should fix I reflashed the ROM . but I think the data is good but I had problems with play store apps
Click to expand...
An hour ago or so carried this out. Downloaded stock images from Google for Nexus 5 5.0 and opened command prompt, put the phone in fastboot, and flashed the image for the system partition after extracting it from the ZIP file with all of the images. Thanks for the advice!
 
I had similar problems.

What worked for me, was to restore a CWM backup, WITH the charger plugged in.

(It did not solve the problem without the charger, just keep getting the loop.)
Go figure... Strange, but this is what worked for me.
 
You must log in or register to reply here.
Back
Top Bottom