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.
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
I am running my Xperia Z3 on various AOSP ROMs. However, I am encountering this problem: after I have booted the phone up successfully for the first time, some times after that, I reboot the phone and it will try to rebuild the cache (as if I just wiped the cache) and will get stuck somewhere or enter a bootloop. when it finished (Starting app...) The only way I can get out of this is to wipe everything and start over. What's the problem here? Is it a ROM that's causing the issue? Or is it a specific app? I am honestly losing my mind because I've owned 6-7 devices and have never seen this behavior before.
maybe you should ask this on the various Rom's thread
Hello,
I've had cm13 on a d320n lg phone for about a year now and today i decided to wipe caches and reset the device and wanted to reboot to twrp to do it but for whatever reason i can't because twrp freezes (for a loooong time and i have to reset).
I decided to wipe and do a fresh start since i'm getting a lot of "Unfortunately [App] has stopped working".
Um. am i missing something ? running 13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w5
Hi there,
I went back to stock some days ago. Worked fine so far. OTA to 1.56.401.81.
When I reboot the phone, it ist starting to optimize the Apps again, like it does after an update. When it ist done, it reboots again and begins optimizing the apps again.
Only thing I can do here is reboot to recovery and delte dalvik cache. (also tried data and cache). Still after a reboot it is looping again.
Any idea what I can do about this?
I found the Problem. IT Happens After I disable the Google app in the settings. Could Not find a Solution exept of leave IT enabled.