so imma newbie and i tryed to flash the destroyer rom onto my evo when i reboot run the rom it keep showing destroyer animation over and over does anyone else know why ?
Wait 10 mins, if nothing, try reboot, still nothing? Flash again.
Make you sure you follow directions when flashing a custom rom. Wipe data/cache/dalvik cache.
hTC Evo CM7-n17
You didn't flash it correctly and you got what is called bootlooping. Just wipe factory/data, cache, and dalvik and then try again.
It will bootloop if you flash the ROM and gapps in the same recovery session. You have to flash ROM, reboot, then go back into recovery, wipe dalvik and flash gapps. If you want the extras, flash larger gapps first, then reboot again and wipe dalvik and flash smaller gapps.
so i reflashed it worked just one problem my visual voicemail doesn't work at all
blakrepublic said:
so i reflashed it worked just one problem my visual voicemail doesn't work at all
Click to expand...
Click to collapse
You need to either flash back to a sense rom, verify that it works, like have someone call you and leave a message, then use titanium to backup the app and data, flash back to The Destroyer rom, restore the app and data, NOT system settings, or use google voice or a third party carrier.
Related
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
KR3UZL3R said:
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
Click to expand...
Click to collapse
need more info. how did you go about trying to do this? what steps did you? More info on what you did can help someone figure out where you went wrong. Did you create a nandroid backup before you flashed the ROM? what recovery are you using? Did you wipe data (factory reset), cache, and davlik cache prior to flashing the ROM? If you did make a back up, and can get to Recovery (volume down and power button, then select recovery) I would wipe all data, cache and davlik cache, then flash a nandroid backup. If you didn't make a nandroid backup, I would try wiping everything again, and try flashing the ROM a second time.
http://shipped-roms.com/index.php?category=android&model=Supersonic
THAT SHOULD GET U BACK TO STOCK
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Probably something wrong with your install. Did you wipe dalvik cache, etc.?
Reflash new boot.img.
Sent from XDA App using HTC One X.
PCHAPM said:
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Click to expand...
Click to collapse
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
vivek_bhoj said:
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
Click to expand...
Click to collapse
Had done the full wipe and cleared both cache but not the reflash of boot imgage this did the trick. Thanks for the great help.......
Hi All,
Seem to have a slight problem with flashing Custom Roms onto my GNex at the moment. Not too sure what's causing it to freeze when booting up. All I get is the X logo and will stay there until the battery dies.
I'm able to revert back to a Google rom and regain use of my phone. Just can't seem to flash any custom roms at all. It's happened with CM10.1, CM10, XenonHD Stable-2.0, Minoco.
I've attempted to flash with CWM and TWRP. Both get the same results. Prior to flashing I've whiped both the Cache and Davlik.
I have previously used CM9 and older versions of Minoco on this device. So seems odd that this is happening now.
Any advise or ideas towards what I should look at would be appreciated.
Thanks,
Drav
you have wipe data before flashing different roms... dirty flashing(only wipe cahce and dalvik) is only if you are updating the same rom.. this is how i normally flash ALL roms
1. wipe data/factory reset
2. wipe system
3. wipe cache
4. wipe dalvik cache
5. flash rom
6. flash gapps
7. reboot
8. wait 10 mins then do another reboot
9. enjoy
PS- the 10 min wait and reboot is soemthing i do that IMO lets the new rom settle
Thanks k786,
It's booted up in a custom rom now after following those step by step. Much appreciated! :good:
Cheers,
Drav
Okay all the sudden on CFX 4.2.2 I am having weird issues, I converted google search to a user app, then back to a system app, and it would constantly crash, I now try and format the phone ie: wipe date/cache/dalvik and reboot into the ROM, I no longer get a prompt about a gmail account or anything like that and the ROM boots right up with no gmail notifications or anything, and google search still isn't working, why can I not format my phone lol?
I even tried re-flashing the ROM after a full wipe/format and it still is all beyond messed up?
WTH, even after a fresh ROM install with no flash over with GAPPS, it's still on the device like it was never formatted -.- im using CWM 6.0.1.5, i've never had issues with this recovery or anything, now all the sudden it's like GAPPS will not delete from the ROM.
Okay, a different attempt at flashing a completely different ROM then reflashing CFX, reflashing a different ROM got rid of GAPPS, so now im in the process of reflashing CFX to see if that fixed my problem, if it did idk why wiping the ROM itself wouldnt get rid of GAPPS.
Okay that fixed it =S.
I take that back, nope i guess im just screwed lol.
Okay i've come to the conclusion that something is just wrong with the ROM
Did you wipe the System partition before installing the new ROM? When you flash the GApps zip file in recovery, it writes those to System. Therefore, if you just wipe Data, they will still be there. Also, always do a full wipe (system, data, cache, dalvik) when switching to a different ROM.
Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!