So I tried to flash Magnolia X 1.0 coming from MIUI. After I wiped from MIUI and tried to install Magnolia I got an error. No big deal right? So I figured I would reboot recovery ( clockwork mod ) and try again, if it didn't work I could restore MIUI. When I hit reboot recovery I got stuck in a bootloop, from white htc screen to off. It just looks like it is trying to get to recovery but it is not loading it for some reason. So I decided to boot it into hboot and reflash the recovery, or possibly flash twrp. Now my problem is that the computer is not recognizing the phone, so none of my fastboot or adb commands do anything I just get <waiting for device>. Any ideas?
So right after I made the post I was able to get the drivers to reinstall and was able to re flash the recovery. Tried both CWM and TWRP and neither will boot. With TWRP I can get to the recovery splash screen but then it just goes black. Downloading the RUU now and I am going to try to flash that through the bootloader. Other than that I have no othe ideas...anyone else have any?
Got it...had to relock bootloader and run ruu then extract the stock recovery and flash it. Rebooted into recovery let it sit, then it rebooted back to the bootloader. Re-unlocked bootloader then flashed TWRP and it worked fine. Back up and running again.
So. I'm sorry to say, but this phone has given the biggest headache. Here's the background:
I really only use this phone for entertainment and stuff. BUT I decided to root and unlock the bootloader, somehow or another the phone apparently lost root a few times (According to some users here) but never lost SuperUser or anything. I've never been able to flash a rom on this thing. Then a few weeks ago the phone just encountered an error of some sort and would only get to the ICS boot animation and loop over and over. I just gave up on it. Then one day I decided to play with it. I got it into fastboot and then into recovery, (Not CWM Recovery) and was able to get it all set up again. So I figured I'd give it one more shot. I downloaded CWM and downloaded recovery, and a custom rom. tried to flash through fastboot>recovery but it's still the stock recovery, not CWM recovery. So I factory resetted it etc and started from scratch. Now if I download CWM it WILL NOT download recovery. It gets about 99% of the way and tells me: "An error occurred while attempting to run privileged commands!" If I download it from a link I can't open the file....... Someone help I just want a good JellyBean Rom. :crying:
Edit: I've Googled as much as I could stand and still haven't come across anything entirely helpful. Please explain so I could understand. Pictures help if needed lol
Anyone?
You can't use clockworkmod app to flash recovery without root.
Get the fastboot image of cwm recovery ( not the app). Or twrp. Flash it with fastboot.
Boot directly into it and flash what you want. If you boot up a stock os it overwrites the custom recovery on boot.
clockworkmod app sucks IMHO and should never be used for anything period. Not fond of the recovery itself either.
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.
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
It's been quite a while since I messed with ROMs on my phone, so I thought I might look into updating it. I am currently running TWRP 2.8.5. Using the app from the app store, I tried to update it to the current version, but it failed. From there, I restarted my phone, and it took me into recovery. From here, I have been unable to escape. I keep rebooting from within TWRP, and it just returns me right back to TWRP. I'm sure it's something that I'm overlooking. Can someone help me figure out what I'm doing wrong? I am rooted, with S off.
Thanks!!
Your recovery may have been flashed to the boot partition. This was a problem with the twrp app a long while back which I assumed had been fixed but perhaps not. Download the latest twrp (2.8.5 is kinda old at this point) and flash it from a computer via fastboot:
Fastboot flash recovery [nameofrecovery].img
Boot into your new recovery, check the version number to make sure it's the new properly flashed recovery, and either restore a nandroid or flash a new Rom.