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.
Related
Update: 08/22/2011
CWM 4.0.1.5
Code:
Changelog:
https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread
Also changed the Init logo. You should like it :P
This brings you up to date.
DOWNLOAD
Internal: http://krylon360.com/file_host/G2x/nvflash-internal-08222011.zip
External: http://krylon360.com/file_host/G2x/nvflash-external-08222011.zip
To flash, use NVFLASH.
I am using Chris's nvflash script from the original cwm. I modified it to flash the new recovery image.
Instructions
Power off phone
take battery out
hold vol up and down and plug in USB
You wont see anything, but it should mount
(If you get an error USB Device not found after running the script, unplug from pc and phone, and redo it)
extract file
type ./flash-recovery.sh and enter
once you see .img sent successfully, unplug usb and put bat back in
hold vol down + power, once you see the 2nd logo, let go
OLD!
This is the newest version of CWM compiled from Source. Along with this comes some much needed changes.
1st and foremost: I am not responsible for any bricks. Know what you are doing before attempting this.
Code:
New Version Changes 06/16/2011
Reverted back to Yellow Color Scheme (this was causing source not to sync)
What ever else changed with the source
This is just to bring you guys to the latest CWM Source.
New Host :)
Changes:
Red font (Much like Voodoo Red CWM) to show EXT4 Support
Able to backup and restore both ext3 and ext4 without any issues
(restore ext3 over ext4 and vice-versa)
EDIT: 2 versions now avail. These instructions are for the Internal SD version only
CWM now mounted to Internal SD. Brought back flashing from Internal SD due to request.
External SD is also mounted, however at this time, unable to flash from both internal and external.
If you would like your old CWM backups, be sure to copy over the Clockworkmod folder from your external to your internal sd.
External version instructions.
There aren't any. Flash as you are use to with the 3.0.2.7 Yellow recovery
To flash, use NVFLASH.
I am using Chris's nvflash script from the original cwm. I modified it to flash the new recovery image.
Instructions
Power off phone
take battery out
hold vol up and down and plug in USB
You wont see anything, but it should mount
(If you get an error USB Device not found after running the script, unplug from pc and phone, and redo it)
extract file
type ./flash-recovery.sh and enter
once you see .img sent successfully, unplug usb and put bat back in
hold vol down + power, when you see the BLUE LG LOGO, let go of the buttons. There is no more ANDROID logo.
EDIT: 05/24/2011
New Update.
Updated 2nd Boot Logo, now no longer Blue LG
Fixed USB Mass Storage option. Now mounts to the PC when selecting.
Reboot option is due to a kernel issue on stock. If you have CM7, this works though.
Thanks oh masterful krylon!
Sent from my LG-P999 using XDA Premium App
how about two versions? one for internal and one for external?
Nismo300zx said:
how about two versions? one for internal and one for external?
Click to expand...
Click to collapse
I knew someone would ask this. LOL
we going up! thank you!
there you go. 2 versions now up.
Internal SD version
and
External SD version
Please excuse my ignorance! In layman's terms, what benefits will I see over the original cwm recovery?
instigator008 said:
Please excuse my ignorance! In layman's terms, what benefits will I see over the original cwm recovery?
Click to expand...
Click to collapse
you can now backup and restore ext4 based partitions.
This also give the option to have the latest cwm, and gives the option to be able to flash from internal sd if you happen to have a small microsd, anotherwords if you have only a 2gb microsd, go for the internal version because that will give you more space for roms, kernels, and mods, and backups.
Thanks Krylon!
krylon help!!! i downloaded external file cuz i have external sd and thats what ive been using and went to extract but my computer sayin format unknown or damaged n wont let me do anything with it im using winrar then tried internet explorer no go any ideas?
sarni84 said:
krylon help!!! i downloaded external file cuz i have external sd and thats what ive been using and went to extract but my computer sayin format unknown or damaged n wont let me do anything with it im using winrar then tried internet explorer no go any ideas?
Click to expand...
Click to collapse
try redownloading it...it unzips fine for me with winrar
sarni84 said:
krylon help!!! i downloaded external file cuz i have external sd and thats what ive been using and went to extract but my computer sayin format unknown or damaged n wont let me do anything with it im using winrar then tried internet explorer no go any ideas?
Click to expand...
Click to collapse
7zip FTW!
the file is valid.
UPDATED to support new recovery: [GUIDE] How to set up and use NVFlash to flash CWM recovery
recovery image has been mirrored aswell: p999-ext4-external-recovery.img
Works great thanks!
can someone plz help i got it extracted didnt have to be extracted anywhere specific rite? and what is the next step after i extract it?
UnionMount/aufs/unionfs?
Anybody remember the discussions and use of aufs (https://secure.wikimedia.org/wikipedia/en/wiki/Aufs) and unionfs (https://secure.wikimedia.org/wikipedia/en/wiki/UnionFS) back in the G1 days? Lots of discussions here in XDA about it but I believe it was available in haykuro, cyanogen and jesusfreak builds. It allows two separate filesystems to appear on the same mount point. I'm not sure what issues exist with it today but maybe some of the kernel hackers could comment?
Anyone else notice that the SD card space free is messed up on the external version? Still seems to be reading the free space from Internal, although SEEMS to be backing up to external SD (as its not failing w/ on 300MBs free)
EDIT: LMAO! Guess i accidentally flashed the wrong version. That's what happens when I work on my phone before coffee........
anyone? idk been trying for an hour i guess il just keep regular recovery aint that much of a diff sux i wanted the new one but after i extract get lost from there
sarni84 said:
anyone? idk been trying for an hour i guess il just keep regular recovery aint that much of a diff sux i wanted the new one but after i extract get lost from there
Click to expand...
Click to collapse
Take a read at the GUIDE thread in this very same forum: http://forum.xda-developers.com/showthread.php?t=1054492. First post has a good step-by-step.
short/y said:
Anybody remember the discussions and use of aufs (https://secure.wikimedia.org/wikipedia/en/wiki/Aufs) and unionfs (https://secure.wikimedia.org/wikipedia/en/wiki/UnionFS) back in the G1 days? Lots of discussions here in XDA about it but I believe it was available in haykuro, cyanogen and jesusfreak builds. It allows two separate filesystems to appear on the same mount point. I'm not sure what issues exist with it today but maybe some of the kernel hackers could comment?
Click to expand...
Click to collapse
Yeah, I remember the Apps2SD via unionfs by MarcusMaximus. TheDudeofLife had it incorporated in his Cupcake builds....ahh, the good old days.
deleted outdated!
Please delete some app to free space in /system (for root and redirector) at least 10 mb of space
to check if there is free space... turn on debugging and
type this in your adb shell prompt: df -h
it will show free space in byte
Can I use this to repair a soft bricked unit?
I would try it... but I cant risk a brick. can't afford another phone, dont have a backup phone.
This can't brick your phone, it doesn't flash a kernel, nor boot or sbl. The only thing it changes is recovery, and adds recovery folders to your /system. Because it's not flashing, it also won't work without ADB being functional, so unfortunately it probably won't work on a soft brick.
EDIT: Testing now. P.S. Noobnl: you forgot quotes on line 19 of run.sh.
EDIT2: tried, doesn't have playlogo, so that part fails.
CWM 3.2.0.1! it works, but filesystem mounting still doesn't work, says "unable to open ums lunfile (no such file or directory)
All of the keys are mapped correctly though!
Found the reason SDCARD mounting fails, it still shows sdcard as being /dev/block/mmcblk0p1 in fstab, even though I remapped it.
I will try editing the recovery.fstab on my phone and see if that works!
EDIT A PALOOZA: in adb in recovery, I see the sdcard mounted on /mnt/sdcard as /dev/block/mmcblk0p1 and I can see everything if I cd to /mnt/sdcard! so now it's just a matter of why it's not able to usb mount!
After all of my Edits/testing, I can verify:
-This flashes a working version of CWM 3.2.0.1
-sdcard mounts, but not for usb mass storage
-keys are all mapped correctly
sduvick said:
This can't brick your phone, it doesn't flash a kernel, nor boot or sbl. The only thing it changes is recovery, and adds recovery folders to your /system. Because it's not flashing, it also won't work without ADB being functional, so unfortunately it probably won't work on a soft brick.
EDIT: Testing now. P.S. Noobnl: you forgot quotes on line 19 of run.sh.
EDIT2: tried, doesn't have playlogo, so that part fails.
CWM 3.2.0.1! it works, but filesystem mounting still doesn't work, says "unable to open ums lunfile (no such file or directory)
All of the keys are mapped correctly though!
Found the reason SDCARD mounting fails, it still shows sdcard as being /dev/block/mmcblk0p1 in fstab, even though I remapped it.
I will try editing the recovery.fstab on my phone and see if that works!
EDIT A PALOOZA: in adb in recovery, I see the sdcard mounted on /mnt/sdcard as /dev/block/mmcblk0p1 and I can see everything if I cd to /mnt/sdcard! so now it's just a matter of why it's not able to usb mount!
After all of my Edits/testing, I can verify:
-This flashes a working version of CWM 3.2.0.1
-sdcard mounts, but not for usb mass storage
-keys are all mapped correctly
Click to expand...
Click to collapse
wait so the recovery works and reads the SD , except you cant mount to PC while in recovery ?
Are you able to make a nandroid backup ?
ayoteddy said:
wait so the recovery works and reads the SD , except you cant mount to PC while in recovery ?
Are you able to make a nandroid backup ?
Click to expand...
Click to collapse
^^^ can we nandroid backup and restore?
I'll try nandroid now, and let you know if it works.
EDIT: Backup seems to have worked, but when trying to restore, it says can't mount SDcard.
Wow this is exciting!
If we get this to koush would he be able to add it to rom manager for easy install?
jahnbodah said:
Wow this is exciting!
If we get this to koush would he be able to add it to rom manager for easy install?
Click to expand...
Click to collapse
He can, not sure if he actually will.
jahnbodah said:
Wow this is exciting!
If we get this to koush would he be able to add it to rom manager for easy install?
Click to expand...
Click to collapse
"Easy-install"??
One- click is hard?
One click still work if already rooted with failcovery? (Unchanged epic4g rec. That came with one click)
Haven't looked at install instructions yet, I'm at work right now
Nandroid indeed worked for backing up! I have full images on my SDcard from today!
I followed the OneClick instructions...appeared to work fine. Rebooted, with no problems. Now, how do I tell if it is still rooted?
Thanks!
You can download rootchecker from market. If you have CWM installed, you're almost positively rooted.
i smell a ROM cooking ..
has the dl link been updated with the editing sduvick did?
Sent from my SGH-T839 using XDA App
now that we have this can we get the images need to fix our soft brick ???
or is der a way i can flaash this soft brick i have no adb i can only use odin it only boots into recovery
I haven't done any editing since that link was uploaded. I figured out how to mount the sdcard as well! it's a script from drockstar, you can mount it by entering adb in recovery and typing 'mountums', and when you're done type 'umountums' to unmount your sdcard. be sure to unmount before disconnecting your phone!
I'll see if it's possible to map the button in recovery to mountums.
Datlilboricua: just relax and wait. when it works, it'll be updated in the stock recovery thread.
EDIT: tried nandroid, still can't restore, still can't mount sdcard.
Ok, I got the recovery on and I am having in issue, I cant install cyanoge.... just kidding.
Anyway, I really did have an issue, I tried to nand backup, and halfway through (after /data BU) it lost the sd card, I believe it said it was not mounted. very odd.
Good work so far guys, keep it up and we should have this thing working very soon! thanks.
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
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.
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