Develop Bugs

Having a huge problem with my phone not wiping.

Okay, I was on AOKP M4 and I wanted to upgrade to M5.
So I backup everything and make a backup of my ROM. I wipe the phone and caches and flash M5 with the GAPPS, with the latest CWM touch recovery. When my phone reboots I notice I have the same wallpaper as before and when I unlock my phone my pin is still requested and all of my apps and settings stayed exactly the same. I was never asked to sign into my Google account and the start up/set up screen never came up. I checked to see if I even updated and yes I was on M5. Now the ROM isn't very fast or smooth and I get a lot of force closes and things not working properly.
I tried the whole process again with the CWM non-touch recovery, and again my phone did not fully wipe and all my apps and setting remained exactly the same.
I tried it again with the TWRP touch recovery, and again my phone did not fully wipe and everything was the same and my phone remains kind of slow and I'm getting a lot of force closes.
Why is my phone not fully wiping? What can I do to fix this?
I would really appreciate some help!

you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.

zephiK said:
you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.
Click to expand...
Click to collapse
Yes, that is what I'm doing. I'm wiping factory/data and I'm still having the same problem

Like with the TWRP recovery, I went to wipe, I hit factory reset, then cache, then dalvik cache and then flashed the ROM and GAPPS and all my apps and settings stayed the same. It was like if I had dirty flashed it. I don't understand what's going on.

zephiK said:
you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
***FORMAT /SYSTEM*** (under mount in CWM I believe)
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.
Click to expand...
Click to collapse
Try that additional step too. May or may not help
Sent from my Galaxy Nexus using XDA

killyouridols said:
Try that additional step too. May or may not help
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
What does that do exactly? Would I have to worry about my media and sd card being wiped?

SubyWill said:
What does that do exactly? Would I have to worry about my media and sd card being wiped?
Click to expand...
Click to collapse
No, all music, pictures ect will still be in place.
Sent from my Galaxy Nexus using XDA

Okay thank you, I guess this time in TWRP I'll do factory reset, cache, dalvik cache, and system and see if it works out

Okay, so I did factory reset, cache, dalvik cache, and format system.
I flashed M5 and GAPPS, rebooted and everything was still the same. My phone did not fully wipe.
I don't understand what's going. I'm so frustrated right now

SubyWill said:
Okay, so I did factory reset, cache, dalvik cache, and format system.
I flashed M5 and GAPPS, rebooted and everything was still the same. My phone did not fully wipe.
I don't understand what's going. I'm so frustrated right now
Click to expand...
Click to collapse
I would do a factory reset, if that doesn`t help flash a stock rom and root your phone again. BTW don`t you have a nandroid backup to revert to

gee2012 said:
I would do a factory reset, if that doesn`t help flash a stock rom and root your phone again. BTW don`t you have a nandroid backup to revert to
Click to expand...
Click to collapse
I have a nandroid backup, but that doesn't solve the problem of my phone not wiping.
I guess I'll unroot my phone and lock the bootloader and re-do everything to see. I don't understand why my phone isn't wiping correctly.

sometimes cwm just doesnt work with factory wipe. i've used it a few times now and sometimes it works and sometimes it doesnt. i have no idea why. you can try doing a factory wipe from the phone settings>backup and reset. ive only done that twice but it worked both times. if that still doesnt work just go with a fresh flash of google images using fastboot.

SubyWill said:
I have a nandroid backup, but that doesn't solve the problem of my phone not wiping.
I guess I'll unroot my phone and lock the bootloader and re-do everything to see. I don't understand why my phone isn't wiping correctly.
Click to expand...
Click to collapse
Init.d folders can only be wiped with a factory reset afaik, or manualy off course. By locking and unlocking the phone you perform a factory reset anyway, so i would flash a stock rom and start fresh. No chance on left files or scripts. You can do it with GNex Toolkit, option 8. Put the downloaded and not extracted .tgz file here C:\Galaxy Nexus ToolKit\put_google_factory_image_here and flash.

Thanks guys, I'll try that!

[Q] Installing JB help please

Ok so I downloaded a JB rom rebooted in CWM touch I then
wipe data /factory reset
Wipe cache partitions
Wipe dalvik cache
Format system
Format cache
Format data
And flashed the rom
I reboot and it gets stuck sometimes in the Google screen or the X screen
I have left it booting for 1hr and nothing
Due system/cache /data have to be unmounted?

hi there, only thing you must do is to wipe factory, and wipe cache, dont wipe and format other things there.. if you have a back up of your prevoius stock rom, restore it again to restore all you had been formated, to restore your phone to normal, and install again your jelly bean rom but this time just wipe cache and wipe facetory thats all you need to do. sorry for the english

Has pestname
ricoraf said:
hi there, only thing you must do is to wipe factory, and wipe cache, dont wipe and format other things there.. if you have a back up of your prevoius stock rom, restore it again to restore all you had been formated, to restore your phone to normal, and install again your jelly bean rom but this time just wipe cache and wipe facetory thats all you need to do. sorry for the english
Click to expand...
Click to collapse
Alright I'm trying that right now thanks a million

kingviper10 said:
Alright I'm trying that right now thanks a million
Click to expand...
Click to collapse
It's pass the Google screen now in the glowing X screen its been on for like 15 min is that normal?

Its should not take that long after flashing the rom max time it takes is 5 mins for me will be same for all there must be something wrong

CMW Touch usually does not play well with JB.
Try flashing with an older CMW.

Alright thanks for the help restoring back to aopk 40 and going to flash a older cwm then rebooting into cwm wipe factory and cache then JB v3 then rebooting it hope fully it works

Good luck, hope it works out for you.

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.

[Q] Desire stuck on CM boot after first reboot

Hi,
I recently rooted my htc desire, unrevoked method, flashed default recovery. Before flashing the stable CM for Desire, I wiped dalvik cache, wiped all data, wiped cache partition. After the installation, I logged into my google account. Problems started when going into settings resulted in going to blank settings page. Same goes for any settings window (system, play store settings). Whats more, after every single CM I install, the phone gets stuck on CM loading screen, after installing the rom, setting everything up and rebooting for the first time. The phone is S-ON. I'll try to upload logs from debugger soon.
Thanks in advance for any help.
http://pastebin.com/Zy6jKANt Log from exact loop during loading
Disregard those settings part above, its non existent now, just the loop.

macolour said:
Hi,
I recently rooted my htc desire, unrevoked method, flashed default recovery. Before flashing the stable CM for Desire, I wiped dalvik cache, wiped all data, wiped cache partition. After the installation, I logged into my google account. Problems started when going into settings resulted in going to blank settings page. Same goes for any settings window (system, play store settings). Whats more, after every single CM I install, the phone gets stuck on CM loading screen, after installing the rom, setting everything up and rebooting for the first time. The phone is S-ON. I'll try to upload logs from debugger soon.
Thanks in advance for any help.
http://pastebin.com/Zy6jKANt Log from exact loop during loading
Disregard those settings part above, its non existent now, just the loop.
Click to expand...
Click to collapse
You should s-off before installing any custom rom. Did you make a backup before installing cm7?

abaaaabbbb63 said:
You should s-off before installing any custom rom. Did you make a backup before installing cm7?
Click to expand...
Click to collapse
Wow, really? Some custom gb seemed to work just fine with s-on. I think I have a backup but I wouldn't count on it, it may have some files missing. I'm not sure now whether unrevoked did s-off on that phone, will check as soon as I get back to it.

macolour said:
Wow, really? Some custom gb seemed to work just fine with s-on. I think I have a backup but I wouldn't count on it, it may have some files missing. I'm not sure now whether unrevoked did s-off on that phone, will check as soon as I get back to it.
Click to expand...
Click to collapse
You don't have to s-off to install custom Rom, only a custom recovery.
However it is much more useful to have s-off than not so it's thoroughly recommended.
For instance, you can change hboot to use your internal memory partition layout and have more space. Currently you are on stock hboot with 250MB /system but your Rom system size is much less, so you are wasting space.
Changing hboot will give you smaller system and more internal memory
S-off will also allow you to change recovery to something like 4ext (see my sig), allowing more reliable and easier partitioning of sdcard.
Regarding your specific problem, not sure you did a proper full wipe before installing? Need to use the wipe data/factory reset option within recovery as a minimum before installing new rom

eddiehk6 said:
Regarding your specific problem, not sure you did a proper full wipe before installing? Need to use the wipe data/factory reset option within recovery as a minimum before installing new rom
Click to expand...
Click to collapse
Every single install, wiping data, cache, dalvik cache as well. Everything done from within recovery. Logs indicate a problem with hw audio decoding, though I might be wrong.

macolour said:
Every single install, wiping data, cache, dalvik cache as well. Everything done from within recovery. Logs indicate a problem with hw audio decoding, though I might be wrong.
Click to expand...
Click to collapse
did you specifically use the "wipe data/factory reset" option within recovery, or only the "format data" option under mounts and storage?
the "wipe data/factory reset" also formats the /system partition, which is just as important /data. cache and dalvik are just temporary files, should get wiped anyway on fresh rom install, but no harm in manually wiping.
haven't had time to look at the logs, not an expert in them anyway. you could try to install a different ROM to see if you have the same issues, or restore a nandoid (hope you made one, you should always do this before wiping/flashing).

eddiehk6 said:
did you specifically use the "wipe data/factory reset" option within recovery, or only the "format data" option under mounts and storage?
Click to expand...
Click to collapse
Wipe data. I'll try to make other roms work.

[Q] HELP. HTC One X Stuck in bootloop. Almost all famous solutions tried out

So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?

anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there

dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing

anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha

anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks

Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.

Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help

Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.