Hi
Was running CM10 nightly from 12 Dec. Bluetooth froze while in car. I rebooted phone. It never came back up after booting, just looping Cyanogenmod logo.
Went into recovery, did a Nandroid, restored my previous backup from the 11th. Still looping Cyanogenmod logo.
Got home. Reflashed stock kernel. Went into recovery and flashed CM10 stable after wiping. Comes up with HTC logo, then black.
Tried to go back into recovery. Comes up with HTC logo, then goes black.
Now it lets me into fastboot, and into the bootloader menu, but recovery does not work. Neither does booting normally. Tried reflashing kernel AND recovery (stable TWRP). It just keeps looping the HTC logo.
HBOOT is 1.14.
Help, please. I'm going to destroy this piece of ****.
If all else fails, run a RUU and skip the thread.
yea, just ruu. i ruu'd a few days ago for kicks.
some car chargers and even wall chargers can make ur phone go wonky, my old moto backflip would randomly press buttons if i used a non-motorola charger.
on a side note, i never used the word "wonky" until this forum.
try running "fastboot erase cache"
also try a clean install instead of restoring nandroid, im assuming your also fastbooting the boot.img from all your nandroid backups. if not they probably wont boot.
strange...
I would say ruu and retry as well.. Sometimes accessories can make a phone go haywire.. Besides the phone is not a piece of crap.Roms can never give you complete stability while stock unrooted can.
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I always export my contact list to /sdcard if a change is made and then backup to google just in case
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I'd suggest keeping a boot.IMG and a stock ROM on the SD card along with adb drivers so you can fix it with a computer without downloading anything.
Sent from my Nexus 4 using xda premium
Related
I've tried more than twice now, and I'm sure it's something simple, but I can't recover my backup. Last night for example, wanted to try another rom, a 2.3.4, I was quite happy with my mosaic setup, as usual, and I was running xcal's 2.0 kernel without issue so I backed up through cwm 3. Flash got me into a bootloop so I tried to recover the nandroid but it wasn't the right one. I chose the right date but the b/u was the rom that failed, the bootup screen. So I had to start from scratch to get the setup I liked. Of course when I tried to flash the new rom there were different kernels etc. But that shouldn't matter should it. What am I doing wrong? Thanks ahead of time.
Sent from the frozen tundra known as Canada.
Do you're trying to restore a 2.3.3 backup (Mosaic) to a 2.3.4 rom?
*phone sig* If you're not on Gingerbread you should be flogged! *
Uh, no. you misunderstood.
Sent from the frozen tundra known as Canada.
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
studacris said:
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
Click to expand...
Click to collapse
Thanks studacris, yeah, tried that and got an error message and couldn't restore. Sorry I didn't take the message down, I'll try again if it happens again, thanks.
Sent from the frozen tundra known as Canada.
Hey,
So I was a victim of not enough reading and doing to much at one.
I had a rooted stock GB ROM on my D2G and through easy enough, BootStrap, CWM via Rom Manager and flash CM 7.1. All should be good.
WRONG
I got hung up at the red M logo and try various things to revert to stock b/c there was no way I was getting into the CWM recovery console again.
After failing at every corner a random and 10,000th battery pull I ended up in CWM.
Since the one thing I did right was a nandroid backup I was restored it and the phone booted. I then shut down, dropped in SIM (rogers) and booted back up.
Now everytime I reboot it takes me to CWM. Forcing me to hit reboot system now otherwise it sits in recovery.
Any way to have it not boot into recovery? Just boot normal?
Thanks.
First, if you are on Rogers in Canada - do not bother trying CM7 - doesn't work properly on GSM. Stock firmware will be much more useful.
Second - There are two CM7's (if you are determined to try it) - one is Froyo base (the one found on CyanogenMod site) and the other one is GB base. It seems you flashed the Froyo based one on top of Gingerbread thus you ended up stuck on red M logo. To fix the problem - you have to either try flashing GB base CM7 from CWM or (better) SBF and start over. Again - if you want Froyo based CM - use the 2.4.29/2.4.33 SBF. If you want to try the Gingerbread based one (check rootzwiki for more info), flash the GB SBF that was recently made available or flash 2.4.29/330 and OTA to 4.5.608. Root, CWM and so and so. But pick your CM7 package carefully!
But if you are not on CDMA - you better don't waste your time with CM7.
Thanks for the reply. The phone boots fine now.
One question tho.
I have some how lost the Accounts and Sync Option.
If I do a factory reset (from phone settings not recovery mode)will I loose root and will I loose the Gingerbread OTA update that was done on the phone before I got it?
Or do you know how to recover something like Accounts and Sync?
I am going to be sticking with the Stock ROM
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
leobg said:
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks I discovered that I had deleted the "Setup.apk" without backing up.
Retrieved that app from another member and all is well.
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
So this has happened to my now twice when trying to revert back to stock...
Starting with a bone stock N5, I unlock the bootloader (I guess technically it was already unlocked the second time I had this problem), then push TWRP over via fastboot. At this point, I do a Nandroid of "stock" and save it. Then I flash PACman ROM and run with that for a bit, one time with the Elemental kernel, the other time with whatever kernel PAC comes with.
So in an attempt to go back to stock due to some LTE issues with PAC, I boot into TWRP, select restore, then choose my original "stock" nandroid. It restores fine as well as I can tell with TWRP, but when I go to boot it just gets stuck on the Google color splash screen (the dots coming together).
Any thoughts on what I'm doing wrong here. I don't have any problem loading any of my PAC nandroids at this point to get back up and running, but I'd rather not have to go to my computer every time to push a factory image.
Make sure you have a good, known working nandroid....then try wiping first. System, data and the caches. NOT internal SD obviously. Then restore. If you have issues still, restore your known good nandroid.
That's worked for me in the past with restore issues.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
Make sure you have a good, known working nandroid....then try wiping first. System, data and the caches. NOT internal SD obviously. Then restore. If you have issues still, restore your known good nandroid.
That's worked for me in the past with restore issues.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
How do I know if it's a good nandroid until I go to flash it and it doesn't work? Tried it again tonight after making sure to wipe everything in TWRP, but it got stuck on the colored dots splash screen again for a good 20+ minutes until I nandroid'd back to PAC. Do I need to be on a certain runtime?
Make sure you've wiped everything in recovery (data/cache/dalvic)... Then format system.
Now try restoring the stock nandrioid backup and see if it works..
There's no way of knowing whether the backup is good or not. If it had some md5 issues, it would have been displayed on the screen.
Sent from my Nexus 5 using Tapatalk
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Did you try wiping everything before restoring your backup?
Sent from my HTC6525LVW using Tapatalk
I had the same, exact issue. Absolutely no reason why it shouldn't have worked. I made sure the Nandroid copied the necessary partitions/directories and also performed a full wipe before restoring the backup. Same issue. I was on TWRP and I'm pretty sure there is some issue with TWRP.
I haven't attempted to make a backup or restore a Nandroid since, so I don't know whether its still an issue.
ChuckFinley1992 said:
Hi all,
Yesterday I was flashing a theme for the Vemon ROM on the M8. I ended up deciding I didn't like it, so I tried to go back and flash a backup I had made. However, once I flashed the backup, the device wouldn't boot up past the HTC One white screen (it will go past the HTC logo by itself, but then the One appears on the screen and stops there). I have no idea why, as I have made backups before and have had no issues. On the default backup name, it does say KOH Release keys. I don't know if that means anything. I was able to get to recovery and flash the base Venom ROM, but I'd like to know why my backups are not playing nice.
Any and all help regarding this would be appreciated.
Click to expand...
Click to collapse
I tried wiping everything yes. I did a factory reset data wipe first, and then tried installing the backup. I don't know why it did not work. I was eventually able to get out of the boot screen with an volume up and power key combination, but it was more frustrating not knowing why this issue was happening. If anyone knows why this is occurring, I would gladly like to know.