Database Info

[Q] Can't factory reset, gives strange error in CWM

I have a US Verizon launch day Xoom that has been rooted since day one. It has been trouble free until now. I recently attempted to upgrade to 2.1 Hammerhead from MantaRay and I got this error in CWM verTiamat R4c-100611 while I was doing a factory/data reset "Error Removing /data/data/com.google.android.location/file/cache.wifi."
I noticed the error but rebooted the system anyway. When I rebooted I was now on Hammerhead 2.1, but noticed several problems. One being I lost function in the Home softkey. I also noticed all my apps and data were still intact as I left them on MantaRay. I like to start fresh with a factory/data reset whenever changing roms to avoid issues so I went back and attempted another wipe and flash of Hammerhead. I got the same error in CWM verTiamat R4c-100611. I rebooted to the same problems in the ROM.
Thinking it might be a problem with the recovery, I reflashed CWM verTiamat R4c-100611, flashed Team Rouges CWM v1.0, and finally reverted back to CWM verSolarnz 120511-2030, and got the same error every time I would attempt a factory/data reset.
I then attempted to do a factory/data reset from within the privacy menu in the ROM. I got the screen with the android and the triangle/exclamation point overhead when I tried. I also unistalled a few apps and cleared data on the google ones. No matter what I do I can not erase the data.
I did some searching around but could not find any info on this specific error. Im hoping I missing something and it is an easy fix. I'm running out of ideas tho. Any advice would be much appreciated!
Pic is of the error message I get no matter what recovery I use.

polarized said:
I have a US Verizon launch day Xoom that has been rooted since day one. It has been trouble free until now. I recently attempted to upgrade to 2.1 Hammerhead from MantaRay and I got this error in CWM verTiamat R4c-100611 while I was doing a factory/data reset "Error Removing /data/data/com.google.android.location/file/cache.wifi."
I noticed the error but rebooted the system anyway. When I rebooted I was now on Hammerhead 2.1, but noticed several problems. One being I lost function in the Home softkey. I also noticed all my apps and data were still intact as I left them on MantaRay. I like to start fresh with a factory/data reset whenever changing roms to avoid issues so I went back and attempted another wipe and flash of Hammerhead. I got the same error in CWM verTiamat R4c-100611. I rebooted to the same problems in the ROM.
Thinking it might be a problem with the recovery, I reflashed CWM verTiamat R4c-100611, flashed Team Rouges CWM v1.0, and finally reverted back to CWM verSolarnz 120511-2030, and got the same error every time I would attempt a factory/data reset.
I then attempted to do a factory/data reset from within the privacy menu in the ROM. I got the screen with the android and the triangle/exclamation point overhead when I tried. I also unistalled a few apps and cleared data on the google ones. No matter what I do I can not erase the data.
I did some searching around but could not find any info on this specific error. Im hoping I missing something and it is an easy fix. I'm running out of ideas tho. Any advice would be much appreciated!
Pic is of the error message I get no matter what recovery I use.
Click to expand...
Click to collapse
That is strange and troubling, if indeed this problem just came out of nowhere. I know that you can wipe data in fastboot, though I can't remember the exact syntax right now, but it should be available.
On edit: try: fastboot erase userdata. & fastboot erase cache
I think you do need to wipe/factory reset between Manta Ray and Hammerhead as the framework was changed/fixed, among other things.

Thanks Okantomi! Your advice worked perfect.

Must wipe dalvik to reboot?

Hi
I'm loving this paranoid android rom (2.53), which I just installed a couple of days ago. Since yesterday I'm having a weird problem though:
Every time I reboot the device hangs at the PA loading screen. I've figured out that rebooting into recovery and clearing the dalvik cache allows me to boot, but then a message comes up saying 'Android updating... optimizing apps', and it goes through and optimizes them all...
So, I can't reboot without this issue.
WTF?
Thanks!

current version are 3.56... you might be using the one that have that bug in its kernel
go to this thread to download a new one.
http://forum.xda-developers.com/showthread.php?t=2139747

Major breakage: phone hangs at unlocked bootloader after first reboot of custom rom

Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?

Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.

angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!

solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.

solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.

I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?

i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"

same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.

Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.

How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.

[Q] Gapps and other processes keep crashing

yesterday I made a backup of my android phone using clockwork mod. After that I installed CM11 and flashed gapps it was working just fine. But I decided to restore to my old backup. So I whipped the phone cache and did a factory reset. But when the restore finishes and I restart my phone the phone becomes practically unusable. It says Unfortunatley the proceses com.google.gaspps has stopped. So every time I press ok the processes says the same thing along with other proceses that keep crashing. My phone is a s4 and the back up was of Kitkat 4.4.2 touchwiz.

try clear all gapps (playstore,gmail,google sync,etc) data and cache

reflasher said:
yesterday I made a backup of my android phone using clockwork mod. After that I installed CM11 and flashed gapps it was working just fine. But I decided to restore to my old backup. So I whipped the phone cache and did a factory reset. But when the restore finishes and I restart my phone the phone becomes practically unusable. It says Unfortunatley the proceses com.google.gaspps has stopped. So every time I press ok the processes says the same thing along with other proceses that keep crashing. My phone is a s4 and the back up was of Kitkat 4.4.2 touchwiz.
Click to expand...
Click to collapse
I have the same issue. i tried everything but when i restore a backup upon restart the phone GAPPS process crashing.
so just for checking i factory reset phone and take a backup. when i restore that fresh backup, it show same result.
any help will be highly appreciated.

April 2016 CM13 update - soft brick - Google Play lockscreen error

Hi - My OnePlus One is the one I purchased from OnePlus One - with all the over the air upgrades.
The most recent was the April 2016 CM13 marshmallow upgrade - but this causes a permanent Google Play Services error - which freezes the screen (soft brick) - right after any reboot.
I'm considering doing a factory reset - (I understand that the process is to hold the volume button down while rebooting?) - but I wanted to check if there were other, better options for fixing this?
Thanks!

I am having the same issue..
after every boot up it gets stucked at lockscreen and doesnt allow me to do anything.... after 2-3 minutes gets automatically restarted..
Please Help

So, i own an OPO, stock, running COS 13 ( received update a few days ago). No ROOT, no Bootloader unlocked.
Today, early in the morning (My local time) I restarted my OPO because my Google Fit was not able to record my activity. After the reboot, i tried to unlock my phone, but it got STUCK. Freeze if you will.
I tried from Cyanogen Recovery to Wipe Cache, it did not worked.
I tried from Cyanogen Recovery to Wipe Data, it did not worked.
i do not the reason for wipping not working but i was scared. Because whenever a tried to boot into system, I was stuck at lockscreen
I tried to perform a wipe from adb, but adb shell was printing a "error closed". So i got scared .
I thought that i could fix my issue by performing a Wipe...
I Download the OPO toolkit. Put my device into fastboot, and unlocked my bootloader ( yes i void my warranty). After that, the toolkit installed the TWRP ( Custom Recovery ) with just one click.
Then i boot into recovery and perform a wipe. Phone was no longer stuck at lockscreen (actually i lost all data)
After that, my phone has been working great. (more than 12 hours from the issue)
Good luck mate.!

Hi all,
Having the same problem, I'm inquiring me about a way to fetch data from the devices. Is there any way to pull data from an encrypted device?

Also had the lockscreen error after the update.
I did:
Wipe Cache,Dalvik, System but not Data
Install Full Rom (COS 13)
Install SuperSU Beta
Reboot
wipe cache/dalvik/system, not data
Afterwards i could login but play services crashed every second. Then I allowed play services all rights again in privacy settings.
Rebooted and i could not get past lockscreen any more.
I restored my last backup, updated all apps, allowed all google apps without restrictions in privacy, cleared their caches.
Disabled lockscreen.
Restarted and updated as above but did not Install SuperSu beta directly.
System booted fine. Then I installed SuperSu beta again. Still no problems
Hope this helps or gives some hints on the cause.