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! =)
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:
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.
Where do i begin?
My phone has these random reboots every day, and random crashes during the weirdest times. Like im sending a text and all of the sudden it just reboots . Im not even running a kernel . I receive double text messages and my battery drains a lot. It's just crazy . Last thing it does is that it likes to be on 3G when 3G doesnt work with me somehow. I have to wait till it shows that 4G or H symbol to get data. anyways I know it's not the ROM cause it happens in every ROM i try. Its not the battery cause I've only had it for like 4 months. What is it? i do a full wipe every time i install a ROM too and Yes I am S-off for those of you who are wondering. Are there any fixes to any of my problems? it really pisses me off.
I would full wipe, reinstall Rom and see what happens. Back- up first!
Ok well i say try the unofficial cm10 latest version if u r on it already re installing with 4ext recovery do a full wipe, cache and dalvik wipe and then flash cm10 and jellybean gapps onto it battery life is better then many others and if not satisfied lower the cpu top speed...
Sent from my Amaze 4G using xda app-developers app
ted619 said:
Ok well i say try the unofficial cm10 latest version if u r on it already re installing with 4ext recovery do a full wipe, cache and dalvik wipe and then flash cm10 and jellybean gapps onto it battery life is better then many others and if not satisfied lower the cpu top speed...
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
im on Bulletproof by eclipze , im not that into Other non-sense roms
msterner123 said:
I would full wipe, reinstall Rom and see what happens. Back- up first!
Click to expand...
Click to collapse
I did that , the results were the same . I heard that it helps if you flash to stock or do something with the RUU
Oh well try that to fix it download stock and lock your phone through htc method and install it then re root and unlock and for a sense rom i would recommend nightmare sense 4.0 awesome sense rom but i only like the sense camera thats why i dont use it
Sent from my Amaze 4G using xda app-developers app
kevinrubio1 said:
Where do i begin?
My phone has these random reboots every day, and random crashes during the weirdest times. Like im sending a text and all of the sudden it just reboots . Im not even running a kernel . I receive double text messages and my battery drains a lot. It's just crazy . Last thing it does is that it likes to be on 3G when 3G doesnt work with me somehow. I have to wait till it shows that 4G or H symbol to get data. anyways I know it's not the ROM cause it happens in every ROM i try. Its not the battery cause I've only had it for like 4 months. What is it? i do a full wipe every time i install a ROM too and Yes I am S-off for those of you who are wondering. Are there any fixes to any of my problems? it really pisses me off.
Click to expand...
Click to collapse
Try this tool I made a while back ago.
http://forum.xda-developers.com/showthread.php?t=1762936
Hopefully that'll help. Make sure you read the instructions in full.
Keylogger_0 said:
Try this tool I made a while back ago.
http://forum.xda-developers.com/showthread.php?t=1762936
Hopefully that'll help. Make sure you read the instructions in full.
Click to expand...
Click to collapse
so what that tool does is update my phone to the latest T-Mobile's OTA ? I'll re-read it again , and do it tomorrow but how will this help me with my phone problems?
kevinrubio1 said:
so what that tool does is update my phone to the latest T-Mobile's OTA ? I'll re-read it again , and do it tomorrow but how will this help me with my phone problems?
Click to expand...
Click to collapse
It installs a stock RUU, but with some modifications (changes only the splash screen, recovery, and hboot), but the rest of it is 100% stock
Also, it's an easy way to install the RUU
Keylogger_0 said:
It installs a stock RUU, but with some modifications (changes only the splash screen, recovery, and hboot), but the rest of it is 100% stock
Also, it's an easy way to install the RUU
Click to expand...
Click to collapse
alright , as sooon as i get my phone fully charged , I'll start the process .
Once im there , do i spend like a few days with it to see if the reboots continue? if they dont ,do i reflash a coustom rom ?
EDIT: last night i did the process and everything was successful, I'm on the Stock Rom now
UPDATE: im not experiencing any random reboots but can i reflash my rom now?
kevinrubio1 said:
UPDATE: im not experiencing any random reboots but can i reflash my rom now?
Click to expand...
Click to collapse
Yeah you can try
Keylogger_0 said:
Yeah you can try
Click to expand...
Click to collapse
will it change? like will the issue begin again?
No your problem was that you were probably never full wiping and that was causing the issues as your phone works perfectly fine after a full wipe (what the stock ruu does) and your battery can go bad after 4 months I went through 2 in 8 months
Sent from my Amaze 4G using xda premium
---
sportsstar89 said:
No your problem was that you were probably never full wiping and that was causing the issues as your phone works perfectly fine after a full wipe (what the stock ruu does) and your battery can go bad after 4 months I went through 2 in 8 months
Sent from my Amaze 4G using xda premium
Click to expand...
Click to collapse
is there like a ZIP file i can flash to make sure i do a full wipe? because every time i would switch roms , i would manually factory reset, wipe system , cache , and the dalvik cache
and do you recommend me any battery or just buy a stock battery ?
kevinrubio1 said:
is there like a ZIP file i can flash to make sure i do a full wipe? because every time i would switch roms , i would manually factory reset, wipe system , cache , and the dalvik cache
and do you recommend me any battery or just buy a stock battery ?
Click to expand...
Click to collapse
I use ankers now there pretty good there is a script in android revolution HD thread to do a full wipe I recommend using 4ext as recovery
Sent from my Amaze 4G using xda premium
sportsstar89 said:
I use ankers now there pretty good there is a script in android revolution HD thread to do a full wipe I recommend using 4ext as recovery
Sent from my Amaze 4G using xda premium
Click to expand...
Click to collapse
Any certain type of the anker battery? Im thinking of buying one and i went to thread to download it but it seems the download link is down, do you happen to have a mirror of it?
kevinrubio1 said:
Any certain type of the anker battery? Im thinking of buying one and i went to thread to download it but it seems the download link is down, do you happen to have a mirror of it?
Click to expand...
Click to collapse
4ext or the super wipe script?
Sent from my Amaze 4G using xda premium
sportsstar89 said:
4ext or the super wipe script?
Sent from my Amaze 4G using xda premium
Click to expand...
Click to collapse
the super wipe script , I already use 4ext as the recovery
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Describe your full wipe. Did you format all partitions except sd card.
Sent from my HTC Ruby using xda app-developers app
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
i told you to take a nandroid backup before doing anything!!
ravike14 said:
i told you to take a nandroid backup before doing anything!!
Click to expand...
Click to collapse
Uum.. he already said he was restoring his backup, so wouldn't this mean he did do a android?
Sent from my HTC_Amaze_4G using xda app-developers app
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
you said something bout you had to flash faux kernel..you tried that aswell??
masondoctorjt said:
Uum.. he already said he was restoring his backup, so wouldn't this mean he did do a android?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
my bad for not noticing it
Im having the same problem
I rooted and flashed CM 10 for Amaze 4g and after the inslallation it booted into CM10 but after a minute or so the phone reboots. This hsppens every time. What should I do?
bad.ar said:
I rooted and flashed CM 10 for Amaze 4g and after the inslallation it booted into CM10 but after a minute or so the phone reboots. This hsppens every time. What should I do?
Click to expand...
Click to collapse
You was on GB or ICS earlier??
Sent from my HTC Amaze 4G
Juopunutbear S-OFF
Super CID
bootloader unlocked
Powered by Faux Kernel V024
HBOOT : 1.93.2222
hit the thanks button if i've helped you :good:
avenged_sevenfold27 said:
i was on viper rom well i was gonna go back to the stock rom cuz my data speeds wasnt as fast well when i restored my backup im stuck on the bootloop no matter what i do i even made a full wipe i hope this aint already posted i tried looking but id didnt see anything like this ive never seen something like this before i feel like a major noob
Click to expand...
Click to collapse
This happen to me after flashing faux kernel v29. What I had to do was fastboot flash stock kernel using hasoon2000 tool then flash v29 via 4ext. Your backup boot.image might be corrupted.
Sent from my HTC_Amaze_4G...Go Canes []_[]
So I'm a bit of a newb. I installed cm10.1 witht eh nightlies, but I want to go back to stock using TrickDroid. Should I do a full wipe, or will that brick my system?
KohansMusic said:
So I'm a bit of a newb. I installed cm10.1 witht eh nightlies, but I want to go back to stock using TrickDroid. Should I do a full wipe, or will that brick my system?
Click to expand...
Click to collapse
You should do wipe cache/dalvik/factory reset and you should be fine. One thing I do recommend is doing a nandroid backup before you do that. If something goes wrong you can restore your phone from it.
Sent from my HTC One using xda app-developers app
Fail
PPPeterP8nts said:
You should do wipe cache/dalvik/factory reset and you should be fine. One thing I do recommend is doing a nandroid backup before you do that. If something goes wrong you can restore your phone from it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So did what you said, and installed the rom. But my Recovery says the installation failed, while the aroma installers says it was successful. I tried booting and it just stays at the HTC one screen?
KohansMusic said:
So did what you said, and installed the rom. But my Recovery says the installation failed, while the aroma installers says it was successful. I tried booting and it just stays at the HTC one screen?
Click to expand...
Click to collapse
Did you do a nandroid backup. If you did. Reboot in recovery and restore you phone. Or rinse repeated the process for a different ROM. Try clean ROM first just to make sure everything is fine.
Sent from my HTC One using xda app-developers app