So I just finished putting the final tweak on a re-install of Vegan Ginger. My previous install had some issues with long boot times and the Gallery was not synchronizing with my Picasa Web Photos. The last step in the process was wiping the external SDcard which was complaining from Ginger since I formatted originally to FAT32 on my PC and was unsure of the "preferred" format for Android/Gingerbread. So I went into settings, and under sdcard2 selected "Erase". I then attempted to mount and got some errors regarding the sdcard was empty or not formatted, so I selected "Format". I attempted to re-mount again and got the same error. So I figured that I would give the CWM format a try and rebooted into CWM. I then selected "format sd-ext" and CWM complained that apps2sd did not exist. I then rebooted the tablet through the CWM main menu.
Somehow in this process my internal sdcard was formatted!
The next boot, Vegan Ginger displayed the G Tab Devs and Vegan Launch screen but would boot loop about 5 times until the screen went black.
I was able to boot into ClockWorkMod (CWM) and attempts to mount /data or /sdcard result in:
mount /sdcard
Code:
Can't mount /sdcard
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
mount /data
Code:
Can't mount DATA:!
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
I attempted to do a restore through CWM which resulted in a failure.
Any suggestions on how to get back to a running system? My guess is the following:
format data
format sdcard
The following information would be very helpful:
Is there any chance recovering the current system?
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
What is the preferred Android external SD card format?
Thanks!
Run nvflash from the dev section. There is nothing there to save anymore
I had this same issue with a 32gb micro sdcard formatted in fat32. After finally getting things back in order with nvflash/wipe/reload, Im hesitant to try again. Any idea on the cause or how to prevent it from happening?
brianafischer said:
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
Click to expand...
Click to collapse
In CWM, do a backup (this is the nandroid backup mentioned often here on xda)
When you boot into android, copy the backup file OFF the device, and onto a desktop PC, or a USB flash drive - anywhere but onto any storage that is on the gtab.
Repeat both those steps any time you're about to make major changes, or do any formatting, or otherwise play with sharp objects near your gtab.
When you screw the pooch, you can always copy your latest backup back to the backup directory on the gtab, and then restore from CWM. You may need to nvflash first to get the thing into some sane state, of course. But you'll have the image which will save lots of setup time after...
Hi guys, I am wondering if anyone can help out. I am trying to flash Gingerbread stable edition RC1 on to my Zpad/G Tab but I am have a lot of difficulty. About 4 months ago, I installed Vegan5.1 on to my Zpad using cwm, I managed to install and all went well. Yesterday I decided to install Gingerbread on to my Zpad, I followed the same steps when I flashed Vegan 5.1, But when I rebooted, it starts up but does not boot up, it seems to hang at the initial starting phase. I followed the same steps that I used when I installed Vegan5.1.
Eventually, I decided to go back to Vegan 5.1, I tried the same method that I have been using to install Gingerbread and it worked like clockwork. So I am now back with Vegan until I can work out how to install Gingerbread.
I am at a loss.
CWM internal MOD v 2.5.1.1-bekit-0 already installed
Booted in to cwm
partitioned SD card”, first option 2048, then second option used 0
Rebooted back in to cwm v08
In mounts and storage set to unmount system and unmount /data
Selected install zip from sdcard and choose zip from sd card and pressed home
Selected gingerbread ROM
Installed ROM
Received the message "install zip from sdcard complete"
Back to cwm menu
Set to unmount system and unmount /data
Selected wipe data/factory reset, Navigated down to “Yes – delete all user data”, and select it to wipe out user data and all the cache.
Then selected reboot.
The unit then starts and hangs on the bootup logo and does not proceed.
If anyone can be so kind as to help out, I would be most grateful. So to recap, I have Vegan 5.1 installed, tried to flash Gingerbread using cwmv8, when I reboot, it wont go past the initila logo and appears to hang.
Thanks All for the help
OKay, So i installed update for checkrom revo4 via Kitchen pro. Everything is working like charm. Now i wanted to change the kernel. Downloaded it, but when it boots to cwm to install is, it says error mounting sdcard 20s, and counting down. no good
Tried manually mount sdcard in cwm, gives error mounting sdcard,
So how to proceed
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
midfieldmaestro said:
So I flashed the latest nightly 9-2-02 and I kept on getting the error in my camera app external device storage needed. I figured the problem was not with my sdcard, but with my internal sdcard folder. When I go to flash via recovery, it says e:/unable to mount internal sd card. Is there anyway to remount this card?
I have Hboot 1.15, s-on. I know some other people have been having this problem, anybody have any ideas?
Click to expand...
Click to collapse
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
note: with dumlock there is no need to fastboot the kernel, with dumlock in boot it can write directly, the reason this method isnt the most ideal is that you are writing to boot multiple times but like i said i think it is the most flexible for newer users
om4 said:
it may some how have gotten corrupted. update twrp to the latest if you dont have it (2.2.2) and then boot into recovery and do a back up, go to advanced and install htc dumlock and reboot, i dont personally like dumlock but it is the most flexible solution barring a few extra steps, go into apps and launch dumlock, here it will write recovery to boot and then reboot directly into twrp because you technically no longer have a boot, it has been replaced by twrp, then go to advanced again and restore boot and go back to menu, go to wipe select internal, this will reformat it, then do the usual factory reset, wipe cache, dalvik, system and then flash cm10, gapps, and reboot, if all goes well you can go ahead and flash any extras you might have had prior
Click to expand...
Click to collapse
Thank you for this explanation, but I believe (thanks to a user from the CM10 thread) that it is indeed corrupted like you said. But instead of going through that, I went and mounted my internal drive via TWRP to my computer. So I have a macosx (ugh) and I reformatted it, but it had trouble doing it and it didn't work properly. Normally in windows it would do a much better job as you are able to set it FAT32 etc etc. So when my phone started up, the phone recognized it was a corrupted drive and repaired it itself, and voila, everything is working, I am able to side load apps and actually download things.
well i wrote those directions to give you the best chance at getting it to work, I always prefer a fresh start when possible. my instruction is also non reliant on a computer which to me is also a plus as windows/mac/and linux can interfere with usb. Glad to hear you got it working
Formatting work
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
g_brownell said:
I would like to thank everyone who posted, I rebooted my EVO to TWRP recovery, mounted the USB drive and connected to my windows PC. The USB drive popped up and windows asked if I wanted to fix it, I said yes and formatted as fat32 adn after unmounting and rebooting, the sdcard mounted perfectly!
Thanks you!
Click to expand...
Click to collapse
So you got the internal to work.
Have you had any issues with mounting the external?
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Yhcho said:
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Click to expand...
Click to collapse
I have followed this thread and I got an error message saying failed due to low battery. I will just charge the phone for a while and see if it gives same error.
I have done the fastboot recovery method from here and its keep giving me "failed (remote: not allowed)" messages.
my Legend is already rooted and currently on S-off.
I have solved the problem.
It was memory card problem. my legend works after installing CM7 using different SD card.
I am suspecting if its because I have messed up something with memory card while dividing partitions to install a Jelllybean rom,
However the faulty memory card is still functioning well on my pc which made me think there is no problem with it.