Ok, so the glass on my nexus one cracked, so I put in for a swap with HTC. it just came today, so I threw my sd card, sim, and battery in it and boot up. It gets stuck on the X. So I pull the battery, fastboot, unlock the bootloader, still won't boot. So I go through the steps to get back to the original shipping rom by flashing through fastboot and it boots. Ok. Now I root the phone, worked ok. So I go grab rom manager and flash clockwork recovery so I can install a rom, or one of my backups. Won't boot into recovery. I tried 3 different versions, nothing. Even tried flashing Amon Ra's, still nothing. It will boot normally into 2.1 at the moment, but it seems I have no way to get into recovery to flash even the stock 2.2 rom. Anyone have any ideas as to why fastboot works, and it boots normally, but won't boot into recovery?
i apply the wrong boot image instead i use a nexus S and my nexus one is stuck forever... -_-..
i tried to recovery on flash boot recovery but the screen also stuck...
below is the file that i use...
http://forum.xda-developers.com/showthread.php?t=1139261
my nexus one is 2.3.4.. any kind soul can guide me.
Thanks!!
Why not just start over if you are that stuck, passimg to stock. Or fastboot flash the img.
Passimg back to stock then seeing as you were trying to use this I'm going to suppose you already have an unlocked bootloader so just flash a custom recovery then flash su from recovery all the files you need are in my sig.
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
how do you flash the old bootloader? if you don't mind me asking.
I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.
ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus
You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063
I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.
anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.
Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse
Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Have you used ADB to delete cache, Then re-flash a recovery ? Then full wipe etc and clean install a Rom ?
Sent from my HTC One using Tapatalk 2
jthornton71707 said:
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Click to expand...
Click to collapse
type fastboot erase cache from PC while phone is in fastboot. you should be able to get into recovery afterwards. If not, flash another recovery from fastboot. fastboot flash recovery RECOVERYNAME.img
I unlocked the bootloader on my HTC One and successfully flashed CWM recovery; however, when I try to boot into recovery the HTC splash screen comes up with "Entering Recovery" for a few seconds (as it should), then the screen goes black for a second and it boots into the ROM like normal without going into Recovery.
I've seen that the general fix for this is to clear the dalvik-cache, but I can't do that without root permission, and I can't install the superuser to get root without being able to boot into the Recovery.
I have developer options enabled with USB Debugging, Fastboot is turned OFF.
I have flashed to plain CWM, touch CWM, and TWRP, all with the same results.
fastboot erase cache had no effect
beotric.android said:
I unlocked the bootloader on my HTC One and successfully flashed CWM recovery; however, when I try to boot into recovery the HTC splash screen comes up with "Entering Recovery" for a few seconds (as it should), then the screen goes black for a second and it boots into the ROM like normal without going into Recovery.
I've seen that the general fix for this is to clear the dalvik-cache, but I can't do that without root permission, and I can't install the superuser to get root without being able to boot into the Recovery.
I have developer options enabled with USB Debugging, Fastboot is turned OFF.
I have flashed to plain CWM, touch CWM, and TWRP, all with the same results.
fastboot erase cache had no effect
Click to expand...
Click to collapse
try reflashing recovery use twrp 2.5.0.0
No Dice
Aldo101t said:
try reflashing recovery use twrp 2.5.0.0
Click to expand...
Click to collapse
Flashed to TWRP 2.5.0.0, same result
beotric.android said:
Flashed to TWRP 2.5.0.0, same result
Click to expand...
Click to collapse
are you flashing recovery with adb-fastboot, what computer os are you using
are you usung the correct recovery image, for the sprint m7wls, (fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls)
use goo manager to flash the recovery and see
or you can use the all in one tool in the dev section
Aldo101t said:
are you flashing recovery with adb-fastboot, what computer os are you using
are you usung the correct recovery image, for the sprint m7wls, (fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls)
Click to expand...
Click to collapse
I am using the "fastboot flash recovery" command on Windows 7 64-bit (I have also tried on 32-bit).
You were right about the recovery file, I was using openrecovery-twrp-2.5.0.0-m7.img, not m7wls. So for anyone who finds this thread later make sure it's the right recovery file for your build and carrier (not just phone model).