Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
*********** Restore Nabi to Factory 1.9.37 from ANDROID ****************
Install recovery to Internal or External SD card?
-If external make sure your card is installed-
1. Internal SD
2. External SD
Choose an option:1
Files are prepared. Press any key to begin restore.
Press any key to continue . . .
rebooting...
When TWRP is done booting press enter
Press any key to continue . . .
Pushing stock recovery to your device
Ignore external SD card error if you have none installed
This files are 1.2GB this will take many minutes. Please wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
mkdir: can't create directory '//data/media/TWRP/BACKUPS/0123456789ABCDEF/abcdst
ock123': No such file or directory
1332 KB/s (8388608 bytes in 6.149s)
9 KB/s (48 bytes in 0.005s)
Click to expand...
Click to collapse
jumbojimx said:
Hello, I have a Nabi sitting around and decide to get it out, update it and put it to use. My flashing skills are novice, I do a phone or tablet once in a blue moon and it it usually been with a AIO or relatively trouble free.
I have TWRP 2.3.3.0 and the Kernel is 1.9.3.7 from last year I install custom recovery
I attempted to install Monarch UI Removed/SuperSU & SU Binaries Installed including BusyBox 3.0.13( Fuhu/Nabi/Keenhi Stuff Removed ) - n3wt when that failed I attempted Stock Rom 3.0.13 via TWRP - aicjofs
I did a full Wipe, attempted to install with TWRP and ADB sideload.
The ADB sideload reaches 100% on PC and is marked failed on the Tablet in TWRP sideload UI.
Installing in TWRP I get the following errors in the Terminal
Code:
Updating Partitions details...
E:/Unable to mount '/data'
E:/Unable to mount '/data'
E:/Unable to mount '/system'
E:/Unable to mount '/cache'
E:/Unable to mount '/data'
E:/Unable to mount '/addon'
I also tried installing Stock Version 1.9.37 with similar results.
In the mount menu I can't selec "Using internal storage" or any of the mount options.
Also all wiping options for cash and system fail.
Next I re-installed TWRP 2.3.3.0 through fastboot to make sure everything was clean and it appeared to all take, and I still get the same results trying to flash.
So I am at a loss as what to try next and would appreciate any help.
While posted I've been trying NabiLab here is the error I received on a stock recovery.
Click to expand...
Click to collapse
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Thanks, got it fixed.
It was the wrong TWRP. Then I wasn't seeing any recovery files. ADB was giving me an odd generic serial number, I did a back up and then dumped the files in the TWRP created folder and they appeared.
Original Post.
aicjofs said:
Wrong TWRP version is my guess. http://forum.xda-developers.com/showpost.php?p=62391871&postcount=2635 There are the 3 versions you need to try.
Click to expand...
Click to collapse
Thanks for the reply.
I tried all 3 versions of TWRP in your post . TWRPv263 for ICS Nothing (cache,data,system, extsdcard etc) will mount. TWRPv285 for JB&KK Everything but /system will mount.
Using all 3 versions of TWRP I tried to install 3013stock.zip and 3013bootloader. No files from the extracted zip show up in TWRP recovery tab.
So I assume the issue I am aiming at is getting /system to mount in either KK or JB version of TWRP. v285?
Click to expand...
Click to collapse
Related
Hello,
I just unlocked my rooted prime and flashed the newest CWM via Rom Manager.
Now I can't backup my existing rom. Also I can't install any custom rom.
When I hit backup in CWM, it sais "Can't mount backup path"
When I hit install zip from SD, there is another error "Can't mount /sdcard/
I also tried TWRP Recovery, with no success.
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Screenshots:
ttp://img37.imageshack.us/img37/561/img20120616114555.jpg
ttp://img801.imageshack.us/img801/2844/img20120616112128.jpg
Just for info: My device is still running stock rom and is encrypted.
Has anyone a solution for this?
Thank you for your help.
With best regards,
B-Paul
Restore is borked in the latest version of CWM. Push 5.8.2.0 and everything will be OK.
Just tried, still the same error message
Brausepaul said:
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Click to expand...
Click to collapse
You can't mount /sdcard/ (which is a symlink to /data/media/) when device is encrypted, cwm/twrp do not know how to handle this.
edit: Looking at my Nexus, only way to step out of encryption is to use fastboot. It should work like this for the Prime as well.
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
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Formatting emmc using mkdosf's...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Click to expand...
Click to collapse
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
E:A render request has failed.
Click to expand...
Click to collapse
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Click to expand...
Click to collapse
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
same problem
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
henkienl said:
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
Click to expand...
Click to collapse
degogar said:
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
Click to expand...
Click to collapse
With the flasher I used all I had to do was remove the battery, plug in the usb and let the flasher do its work.
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) ...