I have system recovery installed and have used it many times. I also have nandroid backups installed......but I'm curious, if I'm boot looping how can I get to the system recovery screen? If my phone's in a constant boot loop can't I only get to the android recovery screen?
I know if I shut my phone down it'll go into System Recovery when it's plugged in, but if I reboot (or constantly reboot) I can't get to it at all, only android recovery and rsd and all that stuff.
xxbgjhn159xx said:
I have system recovery installed and have used it many times. I also have nandroid backups installed......but I'm curious, if I'm boot looping how can I get to the system recovery screen? If my phone's in a constant boot loop can't I only get to the android recovery screen?
I know if I shut my phone down it'll go into System Recovery when it's plugged in, but if I reboot (or constantly reboot) I can't get to it at all, only android recovery and rsd and all that stuff.
Click to expand...
Click to collapse
Pull battery to turn off phone
plug phone into wall
put battery back in
It will go to system recovery UNLESS u previously did a data wipe
I have used this.method many many times when bootlooping and have been able to get into bootstrap and restore nandroid and be all good to go
This is the EXACT reason why I don't mind having to plug my phone in to get recovery
many times I have bootlooped and each time I was able to get.into bootstrap. Of course if u panic and do a data wipe from stock recovery u won't be able to get in as it will wipe the charge_mode_hijack
Previously as in right before, right? Just making sure.
I was thinking that but the last time I bootlooped was when I first rooted and just sbf'ed. (didn't have a backup then...and system revocery possibly)
xxbgjhn159xx said:
Previously as in right before, right? Just making sure.
I was thinking that but the last time I bootlooped was when I first rooted and just sbf'ed. (didn't have a backup then...and system revocery possibly)
Click to expand...
Click to collapse
Bootlooping AFTER SBF is very common
Data wipe from stock recovery fixes that problem.
U wouldn't be able to get into bootstrap after sbf anyways since it takes root away
So what can I do if I DID a data wipe.... I have a nandroid backup, I can see it, but I cant get it to load
shogundogun said:
So what can I do if I DID a data wipe.... I have a nandroid backup, I can see it, but I cant get it to load
Click to expand...
Click to collapse
What did u do b4 u started bootloop?
Related
ok im stuck on my boot logo for my motorola droid 2. its a liberty logo, no the original M logo, ive held in x when it starts up and then it takes me to the triangle and then i hold the search button down and then it takes me to a menu saying this:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
ive already tried just rebooting it and then it does the same thing again and just gets stuck at the boot logo, so please help. thanks!
Have you tried pulling the battery out for about 15 seconds?
See if that clears it up.
with it unplugged and turned off?
Yes Sir. Unlug it and turn it off.
yes i just did that and it didnt work, its still at the boot logo, the only thing i can do is go to that recovery menu that i said about in my 1st post, but idk what to do when i get there?
Try wipe data/factory reset.
Obviously you're gonna have to tweak your settings again.
okay, is there anyway i can get my settings back like a recovery? or something
Well, you might want to head in to the Droid 2 forums to get better responses related to your phone.
Here is a link to start with.
As far as recovery goes, I don't think you have a custom recovery installed. Sounds like you have a stock phone. So, there's no way of backing your stuff up.
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Zimm814 said:
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Click to expand...
Click to collapse
If you have it rooted, did you ever perform a Nandroid backup ?
Do you have a non standard recovery installed?
EDIT: Sorry re-read last few post and come to conclusion that you probably don't.
sorry but doesnt rds lite 4.8 and the correct sbf file let u flash back to stock?
If your phone is rooted then you have changed your kernal.It might be a fault with the kernal.I had a similar thing happen in an SGS.It was rooted and when i flashed the kernal againh via CWM it also got stuck on the same as you.The only way to solve it was boot to download mode and flash via odin again.
I think I bricked my Evo 3D. I was installing a this ROM with this recovery (but I didn't wipe/factory reset anything, just went to the recovery and flashed the .zip) and I am bricked at the Sprint screen after booting. I have a Nandroid backup, but when I flash it, I still can't boot up. Any ideas?
Cwebb03 said:
I think I bricked my Evo 3D. I was installing a this ROM with this recovery (but I didn't wipe/factory reset anything, just went to the recovery and flashed the .zip) and I am bricked at the Sprint screen after booting. I have a Nandroid backup, but when I flash it, I still can't boot up. Any ideas?
Click to expand...
Click to collapse
You are not bricked. If you were bricked your phone would be a useless unbooting paper weight. Reboot back into recovery and wipe system, cache, dalvik cache and data. After the wipes try restoring your nandroid backup. If you really want that ROM you need to follow the instructions on proper flashing the boot.img with fastboot because I'm assuming you have HBOOT 1.5
私のEVO 3Dから送信される。
dastin1015 said:
You are not bricked. If you were bricked your phone would be a useless unbooting paper weight. Reboot back into recovery and wipe system, cache, dalvik cache and data. After the wipes try restoring your nandroid backup. If you really want that ROM you need to follow the instructions on proper flashing the boot.img with fastboot because I'm assuming you have HBOOT 1.5
Click to expand...
Click to collapse
Trying that now, thanks for the heads up.
dastin1015 said:
You are not bricked. If you were bricked your phone would be a useless unbooting paper weight. Reboot back into recovery and wipe system, cache, dalvik cache and data. After the wipes try restoring your nandroid backup. If you really want that ROM you need to follow the instructions on proper flashing the boot.img with fastboot because I'm assuming you have HBOOT 1.5
Click to expand...
Click to collapse
Still stuck at bootscreen, I'm starting to get sick of looking at this Sprint logo
Cwebb03 said:
Still stuck at bootscreen, I'm starting to get sick of looking at this Sprint logo
Click to expand...
Click to collapse
I assume your problem is related to the kernel/kernel modules you have. You need to follow instructions on how to flash a kernel with hboot 1.5.
connect your phone to the computer, open device manager, if you see MTS Device with a warning yellow triangle on it(i think its MTS but it could be MDS or something, i don't remember now), right click on it, select disable. On the same dialog , if there an android device with the same triangle, disable that as well. Turn the phone off, try pulling the battery out(both volume keys and power button may not work, as it will just restart the phone) Now put the battery back, don't start the phone, connect it to your computer, run adb reboot bootloader command.If the phone goes to bootloader mode, issue fastboot command mentioned on the guide page to load your recovery. And reflash. You might have to restart your computer as well. As the problem is windows is not loading android drivers properly.
Another solution could be to load android drivers from device manager it self by right clicking android phone and update the driver.
I guess the issue is some new media drivers or something like that are needed with ICS .
karan_736 said:
connect your phone to the computer, open device manager, if you see MTS Device with a warning yellow triangle on it(i think its MTS but it could be MDS or something, i don't remember now), right click on it, select disable. On the same dialog , if there an android device with the same triangle, disable that as well. Turn the phone off, try pulling the battery out(both volume keys and power button may not work, as it will just restart the phone) Now put the battery back, don't start the phone, connect it to your computer, run adb reboot bootloader command.If the phone goes to bootloader mode, issue fastboot command mentioned on the guide page to load your recovery. And reflash. You might have to restart your computer as well. As the problem is windows is not loading android drivers properly.
Another solution could be to load android drivers from device manager it self by right clicking android phone and update the driver.
I guess the issue is some new media drivers or something like that are needed with ICS .
Click to expand...
Click to collapse
I'm not having any problems connecting it to my PC and getting it into recovery, its just any ROM/Kernel/Nandroid I flash all leads me to the endless Sprint logo
Fixed it by wiping EVERYTHING multiple times, then restoring my Nandroid backup. Still having problems flashing a ROM, I put it on the SD, manually booted to recovery w/o computer, wiped everything, then flashed the ROM but won't boot past the Sprint/Android screen. Any ideas?
freeza said:
I assume your problem is related to the kernel/kernel modules you have. You need to follow instructions on how to flash a kernel with hboot 1.5.
Click to expand...
Click to collapse
You need to listen to Freeza.
Lol that would be called a bootloop not bricked .
Please use the Q&A Forum for questions Thanks
Moving to Q&A
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
klarson said:
Your phone is not bricked. When the phone is stuck on the droid eye, hold the power button and the volume down key at the same time until it reboots. This will get you into bootloader mode. Press the volume down key to highlight recovery and press the power button to enter it. Once you're in recovery go ahead and restore a backup or reflash something new. Either way make sure to do a full wipe.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
thats what i did i restored my backup and this is what happens. and i cannot push any files over to the phone because usb debugging is not enabled so there is no communication between the phone and computer at all
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Jmlannan said:
boot into recovery then use "adb push <path to rom> /mnt/sdcard/" to put a rom on the sd then install. Make sure you use a boot.img that came with the rom if it has one as it may cause problems if you don't.
Edit: you will need another rom for this and I would recommend reflashing a boot.img
Click to expand...
Click to collapse
the problem im having is the phone is not being recongnized by the adb so there for i can not push anything to the phone.i have no communication with the phone at all so i cant push any files at all.im looking for a way around this
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
USB debugging has nothing to do with ADB in recovery, recovery basically has its own kernel and ADB is always enabled. Are you saying ADB doesn't work in recovery? If so, it is probably a driver problem with your computer. Also, some phones randomly get corrupt /data/ partitions (mine used to get them until I started using DSB's stock kernel with system write) and the only way to fix it is to do a factory reset or restore a backup. This might be what happened to you. If so just do a factory restore and see if it will boot.
Perhaps reflashing recovery? Worth a try if ur still having problems, also try installing then uninstalling htcs sync app.
nathan101 said:
i recently rooted my phone and flashed clockwork and was running beastmode kernal on stock rom.everything was working ok i used to get little glitches here and there so i tried to restore my phone back to factory.i entered the recovery mode and wipe date/factory reset and then went on to restore the backup.everything went smooth until i reboot the phone and now the phone is stuck in the droid(eye logo) and wont past that at all and just glitches and freezes on that screen.my friend has tried to fix it but there is no communication between the phone and the computer(usb debugging must have been disabled when i wipe data/factory reset and i basically cant do anything to fix it.is there a way around this to where i can just reset the phone to factory or install a rom or something
Click to expand...
Click to collapse
Try restoring back to stock with the Droid DNA RUU, i had issues with it locking up and freezing and i couldnt do a thing with it. i stumbled on the RUU and followed the instructions and re-stocked it. then just root and flash again. worked for me and im now running the Battery Plus ROM and have no issues yet. good luck
Just be sure to re lock before you flash the ruu
Sent from my HTC6435LVW using xda premium
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Bump...
Ideas/suggestions?
kevinbakon said:
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Click to expand...
Click to collapse
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
OfficerJimLahey said:
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
Click to expand...
Click to collapse
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results, but I do see the devise in fastboot, if I am in the bootloader screen
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Otherwise, I guess I could reinstall factory recovery, but I can't figure out how to do that either.
Unfortunately, the LG G Watch Tool doesn't seem to be working for me either. It just says "waiting for device"
Ultimately, all I want to do is get the latest stock OS installed and go from there
Any advice?
kevinbakon said:
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Any advice?
Click to expand...
Click to collapse
Wait, installed TWRP? If it keeps taking you back into TWRP, then "fastboot flash boot" was used, not "fastboot boot". Read my previous post for difference.
What were the backup errors? Did something not mount? If so, then this (coupled with the original issue), may be hardware related and out of your control.
See if you can get back to the bootloader first. The boot.img can be restored this way, and get you one step closer to booting.
Sent from my ASUS_Z00AD
Helllo yes it seems your partitions are all messed up. Considering that on android wear your "data" on it is almost all on your phone aswell it seems like a waste to try and recover it.
here is a link to the system,recovery and boot images from LCA43 https://www.androidfilehost.com/?fid=24052804347803309 just flash those to each partition correctly ie. fastboot flash boot boot.img etc
and wipe your /cache and /data partition. You will essentially have a completely stock device and if it still thosen't function correctly then it is a hardware fault
Here is a video on how to access bootloader from boot screen: https://www.youtube.com/watch?v=ftSCH7qihRI