Okay so last night I attempted to root my nook tablet 1.4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2037368. I downloaded all the files that were pointed to in that thread, and followed the instructions. Everything went perfect and soon I was setting up my google account, then following the final steps which involved downloading rom manager, and goo manager. All was well, until I decided to reboot the tablet.
After I rebooted the initial loading seemed fine (got the "n" screen"), then cyanobootloader popped up, then the Team B presents XDA logo popped up and then nothing. The tablet stayed frozen on the Team B logo, and rebooting did nothing.
So being the idiot that I am, I tried going into recovery from the cyanobootloder. This took me to TWRP where my dumbass ended up going to advanced and Wiping the system. After that I tried installing Cm-7-Team-B-Beata1-signed.zip and gapps-gb-20110828-signed.zip from TWRP. The log gives several messages that read:
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /emmc
E: Unable to mount /emmc
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
At this point I was freaking out, stopped using my head, and began trying desperately to go back to stock. I tried using this method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/, but it didn't change anything.
I decided then to try redoing the rooting guide again to see if that could solve the problem. It did not.
So now the tablet boots into TWRP when I turn it on. I can also enter CWM-based Recovery using the SD card I made from the guide. However, when I enter CWM-based-recovery I get these messages at the bottom:
E: Can't Mount /cache/recovery/command
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
That's pretty much where I'm stuck on at the moment. I figured I should probably stop messing with this tablet before I made a bigger mess.
Any help would be greatly appreciated.
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard based CWM recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Nook needs a /recovery folder in /cache partition like /cache/recovery.
Somehow that folder is missing
Is so easy to fix that you will laugh
dd zero the cache partition after you make sure cwm/twrp is not have it mounted check by reading mount /cache if it says unmount cache select it first.
Then format cache in cwm/twrp and that's it. Folder will be created by it self and that error print out will stop.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
Related
Hello,
I ran into some issues after installing the Classic Jewel V0.0.4 Rom that ultimately led to my internal SD card not being recognized or not mounted properly. For the record, I am not blaming the ROM nor am I suggesting that there is anything wrong with the ROM.
Below is the sequence of events:
1. Full wipe of everything except SD card.
2. Flashed the ROM.
3. The Phone booted all the way to the setup wizard but then rebooted.
4. Phone went into a bootloop.
5. Re-flashed the ROM without wiping.
6. The Phone won't get pass the HTC logo screen.
7. I went in recovery and wiped everything and Flashed Fresh's rom / this did not work.
8. I flashed maybe two other ROMS and still not working.
9. I went into bootloader and did a factory reset (I think this may have been my downfall)
10. The internal SD card is not mounted (or not mounted properly) in Recovery. (I can see the SD card, and see the TWRP folder but nothing else.)
11. Flashing any ROM fails. I see several lines of this error: "E:failed to mount /sdcard (invalid argument)"
12. I tried to do a restore but the file is not there (I guess it's because the internal SD card is acting up?)
Any ideas on how I can fix this?
----------------
Edit:
Here are some more errors that I see while in Recovery
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard during GUI startup.
*Verifying filesystems...
*Verifying partition sizes...
E:unable to mount /sdcard
E:unable to mount /sdcard
Running boot script...
Finished running boot script.
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard
E:failed to mount /sdcard (invalid argument)
-----------------
Thanks,
Aloupha
I think my problem could be fixed by doing something similar to what's discussed in this thread... but I have no clue on what to do.
http://forum.xda-developers.com/showthread.php?t=1526912
Stab in the dark but can you get Windows to recognize the sd while in recovery? If so open cmd prompt and type chkdsk /X /F <SD card drive letter> and see if it repairs it......just a thought
Sent from my Transformer Prime TF201 using Tapatalk 2
The problem is gone!
The strangest thing happened. I kept flashing roms and they kept failing. Eventually, I tried flashing the MeanRom and it flashed successfully.
I am not sure how that was possible but I am happy! I lost some most of files I had in the Internal SD card though but that's okay!
I am going to install the Classic Jewel rom again and see if the same thing happen again.
I know this thread is a little old but i didn't find much else on this issue. I followed these steps to get a ROM loaded back on my phone
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I am still trying to figure out whats going on with my internal SD I will post if i find a solution.
Do not use clockwork recovery.
Sent from my EVO using xda premium
Just wanted to post this in case anyone runs into this problem with the EVO 4G LTE. I believe I caused it by trying to "Factory Reset" via bootloader.
I was unable to format /sdcard via busybox per instructions in other threads. I was, however, able to format fine with Windows 7. The proper options are:
File System: fat32
Allocation Unit Size: 4096
Perform a quick format: Unchecked
The other settings can be left on default. Similar settings should work from other operating systems. After this, you can mount the /sdcard via your recovery and transfer/flash your downloaded rom.
Edit: must mount via recovery so it will show up in Windows.
Thank your for this post. I was trying to load a ROM and something errored out. Then, I tried to load it again but noticed that I had to following:
E:failed to mount /sdcard (invalid argument)
I was able to format in Windows 7 and then sucessfully load the ROM.
I was actually stuck in a boot loop prior to me trying to reformat the card. To fix that, I pressed down the power button for about 45 seconds and then it eventually stopped rebooting. I was then able to get into recovery.
Anyway, hope this helps someone.
failed to mount /sdcard (Invalid argument)
Hi there, just got the same error message up. I've tried formatting in bootloader (cwm), also twrp and neither allow the sd card to be seen on pc. I've used minitool partition wizard to partition on the pc following instructions from the xda site and that doesn't show up on the android system either way i format from pc it comes up on mounting from android as the "failed to mount /sdcard (Invalid argument)" error
Any other solutions anyone??
Thanks
Dan
Hey there
I have a pretty serious problem with my I9100... I had installed the Paranoid Android 2.52 ROM and I was trying to switch to a different kernel. Which wasn't working for me, I'm guessing due to the Fastboot feature in that ROM.
The last kernel I tried was the Andromeda one. While trying that, I thought I might try to do a factory wipe using its recovery software, hoping that that might get Paranoid Android to boot.
Unfortunately, it would hang while doing the wipe, and I eventually (after about 20 minutes) power-cycled the device. I tried getting back to my working kernel, but Andromeda's recovery would either error out with mount errors, or it would hang altogether.
Eventually, I tried flashing a CF-Root kernel using Odin, and since then I was unable to get past the Samsung boot splash screen. I could no longer access the recovery software, but I could get into download mode and flash stuff via Odin (Kies won't recognize the device).
I've tried a variety of kernels and firmwares (including the stock one for my phone (GT-I9100_XEF_I9100XWKJ2_I9100XXKI4_I9100XEFKJ1, which I've previously flashed successfully to get it back to a non-rooted vanilla state)), but nothing I did would get the phone to boot.
Thinking the partition table might've been damaged somehow, I attempted the stock firmware from the first post here, including the PIT file and re-partitioning. This process would eventually hang when flashing datafs.
Thinking the bootloader might be damaged, I tried partitioning again, flashing the original bootloader from here, and again flashing the stock firmware that I've used successfully in the past.
I can now actually get past the boot splash! However, the phone boots directly into stock recovery, which looks like it's trying to do some post-update maintenance-type stuff, but fails horribly at it. Some of the output from it scrolls past the viewport, but this is the last lines that I can read:
Code:
[COLOR="Orange"]Formatting /cache...
Cache wipe complete[/COLOR]
-- Updating application...
[COLOR="DarkRed"]E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
[/COLOR][COLOR="Orange"]-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEF/system/'.
Successfully applied multi-CSC.[/COLOR]
[COLOR="DarkRed"]E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknown error: 0)
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)[/COLOR]
It definitely looks like a borked filesystem/partitioning to me. I tried doing a factory wipe in this recovery, but it would hang at formatting /cache.
Any ideas of what I can do to get this thing up and running again?
Thanks in advance,
Daniel
I successfully flashed a CF kernel, and can now access CWM.
I get these error messages, however:
Code:
CWM-based Recovery v5.0.2.7
E:Can't mount /cache/recovery/command
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
Wiping cache partition in CWM takes care of those errors. Trying a factory reset will give me "Formatting /data..." for a bit, and then the device automatically reboots.
I can format /cache and /system alright, but not /data... I'm fearing that NAND corruption bug I've heard of, except I don't see how I would've caught it...
All right, so I've now confirmed that the Andromeda kernel indeed has the hard-brick bug. Why on earth anyone in their right mind would release a kernel based on that broken leak is beyond my comprehension.
And, to add injury to insult, the devs know there's a problem, yet do not warn about it in the OP, but they mention it some thirty pages into the thread. Thanks, guys!
Anyway, I'm currently scanning my internal storage for damaged areas so that I can custom-PIT my way around it.
Useful posts for reference:
http://forum.xda-developers.com/showthread.php?t=1760107
http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hopefully I'll see my phone booting tonight.
Using the patched PIT workaround, I now have my phone back up and running 2½ GB lost on the internal storage, though, but hey - beats being a paper weight!
Hi All
I had my phone on charge overnight (as usual), but when I got up this morning, I had an error "Device memory damaged" on screen, it says "The data partition has been corrupted. You need to reset the device to factory defaults. This will erase all your data" and has a button marked "Reset device"
When I tap the button, it boots to recovery, TWRP scrolls some text on screen, it then reboots back to the same error screen.
If I manually boot into recovery and try to wipe data, I'm told
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to wipe '/data'
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
I tried flashing recovery-clockwork-6.0.4.6-i9300 via heimdall to see if that had any more success, but that failed too (although I'm not sure if that was due to the phone or my heimdall set-up).
I've spent most of the day trying to find a fix, but I'm just going around in circles.
The Phone is an i9300, and it was running UltimaROM 17.1
Any ideas how to get my phone working again?
~S
First flash the latest stock firmware for your country then factory reset in recovery before first boot.
If that fails then try the rescue firmware thread in general forum, use the 4 3 version and pit file that thread contains.
If that also fails then it sounds like your memory is indeed damaged.
I wouldn't advise anyone charge the battery in their phone overnight, the processor and nand memory is then running 24/7 and will obviously fail sooner
Sanukk said:
Hi All
I had my phone on charge overnight (as usual), but when I got up this morning, I had an error "Device memory damaged" on screen, it says "The data partition has been corrupted. You need to reset the device to factory defaults. This will erase all your data" and has a button marked "Reset device"
When I tap the button, it boots to recovery, TWRP scrolls some text on screen, it then reboots back to the same error screen.
If I manually boot into recovery and try to wipe data, I'm told
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to wipe '/data'
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
I tried flashing recovery-clockwork-6.0.4.6-i9300 via heimdall to see if that had any more success, but that failed too (although I'm not sure if that was due to the phone or my heimdall set-up).
I've spent most of the day trying to find a fix, but I'm just going around in circles.
The Phone is an i9300, and it was running UltimaROM 17.1
Any ideas how to get my phone working again?
~S
Click to expand...
Click to collapse
I have same problem but phone is s7 edge. Did you found a solution.
Unable to mount is a twrp issue. I've seen it many times before.
I have solved it on a custom rom by flashing an official clockworkmod recovery.
I have solved it on a stock firmware by flashing a stock recovery
I have solved it by flashing back to stock completely.
*I have read that some people cannot recover their phone from that state.*
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) ...