I just got a Thunderbolt to replace Original Droid. With the Droid, I rooted no problem with superoneclick but always got the message E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) when trying to do a backup, nandroid or load a rom off sdcard. After getting Tbolt, I erased and reformated sdcard to fat32 in both my PC and in phone as well as factory reset phone to original settings. I re-rooted, and tried to flash Stock Rooted Gingerbread (Android 2.3.3) ROM Update GPA14 from Rom Manager but still got the same error message. My SDcard does work in terms of storing music or pictures no problem and I tried it in my wife's nook where it also worked fine. I took sdcard from her nook and used in droid with same issues? Very frustrating.
Related
Been having problems since flashing a Rogers stock Froyo Kernel yesterday. I made it back to stock but found I couldn't upgrade to any 2.2 ROMs, it seems that the ext4 lagfix was still activated on the Internal SD card and this prevented me from remounting anything on it or formatting. I am now stuck in recovery mode, although it is possible to get into download mode as well. I have access to CWM, and I've been farting around with wiping caches, formatting partitions, etc.
I have attempted everything I can think of to try to flash back to stock, including the Captivate tookbox 2.6 for Rogers, and the Odin 1-Click with the Master Clear option. Nothing seems to work. I get the classic message:
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA
The real problem seems to be that there is no update.zip on the internal sd card for me to use as a backup to flash back to stock. I am having no luck with the two software packages above, but it seems that if I could push my own backed-up update.zip I made a few days ago to the internal sd, I could get past this.
I need help. Please give me some advice.
Call off the dogs- after I installed the driver package that was included with Odin 1-Click I managed to get a master clear and a flash to the AT&T stock.
I must have spent 3 hours installing different driver packages today.
This has worked for me, depending on how bad the problem is...
Assuming the phone will boot, this will format the internal SD card.
GSM Master Reset: *2767*3855#
pkley said:
This has worked for me, depending on how bad the problem is...
Assuming the phone will boot, this will format the internal SD card.
GSM Master Reset: *2767*3855#
Click to expand...
Click to collapse
Thanks, I appreciate the reply. I couldn't get past recovery mode, so I couldn't access the dialer. I ended up getting the ODIN 1-click to flash the AT&T stock ROM, then I flashed back to my native Rogers Eclair.
Just in the process of getting Stock Froyo back on the handset.
A little information is a dangerous thing...
The problem started yesterday. After rebooting my phone all my apps came back with process faults. I factory reset my phone without success. So i decided to update from darky's 9.3 to his 9.4 extreme edition.
Still had problems so went back to a 2.2 stock rom before going back to darkys 9.3. The stock app problem had been fixed but could not install any apps.
This is where things went drastically wrong. I went into recovery mode to find the sd and ext sd card unmounted. i tried mounting to get this error
'E : Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(device or resource busy) Error mounting SDCARD:!
Neither can I mount usb storage.
Is there any fix to this or am i going to have to take my fallen pride into a samsung repair shop?
Thanks in advance
I have a nook color that was stock 1.3 and i installed cyanogen 7 on it. i reverted back to 1.0.1 but found that i could not update my nook because it wouldn't mount anymore. so i rerooted and did a restore of a backup i made using cwm. i was able to revert back to 1.3 and my nook mounts again but i put the 1.4 update on the nook and when it tries to update it fails. i think it has something to do with cwm since thats what comes up telling me that the update failed. any tips on what i should do? thank you
p.s. i am currently on 1.3 stock on the emmc and i have cyanogen 7 on the sd card, booting with multiboot so i can choose which to boot. thanks
aminthemachine said:
I have a nook color that was stock 1.3 and i installed cyanogen 7 on it. i reverted back to 1.0.1 but found that i could not update my nook because it wouldn't mount anymore. so i rerooted and did a restore of a backup i made using cwm. i was able to revert back to 1.3 and my nook mounts again but i put the 1.4 update on the nook and when it tries to update it fails. i think it has something to do with cwm since thats what comes up telling me that the update failed. any tips on what i should do? thank you
p.s. i am currently on 1.3 stock on the emmc and i have cyanogen 7 on the sd card, booting with multiboot so i can choose which to boot. thanks
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1391931
This will get you back to stock 1.4.1, then you can reuse your dual boot SD...
followed that thread. everything was going ok but after returning to stock 1.0.1 my nook won't mount when i plug it into my computer. i just get 2 new disks in my computer that are lightly grayed out and i can't open them. under device manager i have 2 b&n ebook usbdevices under disk drives. i have uninstalled them and tried to plug the nook back in but they still show up the same. so i again did a restore with cwm back to the 1.3 i had but still can't update to 1.4, cwm interferes when the nook is attempting to install 1.4 and says
verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
--Copying media files...
E:failed to mount /sdcard (no such file or directory
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. Please use UI menu for format and reboot actions.
Media files copy failed.
--Wiping data...
Formatting /data...
E: format_volume: rfs format failed on dev/block/mmcblk0p2
Formatting /dbdata...
Formating /cache...
Data wipe failed.
-- Applying Multi-CSC...
Installing Multi-CSC
Applied the CSC-Code 'ATT'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
frenzisor said:
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
Click to expand...
Click to collapse
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Booting of External SD card
BWolf56 said:
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Click to expand...
Click to collapse
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
frenzisor said:
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
Click to expand...
Click to collapse
***First of all, don't touch ROM Manager, it doesn't do well with the Captivate.
Custom recovery is flashed through kernels with Odin 1.18 (or 1.17). You simply grab the .tar file and put it in the PDA slot while you phone is in download mode. (On stock GB, you'll want Corn kernel)
Now my guess is that your external sd needs reformat. Backup w/e is on it (same with your internal if you can access it from your pc) and full format it to FAT32. If that alone doesn't fix it, wipe your internal as well.
Hi, my brother gave me a used Droid Bionic which I successfully rooted and installed a custom recovery on (Liquidsmooth to be exact) using Safestrap recovery 3.11 but kept my stock rom in a slot.
So basically I now got a problem. I thought I'd try CM11 from the Cyanogenmod website (snaphot) when I created a new slot rom and try to install, I got an error. It was a failed process.
I thought I'd try again so I wiped everything Factory reset, data, cache...etc still failed..
Then I uninstall safestrap recovery using the stock rom and saw that I can use CWM like my other phone Samsung fascinate in rootzwiki. I followed this thread called [Guide] How to install ClockworkMod Recovery from adroidman
but before I installed the bionic boot strap, I made a huge mistake I formatted The internal 8 gb storage then I rebooted to see if that caused any problems and it did basically..
I deleted the /data and /sdcard because I formatted the internal storage and every time I reboot, I get a Encryption Unsuccessful message and it tells me to reset phone. I did but same message. Am I screwed?? I know I still have my stock rom in there but can't access it. Also every time I connect my phone I no longer see the internal storage instead my 32 gb sd card.