After applying a cm10 theme on Dastin's WILD FOR THE NIGHT ROM and then rebooting i got stuck.... This has also happened to me on other AOSP and Sense ROMs after changing fonts... Has this ever happened to anyone else? If so how do you fix it without having to reflash/wipe? So I can recover unsaved data. I tried wiping dalvik, cache, dalvik+cache, flashing a diff kernel, and even dirty flashing the same rom all in different occasions anything i can attempt next time this happens?
Sent from my Evo 3D CDMA using xda app-developers app
Related
Ok. I unlocked my phone using the HTC method. Flashed a working recovery. Flashed synergy ROM and everything went smoothly. Now when I tried to flash miui and steel ROM, I can't get past the lockscreen. Can someone help?
Sent from my PG86100 using XDA App
bleichtman said:
Ok. I unlocked my phone using the HTC method. Flashed a working recovery. Flashed synergy ROM and everything went smoothly. Now when I tried to flash miui and steel ROM, I can't get past the lockscreen. Can someone help?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Problems occur sometimes when something is missed when delating i.e deleting cache, dalvik cache or factory reset etc is missed. Did you do all?
Also i once had a problem because i was using a download manager and partially paused the download. When i switched my laptop back on to resume the download ...it did resume and it did download the entire ROM but somewhere something got corrupted and i couldn't get past the boot screen.
Above is just my personal opinion. No harm in trying to re download a new ROM.
elevation_2 said:
Problems occur sometimes when something is missed when delating i.e deleting cache, dalvik cache or factory reset etc is missed. Did you do all?
Also i once had a problem because i was using a download manager and partially paused the download. When i switched my laptop back on to resume the download ...it did resume and it did download the entire ROM but somewhere something got corrupted and i couldn't get past the boot screen.
Above is just my personal opinion. No harm in trying to re download a new ROM.
Click to expand...
Click to collapse
I actually redownliaded, wiped numerous times. Tried infected and that worked. Could the kernel be a reason?
Sent from my PG86100 using XDA App
Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:
hey ladies and gents,
I have a problem...I went to flash the ZR3D rom because I had a problem updating the new mean rom 3.92 so I wanted to see if the problem occurred with this rom as well (yes I did the cache and dalvic cache and superwipe etc etc haha) and when it gets passed the htc and the boot animation of this rom or any other roms it jus sits there and freezes and wont go to the google login screen....I even re-partitioned my sd card and factory reseted my evo 3d (yes I am on the newest OTA as well fyi)...The odd thing is I been flashing roms forever now and this never happened before...like I said all it does is sit there at the main screen but freezes and doesnt bring up the appropriate set up info....anyways any help or information would be greatly appreciated as I haven't had a working mobile device for 2.5 days now haha
Thanks!!!
Try reflashing your recovery.
#Root-Hack_Mod*Always\
S on/off status? Bootloader? Locked /unlocked? What recovery? Cdma?
Sounds like your kernel didn't flash correctly.
Sent from my PG86100 using Tapatalk
Alright, about a couple of weeks ago my phone started randomly rebooting/shutting off. Was on meanrom 3.x woth stock kernal. Tried superwipe, reflash. No luck. Tried one of the many miui roms, tried aosp roms, tried android revolution, zr3d. Multiple different kernals. Still no dice....anyone have an idea. Hboot 1.4 downgraded, newest radio, ext 4 recovery.....almost bought a nexus last weekend, driving me nuts!
Sent from my PG86100 using XDA
Gonna try updating the recovery..dpnt think thats it but what the hell. Also generally it happens with screen off and unplugged. Never happened with screen on yet
Sent from my PG86100 using XDA
What software are you on the 2.08 or 2.17? Also what recovery? Also are you do you always wipe all the way prior to flashing...
2.17... On mean rom from 3.0 and up I'd just flash over... But since I've been having these issues been using superwipe.. Now I'm been flashing roms since I had a blackberry 8310. But I've never used a superwipe script to delete the rom data... This may be a dumb question since it wipes everything but do I have to select factorywipe too after executing the superwipe script..
1. 0.0.5 rc3 I think.. Just updated it. I think I tried your rom too!
armdavid2 said:
2.17... On mean rom from 3.0 and up I'd just flash over... But since I've been having these issues been using superwipe.. Now I'm been flashing roms since I had a blackberry 8310. But I've never used a superwipe script to delete the rom data... This may be a dumb question since it wipes everything but do I have to select factorywipe too after executing the superwipe script..
1. 0.0.5 rc3 I think.. Just updated it. I think I tried your rom too!
Click to expand...
Click to collapse
I use CWM 4.0 as a recovery.. I never user superwipe just a factory wipe also cache and dav cache.. Everything runs smooth...
I would try a normal wipe then run that script..
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed: