Hi guys.
My rooted mi5 turned off on its own and failed to boot. I opened TWRP and it showed 0MB of space :/
No access to system data or internal storage. Cant basically do anything. Tried to wipe, repair or change the system files but failed. There are few soutions how to fix 'unable to mount system' in TWRP but they dont work at all cause there is no access to the phones storage. I was trying to wipe it through ADB but failed to go through "error: device <null> not found. Is there anything I can do at this point or is it bricked?
Hey,
Look up putting your device to EDL mode and flashing the stock image through the USB cable. It has saved me from far worse situations.
Good luck! Report your progress.
Related
Hey guys n gals i am trying to adb push a rom to my phone (since i screwed it up earlier today) so i can flash it. All goes well up until the point of flashing. when i try to flash it says E:Unable to mount '/data'
E:Unable to mount internal storage.
any ideas on how i can fix this issue?
In your recovery there should be a mounts and storage option or something similar, in there find Internal Storage and mount it, I think this should work since I would get that error but for system and mounting system would fix it.
sideslippy said:
In your recovery there should be a mounts and storage option or something similar, in there find Internal Storage and mount it, I think this should work since I would get that error but for system and mounting system would fix it.
Click to expand...
Click to collapse
i am using twrp and there is a mount option but when i click storage:internal storage it does nothing...it is also saying internal storage is (0mb) which leads me to believe something is not formated correctly. but i don't know of any way to reformat it
OMG!!!!! i am so happy right now...i have been fighting this all day and all i needed to do was format data under the wiping option.
Hey there!
I got my tablet messed up so I was trying to "un-brick" it using the factory images and the temp recovery. All good, until I try to flash a zip. These errors won't go away:
E: unable to mount /factory
E: unable to mount /cache
This prevents me from doing basically anything. I cannot flash any firmware because of these. Of course, the repair partition fails also...
Any ideas?
I managed to format the /factory and /cache partitions so now I got rid of that error. Still, trying to flash a firmware on it and failing miserably from unknown reasons... Isn't there a firmware flash tool available for this device to write the firmware directly into the nand?
Later Edit: Nope, /factory still not mounting...
Even Later Edit: Still no mounting, I managed to dig deeper in the error and it seems that the main message is "can't format unknown volume /emmc". What shocked me is that after unplugging the tablet from PC (using the tethered recovery trying to fix the stuff), I booted in recovery (volume up and power), and to my surprise, I was met by the ol' American Megatrends UEFI - check the attachment... I guess I messed up the bootloader so bad that the Intel chipset took over?
So it seems that the tablet won't boot up in any way. Every boot procedure (power button, power + vol up, power + vol down) will start the UEFI. Go guys!
Ruwin said:
Hey there!
I got my tablet messed up so I was trying to "un-brick" it using the factory images and the temp recovery. All good, until I try to flash a zip. These errors won't go away:
E: unable to mount /factory
E: unable to mount /cache
This prevents me from doing basically anything. I cannot flash any firmware because of these. Of course, the repair partition fails also...
Any ideas?
Click to expand...
Click to collapse
You can find a fix for this problem? i have the same error "unable to mount /factory"
I just tried to clean-install OmniROM with TWRP-3.0 on my Xperia Z1 (6903 UB). I was on CM12 nightly, but my phone went soft-bricked. ): TWRP says:
Code:
Unable to mount storage
Failed to mount /data (no such device)
Any advice? Thanks!
acidrums4 said:
I just tried to clean-install OmniROM with TWRP-3.0 on my Xperia Z1 (6903 UB). I was on CM12 nightly, but my phone went soft-bricked. ): TWRP says:
Code:
Unable to mount storage
Failed to mount /data (no such device)
Any advice? Thanks!
Click to expand...
Click to collapse
As the error says: your /data partition is missing. You can't wipe something that isn't there!
Try these:
1. As an experiment, in case /data is corrupt: repair /data by tapping Wipe > /data > Repair filesystem and format to ext4. I had a similar error with my phone's /cache when I was dealing with an unstable KK build, but performing these steps fixed my issue. Your situation may be different...
2. Transfer a stable LP or KK ROM into a sdcard or phone and flash it. You may also sideload or push the zip through adb if you don't have an sdcard and OS to boot to, but have a working recovery; make sure you have the correct drivers installed on your computer. Depending on the kernel, you may or may not have recovery built in to your boot.img, so flash recovery through fastboot if needed.
3. Planning to return to Sony's default ROM?: Use flashtool to restore your phone to its factory state. Find proper FTF file through XDA and flash. Guide: http://forum.xda-developers.com/showthread.php?t=2428319
Hope my answer is clear enough! Good luck getting this sorted out!
This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.
**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999
Hi, I recently went installed TWRP using the guide here: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
and tried flashing DMVerity after which I went to wipe and format data after which I got:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/sda15 process
ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
Unable to mount storage
I freaked out and went back to the Install option to find that nothing was showing up. I googled for some fixes and found that formatting ext4 would work but I got:
Formatting system using make_ext4fs...
...done
Updating partition details...
Failed to mount '/data' (Device or resource busy)
Unable to mount storage
And then I tried to make it f2fs again. To which I got:
Formatting system using mkfs.f2fs...
...done
Updating partition details...
Failed to mount '/data' (Device or resource busy)
Unable to mount storage
So I finally tried changing it to exfat and it got stuck on Updating partition details...
I forced reboot to TWRP and stuck on the 'blu_spark loading screen'
What do I do please help, I am freaking out.
Okay this is for anyone who might have the same problem (accidentally formatting to exfat) later on. For the longest time, I thought that my device was bricked and there was no coming back. However it hit me that it might be a problem with TWRP not being able to understand exfat partitions properly. So I tried something else and I currently have my phone running Open Beta 19. Here's what I did:
1) Power off the phone by holding down volume up+power button.
2) Hold volume up+power again until you're not in the bootloader and then connect the device to the PC.
3) Go to the fastboot folder, open terminal/command prompt and check if it's connect by typing in: fastboot devices
If it is connected you'll get some sort of device ID with fastboot written next to it.
4) Type in: fastboot erase system
and hit enter.
5) Type in: fastboot format:ext4 system
and hit enter.
6) Now flash the TWRP recovery. Using the method defined in the original link.
7) You should now be able to boot into TWRP and bypass the loading screen.
8) I had a small problem at this step, for some reason you can't flast Open Beta 19 directly from TWRP. I had a copy of Open Beta 13 on my PC from some time ago and I used that and it flashed without a problem.
9) Boot into the device and set it up.
10) Once set up, go back to the recovery and you'll see that you're back to the stock recovery. Wipe everything off.
11) Transfer OB19 to the device and install that through the custom recovery and boot it up.
You should hopefully be running a clean version OB19 after you boot up. Hope this helps.