Hey guys,
need some help here. Some time ago (about 4 weeks), my phone started to crash randomly. Example: I was listening to some music, suddenly the music stopped. I thought I accidentially unplugged my earphones, but instead, my phone rebooted, without any further notice. Since then I got those reboots several times a day, not only while listening to music, but surfing the web, doing literally nothing (during work, I suddenly hear my phone reboot while idling in my pocket) or accessing any app installed on my device.
I am rooted and use a custom kernel and a custom rom. At first I thought, maybe there's something wrong with your kernel/rom, so I updated those. (Was on LeoMar75's Revolution Rom 2.5 -> installed 2.7.1; updated to latest Siyah kernel, I think it was 2.0.1 or something) Of course, I did a full wipe, but it didn't help at all. The first day everything looked fine, but then the phone started crashing again. After some more time, I changed to CheckROM RevoHD 2.0 and then 3.1.1. and changed kernel to Siyah. 2.1.1. then DK-kernel 2.1. Always the same results, always random reboots.
In the end, I thought to myself, that custom rom/kernel might not work properly on my device, so I went into cwm, wiped everything, installed stock kernel and flashed original rom via Kies. But, I STILL got those reboots.
Just for the record, when I say "wipe", i mean going into CWM and wiping cache and dalvik chache, batterystats, doing a factory reset and formatting /system, /data, /sdcard and /emmc. But the last time I did this, I noticed that i could not format /sdcard, I could'nt even mount it. I'm on CWM 5.0.2.7. now.
After that much of annoying text, my question is: Am I doing something wrong or is my phone broken? And if I'm doing something wrong, please tell me what, 'cause I'm kinda desperate here...^^
Looking forward to your help
Check to see if any apps are installed to external SD. If so, move them to internal storage. Also, in my experience, uninstall Dolphin HD if you have it on your device.
Sent from my GT-I9100 using XDA App
Hi SaneinOne,
I have no apps installed to my external_sd. I only store some music there. Additionally, I delete all android related folders from my external_sd before inserting it into a freshly flashed phone.
About Dolphin HD, already heared of that, tried it, didn't help.
But thanks for your help
No clues? C'mon guys, please, I'm desperate.
Maybe it a hardware problem ...
Try using warranty.
Dont know what your rom is but .
I would clean phone and start over .
Boot recovery
Mounts and storage FORMAT cache sd card data system
Remove battery
Boot to download mode flash stock rom via Odin .
Clear Custom rom counter with USB jig if needed .
Return to service centre .
jje
tEsT_MaStEr, JJEgan,
thanks for your replies.
I flashed everything back to stock and reset the flash counter with my friends' jig. I returned the phone to my store, they said they'll send it to Samsung to check it up. Let's see what happens...
Yay, 6 weeks without smartphone...
Related
this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!
Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?
Try wiping dalvik/partition/cache before and after installing the custom ROM
I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk
Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk
the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM
@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk
Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk
thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes
and just a thought, but i keep fixating on the .PIT file. your thoughts?
Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium
if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...
1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition
i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?
So I flash the Ics update (LPQ) last friday and all went well, my phone was working perfectly. However on sunday my phone kept freezing and the only was to get it working again was to pull the battery. So because of this i decided to go back to GB and wiped everything and flask a stock firmware (KI8) which is my carrier firmware. Now my phone keeps turns off every 10 minutes or so any it is really annoying. It only seems to happen when the phone is not plugged in to charge and I have tested it out and it doesn't tend to happen in flight mode either. At the moment I have wiped the phone completely and haven't even installed an app yet it is still happening. Has anyone got a clue what this could be as its driving me mad.
Thanks in advance
I have the same problem, i updated to ICS and now my phone reboots every 2 / 30mins.
I tryed lots of roms and now downgraded to a 2.3.3 stock rom, with re-partition, no SDcard .. but still ... it reboots itself a lot .
The strange thing is that it reboots when left alone, the sgs2 can stay up for 3h+ when it plays music on GoogleMusic ...
Oh, and i also tryed with a new samsung 2000mah battery kit, still no changes, so it's not a battery problem
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Thanks, Ill try flash lightning later when i get home. As i think that it is something to do with the radio I have also tried flashing a new modem (KE7) but that did not solve the issue either. It there any app that can monitor processes so that i can look at what is happening just before it turns off.
I had this when I was using MIUI. I flashed Spikes Pure ICS yesterday and haven't noticed it since.
Strange, I had this issue on GB, and not on ICS. Try flashing some different roms, full wipes of course, and see if that helps
bmbm said:
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Click to expand...
Click to collapse
didn't work for me :'(
First factory reset and then flash the ics.
rocky23 said:
First factory reset and then flash the ics.
Click to expand...
Click to collapse
i did a factory reset by using the *2767*3855# command , then i went to the recovery to format data/system/cache/sdcard/emmc .
Still, no luck and getting reboots
Last night I flashed both lite'ning ron and Check rom. Did a full wipe before both and I am still getting reboots and freezes. Think Ill have to get a jig and bring it back to the shop
So just to update. The latest think i have tried is changing the modem to KE3 and I tried the speedmod kernel and the syriah kernel. Still having the freezing issue. Have also tried a kernel cleaner but to no avail. Anything else I should try before bringing it back. Thanks
Why dont you try to install a stock rom, then root it, and within CWM recovery wipe everything, then reinstall your stock rom thru odin
Have tried flashing the stock firmware 2.3.5 KI7 and wiped the cache,the dalvick cache and factory reset the phone before but that didnt work. Is there specific firmwares that will wipe everything?
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
ctomgee said:
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
Click to expand...
Click to collapse
i agree with you i tried this method last year and it worked,, you should try this and if doesnt work format your phone system wipe data, wipe cache , wipe dalvik for a very fresh start..
Yes I thought it could have been the sd card to so I removed it from from the phone and formatted the internal memory, then wiped the dalvik cache, the cache and the phone and flashed a new rom but my phone started to freeze after about 20 minutes. Its weird originally my phone was Freeze and wouldnt wake from sleep, then it would just randomly reboot and now its back to freezing and not waking from sleep
I would try KH3 rom. For me that was the most stable GB rom
Sent from my GT-I9100 using xda premium
Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
kipdeontdekker said:
Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
Click to expand...
Click to collapse
I've exactly the same problem.
Are your wifi and BT still OK ?
Is your IMEI (*#06#) still the same as under the battery ?
Was your phone locked ? Did you buy it with a SIM ?
My problem appeared after flashing several different modems/RILS : I got no error warning anywhere, but after reboot, I completely lost my netwerk connection. (no voice calls , no mobile data)
At first I thought a bad RIL driver, so I restored my Nandroid backup from the day before (after wipe cache/wipe dalvik/format system), but still no connection with the netwerk. and can't even make voice calls.
Then I was in panic !
After this I did a complete factory reset, and wiped/formatted cache/dalvik/system/data/SD-card and went in to download mode. After loading a stock ELLA for my region using Odin, still no connection. I was also never asked to enter the PIN-code for my SIM to unlock it.
Damned, this is an embarrassing situation : I can't think of loosing my SG3 for several weeks if I have to send it to Samsung !!
Mu phone is bought without SIM, so it's not SIM-locked.
My Wifi and BT are still OK, my IMEI is also still OK.
Any other ideas, please ?
How do I come in the service mode for the Radio ?
This is the way my netwerk is indicated : a circle with a stripe, much like the famous traffic sign.
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
kipdeontdekker said:
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
Click to expand...
Click to collapse
Good to hear your problem is fixed !
I'm still not able to make voice calls or enable mobile data : "insert SIM card" is the message I get.
I did already twice a full reset/factory restore and flash a stock ROM using PC Odin, but no avail.
Today I did a restore from my EFS folder using a backup that a had made before the problem appeared, but no avail.
BTW, did you also have the same indication from network status as on my screen-shot ?
Any idea what else I can try ?
I'm getting desperate .....
I'm having the same trouble after doing backup in TWRP when boot up it doesn't recognize the sim card.
I've flash CM10.1 and it only work after i remove the card e put it back on.
Try to see if it something about the simcard.
Regards,
Rui
Hi All,
I have a weird problem. My galaxy S2 is getting crashed when I use some apps like,
sync up with GMail, play TempleRun game etc., suddenly screen goes blank, and nothing happens. And when I restart, it crashes again during booting.
But surprisingly this crashing is not happening when I do the same while connected to external power, i.e., when it is charging.
I thought it might be with ROM, so i've flashed different ROMs like, RootBox, CyanogenMod etc., but still it is getting crashed.
Even I changed Kernels also, Dorimanx, Siyah and even base kernel which comes with Cyanogenmod too.
So any body could help me out ?
I tried to get the log, but don't know how to check/get the log where I could see the crash file/app.
Regards,
Hereticnine.
hereticnine said:
Hi All,
I have a weird problem. My galaxy S2 is getting crashed when I use some apps like,
sync up with GMail, play TempleRun game etc., suddenly screen goes blank, and nothing happens. And when I restart, it crashes again during booting.
But surprisingly this crashing is not happening when I do the same while connected to external power, i.e., when it is charging.
I thought it might be with ROM, so i've flashed different ROMs like, RootBox, CyanogenMod etc., but still it is getting crashed.
Even I changed Kernels also, Dorimanx, Siyah and even base kernel which comes with Cyanogenmod too.
So any body could help me out ?
I tried to get the log, but don't know how to check/get the log where I could see the crash file/app.
Regards,
Hereticnine.
Click to expand...
Click to collapse
When installing a ROM.
What is the procedure you follow?
It should be this:
1) Factory reset
2) Flash ROM (Rootbox stable version 4.2 for example, make sure you check the md5 sum to make sure it is not a corrupted file)
3) Flash GApps
3) Wipe cache
4) Wipe Dalvik cache
5) Boot device, leaving everything default (kernel etc.)
Then try if everything works without crashing.
kuijkens said:
When installing a ROM.
What is the procedure you follow?
It should be this:
1) Factory reset
2) Flash ROM (Rootbox stable version 4.2 for example, make sure you check the md5 sum to make sure it is not a corrupted file)
3) Flash GApps
3) Wipe cache
4) Wipe Dalvik cache
5) Boot device, leaving everything default (kernel etc.)
Then try if everything works without crashing.
Click to expand...
Click to collapse
Hi,
I did a clean install with full wipe. Still I'm facing this weird crashing problem.
And crash is not happening when I'm in charging mode i.e., when S2 is connected to power cable, its happening only when I use the mobile on battery.
Regards,
Hereticnine.
You are absolutely sure this happens on a clean, full wipe factory reset etc., install?
Because if it is, I'm afraid you are facing with a hardware issue.
The battery could be broken (age, water damage, bumps) somehow for example.
If it is hardware related, to me it seems to be a failing battery (although I'm not an expert).
You could try borrowing a battery from some1 and see if the problem still exists.
Last resort is really flashing stock ROM through ODIN, maybe this will fix the issue.
If this isn't the case you should probably bring it to a service depot for repair (also why you will need to have a stock ROM on your device).
Try to flash stock ROM...see this: http://forum.xda-developers.com/showthread.php?t=2365701
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app