Related
I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
_ice_ said:
I tried reflashing a sense 3.0 2.3.3 rom because of some minor issues. Now I may have nuked my /data partition. first it wouldn't format so I pulled battery numerous times. and Mounted it through mounts and storage menu, then I hit format, and it formatted, so I hit mount again and flashed the rom. and when I restarted the phone after splash screen the phone restarted and went into recovery
Tried everything including mounting /data again and it keeps saying error mounting /data. am I screwed?
I have .2007 eng bootloader btw. shoud I try the pd15img?
Click to expand...
Click to collapse
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
jdkoren said:
I don't think you need to do that. You could do a fastboot erase, then go back into recovery and wipe data to reformat it /data, effectively starting from nothing.
Click to expand...
Click to collapse
Now I am getting mount /cache errors. aww man I think my phone is done....
edit: used the pd15img and I am back on stock :| s= off but I have the stock bootloader wtf.... how do I get my eng bootloader back?
this is how I fixed it:
I was on eng bootloader, but then I got reverted back to the stock bootloader.
This is how I encountered the problem. first of all I was having issues with raffy's fusion 3.0 rom, so I decided to reflash it, but it wouldn't flash or format /data, then I mounted it to through mounts and storage on the latest cwm 3.0.2.4 and hit format.
After that I tried reflashing his rom, it flashed but, after splashscreen I was redirected to my recovery instead. that's when I freaked because when I tried mounting data it said error cannot mount /data. so I fired up adb and did fastboot erase system -w and it erased it including cache.
then I popped up into recovery and BOOM started having cache mount errors experienced by a lot of people lately.
I thought I was SOL, but nope I downloaded the pd15img from http://www.megaupload.com/?d=V4NAODYZ
and put it on the root of my sd card and it worked....
so if anyone of you dudes are having similar problems try that ^
My tab froze and when I rebooted it, I get a black screen right after the AOKP logo. It just sits there forever. I can boot recovery.
My story is below, but I think my question is: How can I format the partitions, because I think /data is corrupt?
Story:
I can boot recovery, and I wiped everything, then tried adb pushing a rom to the /sdcard. That's when things got weird...
adb push failed, so I rebooted and noticed that /data wasn't mounted. (/sdcard is just a symlink to /data/media)
I mounted /data from recovery and tried to push the ROM file again. This time I got some I/O errors on the push. I also noticed that in an adb shell, the /data partition would sometimes unmount by itself, and threw disk errors when copying files around. All other partitions seem to work fine.
So I deleted everything in /data/media, formatted /data, and tried again. This time I could adb push the ROM. I installed the ROM, but I still get the same freeze after AOKP logo.
cryptyk said:
My tab froze and when I rebooted it, I get a black screen right after the AOKP logo. It just sits there forever. I can boot recovery.
My story is below, but I think my question is: How can I format the partitions, because I think /data is corrupt?
Story:
I can boot recovery, and I wiped everything, then tried adb pushing a rom to the /sdcard. That's when things got weird...
adb push failed, so I rebooted and noticed that /data wasn't mounted. (/sdcard is just a symlink to /data/media)
I mounted /data from recovery and tried to push the ROM file again. This time I got some I/O errors on the push. I also noticed that in an adb shell, the /data partition would sometimes unmount by itself, and threw disk errors when copying files around. All other partitions seem to work fine.
So I deleted everything in /data/media, formatted /data, and tried again. This time I could adb push the ROM. I installed the ROM, but I still get the same freeze after AOKP logo.
Click to expand...
Click to collapse
I would say you need to ODIN your TAB:
Use this:
http://forum.xda-developers.com/showthread.php?t=1651794
[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.
Anyone have any idea?
Thanks
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?
You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes
I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.
you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)
Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.
Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.
I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?
I'm really desperate for help and am hoping someone can help me please.
Background :
I am having issue with my Nexus 6P where I would get "no service" (network/SIM) following a factory reset of the phone which is still under warranty. Same as here https://forum.xda-developers.com/nexus-6p/help/nexus-6p-service-message-t3539100
Following advice on forums, I successfully rooted and installed TWRP and SuperSU before trying flashing the Chroma ROM to change bands etc, but to no avail as the problem persists.
Current issue:
Something has consequently gone wrong when playing around in TWRP as installing ROMs as I seem to have stuffed up the "mount" and partition.
The phone is currently ROM-less and I can no longer factory reset nor flash any RAM as I get the error :
"Failed to mount '/vendor' (Invalid argument). "
http://tinypic.com/view.php?pic=97la9x&s=9
Internal memory now shows as 25566MB not 32GB.
http://tinypic.com/view.php?pic=23li3py&s=9
Intended outcome:
Please help me restore the settings and memory mounts to default, so I can return the phone to factory defaults with original ROM before sending off for warranty repairs
McLarenHonda said:
I'm really desperate for help and am hoping someone can help me please.
Background :
I am having issue with my Nexus 6P where I would get "no service" (network/SIM) following a factory reset of the phone which is still under warranty. Same as here https://forum.xda-developers.com/nexus-6p/help/nexus-6p-service-message-t3539100
Following advice on forums, I successfully rooted and installed TWRP and SuperSU before trying flashing the Chroma ROM to change bands etc, but to no avail as the problem persists.
Current issue:
Something has consequently gone wrong when playing around in TWRP as installing ROMs as I seem to have stuffed up the "mount" and partition.
The phone is currently ROM-less and I can no longer factory reset nor flash any RAM as I get the error :
"Failed to mount '/vendor' (Invalid argument). "
Internal memory now shows as 25566MB not 32GB.
Intended outcome:
Please help me restore the settings and memory mounts to default, so I can return the phone to factory defaults with original ROM before sending off for warranty repairs
Click to expand...
Click to collapse
First thing is try to flash the latest vendor image for your device that matches the roms version. That should let the vendor mount so you can do stuff again.
McLarenHonda said:
Please help me restore the settings and memory mounts to default, so I can return the phone to factory defaults with original ROM before sending off for warranty repairs
Click to expand...
Click to collapse
Manually (fastboot) format your partitions and then load a (stock) image normally.
DEVILOPS 007 said:
First thing is try to flash the latest vendor image for your device that matches the roms version. That should let the vendor mount so you can do stuff again.
Click to expand...
Click to collapse
Any attempts to flash the vendor image are unsuccessful as keep getting the Mount error.
v12xke said:
Manually (fastboot) format your partitions and then load a (stock) image normally.
Click to expand...
Click to collapse
Thanks.
I'm only seeing one partition of 25GB. Can't see the missing 7GB as a separate partition
Also would appreciate if you could step me through the fastboot format process.
Cheers!!!
McLarenHonda said:
Any attempts to flash the vendor image are unsuccessful as keep getting the Mount error.
Click to expand...
Click to collapse
Try following this guide specifically the section called return to stock.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
McLarenHonda said:
Thanks.
I'm only seeing one partition of 25GB. Can't see the missing 7GB as a separate partition
Also would appreciate if you could step me through the fastboot format process.
Cheers!!!
Click to expand...
Click to collapse
25 GB is normal, after formatting and the installed OS, that is all that is left. You will never have 32GB. Use fastboot from the bootloader to format your partitions. Then flash a full image using flash-all.bat.
fastboot format system
fastboot format cache
fastboot format userdata
So, today I was going to flash miui 11 andoid 10 and made a backup of all my files to the pc. weird enough some files size was too big (a zip of a rom was like 12 gb) something was wrong there. anyway, after backup, I updated the twrp to the latest chines and after flashing the twrp I wasn't able to enter twrp, it got stuck on the spalsh screen.
So, I flashed the fastboot stable version for eea mi 9t, as usual, to restore to stock. but again it doesn't boot and it still gets stuck on twrp splash screen but after a while, twrp boots and I see that it's unable to mount data and cache.
I try to format the whole data partitions but it only gets stuck there forever.
you can see it in the screenshot attached.
The file system on data appears as f2fs. I tried converting to ext4 and still no luck, it get stuck there forever.
How long should it take to format a corrupted data partition like this?
Any help, please?
Edit: also tried using the command line to format /data myself and it gets stuck here:
Code:
mke2fs -t ext4 /dev/block/sda32
mke2fs 1.43.3 (04-Sep-2016)
Discarding device blocks: done
Creating filesystem with 13518331 4k blocks and 3383296 inodes
Filesystem UUID: 0ea82001-1ff3-47d3-bf7c-19308852ceb3
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information:
It looks like :
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
and
https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I don´t know what exactly was the problem, I was trying custom ROMs and they worked fine but then I went back to stock and found my persist broken. So flashed a persist.img from the fastboot images, that broke widevine L1 and messed up the sensor, I had to recalibrate the camera etc. But after a while, the stock rom started acting weird, not receiving email, not syncing contacts, lag and stuttering etc, so I decided to flash the fastboot rom again with the wipe everything .bat. It flashed everything fine but didnt boot anymore and wasn't able to enter stock recovery anymore. Was only able to access fastboot and twrp. Tried locking the bootloader and wiping everything again and it got stuck on 99.99% when it's wiping on stock. I left it all night and in the morning I found it on the boot animation but it stayed there for hours and hours and it never booted.
On twrp I was able to mount system and all the partitions except data and cache. I tried repairing them and formating but it was always failing. I even used parted through adb shell, deleted partitions and created new ones but with the same unsuccessful results.
So, in the end, I sent the phone to the repair service under warranty and they fixed it by replacing the mainboard. So I guess the problem bricked the whole memory and who knows what else.
So be careful guys, flashing custom ROMs and other region stock ROMs isn't safe with this phone. We have people with broken persist partition, broken internal storage, sensors, bricked phones...
Personally speaking, I won't flash any custom ROMs or stock ROMs not meant for my device anymore. Xiaomi has introduced to many measures that are causing problems with flashing, similar to Huawei.
bihariel said:
I don´t know what exactly was the problem, I was trying custom ROMs and they worked fine but then I went back to stock and found my persist broken. So flashed a persist.img from the fastboot images, that broke widevine L1 and messed up the sensor, I had to recalibrate the camera etc. But after a while, the stock rom started acting weird, not receiving email, not syncing contacts, lag and stuttering etc, so I decided to flash the fastboot rom again with the wipe everything .bat. It flashed everything fine but didnt boot anymore and wasn't able to enter stock recovery anymore. Was only able to access fastboot and twrp. Tried locking the bootloader and wiping everything again and it got stuck on 99.99% when it's wiping on stock. I left it all night and in the morning I found it on the boot animation but it stayed there for hours and hours and it never booted.
On twrp I was able to mount system and all the partitions except data and cache. I tried repairing them and formating but it was always failing. I even used parted through adb shell, deleted partitions and created new ones but with the same unsuccessful results.
So, in the end, I sent the phone to the repair service under warranty and they fixed it by replacing the mainboard. So I guess the problem bricked the whole memory and who knows what else.
So be careful guys, flashing custom ROMs and other region stock ROMs isn't safe with this phone. We have people with broken persist partition, broken internal storage, sensors, bricked phones...
Personally speaking, I won't flash any custom ROMs or stock ROMs not meant for my device anymore. Xiaomi has introduced to many measures that are causing problems with flashing, similar to Huawei.
Click to expand...
Click to collapse
Yeah, same thing happened to me buy flashing a EU beta ROM in September but I was lucky and got my phone replaced by Amazon, since It was still in return period since then I have stayed away from miui custom ROMs and betas only Aosp. But I always return to miui. And always with a back up of my entire partition.