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.

[Q] E: Failed to mount / efs(invalid argument)

Hello All,
I have a Samsung Galaxy I9070.
I have rooted the device from http://forum.xda-developers.com/showthread.php?t=2087424 and it worked fine.
After that i tried to Flash a CWM 5 XX version,
1. I wiped all the data/reset
2. While flashing it from "Apply update from external storage" the device got powered off.
3, I did a hard restart to enter recovery mode and then CWM showed up and stared to blink.
4. Now i got a error as E: Failed to mount / efs(invalid argument).
5. i have restarted the device.
6. i am getting a error as Unfortunately,the processcom.google.process.gapps has stopped.
Now i thought to flash a new rom from SD card and then it may work.
1. i flashed cynogen Mod 11.0
2. after that it is just stuck at the starting screen of Cynogen Mod logo.
Now i have restored the Jellybean from Odin and still i get the same error as Unfortunately,the processcom.google.process.gapps has stopped.
and also in the recovery mode E: Failed to mount / efs(invalid argument). this error stayed.
Please help me to get the device back to working.
Just an update-
1. i have used ODIN and installed Ginger bread on it.
2. The phone got turned on and working.
3. I am not able to connect to Wifi.
4. But when i go to recovery mode, it still shows that error as E: Failed to mount / efs(invalid argument).
5. I think this this EFS file is corrupted and so Mac address of the device is corrupted.
How do i fix this error. Please help. i have not taken a backup of this efs.
Thanks All.

rohanpakala said:
Hello All,
I have a Samsung Galaxy I9070.
I have rooted the device from http://forum.xda-developers.com/showthread.php?t=2087424 and it worked fine.
After that i tried to Flash a CWM 5 XX version,
1. I wiped all the data/reset
2. While flashing it from "Apply update from external storage" the device got powered off.
3, I did a hard restart to enter recovery mode and then CWM showed up and stared to blink.
4. Now i got a error as E: Failed to mount / efs(invalid argument).
5. i have restarted the device.
6. i am getting a error as Unfortunately,the processcom.google.process.gapps has stopped.
Now i thought to flash a new rom from SD card and then it may work.
1. i flashed cynogen Mod 11.0
2. after that it is just stuck at the starting screen of Cynogen Mod logo.
Now i have restored the Jellybean from Odin and still i get the same error as Unfortunately,the processcom.google.process.gapps has stopped.
and also in the recovery mode E: Failed to mount / efs(invalid argument). this error stayed.
Please help me to get the device back to working.
Just an update-
1. i have used ODIN and installed Ginger bread on it.
2. The phone got turned on and working.
3. I am not able to connect to Wifi.
4. But when i go to recovery mode, it still shows that error as E: Failed to mount / efs(invalid argument).
5. I think this this EFS file is corrupted and so Mac address of the device is corrupted.
How do i fix this error. Please help. i have not taken a backup of this efs.
Thanks All.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2677807
Try this maybe.

I have the same problem.
I wanted to flash a new rom and and deleted some unnecessary folders and I deleted some hidden folders.
I can enter on recovery/downloading but I can't flash any rom.
I've flashed a stock rom (JB) via Odin and it restart the device on setup screen but it gives 2 errors (I'll post the images).
I've flashed another stock rom (GB) via Odin and it restart the device on the home screen but whenever I go to recovery it shows me the the message E: Failed to mount / efs (Invalid argument)
I've tried some methods I've found on the forum but they didn't work.
The link posted don't work for me.
My phone connect to 3G and don't shows the error "Baseband and IMEI unknown / Baseband unchangeable".
I didn't find any thread on the forum with the answer for my problem.

[Q] i9000 bricked, help!

so my brother's phone got bricked for some reason. I tried searching for answers but I can't find answers. I'll be detailed as possible so imma list down the problems
Problems:
1. When turning on the device, it gets stuck on the Samsung Galaxy S logo
2. I can open recovery mode (CWM v3.0.0.5) but then these errors show up:
"E: unknown volume for path [/data]
E: Unable process volume! Skipping...
E: can't mount /cache
E: can't open /volume"
...etc
3. ADB can't see/detect the device
4. Went to Download mode but then Odin does not detect it. (I have the latest drivers from Samsung. I also tried connecting my Note 2 and Odin can detect it. I also tried different cables but none would work)
5. Tried inserting an SD card but i cant seem to find a way to flash from a zip file
6. Also tried restoring but errors appear (see #2)
How it got bricked:
My brother said that he simply rebooted the phone because of lag and that happened.
I'm not sure if USB debugging's on before this phone got bricked.
It's running Optimum Jellybean by Likeman and yes it's rooted
Help please (

Wipe & Flashing has no effect

Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.

Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.

i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.

Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031

hi, maybe any1 has already found a solution?

dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!

Question Can't Load Bootloader

First off, I'm a little out of my depth here.
I had originally wanted to root my A8, but stopped short because it isn't officially supported by TWRP. I wanted to roll things back but botched the Odin process. I flashed the AP file but didn't include any of the others. As a result, I can't get into the bootloader. I'm not sure what my options are at this point, or if I have any.
I've already wiped the cache partition and done a data/factory reset.
Output on my Recovery screen is as follows:
Code:
Failed to load locales from the resource files, Failed to compare
#Reboot Recovery Cause is [UNKOWN]#
#Reason is []#
E:Failed to load bitmap installing_text for locale en-US (error -1)
Supported API: 3
# MANUAL MODE v1.0.0#
No command specified.
I'm hoping there's a procedure for completing loading in the other files, or getting back into the bootloader.
Do I have any hope or did I truly brick this thing?

Ok, I got it back by using vol up/down and plugging in the USB. Wasn't able to do it from the recovery, but the physical method worked. Odin worked, I'm back in business.