Trying to Unroot, E:Can't mount SDCARD: - G1 Q&A, Help & Troubleshooting

I'm trying to unroot from Cyans latest.
I'm following these instructions
[HOW TO] UNROOT, get phone to STOCK firmware
After I formated to FAT32 and placed the original SPL (renamed to update.zip) and DREAIMG.nbh on root of sdcard.
I get into Cyans 1.4 recovery. When I hit [ALT+S] Apply update.zip
I get E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
Any help please?

Go back to your PC and make sure it is really update.zip. if you don't have your file extensions turned on, it may really be update.zip.zip.

I'm sure its update.zip. I'm on a mac and I can see my file extensions.

CaliLove310 said:
I'm sure its update.zip. I'm on a mac and I can see my file extensions.
Click to expand...
Click to collapse
If you go to choose .zip do you see the file listed there?
You did say you're using cyan's 1.4 recovery, right?

rp1783 said:
If you go to choose .zip do you see the file listed there?
You did say you're using cyan's 1.4 recovery, right?
Click to expand...
Click to collapse
Yes, CyanogenMod v1.4 + JF
When I click on apply any zip
I get the same error message
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:

CaliLove310 said:
When I click on apply any zip
I get the same error message
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:
Click to expand...
Click to collapse
That sounds more like a problem with your sd card tham the file itself. I would try to format your FAT32 partition again. I know you already did it, but I can't see another reason, unless the file ext is wrong, which we've already established it's not.

rp1783 said:
That sounds more like a problem with your sd card tham the file itself. I would try to format your FAT32 partition again. I know you already did it, but I can't see another reason, unless the file ext is wrong, which we've already established it's not.
Click to expand...
Click to collapse
If I place it into a card reader, I can see it perfectly. Also, if i place it into a spare G1 I have, I'm able to mount it and see the files perfectly.
I have this particular sd:
A-DATA 8GB Micro SDHC Flash Card Only Model MicroSDHC 8G card

CaliLove310 said:
If I place it into a card reader, I can see it perfectly. Also, if i place it into a spare G1 I have, I'm able to mount it and see the files perfectly.
I have this particular sd:
A-DATA 8GB Micro SDHC Flash Card Only Model MicroSDHC 8G card
Click to expand...
Click to collapse
Is the spare g1 rooted? If you have a "recent" custom recovery on that phone, I would try the apply any .zip and see if it lists the file.

rp1783 said:
Is the spare g1 rooted? If you have a "recent" custom recovery on that phone, I would try the apply any .zip and see if it lists the file.
Click to expand...
Click to collapse
Yes, my spare G1 is running the same, Cyans latest, with cyans 1.4 recovery. I tried the same SD card on the spare on and it also gives me the same error as the other phone.

Format FAT32 again, re-download the SPL and try again. The issue has to either be with the SD card or the file.

rp1783 said:
Format FAT32 again, re-download the SPL and try again. The issue has to either be with the SD card or the file.
Click to expand...
Click to collapse
Thanks alot for your help. Wish there was someway to thank you.
I reformatted the SD through windows XP in my bootcamp side.
That worked, I guess it doesn't like Apple's FAT32 formatting.

CaliLove310 said:
Thanks alot for your help. Wish there was someway to thank you.
I reformatted the SD through windows XP in my bootcamp side.
That worked, I guess it doesn't like Apple's FAT32 formatting.
Click to expand...
Click to collapse
Well you're more than welcome to DONATE Although, your thanks is enough.

You don't need to go through all that. just put the RC29 image on the root of your phone and press power. As long as you don't have a custom bootscreen, everything will be replaced

Related

Recovery won't work with new SD Card

So I got a new 16 gb SD Card, I'm not sure if there is a proper way to transfer all your files from one to another but I just copied all the contents from my 4 gb card onto the new one.
Everything has been fine so far but when I tried to do a nandroid backup (using ClockworkMod Recovery 1.8.1.4) I got an error message:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
Can't mount /sdcard
I tried reflashing the recovery through the Rom Manager app but it still gives me that error message.. Will I have to reflash Amon's recovery using fastboot? Does this have anything to do with the fact I'm using a new card?
Thanks in advance for any help
i had a similar problem. my 8gb memory card would NOT let me restore a nand backup. it would create the backup just fine, but would not restore. i got some error saying "run nand.restore mobile via terminal" or some such thing.
i never did figure it out. but when i copied the EXACT contents of that memory card to a different card, nand backups and all, it suddenly worked fine. identical files.
i even formatted the card to make sure, but still wouldnt work. good luck
Yea Roger, I've tried transferring the contents of the old SD card but it doesn't help.
Anyone else ever have troubles switching to a new SD card? I can't do anything from the recovery, flash from SD, format SD, nandroid backup or restore etc. I've tried reformatting the SD card as well as transferring the contents of the old SD card to the new one, still doesn't work.
Any help would be much appreciated.
For anyone who ever has a similar problem, I figured out that my issue was with the Mac Disk Utility I used to format my SD Card.. I tried formatting on a Windows machine and the recovery was able to mount my SD card again.

E:Can't open /sdcard/update.zip

Decided to flash back to stock(was using lag fix ext 2 + root/busybox, etc) and used the odin one-click method. flashed back to stock fine. Decided to flash the SRE v1.2.1a
Downloaded the zip, changed to 'update.zip' and rebooted into the recovery(stock) and selected reinstall packages.
It gives me the error:
E:Can't open /sdcard/update.zi[
(No such file or directory)
Installation aborted.
I've put the sre file on my internal SD card about 5 times now and know it's on there.
What gives?
Did you rename the file update or update.zip, if you included.zip then the file in on your sd would read update.zip.zip and I have seen this happen. Coonect your phone to your pc and mount it then look in the sd and be sure you named it correctly. Thats' where I would start and post this question in the thread so the developer that made this or someone there could help you.
http://forum.xda-developers.com/showthread.php?t=751934
Rhiannon224 said:
Did you rename the file update or update.zip, if you included.zip then the file in on your sd would read update.zip.zip and I have seen this happen. Coonect your phone to your pc and mount it then look in the sd and be sure you named it correctly. Thats' where I would start and post this question in the thread so the developer that made this or someone there could help you.
http://forum.xda-developers.com/showthread.php?t=751934
Click to expand...
Click to collapse
Ditto, I've actually done this myself once so just make sure to rename it to just Update and save it and it still should be a zip file.
One thing that any of the instructions I have read neglect to tell you is that /sdcard is actually the root of the mounted sdcard on your computer so you don't put update.zip in the directory sdcard you put it right in the root.
jaseone said:
One thing that any of the instructions I have read neglect to tell you is that /sdcard is actually the root of the mounted sdcard on your computer so you don't put update.zip in the directory sdcard you put it right in the root.
Click to expand...
Click to collapse
This is incorrect.
Update.zip does indeed go on the root of the internal SD card.
/SDcard/update.zip - this is the proper path
http://forum.xda-developers.com/showthread.php?t=725555 (step 2)
OP - i expect your problem is the file name as mentioned above.
It goes in the root.... Thats how i do it!
Sent from my SAMSUNG-SGH-I897 using XDA App
I get the same message. I looked in the "Files" app and see that the card is named /sd and not /SDcard. Renaming it is disallowed. Could this be the problem?
If so, what next?
[Never mind; that directory is in the root of the internal storage and is not the same as the SD card.]
Thanks
Got it to work. On my windows system when I plug in to USB and mount the device I have two separate devices in "My Computer" for it. One is the internal storage and the other is the external SD card.
For my Galaxy S Vibrant update.zip must be at the root of the internal, not the external SD card. It won't find it if in the latter and it updates fine using the "Reinstall Packages" function when update.zip is placed in the internal root.
On a Captivate when we refer to the sd it is the root or we'll just say external sd when refering to the one you install in the slot inside the battery cover. This was a bit confusing for me in the beginning but sd is the root. I have been doing it this way since day one.
We have about 2 gig internal and 13 gig that the phone sees as sd or sdcard. Now that is confused when you add an actual external sd card. Mine came from my aria and and on my captivate it shows as "/sdcard/sd" I'm not even sure how my pc sees this.
The update should be on root of the internal 13 sd storage. On the phone it is /sdcard but on a pc copying to /sdcard/update.zip may create /sdcard/sdcard/update.zip but I haven't tried.
I use opera browser to download directly to /sdcard. So I'm not sure but I'm guessing what we see on the phone as /sdcard we see on the pc as root of a 13 gig external drive
Sent from my SAMSUNG-SGH-I897 using Tapatalk
ArcaneMethods said:
Got it to work. On my windows system when I plug in to USB and mount the device I have two separate devices in "My Computer" for it. One is the internal storage and the other is the external SD card.
For my Galaxy S Vibrant update.zip must be at the root of the internal, not the external SD card. It won't find it if in the latter and it updates fine using the "Reinstall Packages" function when update.zip is placed in the internal root.
Click to expand...
Click to collapse
thanks for the tip i just updated the zip
I had this as well, (Samsung Galaxy S) and took a few tries of copying the file between my E: and F: drive - I have a Windows PC and both drives letter showed up E: ended up being the external SD and F: the internal sd card.
Also, my folder was labelled /sd and not /sdcard.
I tried a few iterations of copying and renaming the file to both E: and F: in /sd and the root folder "/" and nothing worked.
Finally, I took out the microSD, and then copied "Update.zip" to /sd and also the root folder (so both had a copy), and renamed it to "update.zip" (case-sensitive).
Then ran "adb reboot recovery" and was able to choose "update" and it worked.
Hope this helps someone
blackinches said:
Decided to flash back to stock(was using lag fix ext 2 + root/busybox, etc) and used the odin one-click method. flashed back to stock fine. Decided to flash the SRE v1.2.1a
Downloaded the zip, changed to 'update.zip' and rebooted into the recovery(stock) and selected reinstall packages.
It gives me the error:
E:Can't open /sdcard/update.zi[
(No such file or directory)
Installation aborted.
I've put the sre file on my internal SD card about 5 times now and know it's on there.
What gives?
Click to expand...
Click to collapse
I had this as well, (Samsung Galaxy S) and took a few tries of copying the file between my E: and F: drive - I have a Windows PC and both drives letter showed up E: ended up being the external SD and F: the internal sd card.
Also, my folder was labelled /sd and not /sdcard.
I tried a few iterations of copying and renaming the file to both E: and F: in /sd and the root folder "/" and nothing worked.
Finally, I took out the microSD, and then copied "Update.zip" to /sd and also the root folder (so both had a copy), and renamed it to "update.zip" (case-sensitive).
Then ran "adb reboot recovery" and was able to choose "update" and it worked.
Hate to bring this back up but ....worked for me ! aha i added another .zip to it ...makes me feel dumb
Hi,
I have a Samsung Vibrant and I've tried all options suggested here and everytime I start to phone in recovery mode and select "reinstall packages" it tells me "Can't open sd/update.zip (such file doesn't exist)". Here is what I've tried so far:
- Plug the phone on the pc via usb. I then see the phone as a hard drive and when I open it it displays 2 drives, one is the phone and the other is the SD card (called simply SD). I copied the update.zip file and placed it directly into the SD drive.
- With a micro usb to usb adapter card I copied the update.zip file to the sd card.
- I removed the zip extension from the update.zip file (I tried doing this on the pc and directly on the phone via astro file manager).
- I´ve created an SD folder on the SD drive and placed the update.zip file there.
- I´ve created an SDCARD folder on the SD drive and placed the update.zip file there.
- I´ve tried renaming the SD drive to SDcard (the system wouldn't let me).
This issue cannot be this difficult to resolved. I really want to install I new rom on my phone and it's very frustrating not being able to resolve such a silly thing. Can anyone help?
cheers
Rafa
rawfa said:
This issue cannot be this difficult to resolved. I really want to install I new rom on my phone and it's very frustrating not being able to resolve such a silly thing. Can anyone help?
Click to expand...
Click to collapse
It sounds like your are putting update.zip on an external sdcard. Put it in the root directory of the internal sdcard.
opcow said:
It sounds like your are putting update.zip on an external sdcard. Put it in the root directory of the internal sdcard.
Click to expand...
Click to collapse
How do I do that? I thought I was putting in the root...
Ok. I had this problem the first time too. Plug your phone into your computer(make sure you're in mass storage mode and usb debugging is turned on). A pop up should come up, click on view files. Paste it right there. Then try it again.
Sent from my SGH-I897 using XDA App
rawfa said:
How do I do that? I thought I was putting in the root...
Click to expand...
Click to collapse
Maybe you were. Read what I wrote. If you are putting it in the root directory of the internal sdcard, then I don't know what the problem is.
When I connect using usb debugging mode the drivers do not show up on windoes explorer, although I can see them on the device manager console.
This is insane...I´ve tried everything and it still doesn´t work...and I bet it´s something really silly.

[Q] can't mount sdcard from AmonRA recovery

Hello
I have a problem with my N1. It happened while flashing a custom rom - what caused it, I don't exactly know. The problem is, that now, my N1 wont boot. When i turn it on it is just stuck at the 4-colored X. I can boot into recovery and everything, but it can't mount my sd card from here, all i get when trying to do anything related to the card is this message:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
All my phone can do now is to get to the bootloader, recovery and fastboot. I'm unable to install a new rom or a new recovery. Actually i'm unable to use my phone for anything.
Hope you guys can help me out
Did you do the obvious and try another SD card?
Or try and fix sd card errors or just full wipe the card??
Yeah, i did try another card and got the same message. Both cards works fine when i tried them in another phone. And yes i did try and wipe the card as well.
You can go to Amon/Mounts and mount card or try a repair sdcard
If you have backup of card, I would reformat (sdformatter) and repartition
Do you use Temasek's System Only Wipe zip between new roms in addition to data/cache wipes?

[Q] Not bricked, but can't mount or boot from SD anymore

Ok, so I've been in the world of iPhone jailbreaking for awhile, but freely admit to being a Nookie newb. I was wanting a cheap tablet and after reading about what's available for the Nook Color, I decided to take the plunge.
All was great at frst, I made a CWM 3.2.0.1 bootable SD card on an old 1gb microSD I had laying around and loaded CM 7.1.0 RC1 and the recent June gapps and it all went fairly smoothly. I installed both CWM and CM7 to the internal memory, I then used another 4gb microSD as a data card to try things out a bit. It was awesome! I went out and purchased a 32gb class 10 card with the idea that I was now gonna get serious and load my data onto it. This was also recognized right away.
Now, I'm not sure exactly when it happened, but at some point the SD card disappeared on me. The last time I'm sure it worked is when I decided to load the #144 nightly build of CM7 when I was able to make a backup of RC1 onto the SD card before upgrading using ROM Manager
As of right now, my Nook can not mount or boot from any SD card. Not even CWM can mount them (let alone CM7). I've tried going back to the 4gb and even the 1gb bootable card, but nothing seems to work (multiple hard and soft resets into both CM and CWM). I've tried all three cards in my PC and they are all perfectly readable there, but almost no reaction from the Nook when I insert one. Occasionally (as in twice), with the 4gb card, the Nook has noticed that an SD was inserted, but it thought the card was not formatted and would not mount it. I haven't figured out how to reproduce even that reliably. Not sure what I did (if anthing) that allowed it to get that far.
Any ideas? I find it hard to believe that it could be the Nook itself that's broke, but I'm running out of ideas. My Nook is still running fine (otherwise) on CM7 nightly build #144, but without the ability to mount or boot from SD I'm stuck on this release since both ROM Manager and CWM need one to work. Not to mention that the internal storage isn't really enough to do anything with.
I'm a newb to Android and CM7, but I know Unix / Linux well. Does anyone know the device name for the sd card (e.g. /dev/hd???). Is there a way I can try and mount it manually (vold doesn't seem to be working)? Any logs I can check (syslog???) for possible clues as to why it's not mounting? Any other ideas?
Thanks in advance for any suggestions.
Geko45 said:
I'm a newb to Android and CM7, but I know Unix / Linux well. Does anyone know the device name for the sd card (e.g. /dev/hd???). Is there a way I can try and mount it manually (vold doesn't seem to be working)? Any logs I can check (syslog???) for possible clues as to why it's not mounting? Any other ideas?
Click to expand...
Click to collapse
If your Linux experience is like mine, using Root Explorer and Terminal Emulator to poke around will be illuminating. It's all the same, but it's all different...
Did you try using Settings/Storage to erase a spare SD card? Be sure to get the SD card named SD card and not emmc (although it's pretty much unused by default, it's not what you're trying to test).
Flashing a nightly or the RC should blow away any nastiness that might have happened with vold's configuration files.
The device name for the SD card is /dev/block/mmcblk1p1 (direct) or /dev/block/vold/179:17 (mine mounts here with vold).
If you get Terminal Emulator installed, try:
% su
# mount /dev/block/mmcblk1p1 /sdcard
or
# mount /dev/block/vold/179:17 /sdcard
and see what happens.
Good luck! You might just get an errno message like No such device or No such media, in which case I'm thinking hardware failure on the NC, since your cards work elsewhere.
stolenmoment said:
Did you try using Settings/Storage to erase a spare SD card? Be sure to get the SD card named SD card and not emmc (although it's pretty much unused by default, it's not what you're trying to test).
Click to expand...
Click to collapse
Yeah, treid that a bunch. It just doesn't see anything there.
Flashing a nightly or the RC should blow away any nastiness that might have happened with vold's configuration files.
Click to expand...
Click to collapse
Catch 22, can't flash a new nightly without a working SD card. ROM Manager saves to /sdcard and CWM loads it from there. I'm trying to pull some magic where I've swapped /sdcard and /emmc in vold.fstab. This has worked and re-enabled apps that need sdcard storage (and given ROM Manager a place to download ROMs). Next, I'm gonna symlink /sdcard to /emmc and hopefully CWM will be able to apply them from there. Wish me luck.
The device name for the SD card is /dev/block/mmcblk1p1 (direct) or /dev/block/vold/179:17 (mine mounts here with vold).
Click to expand...
Click to collapse
Thanks, I'll see if I can mount that device to /emmc for testing purposes before making the plunge to reflash a new nightly.
Good luck! You might just get an errno message like No such device or No such media, in which case I'm thinking hardware failure on the NC, since your cards work elsewhere.
Click to expand...
Click to collapse
Yeah, I'm fearing that, but not sure how it could have failed. Right now, just seeing the actual error might tell me a lot.
stolenmoment said:
If you get Terminal Emulator installed, try:
% su
# mount /dev/block/mmcblk1p1 /sdcard
or
# mount /dev/block/vold/179:17 /sdcard
and see what happens.
Click to expand...
Click to collapse
Hmmm, I don't have those devices...
Can you post the output of "mount" and an ls for /dev/block and /dev/block/vold? It'll help to see what it's supposed to look like.
Geko45 said:
Hmmm, I don't have those devices...
Can you post the output of "mount" and an ls for /dev/block and /dev/block/vold? It'll help to see what it's supposed to look like.
Click to expand...
Click to collapse
Attached, I hope. Too bad the XDA Premium app can't attach files, just pics...
I'm back up! I had to re-image my bootable 1gb SD from scratch. I was then able to boot from SD and flash back to RC1. I suspect that Windows somehow "licked" my bootable SD to make it not bootable anymore in the Nook. After re-imaging the SD and flashing to RC1, my 32gb card was usable again too, so now all is good.
Thanks for the assistance!
Geko45 said:
I'm back up! I had to re-image my bootable 1gb SD from scratch. I was then able to boot from SD and flash back to RC1. I suspect that Windows somehow "licked" my bootable SD to make it not bootable anymore in the Nook. After re-imaging the SD and flashing to RC1, my 32gb card was usable again too, so now all is good.
Click to expand...
Click to collapse
Well done!
Thanks for the assistance!
Click to expand...
Click to collapse
Anytime! I've been doing all of my work on Linux, so I've been able to ignore the internal SD slot and imaging app issues.
stolenmoment said:
Well done!
Anytime! I've been doing all of my work on Linux, so I've been able to ignore the internal SD slot and imaging app issues.
Click to expand...
Click to collapse
I haven't tried it, but there is a DD version for Windows which might get around some of the issues with Windows imaging software: http://www.chrysocome.net/dd.

[Q] Cannot flash zips from self-compiled ClockworkMod

I compiled ClockworkMod myself and flashed it to my P970 running CyanogenMod, but now I can't flash zips. When I try to mount the sdcard, I receive an error: "E: cannot mount /sdcard". This device's storage is of course located in /storage/sdcard0, so I suspect that might be the problem.
I don't think that this is the problem. Try to clean sdcard then reboot in recovery. If it doesn't mount, share your recovery with me, I will test if it works
I formatted the SD card from inside CyanogenMod, but now I can't mount it at all. If I choose "Mount SD card" in the settings, it briefly flashes the stuff on the card, and then says "Safe to remove SD card". I performed a factory reset, but it still doesn't work.
What version have you compiled?
//Edit
I remember that to get a fully working recovery for our device you need to edit some files in the device tree, maybe you need to edit some .fstab files or BoardConfig.mk, Evisceration has already compiled cwm for p970, you could ask him for help.
//Edit2
To edit .fstab files (maybe you should edit recovery.fstab) look at gingerbread's device tree.
Lorenzoval said:
What version have you compiled?
Click to expand...
Click to collapse
6.0.3.6, but that doesn't solve the problem with the SD card, which I now can't mount at all. I tried plugging in the USB cable but my computer can't see the card. I may just have to buy an adapter from PC to SD. This thread: android.stackexchange.com/questions/55182/cannot-mount-sd-card-with-error-sd-card-safe-to-remove says to format it with a PC, but that's for a different device.
Roller_REP said:
which I now can't mount at all.
Click to expand...
Click to collapse
Do you mean that you can't mount it even when you're running Cyanogenmod?
Yes. After I formatted the SD card, I can't mount it even in CyanogenMod. In the settings, I select "mount SD card", but it doesn't mount, and I get a notification "Safe to remove SD card".
It could also be a hardware problem, just to be sure send me your recovery or post your sources.
//Edit
I have compiled cwm 6.0.4.6 using 4.3 device tree and everything works good.
Lorenzoval said:
It could also be a hardware problem, just to be sure send me your recovery or post your sources.
Click to expand...
Click to collapse
http://www.mediafire.com/view/4gxxpvc23mttgtb/recovery.img
EDIT:
So, the good news is I solved the main problem. I changed the file "recovery.fstab" to have the other possible partition for the SD card, recompiled, and flashed. Lo and behold, it worked! I can now flash zips from the SD card in ClockworkMod.
But I still can't mount the SD card within CyanogenMod. I know I can flash zips with
Code:
adb sideload
if need be, but I would still very much like to be able to store pictures, etcetera, in that 8 GB of space.
EDIT 2:
I went to the store and bought myself an SD card adapter. I used that to format the card, but now I can't even access it from ClockworkMod.
I flashed your recovery and SD card works.
Which file system is your SD card using now?
If you flash a stock based rom from sideload, can you format SD from settings?
I bought a new SD card for $28 and everything works now. Note to self: never format SD card again.

Categories

Resources