I have the latest recovery mod installed (ClockworkMod 2.0.1.3) on the latest ROM and Radio released June 28th for the Evo and I get the error icon every time i try to load into recovery. I have already tried to re-flash from ROM manager but no luck. Any ideas or on whats going on?
The same thing has happened to me twice. It happened when the program told me there was a new version available, and had to flash the new one. Afterwards, I could not boot into recovery (i'd just stay stuck in the beginning screen).
The way I fixed it is inside of ROM Manager, I clicked "Fix Permissions", and after that was done, I clicked "Flash Amon RA". This at least allows me to use the Amon RA custom recovery.
I had issues with the latest clockwork 2.0.1.3 too. At the bottom of rom manager there is the option to flash previous recoveries, i just went back to 2.0.1.2 and it works fine.
I have tried multiple old versions of clockworkmod and the alt recovery and still no luck. All attempts to load into any type of recovery have failed. HELP!!!
Sent from my PC36100 using XDA App
bump... still no luck
theothermillion said:
I have the latest recovery mod installed (ClockworkMod 2.0.1.3) on the latest ROM and Radio released June 28th for the Evo and I get the error icon every time i try to load into recovery. I have already tried to re-flash from ROM manager but no luck. Any ideas or on whats going on?
Click to expand...
Click to collapse
not sure exactly what you mean by the bolded statement. like you installed the updates in a custom rom or you did the OTA to get the latest rom and radio?
healthpellets said:
not sure exactly what you mean by the bolded statement. like you installed the updates in a custom rom or you did the OTA to get the latest rom and radio?
Click to expand...
Click to collapse
I used the "[ROM] OTA 1.47.651.1 Rooted" method to update my phone then I ran Calkulin's radio update. After this I was able to go into recovery and perform the factory reset / wipe device. I then preceded to restore my phone's data using My Backup Pro. after seeing that everything was working fine i went to try and perform a nandroid backup and found my recovery to be broken. Have been unable to flash a working rom since. I have been using ROM manager to flash different recoveries. and I always have the same result of a picture of a phone with an exclamation mark inside a triangle.
In Brief:
Got New Phone due to light leak. Finally after 2 months
Came with 2.2 on it.
Used the new 2.2 Root Guide with Unrevoked. Worked great.
Installed VirusROMX - working great.
Wanted to try out the Final 6.0 ROM from Cyan.
NanDroided the ViruxROMX
Got an error 7? So I found this link that was to correct that issue.
http://forum.xda-developers.com/showthread.php?t=752832
Flashed the new Hboot and it allowed me to install the CYAN R6.0.
CYAN ROM - Keep on Rebooting and Reloading the CYAN Boot Screen after setup and scrolling some apps.
Removed it and went for a Nandroid Restore.
I get the MD5 Checksum message and then trying to reload boot image. And Boot Image cannot load.
I have tried to reflash the recovery(Clockwork) and still no good.
My working Daily with all my updates and apps are on the Nandroid. I would hate to lose it.
Any help would be appreciated.
Anyone?
Sent from my DROIDX using XDA App
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
tomh1979 said:
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
Click to expand...
Click to collapse
That's is what I tried to do. It would say boot image unloadable and spits me out to the HBOOT options. With no ROM loaded and messes up my current ROM in place.
At least for me when I restored in the past and I have done it often is that I would just restore and not wipe or anything since the restore does all of that for me. Well in this case it does not and when it cannot restore I have to reload a new ROM again in recovery and start the process all over again. I have tried the NANDROID again after going through the entire ROM reload again and still a no go.
I can't nandroid restore my old daily which has text messages and everything that I wanted to reference. I can live without it but the inability to restore any Nandroid is driving me crazy.
It happened when I flashed that HBOOT update on the link I provided in OP. I am just trying to figure out how to reflash the old image back so I don't have to worry about it. The only reason I did it in the first place is to test out the Cyanogen R6 and that wasn't a good experience.
I guess I could post in the thread that started all of this to ask. But I thought I would keep the SECTION POLICE from hounding me about posting in the wrong section
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
tomh1979 said:
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
Click to expand...
Click to collapse
The PC36IMG.zip - I will try the flash.
The Hboot through PC36IMG.zip worked fine. It's the nandroid thats fuxored. Will try later on and see. Thanks for the suggestion.
I had to redo the second part of the Froyo 2.2 update with the Rooted Froyo and the 2.2 unrevoked. It finally worked and I was able to restore. I really want to try out the CM 6.0 again in the future but not at the expense of time to restore to get it back.
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
dude what i just did was go to rom manager and scroll all the way down flash alternate recovery and after its installed go and tap om clockworkmod recoveries and install the 2.5.0.1 and your good to go !!
JJS714 said:
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
Click to expand...
Click to collapse
I doubt *flashing* clockwork would cause force closes. But you can always revert back to 2.5.0.1 or AmonRa and restore a backup. Check the "Legacy" area of ROM Manager.
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
I got this also, but i wasnt using CM...i was on a sense mod and was able to restore a different rom and went to the new amon-RA instead.
Maybe its something with CM specifically
It has to do with the scripts used in the update.zips. Most people are still using the olds version used in 1.5... Net said that he had to change it to the new scripts used in gingerbread which makes it not work with any updates or backups made prior. There is a topic on it in here where he explains it. He says to flash the 2.5 if it's not letting you update something.
snappydave said:
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk
They put up a new version of Clockworkmod recovery 2.6.0.1. This will work for all that had problems with the 3.0.XXX versions of the recovery. All the goodies of the 3.0XXX but with amend support so it will work with all roms.
All I can say is that Amon has never let me down. May want to check it out if you haven't already. Even their recent update was smooth as silk. No problems for me.
I had this happen to me too with a flash resulting in the white evo screen loop. I was able to flash to the amon ra 1.8 but I couldn't flash anything. So I upgarded to the new version of RA but am still not able to flash anything. I go into the white evo screen loop and then I have to pull the battery and nand a restore. Not sure what I need to do now. Any help would be greatly appreciated.
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
mtown_cyclone said:
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
Click to expand...
Click to collapse
Try flashing CW manually and restoring your previous nandroid manually as well
Hope this helps
I always flash using Clockwork. I use Rom Manager to get the ROM but I perform the actual flash in Clockwork. You'll have fewer issues if you do.
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
mtown_cyclone said:
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
Click to expand...
Click to collapse
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
KB3MMX said:
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
Click to expand...
Click to collapse
I went to 3.0.0.7 but I'm back to 3.0.0.8 now. And just flashed RC4. Working great so far. Very fast.
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
drk.hd said:
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
Click to expand...
Click to collapse
Yep, all good.
I've been searching for a solution before writing my own post, for I'm aware there are probably many, many topics of people dealing with the same issue.
Well, here's is my problem.
I've got two wildfires A3333. Flashed CM 7.2.0 on both of them, successfully. GPS does work on only one of them. I've tried the GPS test on the other one. The compass is working, the localization is not.
So, as said before, I've googled for some solution for the other one, and here comes the temporary downgrading of CWM to 2.5.0.7 and then installing one of the following: buzz.radio-3.35.15.31-signed.zip, buzz.radio-3.35.20.10-signed.zip or buzz.radio-3.35.19.25-signed.zip that will be put on the SD.
Ok, everything is set up, let's reboot to recovery.
Now, the recovery screen is showing version 3.0.0.6 and I don't know if that's normal, since I've set it to 2.5.0.7 before rebooting. Won't mind for now.
Let's flash the zips. And all I get is this message, with all of the radios:
E: signature verification failed
Installation aborted.
Uhm, let's try by setting the option toggle signature verification to disabled.
Here's a different message:
Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
It seems that the 3.0.0.6 version shown on the main menu is kind of relevant... Should it show 2.5.0.7 instead of that? What now?
Thanks in advance.
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
lakshan_456 said:
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
Click to expand...
Click to collapse
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Snakebar said:
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Click to expand...
Click to collapse
I wouldn't really recommend using ROM Manager, and what I meant by flashing was to flash the CWM zip with your current Clockworkmod recovery.
And also consider upgrading your recovery.
And about the guide, just make a nandroid backup with CWM, and restore it instead of flashing a new rom.
Hope this helps
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Ok, I've installed the v2.5.0.7 via the install from .zip option and got to install the radios. Woo!!
No, hold back.
Now the GPS icon is showing up but GPStest doesn't detect any activity.
I've installed 13.55.55.24H_3.35.20.10 first, then 13.45.55.24H_3.35.15.31 and then 13.53.55.24H_3.35.19.25. Same result.
Now should I rely on plan B?
I've read of someone who got it working by installing the 3 radios in crescent order. Is it worth a try?
Snakebar said:
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Click to expand...
Click to collapse
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Try this radio file. link, worked for me under cwm 2.5.0.7
lakshan_456 said:
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Click to expand...
Click to collapse
My fault, there's something I should make clear.
The radios I've been talking about before have been installed on the first Wildfire, the one I said the GPS was working (and in the meanwhile it proved to be untrue as I discovered the GPS icon has never showed up before flashing the radio). This one Wildfire has CWM 2.5.0.1, installed with Unrevoked. The second Wildfire (which I'd like to use as my usual phone) was rooted with PC49IMG as Unrevoked wouldn't work with it and is running CWM 3.0.0.6, which I've reported in the first post.
For now, let's discard the CWM 3.0.0.6 phone.
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
ChristianPe said:
Try this radio file. link, worked for me under cwm 2.5.0.7
Click to expand...
Click to collapse
Uhm, link is broken. My CWM 2.5.0.7 looks to be working properly anyway.
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
ChristianPe said:
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Click to expand...
Click to collapse
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Snakebar said:
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Click to expand...
Click to collapse
where you at?, i might be a weather-related issue?
ChristianPe said:
where you at?, i might be a weather-related issue?
Click to expand...
Click to collapse
Unlikely, it's been some days I'm testing the GPS on the phone. But I shall test it away from home to be sure.
I'm from Naples, (IT) by the way.
Snakebar said:
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
Click to expand...
Click to collapse
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
lakshan_456 said:
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
Click to expand...
Click to collapse
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Snakebar said:
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Click to expand...
Click to collapse
Well, I'm sorry mate. unless its a hardware fault or something I'm not in the know of, there are no more solutions I can think of.
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Snakebar said:
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Click to expand...
Click to collapse
Indeed it is, atleast it wasn't a hardware issue
Well done mate...
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Sent from my HTC Wildfire using Tapatalk 2
lakshan_456 said:
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Click to expand...
Click to collapse
Done!
~400s for first GPS lock... yeesh...
Snakebar said:
Done!
~400s for first GPS lock... yeesh...
Click to expand...
Click to collapse
Mission accomplished.
Cheers
Sent from my HTC Wildfire using Tapatalk 2