OK, so first of all I apologize if this is a total noob question, becuase the EVO is the first phone I've rooted and I'm not too familiar with all of this yet. Anyhow, here goes: my Evo's rooted (Using Zikronix's methodas I've go a brand new EVO with Hboot2.02. I've confirmed that I'm rooted by checking for the # symbol in adb shell, and I've got Hboot 2.02 s-off. And I can get into either clockwork or amon Ra recoveries. The problem is, when I go into recovery and select a rom to flash from my SD card, I get the error message:
E:Can't open /sdcard/fresh-evo-3.4.0.1.zip
(bad)
Installation aborted
I just tried it now with the Fresh Rom, but it happens with Ava, baked snacks, and one other that I can't recall at the moment. Basically with anything I try to flash from recovery, and it occurs with both recoveries.
Any thoughts / suggestions?
Just a thought, but maybe the roms arent configured for the new hboot. Idk if it even makes a difference or not.
Related
Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel
N_Jones said:
Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel
Click to expand...
Click to collapse
After flashing rom. Reboot. It will then install the RADIO. Radio installation requires one more extra step after flashing. Once thats done. Load into Android. Then go back in recovery then flash the WIMAX.
+1 the above I use Ra and flashed both just fine.
ok i am running simpleroot evo 2.1 and i was trying to flash the stock froyo rom but everytime i go into recovery to flash it, it gives me a error when attempting to write the boot. error on line 5 to be exact. then on restart the phone goes into an endless white screen reboot. before the flash i did a phone wipe and cache wipe. neither work. has anyone else had this problem and is it fixable? i flashed the radio and wimax fine. and i had this problem attempting to flash the Ava froyo mod also. they all end in a nand restore....
thanks in advance
Damn bro, I'm sorry you are having such difficulties flashing Roms. What recovery are you using to flash? RA or clockwork? Whichever one you are using, try using the other one and see if you get the same error.
Sent from my EVO 4G(Extraterrestial Velocity Object from a 4th Galaxy) - **** is fasttt
tried clockwork and ra neither work, and its with all roms, its line 5 with the froyo roms, line 383 i think with other roms, and another line 400 something error, but there all with the boot. everything else seems go fine
Any ideas? I also used the htc stock 1.47 ruu to restore the phone and re root. Still getting the boot error
ok, well i didnt get any answers to WHY the error was being caused but i did manage to get the stock OTA rooted via unrevoked forever. restored the stock recovery on the evo then did the OTA update, flashed clockwork recovery afterwords then installed superuser from recovery. so basically stock froyo rooted, which was all i wanted. so for anyone else having problems you can still maintain root after the OTA if you install unrevoked-forever.
I'm fairly new to rooting and flashing, but I can figure things out usually after a bit of research. This has me completely stumped though because I have no idea what to attribute my problem to:
I rooted my Evo a few weeks ago and flashed CM7. The problems I had after flashing CM7 was my GPS and I had 1x instead of 3G. Note: I have also updated my CM7 with the recent updates.
I researched some fixes for the GPS/1x issue, which meant I needed to flash to a sense-based rom. I tried flashing a sense-based rom (several different ones) on several occasions via Clockwork/Rom Manager and I had no luck- it would just reboot to the white screen over and over.
The problem I'd like to resolve in this thread is how to figure out why I am unable to flash to *any* rom. I just attempted flashing KingsRom (via Rom Manager) and everything seemed to be going quite well until the very end where it scrolled so fast I could barely catch what the error was- and it seemed to be something with the "boot image."
Side note: During one of my previous attempts at flashing a different rom, which of course was unsuccessful, I was unable to flash a restore of my CM7 backup and I received this error: "error while flashing to boot image." However after just going at it over and over again I managed to flash a fresh CM7
I'd really appreciate any help as it seems a simple flash is giving me a lot of trouble. If any details about my phone are needed to help resolve this please let me know (I don't know what would be necessary to post).
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
plainjane said:
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
+1 on what Jane said. You can use rom manager to flash RA recovery (alternate recovery) but don't use it for flashing roms. Just wipe like she said and flash the zip manually through RA.
Sent from "The EVO" using XDA Premium
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
subjectdelta said:
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
Click to expand...
Click to collapse
Are you wiping fully between installs? It seems like your boot partition may be corrupt... or getting there, if that's possible. Try wiping everything, boot included, and flashing again. The only other thing I can think to do is unroot & go back to stock, then reroot & try again...?
Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet
HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.
Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!
teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?
EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.
Alright, I've been playing around with this for a week with no luck, so Im hoping someone here can shed some light on the problem.
I want to flash my HTC Desire with a custom ROM, but Im not going to attempt that without a working recovery first. Im using the newest version of clockwork recovery (5.0.2). Every recovery I've tried to make on this phone always gives me a md5 mismatch error.
I've only gotten around the problem one way, and thats to create a recovery in clockwork, and restore the backup right away after it's made. If I do that I dont get an md5 mismatch. But anytime the phone is rebooted, any recovery I make does get the error. Ive tried multiple versions of clockwork with no success.
Things I havent tried:
Different SD card
Different recovery
Anybody have any advice?
Please post the details of your Hboot and which rom you are currently running.
SwiftKeyed from CyanogenMod with Transparent XDA App
Would definitely recommend either trying a different SD card, or downloading h2testw.exe to test the SD for errors. This is step 1. Rule out the SD card.
Out of interest, step 2 is using a different recovery. CWM 2.5.0.7 or Amon-RA 2.0.1 depending on what your erase size is:
Download terminal emulator, open it and type:
Code:
cat /proc/mtd
and press enter (note the space between cat and /proc)
Alright, as far as rom and hboot, Im running stock. The phone is S-OFFed.
rootSU: I ran that h2testw on the sd card. Formatted the card and ran the test, came back with no errors. Still having the same problem though. Right now Im using clockwork 2.5.0.9 (oldest one on rom manager). Im thinking of trying a different recovery next. I tried the code you posted and it says my erasesize for everything is 0002000
Kaninm said:
Alright, as far as rom and hboot, Im running stock. The phone is S-OFFed.
rootSU: I ran that h2testw on the sd card. Formatted the card and ran the test, came back with no errors. Still having the same problem though. Right now Im using clockwork 2.5.0.9 (oldest one on rom manager). Im thinking of trying a different recovery next.
Click to expand...
Click to collapse
Go on my guide, I have several links for many different recoveries. Try Ra-Desire it's probably the best.
MatDrOiD said:
Please post the details of your Hboot and which rom you are currently running.
SwiftKeyed from CyanogenMod with Transparent XDA App
Click to expand...
Click to collapse
The rom is stock with hboot 6.06.1002
Kaninm said:
The rom is stock with hboot 6.06.1002
Click to expand...
Click to collapse
I'm 99% sure that there is no such HBOOT version as "6.06.1002"
bortak said:
I'm 99% sure that there is no such HBOOT version as "6.06.1002"
Click to expand...
Click to collapse
I swear thats exactly what it says. Could that have something to do with the problem, or cause problems in general?
Kaninm said:
I swear thats exactly what it says. Could that have something to do with the problem, or cause problems in general?
Click to expand...
Click to collapse
err just out of curiosity is your phone GSM or CDMA (Have you got a simcard).. maybe it goes to that on CDMA phones if you S-OFF
bortak said:
err just out of curiosity is your phone GSM or CDMA (Have you got a simcard).. maybe it goes to that on CDMA phones if you S-OFF
Click to expand...
Click to collapse
Unrevoked sees it as a CDMA, so does rommanager
Kaninm said:
Unrevoked sees it as a CDMA, so does rommanager
Click to expand...
Click to collapse
ahh okay, don't know about CDMA phones - just don't flash anything from the alpharev site or any radios
I'd just suggest trying Amon Ra's recovery and see if that works for you.
Alright, so after awhile of fiddling around I found a way to flash Amon Ra's recovery. I just used unrevoked and set it to custom recovery. However, it didnt work. Booting into recovery after that would just hang at the HTC screen.
I ran unrevoked again to get clockwork back and it went fine, but after it boots into recovery I get this:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted
I got the same thing the first time I rooted it, but i have superuser so I figured it was fine.
Is this a possible cause for concern?
Kaninm said:
Alright, so after awhile of fiddling around I found a way to flash Amon Ra's recovery. I just used unrevoked and set it to custom recovery. However, it didnt work. Booting into recovery after that would just hang at the HTC screen.
I ran unrevoked again to get clockwork back and it went fine, but after it boots into recovery I get this:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted
I got the same thing the first time I rooted it, but i have superuser so I figured it was fine.
Is this a possible cause for concern?
Click to expand...
Click to collapse
Why didn't you just follow my guide on flashing a custom recovery?