By no means am I new to this so I'm at a loss. Any help would be greatly appreciated. I've flashed pretty much everything on my hero and now on the evo but I always go back to CM. About a week ago I wanted to flash the latest CM nightly so I booted into recovery to make a nandroid. It was taking way too long (almost 20 minutes) so I pulled the battery, rebooted to recovery, plugged in the usb cable, and mounted the phone to find out I had a 3.8gb backup. I deleted it, unmounted, screamed, wiped everything, and tried to flash the nightly. Nothing but splash screen. Booted into recovery, wiped all, flashed MikG. Good to go. Recovery, wipe, nightly. Nothing. Recovery, wipe, Evo Classic. Good to go. Anything CM. Nothing. I tried every combination of wiping, powering down, rebooting to recovery, flashing different recoveries (started with RA style, went to CWM, RA 2.3), tried flashing with the Mason kernel. I had to nandroid back to an older unofficial CM7 nightly backup. This has never happened to me before. I can flash Sense but I can't flash CM to save my life. I'm a little worried with Deck Reloaded coming out that it'll be a no go for me. Haven't tried Deck 1.3d yet so not sure if it's CM specific or AOSP ROMs. Anyone have any suggestions? Thanks.
Sent from my PC36100 using xda premium
I reached out to ropodope and he hit it on the head. He told me that I had corrupted one of my main partitions. His solution was to RUU back to unrooted stock to repartition and format every one of the partitions like when I first got the phone. It did the trick. It wasn't bad because I was S-OFF. I flashed an old RUU PC36IMG from HBOOT, booted and updated everything while stock, flashed Smelkus 4.2 PC36IMG from HBOOT, nandroided, wiped, flashed CM, and I was good to go again. No need to re-root thanks to S-OFF. I wanted to share this in case anyone else runs into this problem.
Sent from my PC36100 using xda premium
Related
i just did a nand backup turned off phone and when i turned back on its stuck on white htc evo screen. havent flashed any roms.did a full wipe tried to restore and the same thing happened
defjef123 said:
i just did a nand backup turned off phone and when i turned back on its stuck on white htc evo screen. havent flashed any roms.did a full wipe tried to restore and the same thing happened
Click to expand...
Click to collapse
Need more info like what recovery you used, new or old phone, your rom, kernel etc..
Sent from my PC36100 using XDA App
i have aman ra recovery. just got the phone three days ago and rooted it the next day with the unrevoked beta with no problems. i hadnt done any thing else to it, was doing a backup to check out some custom roms. its software 3.70.651.1 2.02 hboot.
this just happened with me.
running RA, Myn's RLS4, netarchy 4.3, hboot .97
tried flashing a fresh copy of RA...but its not working, either, now. it gets stuck on the white screen when trying to boot into recovery from hboot.
i ended up flashing sprintlovers and that worked for me. id still like to know what went wrong though. glad i had just got the phone so i didnt lose too much stuff. had to put all my contacts back on and reinstall a couple of apps
I had the same problem on my phone, but I didn't do unrevok, I did a full wipe which basically gave me a rooted PC36img, and when I reboot in AmonRA recovery I can reflash that PC36IMG automatically and send me back to stock, then you basically have to reroot, wipe data and reflash the rom..
Ok so most likely I did something wrong, and not Clockwork but I really have no clue how this happened.
Started the day out on my daily driver, CM7 (#39 atm) but got the urge to flash so I figured I'd check out Evervolv. Pretty neat btw, nice work. Anyway, made a nandroid then flashed Evervolv and did some apps, setup etc, flashed an Ubuntu font pack I found in a WarmZ thread which worked fined then decided to go back to CM7 for the time being.
Restored my nandroid and I'm back in CM7, decide I miss the Ubuntu font so I flash that and get bootloops. No problem, restore my nandroid and all is well. Knowing just enough to get myself in trouble I decide to extract the fonts from the Ubuntu font pack, delete CM7 fonts located in /system/fonts, then copy the extracted Ubuntu ones to that location. Had to reboot for some reason and I'm getting bootloops again.
Here's the fun part...restored the same nandroid of #39 as before but now I'm getting bootloops on that. Tried yesterdays #39 nandroid, bootloops. Tried the Evervolv nandroid, bootloops. Every backup I had bootlooped. Btw before these restores I was formatting cache, dalvik, wipe data/factory reset, then went into mounts and wiped boot, system, data, cache. I'm paranoid I guess.
Thinking maybe the sd card was bad I ran a clean install of #39 from another sdcard without issue. Then I got the idea to put my normal sdcard back in and restore my once-was-but-now isn't working nandroid of #39 then flash #39 zip on top of it, and it worked. No more bootloop. Not only that, but now all my other backups are fine again.
So anyone have a clue what happened and how I can avoid it? My guess is I borked something messing with the system/fonts and for some reason the wipes weren't clearing it but like I said I know just enough to be dangerous. Is my wiping ritual wrong? Did I miss something? Any thoughts or ideas?
What version of clockwork were you using out of curiosity?
Sent from my ADR6300 using XDA App
3.0.0.8
HTC Incredible - CM7 - Incredikernel 2.6.37.4 (testA)
I know one of the 3.0 recoveries is known for not wiping completely. That's the only thing I can think of?
Sent from my ADR6300 using XDA App
3.0.0.8 is good far as I know. I suppose it couldn't hurt to downgrade and reflash to be sure (erase recovery checked of course)
HTC Incredible AMOLED - CM7 #39 - Incredikernel 2.6.37.6 (testA)
I think 3.0.0.7 was the one with the problem, I can't remember though. I personally use 2.5.1.2. Not really sure what else would cause that problem though, that's weird.
I was having troubles with 3.0.0.8 and was advised to switch to 3.0.0.7 and have had no problems wiping. I would try that if you think wiping might be the problem.
I'm having an issue with ROM Manager. I've contacted Koush and RA and we're are in the midst of working it out. I am curious if any one else has had the same, or similar issues.
I run CM7031 on my Evo. I recently flashed SavagedZen202 kernel from ROM Manager. I used it for about a week and I wanted to check out a taimat kernel. I backedup with CWM and tried to flash to RA to make a nandroid. ROM Manager said the RA was flashed, but when I booted into recovery I was still in CWM. I ttried everything, clearing cash, erasing recovery, un/re installing RM, flashing earlier versions of CWM. Nothing worked. So, without making a nandroid I flashed tiamat405. I figured that would clear up the issue, but I was wrong. Same issue. Finally I flashed a previous backup to CM with its original kernel and everything was fine. I could flash back and forth between CWM and RA. Thinking everything was alright and that I had done something wrong in my other backups, I flashed tiamat again. Same issue, I can not flash between recoveries.
If any one has similar issues or possible causes I'd appreciate the input.
Thanks
Kinda confused...so what actually is the problem?
Had the exact problem. Stuck on clockworkmod no matter what I do. To top it off clockworkmod didn't even work correctly, couldn't flash correctly. I tried to restore a Rom but it ended up being the same Rom, so it didn't actually restore. I ended up unrooting the phone and flash the Sprint 3.7 ruu to go back stock. Then I rooted again and RA/clockworkmod switching started working again.
I guess the problem is one of functionality, I can't flash back and forth between CWM and RA. Its not a big deal because I'm currently on RA and I like RA. But, I have to wonder if RM isn't working correctly are my nandroids backing up correctly? I could go back to CM7 kernel, but I wanted to push my OC a bit more and I wanted to use _viperboy_ scrip for uv and its built for Evo on tiamat. At least that is my understanding. So, what's the problem? A malfunctioning app, I guess! Or maybe an incompatibility between an app and a kernel?!?! And maybe something to do with the ROM? I don't know! That's why I asked.
I had a problem early on when I uped from CM6 to CM7 with Titanium backup, but I worked that out. I've been running CM7 for a while now without issue, until this.
you should just reboot in to recovery and flash your kernels from there instead of using RM its a much better way...
Yeah, I flashed SZ from RM just to kind of see how it worked. But I flashed the tiamat zip from recovery.
So I have my EVO rooted w/ unrevoked since last years launch. I have run Fresh ROM's up until about 6mon ago when I installed CM7 RC1, then 7.0, then 7.0.2. Last night I decided I wanted to try Synergy or Fresh again, so I updated Clockwork backed up the phone, then installed Synergy.
Everything went fine, wiped Cache/User/Dalvik, installed then rebooted. I was stuck at the Unrevoked splash screen, and about every 20seconds It would reboot and continue the cycle. I battery pulled went to Clockwork and Tried my Fresh ROM, did the same thing. Ok, So i said screw it, im gonna restore it. So I navigate Clockwork to the location i backed up to, then restore.
After a reboot, the unrevoked screen would just stay frozen forever, no ROM booting. So I still had my CM7.0.2 on the card that i flashed 5 months ago, and all be damned it worked back up and running in minutes, whew.
So this morning I am back at it, trying to install fresh again, and im going back throught the same unrevoked spalsh screen boot loop. Any help on figuring out what is wrong?
mrsmegz said:
So I have my EVO rooted w/ unrevoked since last years launch. I have run Fresh ROM's up until about 6mon ago when I installed CM7 RC1, then 7.0, then 7.0.2. Last night I decided I wanted to try Synergy or Fresh again, so I updated Clockwork backed up the phone, then installed Synergy.
Everything went fine, wiped Cache/User/Dalvik, installed then rebooted. I was stuck at the Unrevoked splash screen, and about every 20seconds It would reboot and continue the cycle. I battery pulled went to Clockwork and Tried my Fresh ROM, did the same thing. Ok, So i said screw it, im gonna restore it. So I navigate Clockwork to the location i backed up to, then restore.
After a reboot, the unrevoked screen would just stay frozen forever, no ROM booting. So I still had my CM7.0.2 on the card that i flashed 5 months ago, and all be damned it worked back up and running in minutes, whew.
So this morning I am back at it, trying to install fresh again, and im going back throught the same unrevoked spalsh screen boot loop. Any help on figuring out what is wrong?
Click to expand...
Click to collapse
You cannot install synergy with clockworkmod. It must be installed with amon ra. This is stated in the original post of the synergy thread.
Sent from my PC36100 using Tapatalk
Ok I guess I didnt see that part about Synergy. Howerver I just tried to install the latest Fresh rom, and it was doing the same thing (rebooting at the Unrevoked Screen).
However I was able to flash to the latest Cyanogen 7.0.3 Stable for EVO, so until I find a solution, I guess I am stuck w/ that in the meantime.
mrsmegz said:
Ok I guess I didnt see that part about Synergy. Howerver I just tried to install the latest Fresh rom, and it was doing the same thing (rebooting at the Unrevoked Screen).
However I was able to flash to the latest Cyanogen 7.0.3 Stable for EVO, so until I find a solution, I guess I am stuck w/ that in the meantime.
Click to expand...
Click to collapse
I would still try flashing Ra Recovery and seeing if you can flash Fresh ROM.
Also it could be ur SD card. Alot of times its not partitioned right or what not. I know cm7 leaves SD card alone for most part.
free the dirk
The solution is to get Amon Ra, so you can wipe properly and partition your SD card properly
might wanna wipe boot as well...usually fixes issues in such cases.
theidlemonk said:
might wanna wipe boot as well...usually fixes issues in such cases.
Click to expand...
Click to collapse
Last I used CWM you could not wipe boot without a custom script (ie. Calkulins format all, or VR_Superwipe)
Khilbron said:
Last I used CWM you could not wipe boot without a custom script (ie. Calkulins format all, or VR_Superwipe)
Click to expand...
Click to collapse
Amon RA recovery has that option under the wipe menu.
But then Calkulins format all or VR_Superwipe are good too. Gets the job done.
This is all very helpfull, I am going to try some of that in the next few days. I really didn't have any idea that SD partitions can effect the boot of a phone, Ill read about that as well.
Today I managed to get the Latest Stable CM 7.0.3 on my phone, but the experimental 7.1 wouldn't load, so I am going to stick with that. One of those things when you feel like you have read everything before you start upgrading, then you miss something and all goes to hell. Thanks for the help everybody.
theidlemonk said:
Amon RA recovery has that option under the wipe menu.
But then Calkulins format all or VR_Superwipe are good too. Gets the job done.
Click to expand...
Click to collapse
Yes I know this. I use ra recovery. However the OP uses CWM which is why I assumed you were instructing her to do this with clockwork.
Sent from my PC36100 using Tapatalk
So I installed that Beats Audio for all Gingerbread phones yesterday night.
Flashed fine and the phone worked fine.
Today I wanted to update to the newest Nightly for CM7 and when I went went into the bootloader and chose Recovery the phone restarted back to the Bootloader screen.
Is there any fix for this?
Thanks
Psywar28 said:
So I installed that Beats Audio for all Gingerbread phones yesterday night.
Flashed fine and the phone worked fine.
Today I wanted to update to the newest Nightly for CM7 and when I went went into the bootloader and chose Recovery the phone restarted back to the Bootloader screen.
Is there any fix for this?
Thanks
Click to expand...
Click to collapse
why do you boot into the bootloader first?no multi-boot option?Anyway,it sounds like the CM7 rom you flashed is corrupted,It sounds like you might have to format your sd card and start over,or reload a new recovery from the bootloader.If you had a multi-boot option you might be able to solve this without formatting.
hey,
try doing a factory reset getting rid of any apps you currently have and try using the advanced power menu to boot into recovery if that doesnt work, try re flashing a different recovery. let us know how it goes from there!
Good luck,
Stevo
Just try reflashing the recovery, should solve the problem.
can't flash Elite Series IV Resurrected
maybe a silly question but i have always used cwm to flash all my rom. but last i tried to flash Elite Series IV Resurrected rom but got caught in boot loop with ACS boot screen can this be flash with cwm or do i need to flash to amon ra
input would be greatly appreacited
Blackashell said:
maybe a silly question but i have always used cwm to flash all my rom. but last i tried to flash Elite Series IV Resurrected rom but got caught in boot loop with ACS boot screen can this be flash with cwm or do i need to flash to amon ra
input would be greatly appreacited
Click to expand...
Click to collapse
CWM is junk, for one. Switch to Amon Ra
^^^^^^^^^^^^^^^^^^^^^°^
What he said. Man, I just finished typing the same advice in a different thread. Lol.
Seems people coming from Samsung devices in particular tend to start with CWM. I'm not speculating on the OP here, just a trend I've noticed as of late.
Sent from my PC36100 using xda premium
I used CWM for my initial nandroid, after first rooting with Unrevoked, then flashed Amon. Anyway, as said try re-flashing recovery. Also, FYI, that "all Gingerbread Roms" was just for one device, the article was slightly inaccurate. I flashed the Beats audio zip myself but upon investigating in Roote Explorer saw that none of the files had actually written.
CWM is a great and sometimes better choice for a lot of phones, just not the Evo
Sent from my PC36100 using Tapatalk
I have not been able to get it to work yet.
I have been thinking about Wiping everything and starting from scratch again, but I am afraid that if I wipe I wont be able to get into the recovery and get screwed and not be able to re-flash C-Mod 7.
I will attach a video of wtf my phone is doing.
http://youtu.be/IJ6Scw-SG2w
Got it working!