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.
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
I'm truly lost for how to fix this. I'm trying to restore my phone to factory and I've wound up with major issues with the phone when it starts up. I get immediately those messages you get when a process dies: "Unfortunately, the process com.google.phone has stopped." I get this message for a huge range of apps, as far as I can tell it may be all or most of the built-in system apps, one after the other. I can't access settings or anything.
I tried restarting into fastboot and using "flash-all.bat" to wipe everything and install the stock images, then booted into recovery and attempted to wipe the data. I got everything wiped, or so I thought, but then the same problem still occurs when it starts up. How is this possible? Surely there could be nothing remaining of the old system on there at this stage?
After you flash factory images, there's no need to go in recovery again. Also, when setting up google account, don't sync app data.
I updated to PA 5.1 when I got the notification and now I am stuck in a boot loop. My device is unrecognized when plugging into my computer, even when using ADB. I'm looking for a way to save my data (pictures, videos, apps, etc) while restoring my phone.
After awhile, I don't know what happened, but I tried backing up my files through TWRP and my phone booted up with everything wiped. I got a notification saying superuser needed to be downloaded (even though I had it downloaded it before) and went through the steps, now I'm stuck in the boot loop again. At this point I just want to get my phone up and running again as I think my data is all gone...
Someone said that I may have a big issue as when I open up cmd and run "adb devices" nothing shows up, any help is appreciated thanks in advanced!
Also, I do not mind a fresh wipe if necessary.
P.S. I'm a total noob with this stuff so yeah...I may need the simple stuff explained as well lol
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.