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:
Related
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
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! =)
Ok, I thought I knew what I was doing. Unfortunately, wine had a factor in my issue... I have a rooted Evo 4g LTE. S-on Hboot 1.15. I was using Clockwork Recovery. I probably should have been using TWRP, from what I've read. When I first got the phone, I was over zealous, and flashed a Mod before saving a recovery. I hated it. So I flashed back to Stock ROM (jewel 1.22.651.3). I wanted to try out a Jelly Bean ROM so I flashed codefireX CM10. It worked but when the phone loaded it kept saying "phone error" and wouldn't let me click okay. So I rebooted into recovery and flashed my previous rom. I was a little tipsy, so I tried it again... It still didnt work... Rebooted into revovery, and this time I cleared cache, cleared davaik cache, and did a factory reset... Then, It wouldn't recover my saved rom. I must have cleared everything again, that I remember, now it won't load into Clockwork. I've tried everything I can think. I tried RUU, No luck. I tried flashing through Fastboot, No luck. Tried Well, I really have researched everything I could think about Boot loops... I'm stuck .... Everything I try seems to have a step missing or issue with my phone because its S-on and I relocked it through abd because RUU needs to be lock on.. I read I may have to flash a new kernel. I'm in over my head. I had to revert to using my Palm Pre. (which I loved for many years, But I really miss my EVO!) PLEASE HELP. :crying:
Check out om4's guide in general, it will tell u all you need to know...good luck.
Sent from my EVO using xda premium
Your issue is that you need a different kernel for CM10, and it needs to pushed in before you flash the ROM(because you're S-on and hboot 1.15).
This will help: http://forum.xda-developers.com/showthread.php?t=1847860
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah... I realize now after research... I installed it through ROM manager. Not again. Ugh
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Im now using TWRP. Everythings working again. Thank you.
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 am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
TejasEric said:
I am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
Click to expand...
Click to collapse
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
thicklizard said:
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Recovery: Team Win Recovery Project v. 2.3.1.0
Wipe Cache, Davlik Cache, Factory Reset (figured it couldn't hurt?) System, and even wiped Android Secure (to see if it helped this situation)
What is your baseband? Have you updated firmware? If not that can be the culprit...and also how do you restore,? Use tibu for apps only or are you restoring system data?
Sent from my EVO using xda premium
I forgot to update those things I'll try that. Thanks. I use titanium only for apps not system data.
Appears to have worked. Thank you for reminding me of that. I always did that on my OG Evo but forgot on this phone.
Sent from my EVO
Upgrade your twrp also through goomanager
Sent from my EVO using xda premium