Hello.
I am getting an error that says "not enough space in /data, found 4G" when flashing Ubuntu Touch preview on my Nexus 4. It is running 4.2.
Any ideas? Thanks!
Same - and fixed
Vakman said:
Hello.
I am getting an error that says "not enough space in /data, found 4G" when flashing Ubuntu Touch preview on my Nexus 4. It is running 4.2.
Any ideas? Thanks!
Click to expand...
Click to collapse
I had the same thing happen on my Nexus 7. Try restoring to factory settings by entering Fastboot ~ Recovery ~ Factory Reset.
Good luck!
Hello,
This is often caused by the device not having enough space in the /data/ mount for the initial adb image push. If the initial image cannot fit on the Internal SD Card, this error will happen. A factory reset is the fastest way to resolve this, you can also search for old nandroid backups or roms that could also be on the phone/tablet.
I made the mistake of encrypting my phone without realizing I had to use a password or pin for unlocking, I just wanted to have to type the password on start up, but w.e. From what I understood, though, I'd be able to do a factory reset to remove encryption.. Evidently its not that easy. :/
Now I'm trying to do a factory reset, but I can't do anything in clockworkmod recovery (I think) because of the encryption. I just get this when I try:
--Wiping data...
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext...
Formatting /sdcard/ .android_secure...
Error mounting /sdcard/ .android_secure...
Skipping format...
Data wipe complete.
I've also tried doing a factory reset from the settings, and it just reboots the phone. I've been searching online for 5 hours, and I have no clear idea of what to do. I found this: http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html but I can't get the driver to work properly on windows 8.1.. I followed the instructions for windows 8 here: http://forum.xda-developers.com/showthread.php?t=1996051 but when I type "fastboot devices" nothing shows up. Is there anything I can do to solve this??
Edit: Tried Using The Nexus Root Toolkit, it gives me a success message when checking the driver. But no luck with adb/fastboot recognising the device at all.. When I use it(nexus toolkit) to flash the stock rom it doesn't work, Ill try with "force flash" enabled and report back.
Edit: Was successful flashing stock, no more encryption. So other than adb fastboot not working, problem solved!
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Are you sure that's the right CWM for CM 12.x? To flash 10.2 long ago I used CWM 6.0.2.x
Seems unlikely that an earlier version would be used for CM 12.x
That's a good point, your're on to something. I saw that in the cyanogenmod tutorial it says CWM doesn't support CM > 10.1.3. So your almost certainly right. (Why that's the active link in the beginner tutorial is still confusing to me.) I also see that CWM says it is not in active development for acclaim. So now on to twrp.
I tried the "Bootable SD card" instructions on the twrp acclaim page but can't get that to work. I've copied the img file to the root of the SD and renamed it to recovery.img but I don't know how to "boot TWRP using the cyanoboot menu from your sdcard". There is no cyanoboot menu on the sd card, it's only the img file, so no wonder nothing boots. How do I get the cyanoboot menu on the sd? My initial search led me to a page that has complex instructions on formatting the sd. Is that really the only way to get cyanoboot and ultimately get twrp to run??
Alternatively I've tried to burn the img to the sd using the dd command (thinking that an img file is meant to image an entire sd, not just live as a file on the sd). That gives me the errors that I posted originally (see section "Potentially related side note"). So I think you're right that I need a recovery other than CWM, but how do I get twrp to work?
Being a noob I feel like I'm missing something obvious but have been working for hours (ok, days) with no success.
Yeah, I think it *might* be that CWM is not going to cut it for CM 12.x, but the truth is I have no experience with TWRP so you're asking the wrong guy
I assume you looked at the "official" CM 12 thread here. For me the problem is what it is for you. There's not enough info there for someone who can follow good directions but is not already very familiar with all the ins and outs. What's needed is for digixmax to write a "how-to", but the last one he did was for CM 11. His directions are very clear. I was able to follow them as a noob for CM 10.2 without any trouble.
The hard way to do this is to sneak up on it by starting with CM 10.2, updating to CM 11 following digixmax's directions and then....well there must be a way to go from CM 11 to CM 12....maybe.....
I notice the sparse directions at CyanogenMod for CM 12 on Acclaim do refer to CWM so who knows?
coloradonate said:
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Click to expand...
Click to collapse
Your description sounds exactly like the SD card was not properly formatted with an MSDOS partition table with a primary partition as FAT32. From the CyanogenMod wiki: "Put the micro SD card (SD card from now on) in the computer. Backup all the information on the SD card. Everything on it will be deleted. Make a new MSDOS partition table and add a FAT32 partition as the first primary partition with a minimum of 300 MB. Then make sure you enable the boot and lba flags. This can be done in Ubuntu using GParted. Formats like EXT2, EXT3, and EXT4 do not work. It is not necessary to allocate the entire card. You can add other partitions to the card, but they need to be manually mounted on your Nook anyway." When you set up the partition table a the primary partition, the format must be written/saved to the SD card. Unmount the SD card and mount it again to ensure that the formatting took. Once that is verified then you can write to files to the SD card, unmout it again, and insert it into the Tablet and go through the install steps.
I'm looking at putting 12.1 on my Tablet, which currently has 10.2 and runs pretty well. But the basic setup instructions for the SD card are the same - MSDOS table with a FAT32 primary partition. You can add 3 more FAT32 partitions, but they must be primary and FAT32.
Thanks for the reply. Unfortunately I did partition just like it asked. It is set as Primary, Fat 32, and the boot and lba flags are on.
I'm still stuck, but I'm understanding a few things. The Cyanogenmod install wiki is obviously out of date (even though it says it was last modified Oct. 25, 2015 when I looked tonight). The wiki has you download CWM 5.0.x, which is a 2012 file intended to work with CM 10.x. Then later in the same wiki it says that CWM no longer supports CM>10.1.3, so obviously it is not up to date for CM 11.x and 12.x. Unfortunately the wiki was not updated to provide a link to a recovery that works...at least not that I've found. I've lost faith in that wiki.
I'm totally fine using Twrp, but I can't even get a version of twrp that works with the latest CWM 12.1 release. Should be simple, but for some reason can't get it to work. If anybody is still willing to try to help me, please point me in the right direction!
And here's a total noob question that may solve my problems: why does the cyanogenmod downloads page have a link for the .zip and a "recovery" .img? Is that img THE recovery that I should be using for that particular version of CM? I tried writing the image to the SD but have the same SD errors as I previously reported.
So...did you try following these directions? They are sketchier than I am comfortable with but it is the "official" thread. And there's certainly a recovery link there.
I'm thinking about upgrading from 10.21 but I just can't find directions that make me feel like I'm not going to trash what I already have
2 things to report: 1) I'll respond to the reply above. 2) got it working with CM 11!
1) Yes I have tried following that and read it more times than I can count, but my extreme noobiness has left me floundering in tutorial after tutorial. I tried fastboot, couldn't get it to install. Finally got it to install, couldn't get it to connect to the NT. I tried bootable SD, couldn't get it. Tried root, couldn't get that. Why couldn't I get any of that to work?? I have absolutely no idea, but I hit dead end after dead end and was left unbelievably frustrated by this whole thing. On to #2...
2) I got CM 11 to work! I don't care one bit that it's not 12.1, what's important is that I got CM finally running on my stock NT! I followed this tutorial (http://forum.xda-developers.com/showthread.php?t=2692403). It required one *very* slight modification that I posted at the very end of that thread (post #14.) Don't laugh at my excitement, I'm just happy this things is finally over. (For now at least...I'm sure I'll be digging further now that I've gotten this far.)
I'm really glad that worked for you I still remember how I felt when I got CM 10.21 working starting from stock on an ebay special.
You've given me a little push to get serious about upgrading to CM 11 or perhaps CM 12. I need to read (and reread) those posts until I feel like I've got it down. Your discovery will help, I'm sure.
Just to wrap up this thread, I got CM12.1 to work! Please refer to my last post (post #18) in the following thread for somewhat detailed instructions for how I did it: http://forum.xda-developers.com/showthread.php?t=2692403&page=2#post63932363
I hope that explains it all to anyone interested, or anyone else who was floundering around like I was. Now I'm happily running CM12.1 and loving it. Thanks to all the developers, especially Digixmax for the post that finally helped me through this!
TLDR; After installing Remix OS for PC 3.0.207 on USB and booting in Resident mode, subsequent boots result in REMIXOSDATA partition corruption, and turning off 'Enable disk partition mount' under Experimental Features doesn't help.
Does anyone have a solution?
I realize this problem has been mentioned in several places like here, here and here, but the only solution proposed (turn off Enable disk partition mount under Experimental Features) doesn't work for me. Even if I turn it off on first boot, on subsequent boots the system still reports a USB corruption, and Windows shows the partition as Raw.
Ignoring the error message seems to be one way to live with it, but I feel like it's a shame to waste the partition disk space by leaving it unused.
I know Jide has stopped development on Remix OS for PC, but I am still keen to get Android running on my Windows 2-in-1 if possible.
Does anyone have any solutions?
Assuming you have installed to an ext4 partition, you might want to try 'sudo e2fsck -fv /dev/sdxy' in a Linux terminal. (change sdxy to your partition designation)
Thanks for the reply. I formatted my USB stick with Fat32. I've never tried formatting it in ext4 - I'll give it a go and report back. Do you think ext4 will avoid the whole corrupted partition problem altogether? Or does the 'sudo e2fsck -fv /dev/sdxy' command need to be done to fix the corrupted partition every boot?
Think I have misunderstood. Thought you installed from the USB to a partition on the PC. The command is to clean a dirty ext partition, often created when you force the shutdown, not every boot. I always use ext4, so I have no experience with running RemixOS on fat32.
Okay - no worries. Do you have Remix OS for PC installed on an ext4 partition on your PC? Does it work fine?
Yes I have RemixOS on one of my PC's partitions and it works well https://goo.gl/BJjB0X
Hi, I’m new so please be gentle….
How do I recover internal storage errors on Motorola Xoom MZ604.
Trying to upgrade Xoom to Omni 5.1.1 wingray, It installs but just blinks and antennae twitch - no access (even after sitting overnight) also tried Omni 4.4.4 no difference.
Went back to check TWRP3SD and found errors when wiping. Searched the internet (XDADevelop and elsewhere) for days and could find nothing for a fix. (BTW - I never have used a password on my Xoom)
Mounting internal storage (which has 0MB) indicates “Unable to mount storage”. Also, fails to mount /data and /cache, both with (Invalid argument)
Data and Cache have 0MB size and when trying to repair them, e2fsck gives error 8. System has size of 1007MB and e2fsck returns an error 4 when attempting repair. Also can’t wipe dalvik. Tried changing system from ext4 to FAT - error changing file system
Tried 3 versions of TWRP - 2.4.4.0-wingray/2.6.3.0-wingray/twrp3sd - no change in errors.
Funny - tried to fastboot flash recovery with multiple versions of CWM and all images error and can’t be sent.
In the beginning TWRP couldn’t see/mount the SD card and I believe at that time it mounted internal storage and had a value for Mbs (tho I can remember the amount). I went through the process of wiping and didn’t pay any attention if it worked or not. Sometime after (don’t ask me how) it could see the SDcard and I could install the ZIPs
Also, before this process when Xoom was in Cynogen, when I connected to windows PC (via USB) I could see internal storage and SDcard - now in TWRP, I just see SDcard. When OMNI come up there is no USB connection.
I must have tried factory reset, format data, repair or change file system about 50 times with no change (bordering on insanity maybe?)
I can supply a recovery.log if it will help.
Any pointers would be greatly appreciated!
Thanks!
Solved!
A big THANK YOU to everyone that helped.
I used the instructions at https://forum.xda-developers.com/showthread.php?t=1052644 (thanks Eric Dabbs)
And found the xoom software downloads at http://www.xoomforums.com/forum/motorola-xoom-faq/11756-xoom-software-downloads.html (xoomforums)
This allowed entry into the initial rudimentary recovery whereby cache was deleted and a factory reset was performed. This version (3.0.1?) had about 3-4 updates. After applying all the updates, internal and external storage could be seen.
Then, upgraded TWRP to 2.7.1.0 big part. Internal storage was available and wiped all partitions (finally success) and installed a homemade Omni 4.4.4. Then, cleaned everything up in TWRP and installed a homemade OMNI 5.1.1. All working fine!
I see that there is a 6.0.1 Marshmallow for wingray….wish me luck!