Im currently running Viper4g on my evolte but ive been checking out CM10 and i want to try it out. What would be the usual steps to take when flashing a new rom?
I would do a full NAND backup with whatever recovery you have in case you want to revert back. Then do a full wipe (system, data, cache, dalvik) and flash the new ROM.
Read the guide in my sig lol, explains just about anything you could think of and has a list of basic trouble shooting scenarios that some users are likely to encounter
Come on guys you tell me what a great write up I have and never recommend it?
Edit: I feel like I'm trying to sell myself and I am not a wh***
*runs away in tears*
Of course it's great
However, you said yourself: it's a great reference guide, but not a step-by-step for anything.
The OP asked for steps to take when changing ROMs
Yes but the title of his thread says tips for someone new....ahaaaa.. *cue classic black and white cinema fiend music*
I so wrote it to avoid all these brick and corrupt card threads
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
bilbo524 said:
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
Click to expand...
Click to collapse
Suck up
Sent from the depths of hell
Quiet let me have my moment lol
Absolutely not lol
Sent from the depths of hell
Dude, check out the last 2 scenarios, went to the head and the gf added them. I laughed so hard
Well it looks like i did something wrong cause my phone is stuck in a constant boot loop. I followed the instructions on http://forum.xda-developers.com/showthread.php?t=1794867
for
How to flash a boot image if S-ON Dev Unlocked 1.15 HBOOT:
I was trying to install CM10 btw. I did a backup using twrp tried restoring but that didnt work. What can i do now to fix it?
Maybe the cmx was a bad download or bad flash. If you fasboot flashed the aosp boot IMG you might have problems trying to restore a sense backup. I would download cmx again redo all the steps.
I'm not sure if you have to flash a sense boot IMG when restoring a backup , I would try it tho to be safe.
Hey man. The instructions work, so start over and make sure you follow every step including wiping.
Sent from my EVO using xda app-developers app
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
No i didnt. Right now i just want to get my phone working again since i have work in an hour. What should i do to get it working again?
Start the process over just make sure you wipe fully before flashing anything. Cache, dalvik, factory reset and system.
Sent from my EVO using xda app-developers app
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
So just follow the steps from the link i posted using the boot.img from the viper4g download?
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
bilbo524 said:
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
Click to expand...
Click to collapse
ok im trying to restore again, hopefully it works. i have work in 45 minutes and being without my phone would suck.
It worked! Thanks for the help guys. Im gonna leave CM10 alone until the weekend when im off.
Related
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:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Ventus_zx said:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
Im not an expert, but did you create a backup? or try wiping twice over and re-installing.
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
xndabox said:
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Ventus_zx said:
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Click to expand...
Click to collapse
same thing happened to my phone with CM 10, so i ended up instaling the android revolution rom for the time being.
What recovery are you using? Use 4ext if you aren't, try again, if it loops more than once, you either forgot to wipe before install or you need to flash the kernel manually.
Sent from my SGH-T999 using xda app-developers app
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
I also had a problem when I flashed Speedrom but with versions 6.5 which I had previously working perfectly but then decided to switch to SS3 and then switch back. Now I also had the bootloop issue thing where the thing would just keep spinning. So I re-flashed SS3 with the faux kernel and then just did the two things:
4EXT Recovery btw
Wipe data/factory reset
Clear dalvik cache
Then install the rom and once done, go back to menu and reboot from recovery. It should tell you that the previously used boot.img will be used (that is what I get when I flash my roms and they work perfectly).
+1 is this helped!
Thanks it worked! Though I switxhed back to speed rom lol
Sent from my HTC Ruby using xda premium
Nice! And no problem, just happy your phone's back to normal! =)
I have the Sprint HTC Evo 4g LTE. I have HBoot 2.19, and also twrp recovery. I attempted to flash CM 10 but it did not seem to succeed. Now all I get is the HTC screen and it stops there. If I attempt to reboot or shut down in recovery, I get a message that says NO OS. Also the phone is unlocked but is in S-on. Any help would be greatly appreciated. Can anyone offer a solution?
Sounds like a bad download. Try redownloading your rom of choice and verify the md5
Wipe data,
Wipr cache,
Wipe dalvic,
Wipe system
flash again.
Remember that first boot will take a while especially with cm 10.
Sent from my EVO using xda premium
drlzanej said:
Sounds like a bad download. Try redownloading your rom of choice and verify the md5
Wipe data,
Wipr cache,
Wipe dalvic,
Wipe system
flash again.
Remember that first boot will take a while especially with cm 10.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
wrong
he needs to flash the kernel image separately
flex360 said:
wrong
he needs to flash the kernel image separately
Click to expand...
Click to collapse
Got er done, Thanks guys!!
flex360 said:
wrong
he needs to flash the kernel image separately
Click to expand...
Click to collapse
Not necessarily, i figured he had read the cm10 OP for s-on and alreadr flashed the kernel img.
Sent from my EVO using xda premium
flex360 said:
wrong
he needs to flash the kernel image separately
Click to expand...
Click to collapse
+1
Sent from my EVO using Tapatalk 2
First of all, thank you in advance for any help you can give.
So I made an attempt today of flashing a CyanogenMod Nightlie build using ClockworkMod and now I cannot get passed the spinning Cyanogen logo (I have waited 45 minutes over several different reboot attempts).
The bootloader has been unlocked
I have wiped the data
I have wiped the cache
I have wiped Dalvik Cache
then
I have loaded the nightlie
and then the gapps
then I rebooted and I get nothing but the startup screen.
Can anyone help? Did I miss something? I have been all over the forum looking for insight and havent had any luck.
Again, thank you and I thank everyone for their hard work on these builds.
George
Give us some basic info are you s-off etc
Sent from my HTC_Amaze_4G using xda app-developers app
filthygoat223996 said:
Give us some basic info are you s-off etc
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yes, I now realize that I forgot the important step of S-Off. Can that be done now that I am forever in the bootloader?
Gkins3 said:
Yes, I now realize that I forgot the important step of S-Off. Can that be done now that I am forever in the bootloader?
Click to expand...
Click to collapse
Can you get into recovery? If you can revert back to your nandroid and enable smart flash if you are using 4ext
Edit: oops I see you are using cwm
I guess you can try to restore and try s-off
Sent from my HTC_Amaze_4G using xda app-developers app
filthygoat223996 said:
Can you get into recovery? If you can revert back to your nandroid and enable smart flash if you are using 4ext
Edit: oops I see you are using cwm
I guess you can try to restore and try s-off
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help. No luck on the restore. I guess I hit full wipe on one of my many re-installs. Gotta work in a few hours... will have to work on it tomorrow more. I thought with my prior Blackberry modding I wouldnt make these stupid mistakes... but I was wrong.
Again - thanks.
Gkins3 said:
Thanks for the help. No luck on the restore. I guess I hit full wipe on one of my many re-installs. Gotta work in a few hours... will have to work on it tomorrow more. I thought with my prior Blackberry modding I wouldnt make these stupid mistakes... but I was wrong.
Again - thanks.
Click to expand...
Click to collapse
No problem its always better to be safe than sorry, I'm sorry I'm not more knowledgeable on cwm. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
okay, some things have been done wrong.. to flash a rom like cm10 if the rom isn't booting and your S-ON not using 4ext you need to flash the kernel separate, and 4ext is the recommended recovery for any and all S-ON htc phones.. id still recommended for S-OFF also..
---------- Post added at 11:22 PM ---------- Previous post was at 11:19 PM ----------
and to do a clean install your's suppose to
wipe data / factory
format system
wipe cache partition
wipe delvik cache
flash rom
flash gapps
wipe delvik cache again
boot rom let it sit till the screen goes off
(extra)
boot into recovery
wipe delvik cache once again
fix permissions
boot phone and enjoy
install rom agn !!
I recently attempted to root my HTC thunderbolt, and to do so I used the htc dev unlocker and then this "HTC Thunderbolt Tool'
rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
After that I downloaded a rom and installed it through the 4ext recovery, it all install fine and I did do a factory/data reset but whenever I reboot after the rom install, I get the HTC white bootloader and then the screen become black with a back light to it.
I have tried a number of times to re-install the rom and have tried to use other roms but all of them seem to end the same way.
I have used:
BAMF FOREVER 1.1
BAMF MECHA ICS
AIRBORNE GOUI
Killsense 3.7.19
Lightning501
few more
My phone is a HTC Thunderbolt and when I attempted to root the phone it had a hboot version of 1.0.8 and had a stock version of ICS installed.
Sadly I have a phone without a working rom and I had forgot to make a backup so if anyone can help it would be greatly appreciated. Preferably I would like to keep the phone rooted but its not necessary.
Thank You
I'm a total xda-developor noob, so I hope I didn't mis a thread with a the solution all ready on it.
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
tburns said:
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
aplysenko said:
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
Click to expand...
Click to collapse
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
disconnecktie said:
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have done that.
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE
santod040 said:
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE.
Click to expand...
Click to collapse
Your link dont work for me, id assume you were pointing to this wonderful thread
Milimbar said:
Your link dont work for me, id assume you were pointing to this wonderful thread
Click to expand...
Click to collapse
Correct Thanks I fixed the link in my first post.
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
aplysenko said:
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
Click to expand...
Click to collapse
You can use whatever Recovery you want, Clockwork Mod is old and not really suggested to use, especially with newer roms.
I miss the RA recovery I had on my first bolt. I use the ext4 recovery now. Glad Santod was able to help you out!!
Sent from my ADR6400L using xda app-developers app