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.

[Q] Issues after upgrading to LMY47I

Hi All,
I did an upgrade to 5.1 (LMY47I) on my Nexus 5 and started facing some strange issues and have no clue on how to resolve them. Before the upgrade I had the following config:
Recovery: TWRP
Root status: Rooted
ROM: Stock 5.0 LRX22C
I used following method for the upgrade: http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
It was successful but post that I came across few issues as below:
1. Power button functionality was erratic. Sometimes it would lock my mobile but at other times it was locking and waking up my phone immediately. At times "Power Off" popup was also showing up. While I tried to figure out reason for that, trying power button multiple times, my phone rebooted and started the "Optimising Apps" sequence once again. It happened again a couple of times and so I decided to try out factory reset (since I hadn't done that after upgrading).
2. I did a factory rest from Settings. After factory reset, apps and other settings were gone but I noticed that user data in the storage was intact. I guess that also gets removed on a factory reset. Am I wrong on this one?
3. I wanted to install Cerberus as a system app and so I downloaded its zip from the website and flashed using recovery. I was surprised to see that the app wasn't showing after booting up. I tried couple of times more but got no success. So, I decided to install it from Play store and convert to system app using Link2SD. When I tried doing that, Link2SD gave me an error saying "/system: not enough storage space". I tried converting few other apps but got same error. Any thoughts on what could be going on here?
Thanks,
Anurag

crypticlight said:
Hi All,
I did an upgrade to 5.1 (LMY47I) on my Nexus 5 and started facing some strange issues and have no clue on how to resolve them. Before the upgrade I had the following config:
Recovery: TWRP
Root status: Rooted
ROM: Stock 5.0 LRX22C
I used following method for the upgrade: http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
It was successful but post that I came across few issues as below:
1. Power button functionality was erratic. Sometimes it would lock my mobile but at other times it was locking and waking up my phone immediately. At times "Power Off" popup was also showing up. While I tried to figure out reason for that, trying power button multiple times, my phone rebooted and started the "Optimising Apps" sequence once again. It happened again a couple of times and so I decided to try out factory reset (since I hadn't done that after upgrading).
2. I did a factory rest from Settings. After factory reset, apps and other settings were gone but I noticed that user data in the storage was intact. I guess that also gets removed on a factory reset. Am I wrong on this one?
3. I wanted to install Cerberus as a system app and so I downloaded its zip from the website and flashed using recovery. I was surprised to see that the app wasn't showing after booting up. I tried couple of times more but got no success. So, I decided to install it from Play store and convert to system app using Link2SD. When I tried doing that, Link2SD gave me an error saying "/system: not enough storage space". I tried converting few other apps but got same error. Any thoughts on what could be going on here?
Thanks,
Anurag
Click to expand...
Click to collapse
1- Possibly hardware (power key) issue
2- Factory reset from Android OS *should* erase all user data.
3- Its just that, /system does not have enough free space to put more apps in there. Common issue after Lollipop. Remove some other app from /system, such as Maps, for example, to free up some more space. Be reminded that once you start messing with /system, this will (or might) cause issues with OTA updates.

So I managed to tackle (or at least figured the reason) for all the issues I was having:
1- Yes, there is some issue with the power key. ? But the other issue of optimising apps loop was because I did not do a clean install which disappeared when I did the factory reset after that.
2- After doing some reading on the Internet, I came to know that stock recovery cleans the user data but twrp doesn't by default. Since I had twrp, it just removed apps and settings but retained other data. In order to do a clean install I flashed stock LMY47I again including recovery, userdata etc. (used flash-all.bat). This removed everything from storage and made my phone as good as a new one (software wise).
3- Yes, it was the issue with storage space and was a surprise for me. Thanks for clarifying on that. Before I did a clean install, I tried removing couple of system apps and was able to install cerberus after that via recovery too. However, clean install solved everything.. ☺
Sent from my Nexus 5 using XDA Free mobile app

Nexus 5 hanging, rebooting - initial troubleshooting done, need help on next steps

Hi,
As the title says:
Have a Nexus 5 running the latest lollipop build that has been working properly for a while (Phone is a Google refurb from November 2014, replacing my original N5 that had battery issues; Warranty expired Feb 2015)
4 days ago, it randomly rebooted and then got stuck on the "Optimizing apps" page on initial bootup - would never go past a certain app number
First tried wiping cache - which didn't complete even after 48 hours
Next tried full wipe from recovery, which worked but then shutdowns still happened
Reflashed all stock images (Phone is stock, not rooted) last night - problem still exists with random shutdown - but I can always get past initial setup; shutdown problems happen a little while later during use
Wiping cache from recovery now gives a "Could not mount /cache/" error in recovery
My hypothesis - that there's sector(s) on the eMMC that's borked. It's a 32GB phone - is there a way I can flag off a certain sector as "bad" and put the cache partition somewhere else? Also open to other suggestions, including replacing the eMMC chip if needed (I can find someone set up for BGA work).
I considered doing a file check from Philz / TWRP, but since the issue persists after a full reflash/reformat I assume that it's not a software bug.
Thanks in advance for the help, let me know if there's any other information I can provide that might be useful.

Anyone?

Stagefright OTA update soft-bricks encrypted Nexus 5

I received the Stagefright OTA update notification 3 days ago and installed it 2 days ago on my unrooted Nexus 5 32GB. The installation seemed to progress as normal but during its last reboot as part of the installation it got endlessly stuck at the spinning coloured orbs boot screen. After several hours I rebooted it, and tried that several times more after, but to no avail. Today I tried wiping the cache using Recovery mode, but again no dice.
It seems a 'Wipe data/factory reset' is the only way to fix this, but I'm still curious as to why this happened. After searching the internet I found dozens of people with the same problem on Google's Nexus Help Forum
(its the first result when searching Google for 'forum Jgng3xmHFJg'), but they all had this problem on a Nexus 4 (also stuck at the spinning orb boot screen after a system update). They all had in common that they encrypted their phone. I also encrypted my phone. I have installed other OTA system updates before (I also side-loaded an update once) without a hitch though. I also found other Nexus 5 owners (not sure if they use encryption though) with this problem after the Stagefright update (search Google for 'reddit Newest update bricked nexus5').
Do more people have encountered this problem or are there people who do have an encrypted Nexus 5 who did not encounter this problem? Is there still a way for me to backup data (e.g. via ADB)? Or a way to fix this other than doing a 'Wipe data/factory reset'?

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.