I upgraded my CWM and then loaded a new Rom to my phone. During the install I had. An issue and the phone rebooted. It will not get past the boot logo. I restarted into recovery but when it loads it just reboots. It doesn't allow me to reinstall a Rom. Can I just reinstall CWM recovery to my sd and would it boot into recovery k like normal?
Sent from my LG-D800 using XDA Free mobile app
I have backed up my Rom but recovery won't stay up for me to load the back up
Sent from my LG-D800 using XDA Free mobile app
Are you s-off?
Before upgrading cwm, I am assuming you could flash different roms.
Let me / us know what you have done so far and in what state you are now in.
Edit: I am quite rusty so I may not be able to help.
Sent from my Desire HD using Tapatalk 2
Still unable to use the phone. Yes I was s off. Yeah I've been installing roms every week for years now. I saw a post about an upgrade cwm recovery and updated. I booted into recovery like normal and installed a Rom. The install went bad and The phone gets stuck on the HTC splash screen. When I boot into recovery it opens for just a second and then the phone just reboots on itself. I Havnt been.able.to do anything to it. I'm not sure what to do.
Sent from my LG-D800 using XDA Free mobile app
If you can access the bootloader still you can flash a new (your old working) recovery with fastboot can't you?
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash recovery FILE.IMG
replace FILE.IMG with your recovery image.
also you can extract your recovery image from your last working nandroid backup. it should be just recovery.img
The way it sounds is that your boot.img got messed up somehow. Maybe try just flashing the boot.img from that rom you last flashed? (the one that doesnt work) but I would just really go about flashing a working nandroid backup/ or recovery with fastboot.
You can restore from a backup with fastboot as well I'm pretty sure...
Anyways here's a link you should check out. https://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
Related
Edit:
Hello everybody!
I formatted / boot through the Clockwordmod and now the phone does not boot the android, always turns on Clockword.
I tried to use fastboot to install a new boot, but does not work, is always "waiting for device".
What should I do? Is there any way to install a new boot using the Recovery?
Please! I'm desperate!
By /boot do you mean the bootloader? To me you seem to have removed the OS from your phone so you may have killed it.
Unless you have a bootloader I'm which case your fine.
Sent from my Nexus S using xda premium
I formated /boot. I can enter on Clockword normaly, but just it. I remove the OS, I think.
I had lost my phone??
If I use fastboot with one bootloader img, can I solve this problem?
So, I cant use fastboot. My PC doenst recognize my phone!
Anybody help?
Please, i´m very sad about it!
u might need Odin then to flash your original firmware. Make sure you download the right version for your phone.
Sent from my Nexus S 4G using xda premium
Boot into recovery go into backup and restore from a backup you made earlier. You can also just restore boot using the advanced backup restore.
If you don't have any backups and clearly you have a custom recovery installed, what can I say... serves you right.
Boot is the kernel.
Mount USB storage in clockworkmod recovery. Put a kernel on the phone and flash it.
Or flash a rom
Or restore a backup off the boot as mentioned .
Im kinda outta the know, but i see a few Rogers guys that cant root since the 1.94( i think) update but can unlock thru htcdev. Some of you guys are having trouble getting a flashed recovery to stick, so you cant get a rooted rom flashed. Well, there is a VERY simple solution for you guys.
You have your recovery.img in your adb/fastboot folder and your in your device bootloader.
fastboot flash recovery nameofrecovery.img
Ya ya, you tried that, But Wait!
Now
fastboot boot nameofrecovery.img
That WILL boot you into your custom recovery. Now u can nandroid and flash your rooted rom. Once booted up, go download goomanager and install recovery from there. That one WILL stick.
If you ever temporarily need to use the stock recovery, simply put the stockrecovery.img into your adb/fastboot folder and just do
fastboot boot stockrecovery.img
do whatever, after you reboot you will still have your custom recovery, since all you did was boot the stock recovery, not flash it. Also works vice versa
Added:
if you boot a cwm recovery at first steps, after installing recovery thru goomanager go make a new nandroid because twrp wont restore a cwm backup.
Hope this helps out a little:beer:
Could have used this info a few days ago
Bookmarking this.
Sent from my HTC One XL using xda premium
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
Hey guys, first off new here though I've perused the forums for a couple of years without a profile. Anyways, I just recently picked up my lovely nexus 5, Sunday. And today I got around to rooting/custom recovery and updating to 4.4.1 via sideloader. But for some reason when I flashed CWM or TWRP both the latest versions, neither work. At the moment I have no functioning recovery. All it does is show the Google logo screen, never goes to the little android guy or the custom recovery screen, nothing. Just the white Google logo with black background and small lock at the bottom. Any help would be greatly appreciated. I am on 4.4.1, rooted with cf auto, I have erased the install-recovery.sh, I have tried twrp one click, I have tried manually flashing cwm img file and twrp img file. Each time through adb, each time using fastboot erase recovery and fastboot install recovery recovery.img.
I've followed countless tutorials, and followed them to the letter but nothing has worked. Any help is greatly appreciated!
Sent from my Nexus 5 using xda app-developers app
imyourpriest said:
Hey guys, first off new here though I've perused the forums for a couple of years without a profile. Anyways, I just recently picked up my lovely nexus 5, Sunday. And today I got around to rooting/custom recovery and updating to 4.4.1 via sideloader. But for some reason when I flashed CWM or TWRP both the latest versions, neither work. At the moment I have no functioning recovery. All it does is show the Google logo screen, never goes to the little android guy or the custom recovery screen, nothing. Just the white Google logo with black background and small lock at the bottom. Any help would be greatly appreciated. I am on 4.4.1, rooted with cf auto, I have erased the install-recovery.sh, I have tried twrp one click, I have tried manually flashing cwm img file and twrp img file. Each time through adb, each time using fastboot erase recovery and fastboot install recovery recovery.img.
I've followed countless tutorials, and followed them to the letter but nothing has worked. Any help is greatly appreciated!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
mmh you don't need to erase the recovery before installing a new one, i wouldn't even recommend it
maybe just trying: fastboot devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
by the way, doesn't even the stock rec. occur?
its fastboot flash recovery recoveryname.img not fastboot install recovery recoveryname.img
stay away from root toolkits, its much faster without. without a toolkit this is all you do..
fastboot oem unlock (unlocks bootloader)
fastboot flash a recovery
flash the supersu su binaries in your new recovery
reboot
Sorry about the late response to this, but the conclusion was apparently the guide that sent me to a certain twrp (and cwm for that matter) were previous editions that weren't compatible. As for the question about stock rec. No stock wasn't showing at all, it got stuck on the little Andy with an exclamation mark logo. Finally fixed it by going through a walk through, unrooting it, flashing the stock .IMG and then locking the bootloader. THEN using kwonggers toolkit to unlock, root, twrp etc.
Anyways, in the end it all worked out thanks to looking around XDA thanks guys!
PS: drivers with this thing and windows 7/8 can be quite silly.
Sent from my Nexus 5 using xda app-developers app
Ok here's what happened. I am rooted running Slim Kat with CWM recovery installed. I decide to install TWRP using their app. When I booted into recovery, I got the TWRP splash screen, but the phone immediately rebooted. No recovery. I flashed CWM back using ADB. I was able to get into recovery from fastboot, but once I rebooted into the ROM, I couldn't get back into recovery again! Well, I said screw this! I had been thinking about flashing the factory stock lollipop ROM image, so I guessed this was as good a time as any. That process went well. Flashed lollipop images with ADB . Booted up. Everything fine. Set everything up. Tried to go into recovery. I have no recovery. Pressing Vol up & power buttons just reboots phone. Tried flashing CWM again. It flashed fine and phone will go into recovery from fastboot, but if I boot into ROM, and then try to go back into recovery — no recovery! I extracted the stock recovery from the image and flashed that. Same thing! I am out of ideas! Help!
Sent from my Nexus 7 using Tapatalk
With Lollipop it will install stock recovery after every boot. You can just boot twrp/cwm and flash SuperSU, that should fix your problem. If it doesn't delete /system/etc/recovery-from-boot.bak and you should be fine
Sent from my Nexus 5 using XDA Free mobile app
bm19981217 said:
If it doesn't, delete /system/etc/recovery-from-boot.p and you should be fine
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Correction.
Thanks! Looks like I was making 2 mistakes!
1. Had the button sequence backwards for stock recovery. It's hold power button down, then Vol up, release. I was holding power and Vol up simultaneously.
2. Didn't know that about lollipop. That explains why recovery kept "disappearing“.
Sometimes, trying to figure this stuff out at 3 am is not a good idea.
Still don't know why I had the problems with TWRP on Kitkat.
Sent from my Nexus 7 using Tapatalk
GadgetLady said:
Still don't know why I had the problems with TWRP on Kitkat.
Click to expand...
Click to collapse
Probably because you will have flashed 2.8.2.0 which doesn't work for most people. Try 2.8.1.0 and you'll be fine
Sent from my Nexus 10 using Tapatalk
As a matter of fact , it was 2.8.2.0.
Sent from my Nexus 7 using Tapatalk
GrenW said:
Probably because you will have flashed 2.8.2.0 which doesn't work for most people. Try 2.8.1.0 and you'll be fine
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I think this above post need to be emphasized. TWRP 2.8.1.0 solved all my problems.
With TWRP 2.8.2.0, I spent hours trying to figure out how to make recovery stick, even after rooting with CF Auto root, and the SuperSU BETA from Android L, AND after deleting the recovery-from-boot.p files and the install_recovery.sh files. It just would not load TWRP 2.8.2.0, using either "fastboot flash recovery twrp.img" OR "fastboot boot twrp.img". Either - it would reflash stock recovery (if I didn't properly delete the recovery script files), or, it would show the TWRP boot screen for a second or two, and then boot android normally! Every time!
As soon as I used 2.8.1.0 and retried "fastboot boot twrp2810.img" from a stock reflash, it worked without a hitch. Here are the steps I used to upgrade using fastboot from 4.4.4 to Android L (Euphoria ROM)
reboot into tWRP recovery in 4.4.4
Factory reset
Format system
Format userdata
Format cache
Reboot into bootloader.
fastboot flash bootloader with Android lollipop version. Reboot the bootloader
fastboot flash radio with Android Lollipop version. Reboot the bootloader
fastboot flash boot (stock lollipop). Reboot the bootloader
fastboot flash recovery (TWRP 2.8.1.0). Reboot the bootloader
fastboot flash system (stock lollipop)
fastboot flash userdata (stock lollipop)
fastboot flash cache (stock lollipop)
***Now, here it's really important not to boot into android!!!!
instead of trying to boot recovery from the fastboot menu, and just to be extra careful I did
fastboot boot TWRP2810.img (to boot directly from the img in my platform-tools folder)
Then when I was in TWRP I used the sideload option and did:
ADB sideload BETA-SuperSu-v2.39.img to load root onto my phone.
Then I restarted into Android for the first time and as soon as I got there,
I downloaded root explorer (or ES file explorer - and enable root options in the ES file explorer menu)
deleted /system/recovery-from-boot.p
delete /system/bin/install_recovery.sh and the other file in the folder which is a shortcut with the same name (probably overkill but I wasn't taking any chances).
Then reboot into bootloader - and pick recovery - and hopefully, if all went well - voila, TWRP will properly boot.
Here you can easily sideload Euphoria OS (or other) and the Bpear Gapps (or other) and away you go.
You can also flash franco kernel or whatever.
Now, your root should stick, and TWRP should stick.
Thank you GrenW for pointing out the importance of using 2.8.1.0 instead of 2.8.2.0!!!