Develop Bugs

[Q] Best Way to get Super Wiped?

I tried a ROM update today (Magnolia) and my phone is now seriously slow (including SpeedTest which shows about 50Kbps download speed). I attempted to reinstall the same ROM and to restore a Nandroid (neither of which has helped). I did every wipe present in CWM v2.5.1.2 (I know v3.x.x.x is not a good wiper) and in HBOOT, also all to no avail.
It is possible that the ROM is focused on carefully updating itself rather than completely overwriting.
Does anyone have a recommendation as to the best way to really ensure that no old runaway processes are surviving the flashes (ROM or Nandroid)? I am wondering if flashing another ROM would do it (it wouldn't try to update), but am very open to suggestions.
Thanks!

I had the same problem when I would install a rom with the CW 3.0.0.8 and it will just update the current rom, and not do a full wipe like I just to get before with the CW 2.x.x.x what I have done to get a clean install is this...
- I dont use the Rom Manager no more to update...
- Boot into Recovery and do the Following before you install a new Rom..
1-) Wipe Data/ Factory Reset
2-) Wipe Cache Partition
3-) Install the Rom .Zip with CW
Thats how I have done it before hope it helps...

Dont use rom manager to install go into recovery. Do a factory reset twice, then goto mounts and storage and format manually, data, cache, system, boot. Do that twice or more and youre super wiped as you put it. But as far as magnolia goes...did you make sure that you dl'd the flashover and not the whole rom?
Sent from my ADR6300 using XDA App

Thanks
Pete - Thanks. I never use RomManager to do ANYTHING (and remain surprised that people do). I do factory reset and wipe in CWM but never formatted system; which I just posted in the Magnolia forum as being what I thought is causing all the trouble. At least this lets me know how to manually do it. Thanks

1107963 said:
I had the same problem when I would install a rom with the CW 3.0.0.8 and it will just update the current rom, and not do a full wipe like I just to get before with the CW 2.x.x.x what I have done to get a clean install is this...
- I dont use the Rom Manager no more to update...
- Boot into Recovery and do the Following before you install a new Rom..
1-) Wipe Data/ Factory Reset
2-) Wipe Cache Partition
3-) Install the Rom .Zip with CW
Thats how I have done it before hope it helps...
Click to expand...
Click to collapse
Building on this- I do EVERYTHING from recovery. In addition to the steps listed I also go to "mounts and storage" and wipe /system, /data, /cache, and /boot. Eradicate!
Sent from my ADR6300 using XDA Premium App

I gave out a loud guffah when reading this thread title. Maybe stuff's just funnier before having coffee.

johnchad14 said:
I gave out a loud guffah when reading this thread title. Maybe stuff's just funnier before having coffee.
Click to expand...
Click to collapse
Right? Super Charmin came to mind right away.
Sent from my ADR6300 using XDA App

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?

i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App

KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.

If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed

snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?

Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk

Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.

eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.

Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?

teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.

Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!

I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.

Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.

SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?

when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu

Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk

[Q] Problem flashing GingerTiny

Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?

prinzmetal6 said:
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
Click to expand...
Click to collapse
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.

cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Thank you!

cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Just to add to this. NEVER wipe data after flashing a Sense 3 or Sense 3.5 ROM. Actually even some Sense 2.1 ROMs that is a bad idea.
This is because the way these ROMS are built as the storage in /system cannot hold the whole ROM so they have to build part of it in /data. So wiping data will clear the ROM components as well as the user data. If you have to wipe data, plan to reflash the ROM again. So I say don't wipe data AFTER flashing the ROM unless you plan on reflashing the ROM. You can and will probably need to wipe data before flashing the ROM though.

Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?

prinzmetal6 said:
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
Click to expand...
Click to collapse
Make sure USB debuggging is on. If it is, I don't know.

I think the problem is that I ran out of internal memory, I have a huge sd card so I think I can solve this problem. Thank you for replying though. I would've posted something on the actual rom page but I don't have enough thumbs up

CM10 bootloop

I am new to rooting and rom'ing. I was able to root my Hercules using clockwork 6.0 and was in the process of installing cm10 and it froze up, and after i rebooted it got stuck in a boot loop. I did do a back up of my stock rom and have gotten it to factory reset back to astock rooted rom, not sure if it is my backup stock rom. The process that I read to rom it is to install darkside wipe, then cm10, then gapps. I have wiped data, cache and davlik cache, i am trying to get it to install cm10, but it doesn't seem to want to install. what should i do to get it to start over and get cm10 rom on?

I would only use the Darkside wipe scripts on CWM 5.X. Use Odin to reflash the recovery of your choice and then format system, factory reset, and then flash CM10.
Sent from my Nexus 4 using xda premium

Thanks, I didn't know that, guess the instruction i found were a little outdated. I'll try your suggestion. What do mean by formattin it? (I thought the factory reset does that?) Also how long should it take for cm10 to install?

heath.bse said:
Thanks, I didn't know that, guess the instruction i found were a little outdated. I'll try your suggestion. What do mean by formattin it? (I thought the factory reset does that?) Also how long should it take for cm10 to install?
Click to expand...
Click to collapse
Formatting the system only formats the /system partition and wipe data formats the /data partition.
What do you mean?
Sent from my Nexus 4 using xda premium

I would have made a backup of the stock rom then from the stock rom downloaded goomanager from play store then flash newest twrp recovery, then wiped and installed a appropriate ROM
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 06:33 AM ---------- Previous post was at 06:27 AM ----------
Of course your stock rom would have then needed to be rooted
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

heath.bse said:
I am new to rooting and rom'ing. I was able to root my Hercules using clockwork 6.0 and was in the process of installing cm10 and it froze up, and after i rebooted it got stuck in a boot loop. I did do a back up of my stock rom and have gotten it to factory reset back to astock rooted rom, not sure if it is my backup stock rom. The process that I read to rom it is to install darkside wipe, then cm10, then gapps. I have wiped data, cache and davlik cache, i am trying to get it to install cm10, but it doesn't seem to want to install. what should i do to get it to start over and get cm10 rom on?
Click to expand...
Click to collapse
You missed /System as well [hence why the stock ROM booted again otherwise if you actually formatted where the ROM was there is no backup ROM.
You should move to Jellybean [I have used ParanoidAndroid as a daily druver for months now and it is newer [Android 4.1.2].,
No matter which ROM you choose, first boot phone
download ROM Manager [Free is fine]
Open it, grant Super User
Tap top-most option to install Clockwork Recovery and it will walk you through getting etiher the non-touch for free or paying $2 for touch recovery [unless you flashed that via Odin then skip], but need to be sure you have newest CWM and not an old one from a rooting guide that been around.
Boot to recovery wi[e cache
tap advanced wipe dalvick
go back one menu
go to mounts and storage tap to wipe system, and data
go back one menu to main
tap install zip from SDCard
Tap internatl or external wherver you saved it and find the CM 10 you downloaded and tap and flash it
do the same but find where you saved the gapps pack
now restart device and enjoy

continual boot loop...tried everything here.
RealPariah said:
You missed /System as well [hence why the stock ROM booted again otherwise if you actually formatted where the ROM was there is no backup ROM.
You should move to Jellybean [I have used ParanoidAndroid as a daily druver for months now and it is newer [Android 4.1.2].,
No matter which ROM you choose, first boot phone
download ROM Manager [Free is fine]
Open it, grant Super User
Tap top-most option to install Clockwork Recovery and it will walk you through getting etiher the non-touch for free or paying $2 for touch recovery [unless you flashed that via Odin then skip], but need to be sure you have newest CWM and not an old one from a rooting guide that been around.
Boot to recovery wi[e cache
tap advanced wipe dalvick
go back one menu
go to mounts and storage tap to wipe system, and data
go back one menu to main
tap install zip from SDCard
Tap internatl or external wherver you saved it and find the CM 10 you downloaded and tap and flash it
do the same but find where you saved the gapps pack
now restart device and enjoy
Click to expand...
Click to collapse
I got cm10 on for about 20 minutes then CWM updated to 6.x. I flashed a nightly and it's been in a bootloop ever since. However, when I was on CM10 those few brief minutes I could not hear or he heard on a call.
No idea what to do now. I'm stuck on 2.3.6 unless there's some other trick I can do to get this thing to boot...

Why not just try a different rom? Lots of options out there.
Also, watch the dates on the how to's you read. A lot can be outdated.
Sent from my cell phone telephone....

Messaging and Phone apps keep crashing

Hey all,
I've been searching for a while now and decided I should just post my question finally. I have the Galaxy SIII, rooted, and running CM10 stable. For the last 3 months or so, my SMS app, Messaging, has been randomly force closing and crashing. The only way to fix it is by rebooting the phone. I've tried re-flashing the mod 5 times, and even wiped data and done 2 factory resets. Still no luck.
And more recently my "phone" app has been doing it too. It crashes when I open up the dial pad and drops calls randomly and I have to restart my phone for it to work again.
Both of these will happen randomly. Sometimes I can go 4 hours without having to restart my phone, other times I have to restart my phone every 20 minutes. It's really starting to bug me.
Is there an app that's known to cause these crashes? Or is there a possibility that the mod file is corrupt? Thoughts? Questions? Any help is appreciated!!

When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.

xBeerdroiDx said:
When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.
Click to expand...
Click to collapse
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?

tango259 said:
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one

xBeerdroiDx said:
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one
Click to expand...
Click to collapse
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.

tango259 said:
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.
Click to expand...
Click to collapse
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results

What the???
xBeerdroiDx said:
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data <------------- ????
Reboot
I can't see this is a good thing, but I'm a noob.
You're saying after installing the new ROM and apps (Flash rom Flash gapps), you then go back into CWM and select 'wipe data/factory reset'??
Again, I'm a noob and maybe I'm reading this wrong!
Doing a wipe again right after installing a new ROM sounds so wrong to me.
What would that do?

RoidRulez said:
Wipe data <------------- ????
Click to expand...
Click to collapse
This step (step 7 in your list) isn't necessary.
When in doubt, follow the directions in the OP of the rom you are trying to flash, usually can't go wrong.