Related
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
I recently used ROM Manager to d/l and flash CM6, no issues. But now when I use it to backup the ROM, it freezes up on a f/c screen after the backup is completed and is rebooting. Replicated the issue twice to be sure. Have to pull the battery. So much for not having to do a real nand, lol.
Still searching for the right thread for my issue.
Update: Cleared d/l cache, flashed RA 1.8 then reflashed Clockwork, all better.
ISIDHU said:
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
Click to expand...
Click to collapse
I'm not qualified to tell anyone how to do anything, but you can find directions on how to d/l and place the rom on the root of your sd card, then flash it with recovery. Search out flashing roms and I'm sure you'll get it done.
Clearing and reflashing clockwork on rom manager before you try might not do any harm as well. Never know. Read up, don't trust my word, lol.
ISIDHU said:
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
Click to expand...
Click to collapse
Have you tried other roms besides cm6? You will need the .76 hboot with that one. If you are having issues flashing any rom, then you will meed to try unlocking your nand again with toasts Eng bootloader.
Sent from my PC36100 using Tapatalk
I'm very confused as to what happened, and feel like I'm only making things worse so decided to come here. I've been rooted for about 2 months now after using Unrevoked Forever, and until last week everything was fine.
Using Rom Manager I attempted to flash Salvage Mod coming from Cyanogen 6.1.2. After wiping Data/Cache, when going to open the Zip Clockwork told me that the Rom did not exist in my SD card?
I redownloaded and tried again several times with no luck. I tried downloading other ROMS through my computer and putting them directly on my card and now I'm getting an error saying the Zip files are "(bad)"
Flashed RA Recovery through Rom Manager, the same errors, and now flashing back to Clockwork won't work. Any ideas what the problem maybe? Any solutions would be greatly appreciated
Have you tried booting to recovery directly and flashing a rom? I personally use CWM 2.6 and prefer to do all the work myself through recovery instead of hoping RomManager gets it right.
Yes I've tried booting into Recovery myself, keep getting the error that the zip. is bad
First, this is not for people whom cannot boot into the recovery at all. If your recovery does not load, or you can't get past the "white screen", there are other threads and options for you (e.g. installing the recovery though fastboot or Unrevoked).
PROBLEM: You boot into the CWM3 recovery fine. You can install compatible zips fine. However, when trying to backup, the recovery locks up at some point during the backup process.
Solutions I tried: RUU to stock. Downgrading to 2.5.0.5 and back up to 3.0.0.5. Deleting the clockworkmod folder on the sdcard. reinstalling ROM Manager. wiping cache/dalvik before backing up. None of these things worked.
Solution that seems to have worked: swap out sdcards, doing battery pulls on the phone inbetween and booting back into recovery, until you find one that allows the backup to complete. Once a backup completes fully, you will be able to swap back to your original sdcard and CWM3 should work as intended.
Specifically here's what I did:
Step 0: Flash 3.0.0.5 through ROM Manager.
Step 0.5: Turn progress bar off in ROM manager settings. I do not believe this is important. But for completeness, I did do this.
Step 1: Boot into recovery
Step 2: run backup with Transcend 8gb class 6: No luck. Battery pull, back to recovery
Step 3: Sandisk 1.0gb class unknown: no luck, battery pull, back to recovery
Step 4: Sandisk 512MB class unknown: worked twice in a row!
Step 5: Back to 8gb class 6: backup works now. Still in testing, but I believe this (obscure, weird) solution works.
I just used ROM Manager to download CM7 #40 nightly, backup and install apps through CWM3 and it worked.
Let me know if this works for you.
EDIT: Well, its not perfect, because I cannot restore a backup because I get the MD5 mismatch error. At least there's progress.
EDIT2: There are deeper problems here. Please post your success or lack thereof.
I can't believe that simply getting a backup to work once fixes the problem. I just can't see the recovery caring that it finally got one right, so now it works from now on. Recovery doesn't know what it has done in the past.
Perhaps repeatedly inserting and removing the cards, just that act itself, somehow was the fix.
not impressed with cwm 3 at all, seems real buggy. Sometimes have problems with it not doing a clean wipe/factory wipe. When I install a rom, it has some wierd stuff going on. Stuff like loading a live wallpaper from the previous roms setting. I never use it to download roms anymore. I might switch over to ra amon recovery. Or maybe back to the 2. series
it seems @koush and @dougpiston had a twatt on the twitter about cwm3 borking on the dinc. you can read the full conversation over there, but the gist is that we should enable "erase recovery" option w/in rommanager settings, reflash recovery.
I guess the recoveries are best flashed clean, rather than over one another. ???
okay. the above fix has been confirmed to work by myself and one other user on the htc incredible cm7 nightly thead, AdhvanIt.
So you want to load cwm through rom manager after you enable "erase (previous) recovery" in settings and it will be puppies and rainbows from now on.
Sent from my dinc using XDA App
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Wow I find odd that I have no problems what so ever with cwm 3
Sent from my Incredible using XDA App
tdiman said:
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Click to expand...
Click to collapse
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
tdiman said:
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
Click to expand...
Click to collapse
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Sent from my dinc using XDA App
burnmatoaka said:
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Click to expand...
Click to collapse
There were some changes pushed to CM7 a couple of nights ago for the recovery management, as well as the new ROM Manager update, that got me to try again. This time I deleted all partitions on the sdcard and repartitioned it with a large FAT32 partition and a small ext4 partition after it. I deleted my unused swap partition. ROM Manager recognizes both partitions as it is able to format them, so thats good.
I used ROM manager and installed Amon-Ra, then installed 3.0.0.5. Same hang-on-backup problem as before. Back to 2.5.0.5
erase recovery has been on the whole time...
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
hit up @clockworkmod on the twitter. I know he can be kind of a flake, but he does invite feedback when he drops an update... it was how we found out about the erase recovery thing.
you aren't having any other weirdness with other ROMs, are you? worst, worst case, your hardware is "circling the drain." sucks, but you know plenty of used dincs be hitting the market when Thunderbolt finally drops. See what Koush says though--be persistent, and it wouldn't hurt if you happen to have a RM premium license
good luck, and again, keep us posted.
sent from my dinc using xda app,
burnmatoaka said:
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
Click to expand...
Click to collapse
In the spirit of the title of this thread, I do believe I have an actual working fix over in the DEV forum. I recompiled CWM3 from source. Please see
http://forum.xda-developers.com/showthread.php?t=970032
and let me know your experiences over there, those of you that may or may not still be following this thread
@clockworkmod just dropped a new version of the inc recovery that supposed to fix "wiping /datadata issue from ROM Manager" Has this been our problem?
sent from my dinc using xda app,
I do not believe that was my original issue as the problems I had were independent of ROM manager, but 3007 fixes whatever my issue was as well as the wipe issue, which is great.
3007 also has the option to power off, thanks Koush!
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
phaze one said:
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
Click to expand...
Click to collapse
Fast scrolling is back.
zero issues with 3.0.0.8 for me. SLCD.
Sent from my ADR6300 using XDA Premium App
unable to get 3.0.0.7 to boot, though. no big thing, just looking for that mythical multi-touch fix. <sigh>
(and ZOMG my post#10 means i can talk in the grown-folkxx forums. sorry for the fluff)
Sent from my ADR6300 using XDA Premium App
Hi all. I am a noob at this rooting and flashing business, and I probably did something stupid so bear with me.
The other night I rooted my Evo with Unrevoked. That same night I flashed Baked Snack 1.9 using ROM Manager. Prior to the flash, I backed up my phone using ROM Manager. It was fast and everything but I decided I wanted Gingerbread (a la Salvagemod). I backed up my phone in a similar fashion, and flashed the ROM once using ROM Manager. When rebooting, my phone became caught in a boot loop. After searching through Google for a few minutes, I learned that I simply needed to clear my cache and my dalvik cache. After clearing cache, flashing, and attempting to boot several times (all in clockworkmod... or recovery... or whatever it is called (yeah i suck)...or whichever one is orange!), I gave up and decided to restore to my second ROM Manager backup - that of Baked Snack. Error! "No files found!" I tried my previous backup. Same message.
Looking back on that, I chose "install zip from sdcard" instead of "nandroid". That was a fail.
So I decided to re-use unrevoked. Everything went fine on the PC end, but the only thing that changed on my phone, is that when it boots, it gets stuck on "htc evo" in the white screen. That and clockworkmod is now teal. I disovered the nandroid option on the recovery menu. I navigate to that, then to restore, then to my Baked Snack backup. This gave me the message "Error while flashing boot image". I tried it one more time, except instead of picking recover, I accidentally picked backup (stupid stupid careless, i know). It failed and said "Can't mount /data/!".
Then I decided to go onto xda-developers and here I am now. If you are through facepalming, I would appreciate it if anybody could help me recover my data. I believe I can still flash a completely new ROM (But what do I know? I haven't proven to be the smartest Android guy), and I don't know about you guys, but I like keeping my data.
So, uh, yeah. That's that. Help please.
I'm sorry to hear you are having issues with your phone. It looks like you still have a nandroid backup, unless you formated your SDcard. Clear data, dalvik cache, and cache then run do a restore. When using clockworks recovery clear out the data, dalvik, and cache three times.
Hope this helps.
I have performed all three wipes. After that it reads
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Same as before... Any thoughts? Could the boot.img file be corrupted?
***bump***
Edit: Ive read around some more and heard 2 things. 1) If I just try recovering over and over again, nandroid will eventually give in. 2) the battery has to be 70% or higher or nandroid will just keep giving error messages.
Either way, I'll juice up my battery and report back later.
Have you tried to just do a wipe and reflash the ROM.
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
bccbryan said:
Have you tried to just do a wipe and reflash the ROM.
Click to expand...
Click to collapse
Yes. I tried it again just now because I was feeling lucky. Salvage Mod went smoothly, except it got stuck on the white htc screen when I rebooted. Baked Snack gave me an error message:
Code:
E:Can't open /sdcard/download/BakedSnack1.9.evo.zip
(bad)
Installation aborted
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
I'll try that tomorrow morning. Right now I'm gonna get some sleep before I do any more damage to my phone lol. Expect more questions from me about WiMAX and what to do with that .img file (if anything at all).
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
I believe if you don't update your radio and are running a certain kernel you will get a bootloop, but don't quote me on that.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
bccbryan said:
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
Click to expand...
Click to collapse
I'm 95% sure that I do, I got my EVO in December.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
Click to expand...
Click to collapse
It says S-OFF, so that's good news.
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
When I try to recover, it givese me an error saying that the nandroid directory could not be found. I have my backups in a folder called /sdcard/clockworkmod/backup/NameOfTheRecoveryFolder/. Should I just copy the files in the backup folder to a folder on the root of the card called "nandroid"?
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
Click to expand...
Click to collapse
Yep...just need the PC36IMG.zip and boot to the bootloader.
Since you got your phone last December I think you need to run a rom that is based off the latest code. If you are running htc sense it should be based off 3.70.651.1. For ASOP run the lastest ones.
Here is a nice wiki of the ROMs for the EVO http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
bccbryan said:
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
Click to expand...
Click to collapse
This would be the file called "nandroid.md5"? I'm confused.
OK so I boot into recovery, go to Nandroid restore > BackupName
I am presented with a list of options:
boot.img
recovery.img
wimax.HT0CRHL08393.img
system.img
data.img
cache.img
nandroid.md5
Do I just run each of these individually or am I doin it wrong?
Don't do a nandroid restore. Flash a ROM onto your phone.Fresh EVO or Myn’s Warm TwoPointTwo are good ones to try.
Works great! I lost all my data but I'd rather have a wiped phone than a dead one!
Thanks!
When you used Unrevoked to root your phone it also downloaded Clockwork Mod recovery v. 2.6.0.1. This is what you probably used to do your original backup right after you rooted your phone (http://forum.xda-developers.com/showthread.php?t=895208). You need to go back to this version so you can restore any backups you may have made right after you rooted your phone. Here is an article by Koush explaining why you may be having problems. At the bottom he has v.2.6.0.1. Install it on your phone and then proceed restoring your backup.
Also, I'm going to suggest to you that you read the articles below to get you familiar with rooting, and then I suggest you read some more on these and other forums. Learn the rooting vocabulary and processes involved (rooting, nandroid backup, recoveries, flashing ROMs, kernels, etc.). Also, try and read up on problems people have rooting, flashing ROMs, and troubleshooting should something go wrong. You want to be able to get yourself out of a mess should problems arise. Most importantly, you want to know what you're doing so you don't brick your phone.
http://forum.xda-developers.com/showthread.php?t=865204
http://forum.xda-developers.com/showthread.php?t=790427
http://forum.xda-developers.com/showthread.php?t=881747
http://htcevorooting.x10.mx/wiki/ind...itle=Main_Page
http://androidforums.com/evo-4g-all-...g-dummies.html
I've noticed, that once you flash a rom. It loads folders onto your sd root folder. which are usually
battery history
rosie_scroll
.android_secure
LOST.DIR
media
etc..
*************
I flashed billions of roms over and over, but after my most recent attempt to flash a new rom. it says load complete. but nothing is loaded onto the sd card. (i mean nothing)
I've wiped, re wiped, super wiped, partitioned, formatted sd everything. still, the roms load jack onto my sd card.
1). Is my phone hopeless?
2). Should i just turn s-on back on and turn it in? Or it there a trick around this?
redm1st said:
I've noticed, that once you flash a rom. It loads folders onto your sd root folder. which are usually
battery history
rosie_scroll
.android_secure
LOST.DIR
media
etc..
*************
I flashed billions of roms over and over, but after my most recent attempt to flash a new rom. it says load complete. but nothing is loaded onto the sd card. (i mean nothing)
I've wiped, re wiped, super wiped, partitioned, formatted sd everything. still, the roms load jack onto my sd card.
1). Is my phone hopeless?
2). Should i just turn s-on back on and turn it in? Or it there a trick around this?
Click to expand...
Click to collapse
Did you try using a different recovery? Not sure which one you are using at the moment. Amon ra, CWM or TeamWin not sure if it will sole your trouble but its worth to try. Did you try flashing an AOSP? Or Sense? is this happening with both types?
DrDr3z85 said:
Did you try using a different recovery? Not sure which one you are using at the moment. Amon ra, CWM or TeamWin not sure if it will sole your trouble but its worth to try. Did you try flashing an AOSP? Or Sense? is this happening with both types?
Click to expand...
Click to collapse
I flashed a sense rom, only flash sense roms.. Ive first noticed my phone not booting up after i flashed "r3charged_FINAL" rom. I didnt pay it to much attention. So then i flashed "kings bliss beta3" it worked fine, flashed "r3charged" again, and the same crap.
Flashed "Noctunral rom" it worked, phone died, later on got home, partitioned my sd. format all, wiped, super wiped, flashed those custom flashes "FR_Boot/Recovery_CustomMTD" the rom "r3charged"
Still nothing loading on the card, I checked, i even let it reboot in hopes it might load, but nope.
And yes, I went through all three recoveries in hopes of that might make a difference.
cant get S-On to flash. It keeps showing
unrEV0ked forever S-ON patch v1.3
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in/sdcard/unrevoked-forever-son.zip
(Status 42)
****************************
"S-OFF LOG"
unrEVOked forever S-ON patch v1.3
Verifying system type...
.
.
Got device:
@PID: 73,"SUPERSONIC_C"
Got radio version:
2.15.00.05.02
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
redm1st said:
I flashed a sense rom, only flash sense roms.. Ive first noticed my phone not booting up after i flashed "r3charged_FINAL" rom. I didnt pay it to much attention. So then i flashed "kings bliss beta3" it worked fine, flashed "r3charged" again, and the same crap.
Flashed "Noctunral rom" it worked, phone died, later on got home, partitioned my sd. format all, wiped, super wiped, flashed those custom flashes "FR_Boot/Recovery_CustomMTD" the rom "r3charged"
Still nothing loading on the card, I checked, i even let it reboot in hopes it might load, but nope.
And yes, I went through all three recoveries in hopes of that might make a difference.
Click to expand...
Click to collapse
Custom MTD is your problem I went through the same thing yesterday.
Flash Team win recovery from bootloader and then flash any sense room do not flash the MTD recovery zip.
Anything beyond that would be above my paygrade.
Good luck
DrDr3z85 said:
Custom MTD is your problem I went through the same thing yesterday.
Flash Team win recovery from bootloader and then flash any sense room do not flash the MTD recovery zip.
Anything beyond that would be above my paygrade.
Good luck
Click to expand...
Click to collapse
Tried that, I'll give it another whirl. pulled out all the stops last night. hopefully the phone just needed a nap and it's good to go today. LOL!!
!!Yells!! "S. O. B"
It's working again. And that move, was tried the day before. Guess it just needed a day break of all the flashing.
DrDr3z85 = 20th. thanks!