FIX: failed to mount /efs error message - T-Mobile Samsung Galaxy S II SGH-T989

There are a number of threads throughout xda-developers, but I had a very long journey to find a fix that worked with my T-Mobile T989 Galaxy S2 phone. In a nutshell, sometime over the last week I somehow corrupted my /efs directory/folder enough so that it wouldn't mount. The symptoms I started to have was that I couldn't load any custom ROM without it going into a boot loop eventually. Even the backups that I saved would not work! I was able to use Odin to factory reset my phone back to 2.3.6 gingerbread, and it would run, but if I tried to load any ROM including going thru a Kies factory update, it would fail. (Note I still had a valid IMEI number displayed) Then I saw the failed to mount /efs error on the factory recovery window. So after many attempts to find and try a specific fix for my T989, I came across this thread in the Skyrocket phone section. This guy named icenight89 came up with a method to fix their phones, with a note that it will work on T989's as well.
The fix for me that worked was for me to factory reset to 2.3.6 via Odin. Then load in CWM recovery and then Super-SU to root the phone. Then download a file on icenight89's thread called EFSFix.zip and upload it to your phone. (Nandroid backup first) then boot into CWM recovery and install this .zip file, and reboot, and voila the efs partition is mountable again!! Here is the link to icenight89's thread and in there are the file links: http://forum.xda-developers.com/showthread.php?t=1611796
Hope this can help shortcut the fix for our phones for someone else who runs into this.

Related

Samsung Galaxy S I9000 wont work after firmware update failed.

I attempted to update my phone to the latest firmware, via Kies, & although Kies gave a successful report, the handset said there was an error, & would reboot. Ever since that point, all i can get, is the main Samsung 'GALAXY S GT-I9000' screen. I've also tried hard & soft resets, but nothing seems to get me back to the proper menu. The hard reset gives this report -
Appling Multi-CSC
Installing Multi-CSC
Can't access to '/system/csc/ORA/system/.
Succesfully applied multi-CSC.
clicking 'yes' on the 'wipe data' option gives this report -
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblkop2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Deleting Meta Data
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Data wipe complete.
Anyone got any clues as to what i do next? Now, whenever i try to connect to Kies, i get the following message -
Reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies.
Obviously, as i can't get to the menu screen, i can't change the connection mode.
you have activated lagfix before.. and this is the problem..one solution is you must flash with odin and with .pit file repartition checked
Sent from my GT-I9000 using XDA App
if you say i've used lagfix, then you must be right, but i don't remember using it. what is odin though, & how do i use it? is it operated from the pc?
Kies sucks!
Look like you have never use ODIN and have never mod your SGS.
Follow this thread and download Stock Samsung Firmware and flash via ODIN.
http://forum.xda-developers.com/showthread.php?t=948790&highlight=cwm+3.2
Or follow this thread with ODIN screen capture on how to flash.
http://samsunggalaxysforums.com/sho...firmwares-for-Samsung-Galaxy-S-I9000-Download
you're absolutely right, i'm a complete novice when it comes to upgrading my phone.
on those links you sent, one says the phone needs to be rooted, have busybox installed and have ADB installed on your PC, the other says i need to know the firmware. as i can't access the menu, i can't root the phone, or check the firmware. i don't actually know how to root the phone either.
go into this thread here:
http://forum.xda-developers.com/showthread.php?t=1011901
find the right rom-version for your country/device, important is that the csc matches your product-code!
follow the instructions in this thread for installing with .pit and repartition.
(sorry for bumping)
I had the exact same problem. After having spent some time understanding the PIT files logics, I decided to switch from 512 to 803, based on my theory that the space lost might circumvent the defective internal sd sectors.
I flashed the exact same firmware (which was the JW1), and the traditional CF-Root kernel.
Back in CWM Recovery, I can now successfully wipe data / factory reset the phone.
Time will tell if it was a valid situation, my guess is the sd will continue to degrade over time. Well to me it was well worth a try.

information on any Clockwork recovery that can load via extSD

USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse
xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image

/efs partition not being mounted

I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Bloodyskullz said:
I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Click to expand...
Click to collapse
Have you tried flashing your official rom? Flash your official firmware by downloading it from sampro.pl or sammobile.com, flash it with PC Odin under PDA tab.
After you done, don't let reboot your phone, goto recovery by pressing vol up+ menu key then power key(continuously hold it until your phone restarts might be 4~8 secs.) Then check 'Wipe Cache Partition', and then reboot phone.
Yup and nothing worked.
Anyone?
So the only solution is a $300 fix?

T989D - Update PIT - Now Bootlooping

Hey all,
I've done my best to find the solution on another thread but nothing came up. So here we go.
Like many I wanted to increase the available space for apps and so followed this thread:
http://forum.xda-developers.com/gal.../mod-partition-internal-memory-t-989-t3051556
to install a modified PIT file with an adjusted data partition.
So I adjusted the PIT file and then wiped the phone (using original firmware - not TWRP)
Problem is that when I attempted this the phone went into a boot loop.
I attempted to put the 'unmodified' version and then ODIN stalled at the 'Set Partition' phase.
After that the phone went to the 'Firmware has encountered an issue....' screen. It was at this point that I loaded TWRP via ODIN and am now back at the bootloop.
I am certain someone has overcome this issue and I'm am hoping for a hand.
Thanks kindly,
Additional info if it helps - under TWRP, the only partition showing is Dalvik Cache
Some additional information when I attempt a 'factory reset' via TWRP:
E: UnMount: Unable to find partition for path /system
Well that was a pain. By sheer luck I found a site that had the stock PIT file for the T989D. Located here:
http://forum.gsmhosting.com/vbb/f777/samsung-t989-pit-file-badly-needed-1526176/
Flashing that to the phone I finally had success. Flashed the stock ROM and voila the phone rebooted.
http://forum.xda-developers.com/gal...w-to-restore-stock-android-to-unlock-t3258079
Note to self and to anyone else reading this thread - wrong PIT file = soft bricked phone.
Peace out,

Odin Stuck in Get Partition mapping - Download Mode and Recovery Working

I have n7100, I had corrupted EFS partition, because of which my phone was stuck at samsung logo. I had no backup of EFS partition, so I flashed the EFS i got it from online. My phone was able to boot without any problem but Cell phone is not getting registered to provider because of IMEI.
Next I wanted to root the phone.
I flashed the root file (CF-Auto-Root-t03g-t03gxx-gtn7100) from odin and in haste immediately flashed the recovery file without waiting for the next reboot.
Usually the root file installs the stuff after the first reboot, in my case it didnt happen since I installed recovery on top of that.
Now I am facing problem in full flash with pit file. Odin is stuck in Set Partition, Get Partition Mapping.
I can access Download mode and recovery.
In recovery the following errors are shown
Cant mount /system
cant mount /efs
Is there anything I can do to make the full flash work?
Your eMMC chip is corrupted, or, worse and probably, you have SDS.
Try and flash a stock ROM
Change the USB cable

Categories

Resources