Related
I am unable to flash any roms except cm6 ( I can also flash any nightlies. )
This is driving me crazy. I have tried to flash fresh 3.2 to no avail. I have also tried to install the new virus rom. I attempted to install the rooted version off the newest ota with the same results.
After each attempt the result is the same. It will just hang on the HTC evo 4g screen.
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have deleted all data / dalvik / Cache several times in a row.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
I am completely lost as to why I can only flash cm6 roms
Please let me know any suggestions.
Sent from my PC36100 using XDA App
From what I have read...................
You need to restore a 2.1 or a 2.2 rom you have, boot to that, then you can flash to a 2.2 rom.
You can't go from CM directly to another rom.
I am on 2.2
Sent from my PC36100 using XDA App
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Bielinsk said:
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Click to expand...
Click to collapse
Ok, so basically I am going to unroot - reroot?
I just flashed from cm6 straight to baked snack directly with no problems. Not really helpful but you shouldnt need to flash to a stock rooted rom first. Note sometimes you have to wait a good 5 minutes for the htc screen to go away. Probably took about 5 when I moved from cm6 to snack.
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Defpdp said:
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Click to expand...
Click to collapse
I unrooted- rerooted with the same results, I cannot flash ANY roms other than Cm6 it seems, this is very frustrating..
Anyone else have any ideas at all??
Thanks!
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
crimeslunk said:
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
Click to expand...
Click to collapse
Nothing worked, tried going to different recoveries/versions. Nothing.
Anybody? Any advice?
if you flashed cm6 and have it working... its my understandung that you cqn not just go and flash a different rom. there is a process that needs to be followed.
but i have never and never will use cm6 so i could easily be talking from my rear.
Sent from my PC36100 using XDA App
I flash from cm6 to rooted stock rom when I need to update prl and stuff.
After you flash wipe dalvik and cache again I had that problem when flashing snap.
Im not sure if these don't help. Maybe you can send a tweet to cyanogen himself to get it resolved. If fix pst your findings
Sent from my PC36100 using XDA App
Re root and see what happens
Sent from my PC36100 using XDA App
Also check your kernel, you shouldnt have to flash anything but the rom you want when switching from cm6
My evo is running the latest amon ra recovery and I've never had problems prior,and im running fresh rom, I tried to wipe everything even 3 times in the same session. I then flashed the gb beta 4 rom and I still get the fresh boot animation and once gb starts up, I get a bunch of htc processes fc's. Anyone help me find out what's wrong?
Sent from my PC36100 using XDA App
If you know it's a problem with not wiping properly, might I suggest Calkulin's format all zip?
I am currently running EvoKings GB RC3 and loving it. But since I can't leave well enough alone, I want to update to the RC4.
I just have a couple of questions concerning this ROM.... I see where he mentions its based on CM7... is it based on CM7 7.0.0.0 or CM 7 7.0.2.1?
Also will I need to do the GPS fix again and update PRL, as I assume I have to wipe dalvik/cache to update from RC3 to RC4 (as it seems its more than just an update)?
Speaking of the GPS fix, when I did it, I was on RC3 of the EvoKings GB rom, and this is the steps I followed:
Booted into recovery
Made a Nandroid backup
Wiped All Data
Flashed into a backup sense rom I have (Mikfroyo 4.6)
Performed GPS fix and updated PRL
Booted back into recovery
Performed Nandroid restore (no data wipe)
Back into RC3
Was that correct... that I dont do a data wipe and just do a nandroid restore? I have been reading so many conflicting reports on this. My assumtion was to always wipe data before doing a restore.
Thanks everyone.
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
dougjamal said:
First of all, if you're updating a current rom, them all you should have to do is wipe cache & dalvik and then flash the updated rom. As for not wiping data, no, it isn't necessary, however, I'm one of the people who do especially if I'm changing roms. I don't want any remnants of the previous rom.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Ok cool, thanks. When doing the GPS fix, is the info stored somewhere else, which is why it doesnt get removed when doing a wipe of stuff?
Trying to figure that out... since yeah I am worried about having some type of conflict when switching from a sense to an AOSP rom. I havent had any issues so far with RC3 doing that, minus some issues with the screen not coming on with a button press while playing music.. but not sure if thats just something with the ROM itself or the GPS fix.
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
whiterider13 said:
I am not sure where the gps fix is stored, but there should be no conflicts. I have switched between AOSP and Sense tons many times since I did the fix and have never had any problems.
Sent from my Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
+1.....I've never had to apply a GPS fix and I, too, have switched between AOSP and Sense numerous times. As a matter of fact, my current rom is Salvage-Mod and the GPS works as it should and I still didn't have to apply a fix.
posting & replying via the XDA Premium app.
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
whiterider13 said:
I had to do the gps fix when I first switched to cm7 rc2. Since then I have never had to redo it nor have I had any issues.
Sent from my b3 Infected Evo using Tapatalk Pro!
Click to expand...
Click to collapse
Thank you both, thats what I wanted to hear. I havent wanted to switch roms because I got the GPS working and I didnt want to switch roms and have it broke again. Thank you!
No prob man, just glad I could help.
Sent from my b3 Infected Evo using Tapatalk Pro!
What build of CM 7 is this rom built off of?
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Few suggestions: Are you wiping properly, do you have the latest recovery (amon ra or clockwork), are you flashing gapps, did you update to all the latest radios/wimax/prl?
Why don't you try to flash decks aosp rom!
http://forum.xda-developers.com/showthread.php?t=1078558
Sent from my PC36100
jjchdc said:
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Click to expand...
Click to collapse
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Same problem on friends phone just use amon RA wipe everything twice and flash and be patient with the white evo 4 g screen it may take a while there.
Sent from my PC36100 using XDA Premium App
I'm wiping completely using both Clockwork and Amon but its still a no go and I flash falls when using aosp. I'll try that Rom and report the results.
Sent from my PC36100 using XDA App
playya said:
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Click to expand...
Click to collapse
The format all was just what I needed. Thank you very much!
I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.
Edit:
In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.
If you choose to format the SD card, be sure to back up your important files first.
If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
sjpritch25 said:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
Click to expand...
Click to collapse
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Edit: if you experienced this it may help to figure it out
JAS_21 said:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.
Click to expand...
Click to collapse
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
I've seen more than one user with the issue. One is a long time forum member.
xHoLyx said:
Its a myth.
I don't see a reason why it wouldn't work.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from
I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.
I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.
I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.
I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.
All sense ROMS work.
I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.
I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.
Sorry for all the info. I just tried to give as much detail as possible.
Hope this helps,
Matt
Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.
Also, if anyone has a fix it can be posted here.
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
dch921 said:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
Click to expand...
Click to collapse
Were you running a sense ROM before Miui?
I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.
Sent from my mobile typewriter.
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
ftmaniac948 said:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
stelv said:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
Click to expand...
Click to collapse
No, you should be fine.
Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also
JAS_21 said:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
Click to expand...
Click to collapse
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me
ftmaniac948 said:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
Sent from my Incredible 2 HD using xda premium
Click to expand...
Click to collapse
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.
Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.
Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.