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
Related
Just got a factory refurbished Nook Tablet 16GB from B&N and rooted it and installed CYM 7 and it seemed to be working. After doing so, I started having issues with the SD card readers. I originally had a 16GB class 6 Sandisk card in it, but also tried a class 4 4GB Sandisk and a class 10 Microcenter one and all have problems reading. What I'm trying to do now is restore it to stock and see if I can get some help from B&N. Right now, it will give me the N screen and then will show Cyanoboot(it won't let me hold down N to get any menu) and say loading recovery from EMMC and then it will only go into TWRP. I try to install various images from the different SD cards but all will fail. Error messages in the log show E:failed to mount /emmc and E:unable to mount messages. Any ideas on what else I can try?
Thanks,
Col
IJust in case it's not a hardware fault:
Try making a bootable CWM card, boot into it at start over again.
Or you could try the "repart.img" unbrick card.
Searches should bring you to either.
asawi said:
IJust in case it's not a hardware fault:
Try making a bootable CWM card, boot into it at start over again.
Or you could try the "repart.img" unbrick card.
Searches should bring you to either.
Click to expand...
Click to collapse
Tried the repart.img to a card. It appears like it works and then says it's going to reboot and never does. Rebooting then brings back the cyanoboot screen and TWRP.
I can boot from a CWM card, but I'm not sure what to select. When I try to factory reset, I get errors:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/.android_secure...
Data Wipe complete.
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
OK, if you can boot into a CWM card, do that and put something flashable at the same card so it's there when you boot into it.
I'm guessing your bootable CWM card is 5.x.x so you cannot flash CM10 with it. Try putting a CM7 on the card before booting into CWM. That way you have a working system.
TWRP did not play well with my NT and my SD card. CWM has never failed me though!
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
I guess I'm suggesting something along this post (even though I haven't followed that particular routine myself)
http://forum.xda-developers.com/showthread.php?t=2037368
FWIW, I did something like what's in post 25 of that topic to install my CM10.
OMG! My memoery is really bad! I totally forgot that I had trouble getting into cyanoboot when doing that! I see now my own post in that topic, just a few days ago... I used a CM10 sd-card just to get inti cyanoboot, and then I went on from there.
And by the way, what happens when you run the repart.img? What should happen is first it says "don't turn off you device" (or words to that effect),a dn after a not too long while a green checkmark appear. At that point, remove the card and it probably reboots itself, and goes into a new (smaller) "don't turn off..." and that part takes wuite a while.
I just load everything on EMMC and have a copy of the NT recovery flasher apk on hand in case I need to revert to stock.
Well, I tried to boot to a CM7 boot image on the SDcard and it starts to boot and gives me the CM7 screen, but then kicks back to the Nook N screen and boots back into TWRP.
I tried to the repart.img again and it boots, gives me the Please do not turn off, etc. screen, but with a red X in the corner. It then gives me the message that it's done and will reboot, but never turns back on. If I boot it again, it goes back into the TWRP boot.
Stupid question...is the EMMC the SD card or the internal memory? It seems like the errors I get are related to the emmc.
thanks for all the help.
More updates...I got it to boot from a CWM-based recovery SDcard v.5.5.0.4 and when I try to flash a zip file from the SD card, I get the errors:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Error mounting /emmc!
Ok, what's in this post makes my head spin, but it seems like it could fix the problem...
http://forum.xda-developers.com/showpost.php?p=23602314&postcount=10
Trying to get adb running and seeing the device, but no dice right now. Windows seems to recognize it and see storage, but ADB doesn't see it. Am going to keep fighting with that to see if I can do anything through there.
colavsman said:
Trying to get adb running and seeing the device, but no dice right now. Windows seems to recognize it and see storage, but ADB doesn't see it. Am going to keep fighting with that to see if I can do anything through there.
Click to expand...
Click to collapse
Check android_winusb.inf (Program Files -> Android -> Extra -> USB Driver) to see if you have an entry for the NT.
FInally got adb running on a different PC booting off a USB Ubuntu installation and followed the instructions in the post that Asawi recommended. After that, I used the repart.img file and restored it and it came back up. Now I have to figure out how to tell if the SD card reader is bad.
Thanks for all your help!
So during my battles trying to get JB on my atrix I performed a fastboot wipe on just about everything, including preinstall. Now anytime I flash something I get the error "unable to mount preinstall" is this bad or normal? I just searched quite a bit and found no one mentioning it.
Where are you getting this message? In the recovery?
If you wiped everything, that's perfectly normal. You can't mount a non-existent filesystem. You'll need to create a filesystem first before you (or a script) can mount it.
Not sure if this has been answered, but I have been searching and cannot find an answer.
I'm S-Off with Dirty Racun, have been flashing Roms for the past year, no problems, backing up and restoring Roms with no problem. Recently was using the latest Hatka LTE but wanted to restore to an earlier version. Didn't work. Did a super wipe and tried to install clean. Didn't work.
Have been messing with this all day and am stuck. At first it was saying that it could not mount the /sdcard. I thought maybe the internal sdcard was corrupt, so I formatted the internal sdcard. Didn't help.
Anyways, yes, I can get into bootloader and I can get into TWRP.
Yes, I have tried other versions of TWRP. All my backups were created under 2.4.1, have tried 2.4.4 and 2.5 to restore, no success.
In TWRP 2.4.1:
It will say:
Restoring 4 partitions...
Wiping System...
Formatting System using mke2fs...
Done.
Restoring system...
E:Unable to extract tar archive '/sdcard2/TWRP/BACKUPS/HT2324......
Wiping Cache..
Formatting Cache using mke2fs...
Done.
Restoring cache...
[cache done]
Restoring boot...
[boot done]
Updating partition details....
E:Unable to unmount '/system'
Also, not sure if this is related, but when I do Factory Reset under the Wipe section, it will only show that it is formatting cache, formatting data, and wiping .android_secure. It used to say formatting system, but now doesn't mention it?
Also, immediately after it says unable to mount /system, if I try to wipe system, it will give me a fail, unable to unmount /system
Basically, I'm stuck at TWRP and bootloader.
Also, when I try to install a ROM, any ROM, it will die - for example MeanBean 3.09, it will say:
Formatting and Mounting Partition...
Clearing cache and dalvik...
Installing /system....
Installing /data...
symlink: some symlinks failed
E: Error in /sdcard2/MeanBean-v309-jewel-ltevo.zip (Status 7)
Please help! What can I do to restore it back to the way it was so that I can at least get a working ROM on my phone?
Thanks!
Also, if it will help, I am HBoot 1.19.22222
Radio 1.12.11.1210
OpenDSP-v31.1.0.45.0815
Thanks for any help in advance!! Really need this phone to boot into something working.
Buffpandabear said:
Not sure if this has been answered, but I have been searching and cannot find an answer.
I'm S-Off with Dirty Racun, have been flashing Roms for the past year, no problems, backing up and restoring Roms with no problem. Recently was using the latest Hatka LTE but wanted to restore to an earlier version. Didn't work. Did a super wipe and tried to install clean. Didn't work.
Have been messing with this all day and am stuck. At first it was saying that it could not mount the /sdcard. I thought maybe the internal sdcard was corrupt, so I formatted the internal sdcard. Didn't help.
Anyways, yes, I can get into bootloader and I can get into TWRP.
Yes, I have tried other versions of TWRP. All my backups were created under 2.4.1, have tried 2.4.4 and 2.5 to restore, no success.
In TWRP 2.4.1:
It will say:
Restoring 4 partitions...
Wiping System...
Formatting System using mke2fs...
Done.
Restoring system...
E:Unable to extract tar archive '/sdcard2/TWRP/BACKUPS/HT2324......
Wiping Cache..
Formatting Cache using mke2fs...
Done.
Restoring cache...
[cache done]
Restoring boot...
[boot done]
Updating partition details....
E:Unable to unmount '/system'
Also, not sure if this is related, but when I do Factory Reset under the Wipe section, it will only show that it is formatting cache, formatting data, and wiping .android_secure. It used to say formatting system, but now doesn't mention it?
Also, immediately after it says unable to mount /system, if I try to wipe system, it will give me a fail, unable to unmount /system
Basically, I'm stuck at TWRP and bootloader.
Also, when I try to install a ROM, any ROM, it will die - for example MeanBean 3.09, it will say:
Formatting and Mounting Partition...
Clearing cache and dalvik...
Installing /system....
Installing /data...
symlink: some symlinks failed
E: Error in /sdcard2/MeanBean-v309-jewel-ltevo.zip (Status 7)
Please help! What can I do to restore it back to the way it was so that I can at least get a working ROM on my phone?
Thanks!
Click to expand...
Click to collapse
sorry for the replies to myself, but as an update, now even after rebooting into recovery, I can't even wipe - the first thing that happens after I reboot into recovery is I see
E: Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard', which repeats itself a couple of times
then Running boot script...
Finished running boot script...
This happens before I press a single button in recovery (TWRP 2.4.1), I mean it happens immediately as it is booting into recovery
Buffpandabear said:
sorry for the replies to myself, but as an update, now even after rebooting into recovery, I can't even wipe - the first thing that happens after I reboot into recovery is I see
E: Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard', which repeats itself a couple of times
then Running boot script...
Finished running boot script...
This happens before I press a single button in recovery (TWRP 2.4.1), I mean it happens immediately as it is booting into recovery
Click to expand...
Click to collapse
I had the same issue and ended up using three different versions of TWRP, but if you go to the TWRP thread, captain just posted his version of recovery that he built from source and he fixed some of the issues with the android secure and changed some of the wipes, check it out and reformat using rm rf, works better for me it's in the advanced options...
Edit: link to captain's post
http://forum.xda-developers.com/showthread.php?p=41528948
Sent from my EVO using xda app-developers app
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Gizzy00360 said:
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Click to expand...
Click to collapse
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
petitgregory said:
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
Click to expand...
Click to collapse
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Gizzy00360 said:
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Click to expand...
Click to collapse
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
petitgregory said:
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
Click to expand...
Click to collapse
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Gizzy00360 said:
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Click to expand...
Click to collapse
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
petitgregory said:
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
Click to expand...
Click to collapse
I had a few reboots when it was working, then it just suddenly bricked my phone
Sounds like the eMMC brickbug. You need to get the eMMC replaced. All of you that face the problems.
Well, after four years my S3 was getting very slow. It was bearable with CM, but I decided to say farewell now.
Also, my microphone was busted when I dropped it at some point, so I could only call with a headset anyway.
It's not worth replacing I think, time to move on
The same happened to my Beelink GT1 S912 9377 TV-box (after failed OTA update). Will check eMMC brickbug (from TWRP) ...
It's been a few days and I'm still stuck with nowhere to go. All of the information and guide from youtube doesn't work for me. The thing is I've been trying to install a custom rom that is Hydrogen OS, it is asking for password and I thought the answer to that is my phone may be encrypted. So now when I'm trying to format data with twrp it says
"Failed to mount '/data' (invalid argument)
Unable to format to remove encryption."
So now I'm stuck without anything as I already advance wipe my internal storage.