As Undeads thread has been closed, I needed to start again.
Basically when flashing the new 5.0.2.7 recovery with any method, via Rom Manager or ADB Fastboot the recovery just doesn't work proper.
My sdcard can't mount, hence I can't navigate nor install any roms?
Performing backups & restores don't work for me either.
I've had to roll back to 4.0.0.9, annoying because I want to try out Blues Bulletproof.
Please someone what is the definitve solution to getting the officion CWM recovery to work as I'd expect.
I've even tried a :
fastboot erase system -w
before fastboot flash recovery 'recoveryimage'.img
Rolling back to 4.0.0.9 allows me to do everything as per usual in recovery, but not with 5.0.2.7
I'm really quite baffled with this
1 - Download the recovery via real computer.
2 - Plug in your doubleshot, transfer to sdcard main directory.
3 - Disconnect from computer, use a root file manager (root explorer preferred) to copy the image from /sdcard to /data/local
4 - Open up terminal emulator.
5 - Type:
Code:
su
6 - Then type:
Code:
dd if=/data/local/recovery-clockwork-5.0.2.7-doubleshot.img of=/dev/block/mmcblk0p21
*Make sure all letters are lowercase. You will have to juggle the hardware/software keyboard to get the first "i" after "dd" to be lowercase. Try typing a few characters past it, then using the trackpad to move the cursor back to it. Keep trying the hardware and software keyboards until it sticks as a lowercase "i"
7 - Let it transfer, then exit terminal emulator.
8 - Reboot into recovery, should be good.
**Note - pay close attention to the file name for the image. What Undeadk9 typed into his guide is wrong, what I typed here is correct.
Post if you have any further issues.
Edit:
"if" stands for "input file".
"of" stands for "output file".
dd
One thing I love about the official clockwork recovery is the ability to mount the sdcard while plugged into the computer, and drag and drop files to and from the sdcard while the doubleshot is in recovery mode.
Good luck, hope to see it working for you soon.
Thanks, but still same issues
Hi Blue,
I'm still getting the same errors dude.
I just tried your method, hence I've now tried to install the new recovery with all 3 methods (adb fastboot, rom mamanger and this dd terminal command.)
They all flash/install correct, and when rebooting into recovery each time it looks fine.
But when I try to navigate to 'sdcard' (install zip from sd card/choose zip from sd card... i get "E: Cant't mount /sdcard/"
When I go to mounts & storage/mount sdcard, again I get "Error mounting /sdcard!"
When I attempt a backup, I get this "Can't mount backup path."
I hope you can decipher my mayhem here...... very weird!
Maybe it's my sdcard - however, it works as perfect on modaco 4.0.0.9, I'm unsure on whats going on here
Blue6IX said:
1 - Download the recovery via real computer.
2 - Plug in your doubleshot, transfer to sdcard main directory.
3 - Disconnect from computer, use a root file manager (root explorer preferred) to copy the image from /sdcard to /data/local
4 - Open up terminal emulator.
5 - Type:
Code:
su
6 - Then type:
Code:
dd if=/data/local/recovery-clockwork-5.0.2.7-doubleshot.img of=/dev/block/mmcblk0p21
*Make sure all letters are lowercase. You will have to juggle the hardware/software keyboard to get the first "i" after "dd" to be lowercase. Try typing a few characters past it, then using the trackpad to move the cursor back to it. Keep trying the hardware and software keyboards until it sticks as a lowercase "i"
7 - Let it transfer, then exit terminal emulator.
8 - Reboot into recovery, should be good.
**Note - pay close attention to the file name for the image. What Undeadk9 typed into his guide is wrong, what I typed here is correct.
Post if you have any further issues.
Edit:
"if" stands for "input file".
"of" stands for "output file".
dd
One thing I love about the official clockwork recovery is the ability to mount the sdcard while plugged into the computer, and drag and drop files to and from the sdcard while the doubleshot is in recovery mode.
Good luck, hope to see it working for you soon.
Click to expand...
Click to collapse
I had similar problem, was something stupid. Think usb was still mounted or something. Not plugged into pc, right?
Sent from my RubiX CubeD MT4GS using Tapatalk
if you are using an older version of a rom you have to mount system and data.
Try mounting those and then trying to install from an sd.
If I were you I would do a full wipe /formatsystem/data/dalivk/sdcard. Backup the important things on the sd card to the computer and start fresh with an updated rom and a clean sd card.
You could always try swaping your sd card out but i dont think its the problem. The older roms make running the NEW CWM much more difficult than it should be.
I am not sure it appears you are trying to get an older ROM to run with the new CWM.
dillalade said:
Installed new recovery through rom manager, to 5.0.2.7 and rebooted into recovery.
All seems well.
BUTTTTTTTT when i tried to do a backup of my current virtuous rom i get an error: "can't mount target path"
And then when testing the restore i get an error: "can't mount path /sdcard"
And when testing the wipe & format options, instead of the traditional Yes or No.... I now have like 10 No options and 1 Yes option.
Something seems bogus, ive reinstalled the recovery twice but same effect.
Anyone??
Whats happened to my recovery guys???
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
dillalade said:
I went back to 4.0.0.9 and I can backup/restore again.
Something with the latest recovery doesn't allow my device to mount and see/work with my sd card..... any advice people?
Where can i get the img file so i can try to flash after a fastboot erase wype.... However i dont see how everyone else has it working and mine mashed.
Click to expand...
Click to collapse
pmcqueen said:
so am I the only one who literally can't get this recovery to work at all? perhaps I should contact koush and get him a log... basically, it won't mount my SD card. sd card is not defective as I can mount it fine through modaco recovery without any issues.
I guess I could try formatting the card and then trying the official CWM recovery again, but until then I'm just sticking with the modaco version.
Click to expand...
Click to collapse
pmcqueen said:
No one with sd mounting issues yet? I'm surprised. I think I know what the problem is though... will update shortly.
Click to expand...
Click to collapse
Conlculsion...?
I'm sure I saw it around here somewhere, hell if I know where off the top of my head. I am pretty sure it involved formatting the sd-card if memory serves right.
I have to go, will be on the road for a bit then tied up with the family of my Lady for a bit, so not sure when I can check back in.
Hopefully pmcqueen happens to see this and posts the missing info that was not updated...
I realize I quoted you from the other thread, so this issue has been hanging for you for a while? We need to figure out how to solve it - wish I could be more focused on your problem at the moment.
Try formatting your sdcard through Clockworkmod.
If you can't try powering off the phone and formatting the card directly in your computer.
It sounds like you have Clockworkmod successfully updated to the 5.0.2.7 version, but now reading the sdcard is the problem.
Can you try a different MicroSD card, do you have another one?
What ROM are you using? Becaause anything that dates before the official ROM.manager release date was unmounted. Basically there was a feature that the new ROM doesn't have. Undeadk9 confimed this in that thread. Everything you need to know is there. They go into full detail as to why it wasn't working. Even decided to open a full wiki about why. Did you even read it?
Basically you have to manually mount. Also in the rom try scrollong down and keep going until it unlocks.
Sent from my mt4gs
Not sure if you already tried this, but if you haven't, try doing:
Get the SD Formatter here and format your sd card (use a card reader if necessary).
Use quick format, but make sure "Format Size Adjustment" was off (all available under options...)
Two reminders:
1. The recommended filesystem for an android SD Card is FAT32
2. Remember to back up whatever you have in the SD card so you can put them back in once you're done formatting
Thanks for all the input guys.
Will try an sd format etc and report back soon.
Cheers
Sent from my Bulletproof_Doubleshot using XDA App
dillalade said:
Thanks for all the input guys.
Will try an sd format etc and report back soon.
Cheers
Sent from my Bulletproof_Doubleshot using XDA App
Click to expand...
Click to collapse
I can almost guarantee you formatting the sd will fix your problems with sd mounting in 5.0.2.7
You won't be able to do it via cwm recovery (it's not able to even recognize the sd, that's why you're having mounting issues) but if you put the card into an sd reader and format it for a normal fat32 partition I bet that fixes it.
So I just thought I'd chime in here...
I recently updated from Modaco to CWM and had this sd card issue however, I have like 10 different sd cards and the first thing I did was put the ROM I was trying to install on a sd card with nothing on it and BAM it worked. I'm going to try and put my 16gig back in after everything settles in the rom and I'll update with the results. tomorrow.
Hi guys,
similar issue here
I can't make a backup or restore, I can't install somethink because I always get "Can't mount sdcard"
any idea?
thanks
Oh damn I completly forgot to post my results.
Sd card needed a reformat, then the new recovery was able to mount sd etc.
Thanks to everyones 2cents in this thread, helped me out.
Enjoy
I've tried to format but without result
Did you try SD Formatter using a PC? I was able to resurrect a dead 16gb microSD using that method.
Sent from my RubiX CubeD Extreme MT4GS using XDA App
1) Download CWM recovery from the main site.
2) Connect your phone to your PC.
3) Open your PC's Terminal.
4) Type "adb shell reboot bootloader".
5) Type "fastboot flash recovery name-of-recovery.img".
6) Type "fastboot reboot".
Sent via smoke signal.
blackknightavalon said:
1) Download CWM recovery from the main site.
2) Connect your phone to your PC.
3) Open your PC's Terminal.
4) Type "adb shell reboot bootloader".
5) Type "fastboot flash recovery name-of-recovery.img".
6) Type "fastboot reboot".
Sent via smoke signal.
Click to expand...
Click to collapse
This works for me.
Boot into recovery 5.0.2.7 and make backup. All good.
Related
Hi everyone, looking for a little guidance.
Phone: Android G1 (Rogers Canada Dream) running Cyanogen 4.2.15.1, been running fine since 4.2.6.1
Removed SD card while it was on and it rebooted... when it restarted it showed no applications and said the SD card was inaccessible and required a format. After rebooting a few times with no success I bit the bullet and formatted it... all apps are gone except for the ones that are on that image for Cyanogen. I have no market app to download new apps and when I plug it into my PC and mount it I don't see it show up as a drive like it did so I have no way to get the apps back on.
Has anyone had this happen before? Phone still works but I need to get it back to a state where I can get access to the SD and install the market... Any suggestions appreciated!!
There is a thread on the HERO section of Modaco site called "no adb, no sd". I think the 1st post on the last page MIGHT help. There are adb commands you can run to see if the phone has randomly stopped accessing the SD. Worth a shot.
PM me if you have trouble finding the thread n I'll have a look when I'm at my laptop.
Sent from my HTC Hero using XDA App
I misunderstood I think.
So it is now showing an sd present? Have you tried formatting in a pc?
Tried reboot without the sd in, then insert once fully booted again?
Sent from my HTC Hero using XDA App
I remove the SD Card, formatted it in my PC put it back in the phone and I can store pics and vids on it and access them but cant see or access it from the PC when in the phone. I also have no file browser so I cant install any apps or even access the market icon is gone).
D RoiD said:
Hi there! I had posted on the forum with the G1 issue where my SD card seemed to have died.
http://forum.xda-developers.com/showthread.php?t=738105
I have since removed the SD card and reformatted it, I can store pics and vids and replay them so the card is fine. I tried letting it boot up then adding the SD card when booted, that caused it to reboot, same issue...
Not having access to the card, I cant install any apps or browse the SD to install from there... really sucks
I'd be willing to blow it away and restart too and install CyanogenMod-5.0.8 but I need some guidance.
Click to expand...
Click to collapse
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
ddotpatel said:
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
Click to expand...
Click to collapse
Pics taken DO save to me SD. I Can access them from a PC is I remove the SD and put it in the PC. Not when I plug the phone in via USB then tell it to mount.
I just did a low level format, same issue.
UPDATE: Just tried the Android System Recovery and Toggle USB-MS and it shows on my laptop now! Going to try the recovery backup now.
aha,... so its just a mounting issue, not that the hardware has turned itself off.
Once when using an older ROM (maybe Villain 10?) we had this same issue, not able to mount SD,... going into Settings --> Connect to PC --> and turning off Notify/ask me solved the problem.
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
D RoiD said:
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
Click to expand...
Click to collapse
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
akapoor said:
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
Click to expand...
Click to collapse
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
D RoiD said:
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
Click to expand...
Click to collapse
If your contacts are saved in the phone's memory, then yes. Any settings, apps, configurations that are stored on the phone will all be gone.
A wipe pretty much gives you the factory settings. (As if you just bought the phone) So you'll have to re-signin into your Google Account and let the Contacts Sync, etc..
EDIT: Depending on what you are flashing (flashing and wiping are two different things), you may not even need to wipe.
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
D RoiD said:
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
Click to expand...
Click to collapse
Try this:
-Confirm the Image-
1) Make sure you have the full image you are going to flash. (Compare MD5 Hashes and/or just redownload the image)
2) Make sure the image you are flashing is the in the ROOT directory of your SDCard. In other words, it shouldn't be in any folder.
-Flash the Image-
1) When in Recovery, choose to flash an image.
2) Depending on what recovery you have, you may have to select/find the Image you want to flash.
3) Flash the image
-Wipe (Depends)-
1) If you are coming from a different ROM base (ie anything -> cyan), you'll want to wipe.
2) After the phone successfully flashes the image, wipe the phone.
Reboot.
Let me know how it goes.
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
D RoiD said:
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
Click to expand...
Click to collapse
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
akapoor said:
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
Click to expand...
Click to collapse
The SD card reader in my phone? It has to work if I can read an write to it ( tested photos and videos) and in recovery I was able to make a backup.
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
D RoiD said:
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
Click to expand...
Click to collapse
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
akapoor said:
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
Click to expand...
Click to collapse
Ok I did a wipe and now I see the SD when mounted on the PC with the phone on.
I have my market icon back so I can reinstall my crap.
I'll leave it as is for a bit but appreciate everyones input!!!
Hey guys,
I goofed. Big time. I accidentally wiped the sdcard in recovery mode when flashing to another rom.
I have her booted into red recovery and mounted the USB mass storage but it isn't showing up on my computer (I have a Mac that is running a dual boot of windows) on neither the windows or Mac side. Positive the drivers are installed on both.
Please help. If I can put a rom onto the card I'll be fine...but I can't get onto the card
Any suggestions?
Could use Odin or heimdall I've never tried to use mass storage while in recovery
Sent from my SGH-I997 using xda premium
Downloading Odin currently. Will post results. I hate my slow school Internet :/
ODIN Worked. Thanks
Wiped SD using CWM
So I had a problem almost the same.
I was using JellyBelly 4.2, and didn't like it. I wanted to go back to Cyan 10.0 and installed the files on my phone. I decided it was a good time to wipe everything, and started to do so. One of the files was the SD format. So I did that, and then wipe/data factory reset. Crap. So now I have no rom installed, and no files on my SD card.
I need help to place my zip files for CM 10 on my SD card (they are on my MAC now). I can't start up my phone to enable file transfer. I can only boot into CWM recovery. Is there a (step by step) way to push files from my MAC onto the SD card? Or is there a different way to tackle this?
I have a GNex (Toro) VZW
MacBook running snow leopard.
I am afraid that anything give me advice on you're gonna have to pretend that I am really dumb and need step by step directions. I tried to push via ADB but got this error, I don't know the correct commands for that. View attachment 1508775 Any suggestions?
It seems you do not have the android sdk set up along with adb.
Is this it?
andros11 said:
It seems you do not have the android sdk set up along with adb.
Click to expand...
Click to collapse
I thought I did. Here is what I have, I just don't know how to force my ROM's onto the SD card using it.View attachment 1508841
FIrst make sure you added the tools directory to your PATH.
There's a guide on how to set up the sdk on a mac: http://peter.boctor.net/2010/12/02/installing-the-android-sdk-on-mac-os-x/
you can skip the eclipse parts.
Of course, make sure you use your own path.
After that, adb should be recognized as a command.
To push, use this:
adb push "file.zip" /sdcard/file.zip
change "file.zip" for the location and name of the zip.
I often place files on my Home directory before pushing since it then only requires I specify the file name.
Problems with ADB path
So this is what I get when trying to install different commands into my path. I guess I am still doing it wrong? View attachment 1509964
You need to edit the Path to make it fit yours. Your sdk directory reads android-sdk-macosx 2.
It also depends on where you have that folder.
shooter5635 said:
Hey guys,
I goofed. Big time. I accidentally wiped the sdcard in recovery mode when flashing to another rom.
I have her booted into red recovery and mounted the USB mass storage but it isn't showing up on my computer (I have a Mac that is running a dual boot of windows) on neither the windows or Mac side. Positive the drivers are installed on both.
Please help. If I can put a rom onto the card I'll be fine...but I can't get onto the card
Any suggestions?
Click to expand...
Click to collapse
Pretty sure usbmount never worked with red cem for us...at least ot never did for me
MaxJ360 said:
So I had a problem almost the same.
I was using JellyBelly 4.2, and didn't like it. I wanted to go back to Cyan 10.0 and installed the files on my phone. I decided it was a good time to wipe everything, and started to do so. One of the files was the SD format. So I did that, and then wipe/data factory reset. Crap. So now I have no rom installed, and no files on my SD card.
I need help to place my zip files for CM 10 on my SD card (they are on my MAC now). I can't start up my phone to enable file transfer. I can only boot into CWM recovery. Is there a (step by step) way to push files from my MAC onto the SD card? Or is there a different way to tackle this?
I have a GNex (Toro) VZW
MacBook running snow leopard.
I am afraid that anything give me advice on you're gonna have to pretend that I am really dumb and need step by step directions. I tried to push via ADB but got this error, I don't know the correct commands for that. View attachment 1508775 Any suggestions?
Click to expand...
Click to collapse
Since your on jb with blue recovery you should be able to Mount USB storage from recovery...mounts and storage>mount USB>plug into computer
Sent from my SGH-I997 using Tapatalk 2
Mounts
So when I boot CWR and go to the mounts and storage menu I only see the following options.
Mount /sdcard
Mount /system
Unmount /cache
Unmount /data
Format /sdcard
Format /system
Format /cache
Format /data
I've tried them all while plugged into my Mac, and nothing happens on any of them.
Try getting your adb set up.
I'm pretty sure that if you right click on the tools folder and go to get info or anything similar to properties, it will show you the whole Path.
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
I need help installing a ROM, I know how to root and i have superuse and red recovery, however, everytime I install a ROM, i get soft bricked with a robotic woman's voice saying, "convert system partition, data not available... Convert data partion, system not available.
Any ideas? I use the ODIN-one-clcik KJ2 tar i believe.
Thanks in advance for any help.
Sent from my SGH-T839 using XDA Premium Apple
Finally Installed a ROM successfully, thanks guys for you help,
My solution:
Disable Anit-Virus from blocking important programs (SuperOneClick & One Click KJ2 ODIN)
SDCard needed to be partitioned to ext 2048 and swp 0 (backup card before doing so)
Place Recovery file in system/bin with root explorer, and update.zip on SDcard( Don't Flash !)
Delete any ClockWorkMod on your SDcard,
intsall Rom Manager,
Flash Rom Manager with Sidekick 4g,
reboot into recovery, by using 2click + power method, if still blue recovery, re-install packages; it should go to Orange recovery version 4.0.0.2
Make sure Mounts are correct before flashing ROM,
Thanks for all you help guys :good::good::good:
d9vabder said:
I need help installing a ROM, I know how to root and i have superuse and red recovery, however, everytime I install a ROM, i get soft bricked with a robotic woman's voice saying, "convert system partition, data not available... Convert data partion, system not available.
Any ideas? I use the ODIN-one-clcik KG2 tar i believe.
Thanks in advance for any help.
Sent from my SGH-T839 using XDA Premium Apple
Click to expand...
Click to collapse
The woman - aka: Linda
This is the voodoo/ext4 lagfix.
IIRC, and knowing krylon360, it uses the sd-ext partition on your sdcard to temporarily store your files while it converts your partition.
Backup your sdcard, go into recovery. Partition your sdcard. Give EXT 2048 and 0 for swp.
Then try Odin again.
Thank you, will do
Sent from my Inspire 4G using XDA Premium App
after I ODIN, I get stuck on SuperOneClick now, *daemon not running. starting now on port 5037* and when I look at my processes, I have two ADB.exe running, I end the one with the lowest memory (984kb) and one click pops up a window "Automatic version check failed. Is your OS version 2.0 or higher." (Yes) I click ok and then it gets stuck on waiting for device.
d9vabder said:
after I ODIN, I get stuck on SuperOneClick now, *daemon not running. starting now on port 5037* and when I look at my processes, I have two ADB.exe running, I end the one with the lowest memory (984kb) and one click pops up a window "Automatic version check failed. Is your OS version 2.0 or higher." (Yes) I click ok and then it gets stuck on waiting for device.
Click to expand...
Click to collapse
So, I'm guessing Odin worked and Linda talked a bunch and everything in that part worked.
If that is the case. When you boot to recovery, can you run 'adb shell' and get a root prompt?
If so, first mount /system
In adb shell:
Code:
mount /system
then close out of adb shell by typing 'exit'
Then download this zip.
extract it and cd to the directory it extracted to.
Then type:
Code:
adb push su /system/xbin/
adb push busybox /system/bin/
adb shell
back in adb shell, we just need to make sure su and busybox are set with the sticky bit:
Code:
chmod 4755 /system/xbin/su
chmod 4755 /system/bin/busybox
You now just need to reboot, go to the market, install supersu by chainfire and busybox by stericson and run them both (to mostly upgrade the su binary, but also to make the 'smart links' in busybox)
You are now rooted.
If you don't have adb shell in recovery, please point me to your recovery and I will fix it.
I was never very familiar with using ADB shell, is it, my cmd? Or is it in some kind of emulator?
After this , I think I'm will to have some one do it for me, I'll pay for shipping and everything
The recovery I have after ODIN restore is blue, with no mount options, advanced, etc. All it has is this:
Android System Recovery <3e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete all user cache
delete cache data
I think my SD card is corruput, it doesnt show up when I plug it into an adapter to USB to computer; my 16gb does show up.
Im going to retry everything with the 16gb card and I found out how to ADB push, hopefully I'll be able to Root Again on the 16gb
d9vabder said:
I was never very familiar with using ADB shell, is it, my cmd? Or is it in some kind of emulator?
After this , I think I'm will to have some one do it for me, I'll pay for shipping and everything
The recovery I have after ODIN restore is blue, with no mount options, advanced, etc. All it has is this:
Android System Recovery <3e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete all user cache
delete cache data
I think my SD card is corruput, it doesnt show up when I plug it into an adapter to USB to computer; my 16gb does show up.
Im going to retry everything with the 16gb card and I found out how to ADB push, hopefully I'll be able to Root Again on the 16gb
Click to expand...
Click to collapse
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
TheLastSidekick said:
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
Click to expand...
Click to collapse
When I copy the recovery file into the bin folder in system, and place the update on root of SD, it still comes up blue, however, if I take a recovery out of a ROM file and replace it, it still comes up blue, but, if I hit re-install packages on stock recovery. I was finally able to change my mounts, and now I get this after installing ROM in orange recovery, " Convert system partition, 2 min... back up operation." Wow, now I have a red VooDoo recovery. Wouldn't reboot, or install any ROM from SD because it wouldn't let me mount the SD CARD,
mount /sdcard
error
bhundven said:
The woman - aka: Linda
This is the voodoo/ext4 lagfix.
IIRC, and knowing krylon360, it uses the sd-ext partition on your sdcard to temporarily store your files while it converts your partition.
Backup your sdcard, go into recovery. Partition your sdcard. Give EXT 2048 and 0 for swp.
Then try Odin again.
Click to expand...
Click to collapse
After I did this to my 8gb micro sd, It is now unreadble, evene after setting back to defaults.
I'll test it on a 1gb, before my 16gb.
Right now I have the VooDoo recovery, but I can't install ROMS because it says, "can't mount sdcard," and when I try to mount it, it says:
E:Can't mount /sdcard
Error mounting /sdcard!
And Rebooting system takes me back to recovery or a boot loop.
TheLastSidekick said:
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
Click to expand...
Click to collapse
The stock recovery has voodoo lagfix?
d9vabder said:
After I did this to my 8gb micro sd, It is now unreadble, evene after setting back to defaults.
I'll test it on a 1gb, before my 16gb.
Right now I have the VooDoo recovery, but I can't install ROMS because it says, "can't mount sdcard," and when I try to mount it, it says:
E:Can't mount /sdcard
Error mounting /sdcard!
And Rebooting system takes me back to recovery or a boot loop.
Click to expand...
Click to collapse
Can you mount that sdcard with a card reader?
Run a filesystem check, make sure it is good.
bhundven said:
The stock recovery has voodoo lagfix?
Click to expand...
Click to collapse
No. I mean to say he's talking about a blue recovery..this could be the factory Samsung recovery. On the Sidekick the default CWM is Orange, and Voodoo CWM is Red.
TheLastSidekick said:
No. I mean to say he's talking about a blue recovery..this could be the factory Samsung recovery. On the Sidekick the default CWM is Orange, and Voodoo CWM is Red.
Click to expand...
Click to collapse
Don't just ask for colors, ask for versions
Does it say 3e?
Or is it version 3.0.2.8 (red or blue)?
bhundven said:
Don't just ask for colors, ask for versions
Does it say 3e?
Or is it version 3.0.2.8 (red or blue)?
Click to expand...
Click to collapse
Point well made haha, but for people who often times run into these problems don't know the versions. The only way I was able to establish versions were through color. Sorry if it doesn't make sense.
Sent from my SGH-T989 using Tapatalk 2
TheLastSidekick said:
Point well made haha, but for people who often times run into these problems don't know the versions. The only way I was able to establish versions were through color. Sorry if it doesn't make sense.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well, the version number is on every screen in recovery. It's always easy to find, because it says v3.0.2.8 or similar.
The point is, in the future, there maybe newer versions, and if you get in a good habit of knowing the version number, it helps to differenciate between different versions of CWR and other recoveries:
2x from Stock Android Recovery (v2 is from donut to eclair)
3e from Stock Android Recovery (v3 is from froyo to jellybean)
v2.5.1.x from Froyo CWR
v3.0.2.8 (Stock CWR- blue or Voodoo CWR- red) from early Gingerbread
there was a v4.x.x.x, but I don't remember how long that lasted...
v5.0.x.x from newer Gingerbread CWR
v6.0.1.x from ICS and Jellybean CWR.
It helps you to know where the recovery comes from. This info is useful for any phone you are on
No, I had stock recovery, I would place a recovery from the Glorious+Overdose ROM into the system/bin, and it would still come up blue, however, when I choose install packages on blue recovery, it takes me to Orange recovery, I'll check versions. And yes, I have an adapter for the sdcard, I checked it, nothing comes up, its done/fried. I'm afraid to try changing the ext and swp on my 16gb 10class because I don't the same results.
d9vabder said:
No, I had stock recovery, I would place a recovery from the Glorious+Overdose ROM into the system/bin, and it would still come up blue, however, when I choose install packages on blue recovery, it takes me to Orange recovery, I'll check versions. And yes, I have an adapter for the sdcard, I checked it, nothing comes up, its done/fried. I'm afraid to try changing the ext and swp on my 16gb 10class because I don't the same results.
Click to expand...
Click to collapse
Sounds like you had a bad sdcard and did something wrong with the overdose rom stuff. I wouldn't be afraid of the 16G sdcard. Go for it.
Repartitioning your sdcard doesn't fry sdcards.
Maybe TheLastSidekick will chime in and help out with your recovery issue, but I'd still suggest moving to the 16G, partition with 2048M of ext and 0 swp and odin again. try the glorious+overdose rom directions again.
Cool, so I re-did everything (ODIN, rooting) I deleted the clockwork that was already on the SD with RootExplorer, put the Update.zip on root of sdcard, and the recovery in the system/bin and rebooted into recovery successfully with Rom Manager, I have Orange CllockworkMod Recovery v4.0.0.2, now I am going to partition the SD card.
Just one more question, Can I use the same 16gb SD card on my rooted HTC Inspire 4G for ATT? Or do I need to re-partition the sdcard?
d9vabder said:
Just one more question, Can I use the same 16gb SD card on my rooted HTC Inspire 4G for ATT? Or do I need to re-partition the sdcard?
Click to expand...
Click to collapse
I'd repartition, but don't forget to backup first.
I've got my tf300t stuck in a boot loop when i turned it on today. (Ive looked around the forums for this issue already and been able to find little or no solutions that work for me)
I'm using cm10 and twrp. last night i shut the tablet off as usual and go to turn it on today and i cant get past the white asus logo and device unlocked screen.
I can access my twrp recovery menu, wiping dalvik returns a "E:Unable to mount '/data' (tw_mount)" cache wipes fine no errors.
I'm unable to flash another rom or restore from a back up as well.
Fastboot says its working but in cmd prompt it wont list the device. (computer recognizes it and it shows in device manager as android adb interface)
If there is any other information needed I will be more than happy to provide it.
any tips or help is greatly appreciated.
thanks in advanced.
I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.
stenc55 said:
I'm not yet very fammiliar yet with TF300, but from SGS 1 and ICS I remember one trick. If you have external microSD pluged, take it out or of you don't have it plug it in and then enter TWRP.
It probably won't work but you can try anyway.
Does TWRP have any file browser? I'm using CWM so I don't know much about TWRP.
Click to expand...
Click to collapse
Yeah it does have the file browser, upon initial booting i can browse an sd card ( i have a few of various sizes none seem to to be having any affect) and i can browse the internal storage as well. Booting both with and without the sd card in the device still leaves me in the boot loop.
So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.
stenc55 said:
So, can you copy new rom to sd card, then copy from sd to internal and install new rom? I think only option you have is to reinstall rom.
Click to expand...
Click to collapse
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems
Hagenator said:
I can and have tried but it wont let me flash with the "unable to mount /data" error. It tells that my external sd-card and whatever rom i attempt to flash has problems
Click to expand...
Click to collapse
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.
M
Repairtech123 said:
Be sure your sdk is up to date.
1. If you hold volume down plus power button to get to fastboot.
2. shift + control right click fastboot folder on computer then open command prompt.
3. type devices... and if it is not showing a device there something is not right.
4. you can try adb push to apply a flash if your device is not wanting to flash from sd card.
Click to expand...
Click to collapse
I've tried this as well. It was my first thought. Also it states in my original post that fastboot doesnt list my device, adb doesnt list it as well. Both are recent and up to date. However device manager does recognize it and windows makes the little notification sound. In safely remove devices it shows up as fastboot when i enable fastboot on the device.