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

Root Q:Stuck in bootloop Help!

kev48173

Lurker
Okay, so I am stuck in a bootloop, b/c I tried to remove boot sound. I can access recovery and did a factory reset but it didn't help. In adb and fastboot the device isn't found even though I have the drivers installed. Suggestions?
 
welcome to the forums! :shakehands: what exactly did you do to delete the boot sounds? do you by chance have a nandroid saved?
 
We have no custom recovery, no nandroid. :(


Can you get adb while in the stock recovery? With no adb in fastboot or the recovery, you cant push any files. A factory reset will not restore any /system files you deleted, and we don't have a stock update.zip yet either. You can try to reinstall your phone drivers.

Edit, wow lulzzz
 
User error is not a valid reason for a warranty replacement, talking about it amounts to fraud and any further discussion won't be tolerated.
 
welcome to the forums! :shakehands: what exactly did you do to delete the boot sounds? do you by chance have a nandroid saved?

How would it be possible to have a nandroid backup if there's no custom recovery for the RiSE yet? Sure, you can backup through Titanium, but if he's stuck in a bootloop, there's no way to it.
 
How would it be possible to have a nandroid backup if there's no custom recovery for the RiSE yet? Sure, you can backup through Titanium, but if he's stuck in a bootloop, there's no way to it.

The paid version of tiB has the ability to create an update.zip. Whether or not it would flash in the stock recovery, I don't know, i've never used it.
 
OK guys sorry I thought I read somewhere you could do it from adb. As for the flash able zip in TiBu I wild NOT recommend this without custom recovery!
 
OK guys sorry I thought I read somewhere you could do it from adb. As for the flash able zip in TiBu I wild NOT recommend this without custom recovery!

I think your right, I do recall a thread guide on how to do a backup through adb, but I think it was hit or miss, if it worked reliably.
 
ok this is what i found in regard of a nandroid:
WARNING: only attempt if you know what your doing!!!
You could do adb pull for the system, and data.

this is prob the easiest method to pull all the files out. if you wanted to make it simplier, you could create a tar of the directories onto the sdcard and then adb pull the single .tar file
first, make sure to mount the partitions:
adb shell
mount -o rw /system /system
mount -o rw /data /data
then exit the shell
something such as: adb shell tar -cvf /sdcard/system-backup.tar /system
and: adb shell tar -cvf /sdcard/data-backup.tar /data

for using the straight adb pull method, you'll want to mount the partitions first and then you can execute the adb command.
adb shell
mount -o rw /system /system
mount -o rw /data /data
then exit the shell
adb pull /system c:\android-backup\system
adb pull /data c:\android-backup\data

I copy that from a thread at XDA here http://forum.xda-developers.com/showthread.php?t=1526555

You could then push them back.

Hope that might help.

once you have a nandroid (from a bootable phone) you can get the files you need to push back to your device with android commander. we would need someone with the nandroid to extract it and upload the files you need so you can push them back to your device with android commander.
 
Anyone tested the above? I did do a backup of "system" before modifying anything in it, But I would be scared to actually try to "push" it back. Would permissions of the files remain unaffected? And would overwriting all those files cause a problem while android is loaded up? Just sounds risky to me.
 
Back
Top Bottom