I tried to use TWRP last night to wipe my data partition before flashing Syngergy to my phone. It would instantly give an error message that the wipe failed. I assume I could use adb to wipe the data, but would like to figure out what may be causing this to fail.
Does any one have any suggestions as to what might be causing this, or perhaps some steps to troubleshoot? I thought about attempting to rebuild the filesystem through the shell, but wanted to see if anyone had experienced this problem first.
Related
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
EDIT (Update):
I tried accessing the Xoom through ADB, and try to delete manually the pesky file. I was succesful. When I tried another "wipe data" from the recovery, I got a similar error:
Error removing /data/data/com.android.browser/databases/autofill.db (another file)
When I tried to delete it, I got the following error message (through adb) [why did it work the first time and not now???]
rm: can't remove 'autofill.db': Read-only file system
Any help, please? I'm at a loss here...
I post some photos of the errors
iruiz2 said:
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
Any help, please? I'm at a loss here...
I post some photos of the errors
Click to expand...
Click to collapse
have you tried re-flashing the rom completely?
daley stephenson said:
have you tried re-flashing the rom completely?
Click to expand...
Click to collapse
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
iruiz2 said:
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
Click to expand...
Click to collapse
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
daley stephenson said:
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
Click to expand...
Click to collapse
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
iruiz2 said:
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
Click to expand...
Click to collapse
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
daley stephenson said:
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
Click to expand...
Click to collapse
I will try this, as a last resort. Now I am making a backup of my internal sd card, because this process will delete everything in it. In case somebody wonders how to do this (I didn't know it myself), I used adb. The exact command I used was:
adb pull /data/media .
It's taking ages to backup my internal sd files (at a rate of 7Gb/hour aprox).
Meanwhile, anybody knows what possibly is happening to my Xoom?
After wating several hours to back up my internal sd card, I have been able to wipe (format) /data from fastboot. In case somebody needs to do something similar:
Once in recovery, type in your computer:
adb reboot bootloader (wait for the xoom to reboot into fastboot)
fastboot erase userdata
I then rebooted into recovery, and restored a nandroid backup. This time, no problems.
Now I am in the (again) long process of copying the /data/media files back to my Xoom, but I was VERY relieved to see that it was booting normally after this...
glad you got it fixed dude
Has anyone had issues with ROMS showing "failed" in TWRP, or just locking CWM up and requiring a battery pull? I have checked the MD5 and they always match. I have also flashed a ROM, tried something else, and when I try to reflash the original ROM again, suddenly it won't work and I get the failed message.
I always wipe system, cache, dalvik and format system between flashes. Thankfully I am able to restore a backup when this happens
Thanks
spydersilk said:
Has anyone had issues with ROMS showing "failed" in TWRP, or just locking CWM up and requiring a battery pull? I have checked the MD5 and they always match. I have also flashed a ROM, tried something else, and when I try to reflash the original ROM again, suddenly it won't work and I get the failed message.
I always wipe system, cache, dalvik, format system.
Thanks
Click to expand...
Click to collapse
Hi,
My Nexus 5 has been working pretty well until now. Earlier today I decided to disable lightflow and try the Xposed LED Control module. I installed and rebooted and it seemed to be fine. But then while using the phone shortly after unlocking it it completely froze then rebooted itself. Since then it's been stuck in a bootloop where it gets as far as the boot animation but then freezes for a few seconds and returns to the Google screen again.
I tried power off and back on and tried loading into recovery to see if wiping dalvik + cache might get me as far a boot but when it loads TWRP it asks me for a password (I've never set one nor enabled encryption of any kind) so my only option is to cancel but then it can't mount the partitions to wipe the cache.
I suspect it's the Xposed module I installed that caused this but I can't be sure it's not just coincidental. I haven't done anything else unusual on the phone today.
Is there anything I can do to fix this that won't require a complete factory reset? Is there any way I can at least backup or keep my data? Unfortunately I'm not at a computer where I can run or install ADB but if that would let me save my current setup or data I can do so at home tonight.
Thanks!
Try flash stock cache.img from fastboot
I don't see this being xposed related but who knows?!
Sent from my Nexus 5 using Tapatalk
I know clearing the cache asks for a password, but try to see if you can flash something. The something is the Xposed disabler zip file in the root of your scard.
Hi,
From the Xposed Framework thread:
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process
Click to expand...
Click to collapse
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).
You could try re-flashing recovery in fastboot mode to see if it fixes the password issue or also I believe philz touch recovery can read twrp backups if you want to switch to a different recovery.
The original bootloop seems like /data corruption to me (freeze + fsync perhaps), then the twrp password further evidences that but.... hmmmm
Sent from my Nexus 5 using Tapatalk
viking37 said:
Hi,
From the Xposed Framework thread:
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).
Click to expand...
Click to collapse
I think I was able to flash this. I keep getting errors about unable to open "/data/app-lib/com.h3r3t1c.onna" - rest off screen, then "Not a directory" and "unable to mount '/persist'", but it seemed to mount /system and flash successfully.
Unfortunately, this doesn't fix the bootloop.
I guess I'll try flashing the cache.img as suggested tonight and see if that works. If not, I guess I'll have to try and wipe.
If I do a factory wipe from TWRP, will I lose photos, videos I've taken? Restoring everything else will be a pain but it's really the photos that I haven't backed up yet I'm more concerned about.
Thanks!
Twrp doesn't wipe /sdcard
Sent from my Nexus 5 using Tapatalk
I just installed that module today and its working fine. I'm on the stock ROM. But doesnt Xposed put an Xposed disabler flashable zip file on your sdcard? Or is that something that maybe I just transferred over and forgot that I did. Because I dont remember transferring it to my phone or downloading it but I have it on there. If you have it, maybe try flashing that to disable Xposed and see if it boots.
EDIT: viking37 actually already suggested this.
Wiping or flashing cache didn't help either.
I tried a factory wipe, which didn't help.
Then I formatted data from TWRP and was able to boot but there were strange issues including a complete inability to connect to the cell network.
Also, TWRP kept complaining that it couldn't mount /persist
So finally I ran flash-all.bat from the factory image download to try and completely return to a factory image. It seemed to work but then I got into a bootloop where it reboots after upgrading android then apps starting.
I tried to do it again but now fastboot keeps giving me this error: FAILED (remote: flash write failure)
or if I try to wipe: FAILED (remote: failed to erase partition)
I'm starting to thing maybe it's a hardware problem with the internal flash... Is that likely or is there still something I can do?
Will I be able to RMA it in this state?
Thanks again for the help!
So I've encountered the issue once again where I get a message saying "System UI Has Crashed" and then a crash loop occurs continuously after each boot. So I went to restore my phone from a backup and found that /system, /cache, and /data were all corrupted and could not be mounted by TWRP.
Flashing the BLU_SYSTEM_0.img file using SP Flash Tool fixed the issue with /system, and wiping the cache seems to have fixed it, but I still am getting messages that TWRP can not mount /data and storage and it has been sitting on "Formatting Data using make_ext4fs..." for an extended period. I had attempted "fastboot format userdata" and that didn't fix the issue.
Will TWRP eventually correct this on its own, is there something else I should do, or is my phone just a brick?
Ive had luck letting it sit for LONG time;
but i find TWRP 2.8 seems much better and quicker with wiping...
also Ive had luck using SP FLASH tool flashing ALL parts, (using allview or gionnee complete roms)
reflashing all the partitions to fix corruptions was a pain; but it worked... then I restored a nandroid back to BLU
uchua said:
So I've encountered the issue once again where I get a message saying "System UI Has Crashed" and then a crash loop occurs continuously after each boot. So I went to restore my phone from a backup and found that /system, /cache, and /data were all corrupted and could not be mounted by TWRP.
Flashing the BLU_SYSTEM_0.img file using SP Flash Tool fixed the issue with /system, and wiping the cache seems to have fixed it, but I still am getting messages that TWRP can not mount /data and storage and it has been sitting on "Formatting Data using make_ext4fs..." for an extended period. I had attempted "fastboot format userdata" and that didn't fix the issue.
Will TWRP eventually correct this on its own, is there something else I should do, or is my phone just a brick?
Click to expand...
Click to collapse
Reboot your phone and boot to TWRP again, then try to Wipe > Advanced Wipe > Tick "Data" only > Swipe to Wipe. If it doesn't work, reboot and keep trying until you get tired of it or it eventually works, whichever comes first.
Hello all,
Hopefully you will be able to help me with this problem as I am currently without a phone until I can resolve this.
To run you through the process, I flashed Nitrogen OS, rebooted to recovery, flashed gapps and all was well. I decided to attempt to encrypt the device once I had setup my Google account. The battery was 100% and plugged into the charger. Shortly after the process started, the phone went into a bootloop. Since, I have attempted to wipe system , cache, dalvik and data, then reflashed Nitrogen OS, but it is still in a bootloop.
When I wipe system , cache, dalvik and data, I also get the error "Unable to mount storage" in TWRP.
I have even attempted to restore the backup I took before flashing Nitrogen OS, with no luck.
Any ideas?
SOLVED.
If anyone else has this problem and looking for a solution, you need to completely reflash stock firmware via fastboot. PM me if you need any help or info regarding this.
OPO_UK said:
SOLVED.
If anyone else has this problem and looking for a solution, you need to completely reflash stock firmware via fastboot. PM me if you need any help or info regarding this.
Click to expand...
Click to collapse
i have yureka plus facing same problem.I was using aex5.2 rom .Once all the apps kept starting and so i rebooted. After that message came showing that your data is encrypted and you need to factory reset.I tried factory resetting through twrp but did not help.Error shows unable to mount system storage and cache.Tried all possible things through twrp bt no use.Did not use fastboot mode as my pcb is damaged.(only charging occurs, no data transfer.).Willing to use fastboot. please help.