Database Develop

Help me troubleshoot my SDCard errors!

Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you

Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.

My Optimus Dead Help me

First a good afternoon,
my phone is faulty, it no longer starts when I turn on my phone it goes into recovery mode, volume tightening down and put the cable into your computer boots into recovery mode, the worst that he would not let me do anything in recovery, because it the error
E: Can not mount CACHE: recovery / command
E: Can not mount CACHE: recovery / log
E: Can not open CACHE: recovery / log
Formatting MISC: ...
room for the chuck norris I can install but not work so back to the recovery, I have a doubt with chuck norris in the installation I get into the system and see the folders inside the cache cell type, root etc., if I do a arrumasse backup of the original cell or coerce people to copy to my phone work?
Help me please, I do not know what to do, my phone is not even 1 month of use.
If you have any idea really need help because I can not connect to the phone can not put debugging usb or anything.

remove battery to 5 min and try again... i hope will be fine...

robsonverly said:
First a good afternoon,
my phone is faulty, it no longer starts when I turn on my phone it goes into recovery mode, volume tightening down and put the cable into your computer boots into recovery mode, the worst that he would not let me do anything in recovery, because it the error
E: Can not mount CACHE: recovery / command
E: Can not mount CACHE: recovery / log
E: Can not open CACHE: recovery / log
Formatting MISC: ...
room for the chuck norris I can install but not work so back to the recovery, I have a doubt with chuck norris in the installation I get into the system and see the folders inside the cache cell type, root etc., if I do a arrumasse backup of the original cell or coerce people to copy to my phone work?
Help me please, I do not know what to do, my phone is not even 1 month of use.
If you have any idea really need help because I can not connect to the phone can not put debugging usb or anything.
Click to expand...
Click to collapse
Remove the Battery.Plug in the USB to the computer.while keeping the Volume Down key pressed Attach the USB to the Phone.it should take you to the Software Update Mode.Flash A KDZ file(look for tutorials on XDA) and your phone SHOULD be back to Normal.

Either u can use NV flash
manasgirdhar said:
Remove the Battery.Plug in the USB to the computer.while keeping the Volume Down key pressed Attach the USB to the Phone.it should take you to the Software Update Mode.Flash A KDZ file(look for tutorials on XDA) and your phone SHOULD be back to Normal.
Click to expand...
Click to collapse
Either u can use NV flash, follow the link http://forum.xda-developers.com/showthread.php?t=1229407

Try flashing using another computer. It did work for me...happy flashing

[Q] Q: Stuck, Unlocked, Cannot mount E:\, In TWRP, 22hrs In

Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:

rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.

unremarked said:
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.
Click to expand...
Click to collapse
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"

rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?

rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.

unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
1. Have NOT tried to format data
2. Originally tried to install cm touch, which at that time seemed like it didnt work (could not boot into rom) so I tried to install TWRP for some reason
3. I have attempted to boot stock rom, but always gets hung up on "beats audio" audio screen

unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
Wow, saved my ass. I formatted /data and now I can finally boot into CM after a fresh ROM install.
Thanks

nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
1. Loaded ClockworkMod Recovery v6.0.3.1
2. Rebooted to recovery
Result:
Loaded CM Recovery and at the bottom it says:
"E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
Q: Should I try formatting the drive

nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...

rafalk86 said:
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...
Click to expand...
Click to collapse
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.

kenyu73 said:
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.
Click to expand...
Click to collapse
1. Cleared cache - fixed
2. Both datas formatted
Q: Its been a long 24hrs, now I load rom, correct?

rafalk86 said:
1. Cleared cache - fixed
2. Both datas formated
Q: Its been a long 24hrs, now I load rom, correct?
Click to expand...
Click to collapse
It sounds like you have a ROM loaded if its cycling at the BeatsAudio screen. Yes, you can do the ROM now. Make sure you do a factory reset before installing the ROM (or after I suppose)

rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Are you using Mac OSX? What is the format of the external_sd card? Is it formatted FAT, FAT32, or EX_FAT?
Clockworkmod does not support EX_FAT, so you must format it to FAT in order for it to mount. OSX can't format FAT32, so you must format FAT.

Stock Recovery Infected?

I'm having issues flashing a custom recovery. After booting into the Clockwork Mod recovery (just flashed) I get the error codes:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also only have 118MB of free space on the SD Card (seen through recovery).
So I'm trying to download the stock recovery from
http://forum.xda-developers.com/showthread.php?t=2158763
so that I can flash it to start all over to see if it helps, but ESET is coming up with it as infected with a trojan. I'd like to flash it but I'm not sure if I can trust it...
Any help?

That link downloads a rar archive that contains the stock recovery image plus other stuff. My virus protection also picked it up, but I downloaded and check it out and even had another user flash that recovery image so I am pretty sure the download is not infected.

Alright, I'm going to flash it.
Any ideas on the error codes?

Looks like you got fungi on your recovery. DON'T LET IT GET EXPOSED TO WATER!
lesson learnt.

jags_the1 said:
Looks like you got fungi on your recovery. DON'T LET IT GET EXPOSED TO WATER!
lesson learnt.
Click to expand...
Click to collapse
Well, I'm not going to pretend that I don't have any clue what that meant

Myrloc said:
Alright, I'm going to flash it.
Any ideas on the error codes?
Click to expand...
Click to collapse
Maybe fastboot erase cache. Perhaps reflash and try TWRP recovery.

Any idea which recovery to flash. The file I downloaded came with a bunch to choose from.

Oh yeah, I remember now. I didn't use those because I thought they were labeled weird. Here is a zip that contains the stock recovery.img :
https://dl.dropboxusercontent.com/u/36946918/ResetRecovery.zip
I would just try to reflash a custom recovery.
Go to this thread and get TWRP. Rename the file to twrp.img and place it in the same folder as your fastboot. Your phone should still be in fastboot, if not, get there.
Type: fastboot erase cache
Type: fastboot flash recovery twrp.img

since acipen
I can't flash any other recoveries...
When I try to flash another one, the one with go to the "Entering recovery" screen for several seconds and then turn off.

Myrloc said:
I can't flash any other recoveries...
When I try to flash another one, the one with go to the "Entering recovery" screen for several seconds and then turn off.
Click to expand...
Click to collapse
I sometimes get those error messages when I go from Twrp to Cwm, but after I do a backup or flash something it goes away the next time I boot into recovery.
Sent from my HTC One using xda premium

The other issue is that when I'm backing up in CW, it says:
Backing up system..
Can't mount /system!
Is this a problem or should I ignore it?

I have CW flashed, but now I can't start my phone. Everything's been flashed (data/factory reset, etc.). I don't think I wiped the system, but now I'm not sure. Any help guys? This kind of blows.

N900a Failed to Mount EFS

I woke up today and my Note 3 was dead. I assumed the battery died as that is in all likelihood what happened. I plugged my phone into the charger and attempted to turn it on. It stayed on the Samsung logo for several minutes. I then booted it into recovery mode, and noticed at the bottom, E: Failed to mount /efs (invalid argument). I attempted a cache wipe and at first it said failed to mount /cache, however another attempt and it completed without error. I then tried a reboot with the same problem. Next I tried a system/data wipe and got the same problem (failed to mount efs).
So, I used a 4 part Odin flash to 5.0 Lollipop OEM. This succeeded and upon reboot the phone got as far as the AT&T logo then hung again. Once in recovery I noticed the same E: Failed to mount /efs (invalid argument). I have searched on this and many other forums attempting to resolve this issue without success. I've been at this nonstop for 12 hours now. I know of a way to use adb to create a generic EFS folder, the problem is the phone is 100% stock, including no developer options(adb), custom recovery, etc. Not even busybox.
Anyone with any info on how I can unbrick this phone would greatly appreciated. Or even how I can use Odin to install safestrap w/ root thereby giving me the ability to mount the system with TWRP and send adb commands that way. To clarify, I have access to nothing but the stock recovery and download mode without ADB active on the phone. Thanks for your time.