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.
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
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
wtoj34 said:
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
Click to expand...
Click to collapse
Just plugged it into my pc to try to flash philz and a pop up came up saying that the file system is currupt. Ugh. I'm so p/o'd right now. Is RUU my only choice right now to repair this if any?
Just flashed RUU. Same thing. Going to dry formatting in windows device manager now
wtoj34 said:
So I just went into recovery (buck's twrp) to flash me some aosp, it worked fine but I forgot to get a gps lock in sense before I flashed so I went into recovery to restore a nandroid and I got the dreaded "unable to mount /data, and unable to mount internal storage. Tried reflashing buck's twrp in fastboot and no dice. I have the RUU downloading although I would hate to have to go through that. Any recommendations? I;m going to try flashing philz recovery right now
Click to expand...
Click to collapse
In TWRP go to Wipe < Format Data and do that and it should fix your /data problem. Before doing that I recommend just using the advanced wipe and ticking /data /cache /boot & /system and then re-trying. Also afterwards a good ROM to start with would be Cyanogenmod, I've had the least number of problems with that than any other, especially when helping people with issues like this. I actually had someone who's only way of fixing his issue was flashing that.... odd I know but that is why I always recommend it after having this issue.
Edit: just seen you've did an RUU and your problem is still persisting, I still recommend doing the 'Format Data' option in TWRP, this is known (at least to me) to fix most if not all problems with mounting...
S1L3nTShaDoWz said:
In TWRP go to Wipe < Format Data and do that and it should fix your /data problem. Before doing that I recommend just using the advanced wipe and ticking /data /cache /boot & /system and then re-trying. Also afterwards a good ROM to start with would be Cyanogenmod, I've had the least number of problems with that than any other, especially when helping people with issues like this. I actually had someone who's only way of fixing his issue was flashing that.... odd I know but that is why I always recommend it after having this issue.
Edit: just seen you've did an RUU and your problem is still persisting, I still recommend doing the 'Format Data' option in TWRP, this is known (at least to me) to fix most if not all problems with mounting...
Click to expand...
Click to collapse
Thanks a bunch dude, appreciate it. Restoring a nandroid now, had no issues with data yet. Phew. That was an exciting night
Yep its a stressful problem when it happens.
Sent from my One M8 using Xparent BlueTapatalk 2
I've read this issue with other devices, however. i've not found a solution for this yet
I'm new to this forums, let me know if i don't do something right.
I've been using Alberto97's AOSP Lollipop 5.1.1, it's my first custom rom install, i got it on
the first try, TWRP 2.8.6.0 running with no problems.. flashed other stuff like moto camera, marshmallow bootanim, and that's all
Last week i've tried to update to the CAF latest version of his build, however, TWRP
reboots when i try to wipe the /data partition, in the custom TRWP 2.8.7.0 thread found
i might need to repair the partition, i tried it with no success, repaired /cache with no problem, but when i try to fsck /data on TWRP it gaves me an error, haven't tried /system yet.
tried using CWM and it got stuck at wiping /data for like an hour (endless loop), i rebooted, the data was wiped, but i couldn't flash the ROM image, rebooted to clean system with no problems, it wipes cache and dalvik with no issues.
What's causing this? i have not faced apps FC or anything, just the TWRP random crashes at wiping, i'm using a Moto G XT1032 16GB TWRP 2.8.6.0 No custom kernel or non official recovery.
justpaste.it/wipedar
Leaving recovery.log on external page for reference.
hope you can help, thanks in advance.
Same problem here
You can use CWM by PhilZ for fixing what I think is a broken symlink to the emulated internal storage card.
I am using philz-6.58.7-falcon that you can find and download here: http://forum.xda-developers.com/showthread.php?t=2639583
Once you have flashed the new recovery you can go to "Advance menu", then to "change sdcard target" and define it to /data/media (you just have to tap on the option to set it).
Go back, select "Wipe option", then "Wipe User media" and the process should be successful.
If you reinstall TWRP and wipe "/data" now the rebooting problem should be gone and everything back to normal.
Hope this helps for you.
By the way this is my very first post here. So I hope I am doing this right.
Greetings.
Thank you for the help, i fixed it by repairing the userdata partition with the latest TWRP
My S6310N refuses to complete boot up, after trying quite a few ROMs stays frozen during booting. Even giving me errors in the recovery, are the kind Unable to mount '/ data'.
This is the error log during wipes on TWRP recovery: i1352.photobucket.com/albums/q655/obiwan2208/zx.jpg
For the rest I can flash with Odin stockROMs and TWRP, but after the Samsung's animated logo leaving the SAMSUNG letters flashing and stay frozen there.
I tried to make wipes and although do something, continue without mount 'storage', '/data', etc.
Also with Odin I checked the option "Nand Erase All".
Has been corrupted the file system? Must to be formated somehow? Any fix will be welcome. ThnX
Fixed by myself
It's done
As I see the smartphone can't mount '/data' I played with TWRP recovery and I formated 'data' partition.
Then for be more sure and works I checked out making one wipe (before gave errors) and it's OK: any red text.
Right now I'm flashing stockROM, TWRP, SuperSU... :victory:
Seems that 'data' partition was kept corrupted despite had to flash stockROMs
Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .