Hello, i have a problem with bricked VSU6. I can only boot to twrp 3.0-2.0 and i can't flash anything. The error i get is that the internal storage can't be mount (0mb). I've tried any solutions i've read in the internet (wipe data, change filesystem to exte2,fs2fs and then back to ext4, trying from adb) but nothing works, always taking the "failed to mount /system, /data, /cache. Probably the phone bricked the eMMc? Also if that helps my phone have screen lock patter.
Can save the phone or i'm going for a new one?
Thank you.
Related
Hello all,
I have run in to some issues with my phone today, and have spent several hours trying out different things, and reading through the forums.
My phone is unlocked, s-on, and have had no problem loading multiple different ROMs in the past. The most recent ROM I was using was Carbon 1.7. It had been working well for the most part, periodically the phone would restart itself, but I didn't really consider that an issue.
Today though, I was taking a photo with the phone, and it restarted itself. Upon the restart, it became stuck at the HTC boot logo. Once I got home I investigated it some more, and figured I'd try and just wipe the cache/dalvik, and this is where I came to realize I might be in a big mess than originally thought.
I'm not able to wipe the cache, dalvik, system, or anything. I try to flash a ROM, and it seems to work, and since i'm S-On, I try to load the boot image with Hasoon's All in One Kit, but still stuck at the boot logo. I try to do a full wipe from within the ROM when install, and also tried a full wipe with Super Wipe, but no luck.
This is what I'm seeing (I've tried using TWRP, CWM, EXT, and all come up with something similar):
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog'
E: Unable to mount '/emmc'
E: Unable to mount '/emmc'
E: Unable to mount internal storage
I've racked my brain as much as I possibly can. I consider myself a noob when it comes to most of this stuff still, so any help would be greatly appreciated.
Thanks so much
I recently sold my amaze to a coworker and over the weekend if started doing the same thing i spent all night trying to figure it out... I did a full wipe except sd and it wouldn't recognize the sd card. It was running cm10.1
Sent from my SGH-M919 using Tapatalk 4 Beta
S-Off your amaze. Then apply a stock RUU. I had to downgrade to GB to recover my phone. Android 4.1.x and 4.2.x roms tend to have this bug of partition corruption with our phones.
Fix internal storage error
If you wipe or factory reset it from the bootloader, it may kill the internal storage partition. Just connect USB, go into recovery, unmount and remount USB storage, it will recognize the internal storage and say its unformatted. Then format it as fat32. Then you can do a wipe and reimage. Thanks to OM4 from XDA for posting this. Worked for me!!
http://forum.xda-developers.com/show....php?t=1975989
heyliddle said:
Hello all,
I have run in to some issues with my phone today, and have spent several hours trying out different things, and reading through the forums.
My phone is unlocked, s-on, and have had no problem loading multiple different ROMs in the past. The most recent ROM I was using was Carbon 1.7. It had been working well for the most part, periodically the phone would restart itself, but I didn't really consider that an issue.
Today though, I was taking a photo with the phone, and it restarted itself. Upon the restart, it became stuck at the HTC boot logo. Once I got home I investigated it some more, and figured I'd try and just wipe the cache/dalvik, and this is where I came to realize I might be in a big mess than originally thought.
I'm not able to wipe the cache, dalvik, system, or anything. I try to flash a ROM, and it seems to work, and since i'm S-On, I try to load the boot image with Hasoon's All in One Kit, but still stuck at the boot logo. I try to do a full wipe from within the ROM when install, and also tried a full wipe with Super Wipe, but no luck.
This is what I'm seeing (I've tried using TWRP, CWM, EXT, and all come up with something similar):
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog'
E: Unable to mount '/emmc'
E: Unable to mount '/emmc'
E: Unable to mount internal storage
I've racked my brain as much as I possibly can. I consider myself a noob when it comes to most of this stuff still, so any help would be greatly appreciated.
Thanks so much
Click to expand...
Click to collapse
I've unlocked the bootloader and installed TWRP but I keep getting a E:Unable to mount ' /emmc
E:Unable to mount interal storage
Error when flashing certain things in TWRP. TWRP allows me to install the rom but it doesn't boot up after flashing, just gets stuck on the white HTC screen. I may have borked something with the internal storage as it doesn't allow me to write to it, can anyone guide me on how to remedy this?
Sounds like you are still s-on. You need to fastboot flash the boot image after installing a ROM. See this thread http://forum.xda-developers.com/showthread.php?t=2570888.
Sent from my Nexus 7 using Tapatalk
Manbot27 said:
I've unlocked the bootloader and installed TWRP but I keep getting a E:Unable to mount ' /emmc
E:Unable to mount interal storage
Error when flashing certain things in TWRP. TWRP allows me to install the rom but it doesn't boot up after flashing, just gets stuck on the white HTC screen. I may have borked something with the internal storage as it doesn't allow me to write to it, can anyone guide me on how to remedy this?
Click to expand...
Click to collapse
To fix the internal storage, try wiping Internal SD via TWRP, if that doesn't work, see if you can mount it to a PC and format it, if that doesn't so it, you'll probably need to RUU your phone to repair the filesystem.
As for the other issue, as pointed out, need to flash the kernel separately if you're s-on.
So a friend of mine recently gave me this YP-G70, asking me to fix it for him. His cousin had promised to put KitKat on the device, no problem, as a replacement to the stock software. This is all I know.
When I received the device, it would not boot into any ROM, only into recovery (CWM was flashed). In CWM, I could see that /system, /data, /emmc, and /sdcard partitions were all unmounted. I tried to remount them in CWM, but alas, this did not survive a reboot, even just back into recovery.
I have tried to flash the stock firmware for this device (obtained from sammobile) through odin, which was a success... until it booted up, and found that again, the proper partitions were not mounted. From there, I went on to flash CM9, which ended me up to where I am now.
As it currently stands, /dbdata, /data, /emmc, and /sdcard are all unmounted and are stuck that way. Does anyone know how to solve this, cause I am lost right now.
nicholician said:
So a friend of mine recently gave me this YP-G70, asking me to fix it for him. His cousin had promised to put KitKat on the device, no problem, as a replacement to the stock software. This is all I know.
When I received the device, it would not boot into any ROM, only into recovery (CWM was flashed). In CWM, I could see that /system, /data, /emmc, and /sdcard partitions were all unmounted. I tried to remount them in CWM, but alas, this did not survive a reboot, even just back into recovery.
I have tried to flash the stock firmware for this device (obtained from sammobile) through odin, which was a success... until it booted up, and found that again, the proper partitions were not mounted. From there, I went on to flash CM9, which ended me up to where I am now.
As it currently stands, /dbdata, /data, /emmc, and /sdcard are all unmounted and are stuck that way. Does anyone know how to solve this, cause I am lost right now.
Click to expand...
Click to collapse
I would try to find out what the log files say. If you can still make a full backup under CWM, I suppose this should include the last log written by android. This is where I would start my investigation. It is of course strange that android fails to mount the /data partition. I have no clue what /dbdata is for. My gut feeling is that your friend messed up the partioning, but I think it is key to find out what happens during boot time.
Finally, since you didn't write about this: Did you try wipe the cache and dalvik cache in CWM?
I have an old Oneplus one that I would like to get working to recover some data. The phone is stuck in a bootloop. This happened out of nowhere one day while charging. I was running CM 11. I can still access twrp(version 3.0.2-0) and i can enter fastboot. The various partitions are as follows Boot(16MB), System(733MB), Data(OMB). The 0 MB in data in odd. Also the storage doesnt mount. Whenever i try to format data it says, "Failed to mount '/data'(invalid argument), unable to recreate /data/media folder, unable to mount storage". If i try to repair or change the file system, it says the same thing. Any help would be appreciated. Thanks.
Hi all.
I'm trying to make a last backup of the stock Android of my Swift 2x before flashing LineageOS. But TWRP (version 3.3.0-0) Seems unable to use the /data partition. I got various messages like:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid Argument)
I tried to format the partition: Wipe -> advanced wipe -> repair or change filesystem -> change filesystem -> ext4 but it didn't change anything.
What's wrong? What can I do?
Thanks a lot for any hint.
bumping this thread as I also ran into this issue.
When using TWRP, the data and system partitions can't be mounted. they also show up as being 0mb in size.
Because of this, no backups can be made and a full system wipe also yields errors.
What I did was change the filesystem to ext2 and then change it back again to ext4.
Doing this at least allowed me to flash crdroid, but making backups still doesn't work.
Whenever i go into TWRP again, it's the same thing again: unable to mount and partitions show up as 0 mb in size.
Anyone know what's causing this?
Wileyfox encrypts there data when you factory reset your device or after youve rooted your device .To get around this you need to do a factory reset using stock recovery once thats done then turn off the device. Then using minimum adb and fastboot type (fastboot boot twrp.img) that will boot your already installed twrp now erase data internal storage etc you'll notice you can finally delete stock os youll see internal storage is showing mbs available again etc worked for me perfectly.