Related
trying to install rom from sd card (phone has been wiped after trying to install leedroid 3.0.3) and I get the following messages when in recovery;
unable to moun't sd card
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(no such file or directory)
E: Can't mount /sdcard
HELP!!!!
Does this when I try installing from SD, formatting SD, all sorts. I cna access the card though from the computer when I select mount USB storage.
any ideas? I'm phoneless at the moment. eek. Thanks
westleydan said:
trying to install rom from sd card (phone has been wiped after trying to install leedroid 3.0.3) and I get the following messages when in recovery;
unable to moun't sd card
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(no such file or directory)
E: Can't mount /sdcard
HELP!!!!
Does this when I try installing from SD, formatting SD, all sorts. I cna access the card though from the computer when I select mount USB storage.
any ideas? I'm phoneless at the moment. eek. Thanks
Click to expand...
Click to collapse
This sort of happened to me before. try downloading and installing the file attached. It should do the trick. N.B- You need to have root access.
ok thanks. I have root access (i think, fairly new to all this, apologies).
How do I run the file??
Thanks.
sorry to be a pain
westleydan said:
How do I run the file?? Thanks. sorry to be a pain
Click to expand...
Click to collapse
Boot your phone (make sure the file is on your phone), then simply select the file and follow the onscreen instructions. After that, select it's icon in the menu and choose to allow it to automatically operate when USB is connected. Then just allow root access and you're good to go. Try your rom flashing again and it should be successful.
hey
thanks for your help, but I currently have no ROM / OS installed on the phone, so can only boot into recovery / fastboot etc.
not into android os.
westleydan said:
hey
thanks for your help, but I currently have no ROM / OS installed on the phone, so can only boot into recovery / fastboot etc.
not into android os.
Click to expand...
Click to collapse
Since you can boot into recovery and access your phone from your computer, then just flash the stock windows mobile rom to your phone. I think that would work and it does make sense. If it does work then you can continue doing what you want after you have done it.
Do you mean flash it via fastboot? I'm sturuggling to get files across from my pc... sorry to be a pain...
I can access the SD card to drag files in recovery. but cant isntall from the sd on my phone.
tried flashing files direct to phone with fastboot but coundt. probably just got it wrong. gahhh.
westleydan said:
Do you mean flash it via fastboot? I'm sturuggling to get files across from my pc... sorry to be a pain...
I can access the SD card to drag files in recovery. but cant isntall from the sd on my phone.
tried flashing files direct to phone with fastboot but coundt. probably just got it wrong. gahhh.
Click to expand...
Click to collapse
Have you tried a different SD Card or a sdhc card? One of them might help.
I haven't tried another card yet no.
I need to purchase one first, hopefully will get chance this week.
Any links to best guide to make a goldcard btw?
Thanks.
westleydan said:
I haven't tried another card yet no.
I need to purchase one first, hopefully will get chance this week.
Any links to best guide to make a goldcard btw?
Thanks.
Click to expand...
Click to collapse
Go here and read my first post [OP]: http://forum.xda-developers.com/showthread.php?t=1052063. Hope this helps.
XDA developers, Kejar, nor I are responsible for anything you do to your phone so as always use with care​
For those of you using a custom kernel with Build EE4 to gain root and have run into the Write protection pop up when trying to transfer files to your sdcard.
sdcard patch:
simply download below
place on sdcard
and flash using clockwork
All credit to Kejar , so please remember to thank him
You are a beast!!!
I think his username is kejar, BTW.
yyhd said:
You are a beast!!!
Why aren't you on irc foo?
Edit: KELJAR IS A BEAST!!!!
Btw dxc...keljar said it was a dam easy fix. Give me my macchiatos back!
Click to expand...
Click to collapse
Ill refund you tomorrow EDIT: DONE
and its as easy a fix as anything else is i never said it was a hard fix...ill pull the whole thread sorry
After first running this patch, the first time I plugged it in the usb storage option popped up, but then never came up again. I ended up having to go into Setting>USB Settings while the phone was unplugged and changing it to "Ask on Connection" and it works perfectly. When the "Mass Storage" Option is selected, Windows recognizes the phone as a cd rom. Thanks for all your work DroidXCon, Kejar, and everyone else.
How to Save it on SD when Its readonly
If the SD card is in read only mode, then how can I save the zip on sd card? Also the usb is not recognized because iof it being a read only mode
rukshmani said:
If the SD card is in read only mode, then how can I save the zip on sd card? Also the usb is not recognized because iof it being a read only mode
Click to expand...
Click to collapse
I would suggest putting the file on the SDcard before you update or pull the sdcard out and use a micro USB card reader to put it on.
rukshmani said:
If the SD card is in read only mode, then how can I save the zip on sd card? Also the usb is not recognized because iof it being a read only mode
Click to expand...
Click to collapse
You can unmount the SDCard and push the file to the SDCard via adb. The SDCard is only read-only when it is mounted as mass storage. I have a feeling that this change is going to cause a few short-term issues with custom kernels at some point, but only time will tell.
BTW - TY to kejar & DroidXcon, regardless of how easy a fix is or isn't they still deserve all the props and I will gladly donate the macchiatos to the guys, consider it done
imnuts, I know you are working on an update to your debloated ROM, likely built off of EE4, will you be using a custom kernel in yours or stock until we know if it will cause issues?
DroidXcon said:
Ill refund you tomorrow EDIT: DONE
and its as easy a fix as anything else is i never said it was a hard fix...ill pull the whole thread sorry
Click to expand...
Click to collapse
Aw man. I was kidding, dxc.
Sorry if I offended you.
For reals, I was just joking around. I guess it didn't come off that way.
My bad. Sorry.
rukshmani said:
If the SD card is in read only mode, then how can I save the zip on sd card? Also the usb is not recognized because iof it being a read only mode
Click to expand...
Click to collapse
My card wasn't really read only, just not accessible via usb. I just downloaded the file via my DC browser and it saved to the card no problem
Orrrr. Just send the download link to your phone via email or whatever method you choose. Then use your supa fast 4G facemelter to download the file on your phone and then go into CWM and flash it.
Quick (noob) Question. When going to apply this patch in CWM, do you use the "apply patch option" or "zip to apply". Literally popped my rooting cherry an hour ago. Everything works besides SD Card being Read Only Status. Thanks in advance.
1) download the sdcard fix from here and rename the file to update.zip
2) place update.zip in the adb platforms tools directory, where the adb command exits.
3) with USB mass storage off, I used ADB shell to push the file from the host computer to the Charge into the root folder of the SD card, /sdcard
(this assumes you don't have any file named update.zip already in the root of your sdcard)
adb devices
adb push update.zip /sdcard
adb reboot recovery
4) CWR should run and now you use the menu to apply update.zip.
Thanks OP.
Now I'm experiencing something slightly different...and this fix isn't helping.
Since the day I got the charge I've had issues writing to it in windows, wasnt til yesterday I started to really question more so why...thinking it was just a cheap card going bad.
I rooted the phone the day I got it, everything worked fine except being able to write to the sd card when mounted. Now I wasnt getting write protection, I was more so getting windows locking up, and things of that nature (thinking bad card right).
Yesterday I unrooted, and updated to ee4. it does the auto mount thing now, I mounted and was able to transfer 200 and some songs to the card, no issues.
Rooted late last night now running the debloated ee4, with pb&j kernel (voodoo enabled) and tried to move some icons over and unzip them, and it failed again, with io errors in the logs...
Anyone have any thoughts on this one...
I was able to just plug my microSD card into a card reader to my laptop, and drop the zip file in there. booted into CWR and flashed the update. Worked like a charm. Thanks!!!
My way of testing was to take a screenshot. and verify that it was in the screencapture directory.
Cheers!
No more root
So I installed cwr w Odin, then pb andj kernal w car and the fix w cwr and rebooted. Checkedrootchecker and o was root checked. Then I flashed debloated eel and it worked but now I have no root access. Root heck says busy box is installed correctly but it says "su binary not found in the system declared path??
Thanks
Chris
clk5068 said:
So I installed cwr w Odin, then pb andj kernal w car and the fix w cwr and rebooted. Checkedrootchecker and o was root checked. Then I flashed debloated eel and it worked but now I have no root access. Root heck says busy box is installed correctly but it says "su binary not found in the system declared path??
Thanks
Chris
Click to expand...
Click to collapse
Hmmm, strange. Try reflashing PBJ. If that doesn't work, try flashing GummyCharged and see if that helps?
Isn't that another rom? Don't I have to be rooted first?
I was on humble and i downloaded Gummy Charged 2.0 GB
and after i flashed it with CWM it wouldn't boot just got stuck on Samsung logo,
so i go back to CWM and i tried flashing it again, and now its telling me it cant mount the SD card? wtf??
any help??
cj316x said:
I was on humble and i downloaded Gummy Charged 2.0 GB
and after i flashed it with CWM it wouldn't boot just got stuck on Samsung logo,
so i go back to CWM and i tried flashing it again, and now its telling me it cant mount the SD card? wtf??
any help??
Click to expand...
Click to collapse
you could try mounting it in mounts and storage options then reboot CWM and see if that did it
anoninja118 said:
you could try mounting it in mounts and storage options then reboot CWM and see if that did it
Click to expand...
Click to collapse
nothing happens?
and when i odin back to humble it works but as soon as i flash to gummycharge it wont mount it?
would it be due to the sd card? and maybe some files are there?
cj316x said:
nothing happens?
and when i odin back to humble it works but as soon as i flash to gummycharge it wont mount it?
would it be due to the sd card? and maybe some files are there?
Click to expand...
Click to collapse
no it sounds like something to do with Gummy... you're trying to load up GBE 2.0? you could try redownloading it, maybe you got a bad .zip
cj316x said:
I was on humble and i downloaded Gummy Charged 2.0 GB
and after i flashed it with CWM it wouldn't boot just got stuck on Samsung logo,
so i go back to CWM and i tried flashing it again, and now its telling me it cant mount the SD card? wtf??
any help??
Click to expand...
Click to collapse
I'm having the same problem man. Tried flashing the same rom as you. Any resolve??
Just for the heck of it maybe try this: http://forum.xda-developers.com/showthread.php?t=1118111
Download the sd card patch zip file to your computer. Take out your sd card and use an adapter to plug it into your computer. Paste the zip onto sd card. Re-insert sd back into your phone. Pull up your recovery and install the sd card patch zip file through the recovery system. Then reboot.
Let us know if that works.
Had a similar issue and had to remount through ADB. I'm a complete noob and was able to figure it out. I found this posted on Rootzwiki, maybe this will help:
Run the commands when in recovery, press and hold Vol. Up, Home, and Power until the screen goes black and then SAMSUNG shows up again, then let go to get into recovery. And ADB is part of the Android SDK. Here's a guide on installing it.
Use the following (you need adb for this)
Code:
adb shell rm /sdcard
adb shell mkdir /sdcard
adb shell mount /sdcard
Hello,
I rooted my tf101, all went well. Put clockworkmod recovery on it and still no problems. Now I wiped all partitions by mistake of my tf101. The only thing left is the recovery image (cwr) but if i try adb tool to push a file on the system it says the system is readonly. If i try nvflash tool is also says error onable to write and it disconnect the tf101.
Can any body help me, or do i have to put it back to repair
thanks Ernst
Well, if you have a microSD card, and a CWM that can read from it, you could just hook the card up to your PC (using a phone with microsd slot, or a cardreader, etc) and place the new image on the card.
Also, have you tried running 'adb root' to make sure ADB is running as root?
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
ernst99999 said:
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
Click to expand...
Click to collapse
If you are using cwm 5.5.0.4, go to the following link.
http://forum.xda-developers.com/showthread.php?p=23256536
@kokopopz
I have indeed version 5.5.04, have read the tread you mentioned, but no solution. My problem is that if i try to push a file to the TF than it says "read-only file-system". Tryed in cwr to fix permisions, but no help.
Problem stays the same.
@kokopopz Thanks for your link.
I Found the solution !!!! My TF is UNBricked. YES YES YES.
For the record: "adb push rom.zip /data/media/rom.zip" will do the trick, after that reboot to cwr and do install zip from sdcard.
So ive been at this for 2 days. I finally got the micro sd card with both files to install rom but in clockworkmod recovery i cant mount sd card nor format or anything. I can mount and unmount in the normal settings of the device and see it in root explorer but thats it. Its formatted to fat32. also on rom manager where it says to install from sdcard it only takes u to the internal sdcard which makes no sense because i was told u cant install a rom from the internal sdcard.
PS. This is my first Android Device!!!!
yeah
I am in the exact same situation. I am rooted on 4.0.3 and I wanted to install 4.0.4 or one of the custom ROM's. This is not my first android device but I am at a loss. I can not enter fastboot, can't load anything from the SD card in CWM recovery (get the message E:Can't mount /sdcard/), can not connect via ADB on my PC.
I feel that I have enough skill to do all of this because I have done it in the past. My ADB works fine with my Galaxy Nexus (just updated that and installed new kernel) so I don't know what is causing the problem. I have tried different SD cards(3) as well and nothing.
The biggest problem is I can not get into fastboot and SBF if I wanted to. I have been having issues with drivers even though I have installed motohelper like 6 million times.
I have tried factory resets and wipes and everything. I tried to do the factory update that is being pushed to me and I get an error. Any help would be greatly appreciated.
Sorry if this is stealing your thread but I think we are having the same problems.
check out my thread at xoomforums:
I PM'd it to u cus it dont let me put it here
Read all 3 pages. I think it will help u. posted same question there and a guy suggested to install the rogue cwm 1.5 recory via adb fastboot or whatever. he says that will read your sdcards. if i were u id try and fastboot on a different pc cus it looks like thats what we both have to do unfortunately. it looks like a pain!!! u have a xoom?
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
platt said:
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
Click to expand...
Click to collapse
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
+1 i agree with the above, fixed this last night. I download a couple recovery images, which were blank for some reason, so i downloaded the zips and extracted the recovery image folder. Then opened the command window from the folder with the recovery image and flashed it with fastboot. Now it works perfect.
Sent from my MB855 using xda premium
Fastboot
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
TheAv8tor said:
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
Click to expand...
Click to collapse
Atleast you got it out, mines been acting up since i flashed cm9. I think i might have to do that
Sent from my MB855 using xda premium
okantomi said:
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
Click to expand...
Click to collapse
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
error mounting /internal_sdcard!
error mounting /internal_sdcard! pls help me it got stuck in boot loop tried to wipe cache and user data bt cwm says error mounting /internal_sdcard!
Ipse_Tase said:
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
Click to expand...
Click to collapse
Delete any zip files or IMG files from sdcard and reboot it this helped me ............ Hit thanks if helped
Sent from my HTC Desire C using XDA Premium 4 mobile app
This is my first attempt at unlocking and rooting. So far I did manage to get unlocked. Now I am stuck at: Can't mount/sdcard . . . . .
I have been following the thread: [HOW] Rookie Rooting, Flashing And UnRooting Under One Roof
It seems to be layed out quite well and well, I'd never have gotten this far if it weren't for following those directions. I'm not discouraged because I know this is just a stumbling block. I can't wait to kill the bloatware and see if I can O/C this beast just a little.
Good luck to the folks who posted above me. I will post my results here.
Mike P.
I think the solution is much more simple...
The recovery uses normally e: an external sd card , you just trying by d: internal sd card , so take another sd card and dun let it be internal sd card...
And the recovery back on working with you