I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51
deathvalley1981 said:
I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51
Click to expand...
Click to collapse
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
How do I check the md5? I'm not sure what that is... Thank you for your help, I'm going through this process right now.
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.
nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again
deathvalley1981 said:
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again
Click to expand...
Click to collapse
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?
nschiwy said:
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?
Click to expand...
Click to collapse
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.
deathvalley1981 said:
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.
Click to expand...
Click to collapse
yeah, try one of those.
nschiwy said:
yeah, try one of those.
Click to expand...
Click to collapse
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!
deathvalley1981 said:
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!
Click to expand...
Click to collapse
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though
nschiwy said:
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though
Click to expand...
Click to collapse
I'm actually going to try yours, but can you re-educate me on flashing gapps?
deathvalley1981 said:
I'm actually going to try yours, but can you re-educate me on flashing gapps?
Click to expand...
Click to collapse
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.
nschiwy said:
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.
Click to expand...
Click to collapse
thank you so much for all your help and I like your rom already! It's super quick.
deathvalley1981 said:
thank you so much for all your help and I like your rom already! It's super quick.
Click to expand...
Click to collapse
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
deathvalley1981 said:
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.
Click to expand...
Click to collapse
Now see if you can access recovery. If you can wipe everything in the mounts and storage menu except emmc and sdcard, and then restore a known good backup or flash a rom fresh.
deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
No, I've not heard this before. Let me test on my phone and I will get back to you.
deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.
cmlusco said:
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.
Click to expand...
Click to collapse
do you think his file system got borked somehow?
nschiwy said:
do you think his file system got borked somehow?
Click to expand...
Click to collapse
Could be, have to see what he reports back.
Related
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.
So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.
MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828
_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.
OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha
Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds
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 get the error:Can't open /sdcard/.....zip(bad)
Any other solutions besides the one in the older thread. It's directions were not clear at all.
It's a bad dowload.....try redownloading....happens to me all the time when DL'in from my PC....not sure what the other responses to u were.....but that's what's happeneing
Sent from my PC36100 using XDA Premium App
Reverepats...I downloaded two different MikG Roms and neither worked, I also tried Kings Alliance it had the same error. When I ran the Rom I was running before, SalvageRom, it worked. I see you are running MikG, where did u download from?
I'm assuming that you've tried reflashing recovery? Or possibly switching recoveries?
(from... Evo/MIUI/Tapatalk)
The file corrupted, and you just need to download it again.
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
corey140 said:
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
Click to expand...
Click to collapse
2.3 is the latest version. If you choose to reflash just do it via PC36IMG; though I'm positive its just a bad download.
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
corey140 said:
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
Click to expand...
Click to collapse
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
teh roxxorz said:
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
Click to expand...
Click to collapse
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
corey140 said:
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
Click to expand...
Click to collapse
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
teh roxxorz said:
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
Click to expand...
Click to collapse
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
corey140 said:
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
Click to expand...
Click to collapse
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
corey140 said:
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
Click to expand...
Click to collapse
Yea, unfortunately, that backup is corrupted, and you'll have to scrap it. Hopefully you have another one, or in a position to create a newer one.
Can I just Reboot and go back to what I was using?
corey140 said:
Can I just Reboot and go back to what I was using?
Click to expand...
Click to collapse
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
teh roxxorz said:
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
Click to expand...
Click to collapse
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
corey140 said:
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
Click to expand...
Click to collapse
Well I'm certain it is.
IF all else fails, go to the link on your evo, then download the zip from your phone, make your backup, do a full wipe, then locate it in the folder when you flash.
I'm almost certain it's an issue with your SD card. I've seen it before, but just recently remembered what the problem was. Sorry for the late reply, I was at work.
Backup everything on your card to your computer, this will erase all of your files. Also try to have a full battery, this could take some time depending on the size of your SD card, the class, and the number of files. Then, boot into recovery and select partition SD card (I can't remember where it is, sorry). If you move apps to your SD card - which I think is kind of necessary with the ginormous Sense 3.0 roms - use a larger size for the Ext partition. I never move apps to my SD card, so I set mine to the smallest option other than zero. For the swap size you can use the default 32mb - you may want to look into this more to see if there's a more recommended size.
When it finishes partitioning, go back to the main screen in recovery, plug your phone into your computer and select USB-MS toggle. This will mount your SD card so you can move files back to the SD card. If you're using Windows, it may want to scan and fix the card... just skip it. If you want to save time and/or battery, you can power down the phone and use a card reader instead. Then you can try to restore/make a nandroid backup or flash a rom - it should work.
Good luck, hope you get it fixed!
(from... Evo/MIUI/Tapatalk)
Download MikG 1.04 from http://dev-host.org/lv6fjpxaq9x4/MikG-Sense2.1-v1.04-signed.zip
After downloading the file, get an MD5 checker application such as this one: http://getmd5checker.com/download
The MD5 sum for the zip of MikG 1.04 is: fb81c61a19b5db6d4fa67acbfb17907f
When you run the MD5 check on the downloaded zip, it should match.
If it doesn't then the download is corrupted.
If it does match but you're still having issues flashing it, then there's a pretty good chance that it's the SD card. MicroSD cards are a dime a dozen nowadays so it should be pretty trivial to get some other card that you can pop in and try to flash with.
I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks
Honestly you should stop flashing roms as PC36IMG because you'll forget what they are eventually. Download the rom you want, place it on your sd card, then do a full wipe, and flash it in recovery, boot up, and you should be fine.
That is what I do. but after flashing yesterday's miui rom from the zip file my system wouldn't let me do a nandroid backup. In desparation I used my pc36img update and now a I am screwed
pc36img probs
yesterday I flashed a bunch of roms from the sd card but something happened after the miui zip file
pc36img
in desparation I used the pc36img update. Now I am looking for a way to fix the system update part of the pc36img update which doesn't work. I only use the pc36img when nothing else works.
can anyone point in the direction of some good pc36img files. I am very desperate here. I have tried everything
Take it to Sprint, tell them it just broke. They will happily load stock GB, then you can start over.
KJ
it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot
Did you try wiping everything except sdcard 3 times in recovery than flashing a .zip rom in recovery
Sent from my PC36100 using XDA App
pc36img probs
I will try that. It will have to wait until monday bc I am on call this weekend. I can't lose my phone. thanks for the tip. I will post the results on monday. I hope it works. btw should I wipe with the sdcard removed?
pc36img
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?
The only PC36IMG's you should ever flash, really is recovery and RUU. Everything else you should do in recovery with a flashable zip.
jjdellorusso said:
I couldn't wait. I tried it and it again said Fail-UZ when updating the system. it also said image unzipping fail. Any other ideas?
Click to expand...
Click to collapse
You hav to flash in {recovery} not bootloader
Download file (click link below) Keep as is go into bootloader let it scan hit no if it ask to update then hit recovery then click wipe then wipe everything except sdcard 3 times then hit flash zip from sdcard then go to this file that you downloaded and select it
http://link.geekfor.me/freshevo431
Sent from my PC36100 using XDA App
pc36imgprobs
tried wiping 3 times
now I can use roms but when running pc36img (sprint lovers) it always sais fail-uz (failure unzipping) should I just ignore this and move on??? I don't really know the significance of this. I can flash working roms now but something makes me feel uncertain. Why can't I update the system with the ruu? any other ideas?
pc36img probs
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?
jjdellorusso said:
just wiped everything again... and still no dice. The phone now works like it did before, but the pc36img (sprint lovers) system update always fails. I am running hboot 6.16.1002. Is that the wrong one?
Click to expand...
Click to collapse
ok this is all i can think of:
1 - get the original pc36img.zip file and put it in your sd
2 - delete the amon ra pc36img.zip that you have
3 - go into bootloader and when asked to update hit yes
4 - when asked to reboot hit yes
5 - if your phone reboots fine (i will give it a pretty good amount of time) download rom manager
6 - in rom manager flash Clock Work Mod (CWM)
7 - Then make a back up (optional).
8 - scroll down in Rom manager and flash alternate recovery (this will give you amon ra w/o having to put the pc36img.zip into your sd card.
9 - do what you wanted to do at first.
jjdellorusso said:
I have been using the very stable pc36img spring lovers version. I flashed a bunch of roms yesterday like I usually do. The last one was the miui rom from yesterday. It didn't work. tried to do a nandroid update but could not. Then I used the pc36img that has worked well for a while but everything updated except the system. it said failure-UZ. luckily later I was able to instal a hybrid rom with MANY bugs. I no longer can upload my contacts. If you have an idea or can point me in the direction of a pc36img that may solve this I would greatly appreciate it. I know I should have moved my backups to the sd card but I messed up here. Please help. Thanks
Click to expand...
Click to collapse
You guys are talking about PC36IMG.zip as if its a ROM that is being flashed. Sprint Lovers, if I am not mistaken, is a ROM that should be flashed via recovery like all ROMs should be. You should not be flashing PC36IMG.zip files through Bootloader unless you are updating radios, RUU back to stock, splash screen updates, etc. It sounds like you are spending a lot of time flashing things via bootloader and that is what got you in this mess to begin with. Can you get into recovery? If so then download any ROM, enter recovery, wipe cache/dalvik cache/data, flash ROM, and then quit using the bootloader before you permanently screw up your phone. This problem should be able to be fixed without the use of a PC36IMG.zip file. Because you've gotten flash happy in your bootloader and as of right now you can't tell us exactly what you've flashed.
If you cant get into recovery then just download Amon Ra v2.3, flash it, and then do the steps I mentioned above. It's not difficult. Just stop getting flash happy with your bootloader.
There is a version of Sprint lovers that can be flashed thru bootloader
And for jj that might just mean the pc36img is corrupted you can download a new one but I say just nice on and use recovery instead of bootloader
Sent from my PC36100 using XDA App
jjdellorusso said:
it is S-off. warrenty is finished. also I would like to fix it myself. All of these little messups teach me a lot
Click to expand...
Click to collapse
"Warranty's" can be restored
pc36img probs
hmmm? I have tried everything as described above. maybe my sprint lovers pc36img has been corrupted. but I really don't think so bc I saved it in many different sdcards and in my computer. Should I try another .zip? can anyone point me to other pc36img files that may help. I must say that I do not flash anything by pc36img, but after I flashed hybrid I couldn't do anything. In desperation I tried my sprint lovers pc36img assuming I could go back. I had to many backups saved and it told me that I didn't have enough space when I tried to do a nandroid backup. I guess the take home message is to save nandroid backups to the sd card also. unfortunately mine is lost.
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful