Related
By default, CWM makes a backup to my external sdcard. The only problem with that is my sdcard is 1GB, which is a little under the total size of the backup, and so the whole backup doesn't complete. One solution would probably be to remove the external sdcard and run CWM so that the default storage location would be the internal sdcard, but that's annoying. There should be a way to specify the backup location.
EDIT: I removed the external SDcard, and now I get the error E: Can't mount /sdcard. So I guess it won't use the internal card if it can't find the external one... So I pretty much can't backup my ROM. And the problem can't be that it doesn't see the internal SDcard, because I can go to choose zip from internal sdcard and it will show the folders from the internal card.
If you using romracers cwm you have options for both..
XRange said:
If you using romracers cwm you have options for both..
Click to expand...
Click to collapse
Sorry I should have specified. I flashed CWM from ROM Manager. I guess I'll try out romracer's cwm.
EDIT: Yup, romracer's cwm work's great, and it was easy to flash.
So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
I'm running 3.1 rooted
I've flashed Thor's 1.4.2 recovery.
I have two sd cards: a 2g and an 8g.
Both work when accessed on a PC and on the iconia.
Neither work in cwm so I can't flash any roms.
I have tried formatting the sdcards on two different PCs. for the 2g I tried both fat and fat32. The 8g is fat32. In every case cwm says it can't mount it.
Additionally, I can't seem to use a USB key, although that may be that i don't know how to use it.
Thanks for any help.
-Bert
When in CWM and you go to install zip from sdcard do you see any folders where you choose the zip. Just wondering if it isn't mounted already. Physical sdcard is in /mnt/external_sd
and not /mnt/sdcard.
PsychosisNC said:
When in CWM and you go to install zip from sdcard do you see any folders where you choose the zip. Just wondering if it isn't mounted already. Physical sdcard is in /mnt/external_sd
and not /mnt/sdcard.
Click to expand...
Click to collapse
Thanks for your reply. I'm prety sure It's not mounted already.
I'm attaching a screenshot to show the exact message I get when trying to browse for a zip. I get a similar message when I go to mounts and storage and try to mount the sdcard.
im bumping this because I'm really becoming concerned that the device is defective in some way.
I'm hoping that someone can give me some guidence on what I may be doing wrong.
So, brosell, did you figure out a solution? I have the exact same problem - cannot mount sdcard in recovery and I get the exact same message.
When the system is booted normally, the internal storage mounts ok as /sdcard
EDIT:
It seems CWM treats the external sdcard as /sdcard, not the internal storage. So, to flash an update, you need to place it on an external SD card
I always get that error, and I never had to mount anything using cwm, just booted it selected the zip to flash and flash. I still don't mount anything...?
And the zip goes on the external sd not the inturn
Can't format SC Card in Window. If won't mount.
Guys,
Unfortunately SD cards for Android must be formatted by Android. If the card is not properly formatted CWM can not mount it, nor can CWM format it. The best way to get it properly formatted is to put it into an Android Phone and use its format functions. There really is no way on the Icona Tab to reformat an improperly formatted card or a new formatted card. If you don't have an Android phone borrow a friends. You will know that it is properly formatted when you see a lost files folder created on the card by the Android phone formatting process. This is a common problem that many people encounter when performing their first ROM flash. If it was formatted under windows as FAT 32 you can access it and store on it in normal operation mode. But ClockWorkMod can not mount it in recovery mode. Hope this helps. Good luck.
Can mount SD card in Recovery
I should have also mentioned last night in my post here, that my experience has been that it is much easier to flash a new custom ROM from a USB thumb drive. Flashing a custom ROM from USB seems to be less problematic than from an SDCard that appears otherwise to be good and formatted with FAT32, but CWM can't mount it. You can fast format the thumb drive on Windows to clean it off. Then copy your custom .zip ROM to be flashed on to the thumb drive from within Windows then insert it into the USB port of your Icona Tab, boot into CWM recovery (I'm assuming you know how to do that so I won't go into it here.) I forget exactly where in the CWM menu it is, it might be under the CWM advanced sub-menu but it say's something to the effect of Install zip from USB. It always works for me with no problem. The advantage is that you do all your prep work on Windows and then flash from the thumb drive which I believe has an ISO standard across all platforms and usually comes already per-formatted. This is an alternative method if you can't get your SDCard properly formatted (see my previous post in this thread for how to get it properly formatted so that it will mount under CWM.) Again, good luck!
I want to cry!!
I tried re formatting! Nothing! Cmw is not on sd card! Nothing is working! Still stuck on acer start screen! Yes i am a noob! But i read alot into this stuff b4 i do it! I wish there was someone i can have come to my house and do this for me! I have tried everything!!!!!!!!!!! So frustrated!!! Someone pls help me!!!!
in CWM recovery, there are 2 options,sd and "internal sd" i think(for me atleast). i chose the internal sd and it mounts.
brosell said:
So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
-Bert
Click to expand...
Click to collapse
Thank You Sir! been looking for this fix for a long time
brosell said:
So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
/QUOTE]
thanks brosell, for the solution,
I have a 512MB SD card in the g5360, was FAT formatted. reformatting the sdcard with the tool from sdcard.org worked for me as well, afterwards it could be mounted by the stock recovery
and could install update.zip (prior to install CMW)
kr, Erik
Click to expand...
Click to collapse
Hi!
So I'm running civato's FLEXREAPER-R6 ICS 4.0.3 ROM on my Iconia A500 after using timmyDean's "root-3.2.1-V4.7z" method to root my stock HC 3.2.1 ROM. I had ClockworkMod Recovery v5.0.2.3 (rev 1.3.4 by thor2002ro) and was unable to do a full Nandroid backup so I upgraded to the latest ClockworkMod Recovery v5.5.0.x (rev 1.7 by thor2002ro) but I'm still having the same issue.
When I try to backup data I get the error "Error making a backup image of /data!" and then when I look at the sdcard in \clockworkmod\backup\YYYY-MM-DD.HH.MM.SS I see "data.ext4.tar" and the size is 4,294,967,296 bytes), which is exactly the 4GB filesize limit on a FAT32 partition. Looking inside the data.ext4.tar file, I see data/app and all the .APK installer files for apps installed on my Iconia plus a few .ZIP files as well. ES File Explorer won't show me how big /data/app is but DiskUsage says it's 4.7GB. From what I'm reading Android needs a copy of all the APK user-installed app installation files of in /data/app so that it can restore the default data/configuration when requested (under Settings/Apps/Manage Apps/Delete Data & Cache). So...how can I get a successful Nandroid backup if I have more than 4GB of apps installed? Can the data portion be broken up into <4GB chunks? Or can Nandroid/Recovery be updated to support exFAT or NTFS? Or would it be safe to exclude /data/app from the backups?
Since I've been unable to do the Recovery/Nandroid backup of "data", I've been doing a custom backup of everything except for data and then backing up all my installed apps and settings from inside the OS with Titanium Backup. But with this method, a catastrophic failure would still require me to use Recovery to restore the OS and then use Titanium to restore app my apps.
What's the solution?
You can try doing several backups, in other words, do a nandroid backup of /data separate from the other back ups of /system /boot /recovery and other paritions. Then when you have to restore, first restore the backup with your system partitions and then restore your data partition afterwards. You are probably backing up to many things to have a nandroid file that large anyway. When you do a full data wipe it does not wipe the data on the internal sd card only the data on the data partition.
cruise350 said:
You can try doing several backups, in other words, do a nandroid backup of /data separate from the other back ups of /system /boot /recovery and other paritions. Then when you have to restore, first restore the backup with your system partitions and then restore your data partition afterwards. You are probably backing up to many things to have a nandroid file that large anyway. When you do a full data wipe it does not wipe the data on the internal sd card only the data on the data partition.
Click to expand...
Click to collapse
Hey cruise350! I have an Evo 3D as well. I'm running Virus's "Eternity 3.0 r193 ROM" with the Stock theme on my Evo 3D, how about you? Anyway, I have tried doing separate Nandroid backups. I can backup everything but "data" and that will complete just fine. I don't see any way to break up the "data" backup into multiple smaller backups. But as I said, if I backup everything else with Nandroid, I feel pretty confident that I can restore all my apps/data with Titanium.
Would it be safe to try to move /data/app temporarily somewhere else (such as /mnt/sdcard), do the Nandroid data backup, and then move it back?
It seems to me that doing full wipe (system, data, cache, dalvik cache, superwipe, etc) would wipe out /data and everything underneath (including /data/apps) but that it would get recreated automatically when I restore everything with TB, right?
The way to get rid of that problem once and for all is to format your SD card as EXT4... You won't be able to read it with non-Linux (or BSD) OSes after that, though. Mounting via USB should still work, as this doesn't access the SD filesystem directly...
I would try changing recoveries then, I am using RA recovery and it has a compress backup feature. It takes about 45 minutes to do a nandroid when compressing but it cuts the size of the backup significantly. I bet RA will solve your problem though. And, I am running Steelrom on my Evo 3d. It's really stable, has some good tweaks, and the battery life is incredible.
haag498 said:
The way to get rid of that problem once and for all is to format your SD card as EXT4... You won't be able to read it with non-Linux (or BSD) OSes after that, though. Mounting via USB should still work, as this doesn't access the SD filesystem directly...
Click to expand...
Click to collapse
Thanks, haag498. That's an interesting idea. So any Android OS or Recovery would be able to read/write to an EXT4-fomatted SD card? It would work in both my Iconia A500 and my Evo 3D both in Recovery and inside the OS? That might be a good option. I see that EXT4 supports very large filesizes so that problem would go away. What tool would you recommend for formatting the SD card with that filesystem? Can it be done from inside Android?
Not being able to mount the filesystem natively in Windows might present occasional inconveniences but it shouldn't be a major problem as long as the Android devices can present the storage as USB Mass Storage mode. That being said, I have some issues with the Iconia when accessing the storage over USB. Namely, when I try to move files and folder off the device or delete them from Windows when attached via USB, the task often won't complete. I've worked around the problem by just doing internal moves, deletes and renames from inside Android (using ASTRO or ES File Explorer) and, if necessary, mounting the SD card directly in my Windows PC, which won't be possible anymore.
cruise350 said:
I would try changing recoveries then, I am using RA recovery and it has a compress backup feature. It takes about 45 minutes to do a nandroid when compressing but it cuts the size of the backup significantly. I bet RA will solve your problem though. And, I am running Steelrom on my Evo 3d. It's really stable, has some good tweaks, and the battery life is incredible.
Click to expand...
Click to collapse
Okay...so if I wanted to install RA Recovery instead, would I flash that from inside CMR? I have "Acer Recovery Installer" installed as well but I believe the version of CMR I'm using is newer than what that tool would have been able to install. So, what's the procedure to switch to RA from CMR? Any other features of RA that you prefer?
JesseAaronSafir said:
Okay...so if I wanted to install RA Recovery instead, would I flash that from inside CMR? I have "Acer Recovery Installer" installed as well but I believe the version of CMR I'm using is newer than what that tool would have been able to install. So, what's the procedure to switch to RA from CMR? Any other features of RA that you prefer?
Click to expand...
Click to collapse
You can flash from within CWM. If you look in the RA threads, you will find some flashable versions. I use 3.15, as I have been lazy to update to 3.16.
No wipes needed. Just install zip from SD
http://forum.xda-developers.com/showpost.php?p=22392691&postcount=104
JesseAaronSafir said:
Thanks, haag498. That's an interesting idea. So any Android OS or Recovery would be able to read/write to an EXT4-fomatted SD card?
Click to expand...
Click to collapse
They should, if they're using a reasonably up-to-date Linux kernel, as EXT4 is built in for these... If you want to be absolutely sure, use EXT2/3 (they're pretty much identical from a user point of view), which still support large files and all, but are somewhat slower (and they can't use more than 4TB, which shouldn't be an issue anyway...).
JesseAaronSafir said:
It would work in both my Iconia A500 and my Evo 3D both in Recovery and inside the OS?
Click to expand...
Click to collapse
Read above.
JesseAaronSafir said:
That might be a good option. I see that EXT4 supports very large filesizes so that problem would go away. What tool would you recommend for formatting the SD card with that filesystem? Can it be done from inside Android?
Click to expand...
Click to collapse
Formatting the SD card can be done from any Linux live CD (Ubuntu, Knoppix, ...) or from within Android (if you're rooted and have a chroot Linux) using parted (or cfdisk) or some GUI tool like gparted... Internally, they'll all use mkfs.ext4, which is anything but user-friendly, though...
JesseAaronSafir said:
Not being able to mount the filesystem natively in Windows might present occasional inconveniences but it shouldn't be a major problem as long as the Android devices can present the storage as USB Mass Storage mode. That being said, I have some issues with the Iconia when accessing the storage over USB. Namely, when I try to move files and folder off the device or delete them from Windows when attached via USB, the task often won't complete. I've worked around the problem by just doing internal moves, deletes and renames from inside Android (using ASTRO or ES File Explorer) and, if necessary, mounting the SD card directly in my Windows PC, which won't be possible anymore.
Click to expand...
Click to collapse
That's actually a known problem... I usually just use a NAS for data exchange, as it has plenty of space and good speed, even on WiFi. Another way to do it would be a USB drive (2.5'' hdds tend to need more power for spin-up than they get from the internal port, though). Also, as I use Linux on all my computers, mounting EXT4 partitions is no problem for me ...
Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.
Hello, in this thread I'll show you how to move the /data partition to your microSD card in order to increase the storage space, and bypass the speed limits of our poor eMMC memory.
Disclaimer:
I'm not responsible for any data loss or any other kind of problems. Follow the tutorial and everything will be fine. In case of problems, reflash the boot.img of your ROM or reflash the whole ROM and you'll reboot to Android using the usual /data partition.
Pros:
more storage space
slightly shorter app loading times
Cons:
you cannot eject your SD card from your phone when it is turned on
Requirements:
a computer
some kind of adapter to put the microSD into the computer
a 16 GB (or higher), class 10 (or better) microSD
Any recent L (untested), M (tested) or N (tested) ROM and TWRP 3
these two zips: https://www.androidfilehost.com/?w=files&flid=113749
Step 0: prepare the SD card
using your computer, shrink the only partition you have on your SD card and leave at least 6 or 7 GB of unallocated space. Be sure not to shrink too much the first partiton (which will continue to be used as a normal storage partition) because you'll have to store a nandroid backup in it! This is why I recommend you to use a 32 GB SD card. Then create a new partition using the unallocated space. If you're using Windows or OS X, create a fat32 partition, if you're using Linux, create an ext4 partition.
Step 1: patch the recovery and backup, then restore
In the AFH folder I posted in the requirements you'll find two zips. Download them and reboot to recovery, then take a nandroid backup of your /data partition and store it on your SD card (TWRP will automatically use the first partition of the SD card, the one with all your current content). Now flash twrp_fstab_patcher.zip. Power off your phone and then turn it on and boot into TWRP. Now go to Wipe > Advanced Wipe > select Data > Change Filesystem > choose ext4 or f2fs (as you prefer). Confirm and check that the Data partition has been formatted to the chosen filesystem. Restore the backup you've made.
Step 2: migrate the data of the internal storage
Reboot to Android and using a file manager that lists both of your SD card's partitions (FX works for me) and copy all the content of your internal storage (photos, music, app data etc.) to *2nd_sdcard_partition*/media/0.
Step 3: patch the kernel
Now you're ready for the last step. Flash kernel_fstab_patcher.zip and reboot. The end!
Warning: you need to reflash kernel_fstab_patcher.zip after you change/update ROM/kernel otherwise your phone will use the "old" data partition! Similarly, you must flash twrp_recovery_patcher.zip each time you update TWRP 3 (this doesn't happen very often).
Well, I hope I put all the needed info in this thread, I'll keep it updated with my latest suggestions etc. If you have got problems, report them. If you find something that doesn't make any sense in this post, tell me. Enjoy!