Ok where to start? I've been trying to get cm 6.1.2 running correctly on my evo and get it themed but can't seem to get it done and all the back ups I make through amon recovery just send me into boot loop or white screen. Everytime I flash cm and try to flash the 7.6 or 8.x kernel the rom becomes unstable and I get fcs everywhere then I try to restore and it freezes. Now if I just leave the kernel alone and try to flash themes I seem to be getting some unverified package error even after I turn off the security or some other error. I'm not sure if it is because I have ra2.2.1 and hboot. 76 if so I can't find the older ra1.8 anywhere but even with that out of about 15 backups only 1 or 2 where working and those where only sense that would restore.
Any ideas, all you brilliant people of xda?
You need to disable signature verification in Ra recovery to stop the unverified package errors.
As towards your boot loops after restoring a backup, I had the exact same problem with RA 2.2.1, I ended up switching back to clockword 2.6 and all my problems went away.
I have disabled the sig verification and I'm getting another error I can't get around it. I'm wondering if it is because I have the Eng .76 hboot running the newest clockwork and amon.
Related
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 am running MIUI 0.11.12 beta, and seem to have trouble with the ROM Manager app (premium license btw). Everytime I try to flash Amon RA recovery and reboot, it get stuck on the "HTC EVO" screen and hangs. I've let it sit 10-20 mins and it stays that way. If I flash ClockworkMod's recovery, I can reboot into recovery and no issues. I've manually installed Amon RA recovery since.
I am also getting issues with trying to Fix Permissions. I continuously get "An error occurred while attempting to run privileged commands!" I've uninstalled, reinstalled the app, wiped and flashed ROMs and get the same exact thing.
Is there a known issue with this app, or is there a fix for this issue? I am not getting any force closes as I just flashed 11.12 up from 11.5, but I'd like to fix whatever the problem is ASAP. Thanks.
dellibedaboss87 said:
I am running MIUI 0.11.12 beta, and seem to have trouble with the ROM Manager app (premium license btw). Everytime I try to flash Amon RA recovery and reboot, it get stuck on the "HTC EVO" screen and hangs. I've let it sit 10-20 mins and it stays that way. If I flash ClockworkMod's recovery, I can reboot into recovery and no issues. I've manually installed Amon RA recovery since.
I am also getting issues with trying to Fix Permissions. I continuously get "An error occurred while attempting to run privileged commands!" I've uninstalled, reinstalled the app, wiped and flashed ROMs and get the same exact thing.
Is there a known issue with this app, or is there a fix for this issue? I am not getting any force closes as I just flashed 11.12 up from 11.5, but I'd like to fix whatever the problem is ASAP. Thanks.
Click to expand...
Click to collapse
As soon as I flashed that new build of miui everything about rom manager got screwed up and has never been the same. None of my previous backups of saved Roms will flash either through rom manager or if I try it manually. All I get if I try it manually is md5sum mismatch. WTF! If anyone from clockwork could at least explain what happened that way I won't do whatever it did. I have a feeling it was the 1.12? I miui build that did it because I never had a problem flashing my backups with older MIUI builds. I think my backups are corrupted. I am running the same version of romance manager as the op and no other older version of romance manager will flash to recovery. I Among range 1.80 won't work either.
Thank you anyone for shedding some light on the subject.
Charles
dellibedaboss87 said:
I am running MIUI 0.11.12 beta, and seem to have trouble with the ROM Manager app (premium license btw). Everytime I try to flash Amon RA recovery and reboot, it get stuck on the "HTC EVO" screen and hangs. I've let it sit 10-20 mins and it stays that way. If I flash ClockworkMod's recovery, I can reboot into recovery and no issues. I've manually installed Amon RA recovery since.
I am also getting issues with trying to Fix Permissions. I continuously get "An error occurred while attempting to run privileged commands!" I've uninstalled, reinstalled the app, wiped and flashed ROMs and get the same exact thing.
Is there a known issue with this app, or is there a fix for this issue? I am not getting any force closes as I just flashed 11.12 up from 11.5, but I'd like to fix whatever the problem is ASAP. Thanks.
Click to expand...
Click to collapse
As soon as I flashed that new build of miui everything about rom manager got screwed up and has never been the same. None of my previous backups of saved Roms will flash either through rom manager or if I try it manually. All I get if I try it manually is md5sum mismatch. WTF! If anyone from clockwork could at least explain what happened that way I won't do whatever i did. I have a feeling it was the 1.12 miui build that did it because I never had a problem flashing my backups with older MIUI builds. I think my backups are corrupted. I am running the same version of rom manager as the op and no other older version of rom manager will flash to recovery. I Among range 1.80 won't work either.
Thank you anyone for shedding some light on the subject.
Charles
Hey Charles...
Following the MIUI thread, the problem seemed to be the stock kernel. What version are you currently running? I am on 11.9 and I no longer have those issues with the stock kernel.
If you are in an older version and seeing this issues, the fix was to flash another kernel, maybe CM6 snap kernel. That worked for me. How this helps. Don't forget to wipe the caches before flashing.
Swyped from my EVO 4G using XDA App
ok i have a MAJOR problem. im kind of a noob at this stuff so im still learning. i was messing in my system files trying different phone.apk. i think i may have deleted something essential. when i turn my phone on it doesnt get past the boot animation. my phone was rooted with unrevoked 3. but everytime i try to install a new rom using clock work recovery, it gets to the part where it "opens update pakage" and just stops and goes back to the first menu screen of clockwork. i dont have a nandroid backup either so i cant even restore.
Did you wipe everything before flashing?
Which rom did you try flashing?
yes i wiped everything. i tried multiple roms like cm 6, and stock. none worked. also. everytime i try to load up the pc36img.zip nothing happens it says "no image or wrong image"
You should try using Amon_RA instead. Just flash it using ROM Manager. Good Luck.
is it possible for me to change to amon? im not able to get past my boot screen on my phone, so if it requires me to turn my phone completely to use it, then i cant. i dont really know much about amon.
Search for the Amon_RA thread. If you downgraded your HBOOT, you can flash from Fastboot. If not, you can try an RUU.
drmacinyasha said:
Search for the Amon_RA thread. If you downgraded your HBOOT, you can flash from Fastboot. If not, you can try an RUU.
Click to expand...
Click to collapse
. I'm using ROM Manager with ClockworkMod, and every attempt leads to the screen flashing code for a few moments, and going right into the ClockworkMod Recovery main menu. it wont let me flash ANYTHING period. I have HBOOT-0.97. i dont know what can be the problem. and Amon RA is too complicated for me to understand right now cuz im still a noob. :-(
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'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...?