[Q] Cannot mount efs on gs3 gt-i9300!!!! - Galaxy S III Q&A, Help & Troubleshooting

10 hours after i tried using the swapper 2...my galaxy s3 GT-I9300 rebooted suddenly and got stuck in the galaxy s3 logo. I was rooted and had sotmax v14 running on it. I flashed it several times with that ROM and also cm 10.1 from the sd card. Then i flashed it with a stock ROM using odin. I had access to download mode and recovery mode. In the stock recovery mode it showed something like "E:/eror mounting efs((invalid arguement)).
I have very little knowledge about flashing and i do not even know what EFS is and thus i dont remember of taking a backup of that efs. I flashed it with CF root to access CWM recovery. Now in CWM recovery when i chose sd car it says
"E:cant mount sd card" and when i tried to mount efs it displayed "error mounting efs".
I have been trying hard for 2 days with little food. Any help would be highly appreciated. Help me. What should i do now?? Iam stuck on the galaxy s3 logo no matter what i do...i tried everything factory reset wipe data cache etc etc. please help!!!!

please help i have the same problem when i try to restore my efs folder
i have access to download mode and costum recovery but the phone is all time in bootloop in the logo of samsung galaxy s3 gt i9300

just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.

Glebun said:
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
Click to expand...
Click to collapse
thanks for your help my problem is solved by flashing a stock rom 4.0.4 with odin but i have cheked the phone bootloader update option

good, make sure to hit "thanks"

Glebun said:
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
Click to expand...
Click to collapse
The main problem is I am not able to access the sdcard as it says sdcard cannot be mounted. I remember to have made backups with ROM manager but i dont have access to it. I had ICS 4.04 running on it when i purchased the phone. I tried flashing the phone with two compatible ROMs from Sammobile.com which are jellybean ROMs and factory resetting it, but that did not help too. Are those the stock ROM for the galaxy S3 or should I flash it with ICS 4.04??? Please help me. Thanks in advance!!!!

vijay005100 said:
The main problem is I am not able to access the sdcard as it says sdcard cannot be mounted. I remember to have made backups with ROM manager but i dont have access to it. I had ICS 4.04 running on it when i purchased the phone. I tried flashing the phone with two compatible ROMs from Sammobile.com which are jellybean ROMs and factory resetting it, but that did not help too. Are those the stock ROM for the galaxy S3 or should I flash it with ICS 4.04??? Please help me. Thanks in advance!!!!
Click to expand...
Click to collapse
Were you able to fix the problem?

Please help !!
Quote:
Originally Posted by Glebun View Post
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
---------
thanks for your help my problem is solved by flashing a stock rom 4.0.4 with odin but i have cheked the phone bootloader update option
---------
:crying::crying:
I have got the exact same problem with my S3 GT-I9300, phone bootloop, error mounting efs after flashing omega rom aokp. Can you please explain in detail
which stock rom 4.0.4 you used ?
which odin version you used because I am finding that it is greyed out on every flashing of rom that I did ?
any other detail you think I should know coz I am quite new to this flashing stuff.
Thanks

Thanks you !!!
YESS i tried flashing the stock rom i was previously on cm10.2(andriod 4.3) now im stuck in a bootloop do i have to flash the gapps also?please urgent please reply

gmat11 said:
YESS i tried flashing the stock rom i was previously on cm10.2(andriod 4.3) now im stuck in a bootloop do i have to flash the gapps also?please urgent please reply
Click to expand...
Click to collapse
Try reading the stickies in general forum, follow the instructions on how to return to stock.

Related

[Q] Nandroid Restore issues with Sammy JB

Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Nyssa1104 said:
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
Thanks for your reply.
I only use mobile odin to flash official firmware so its a fresh start before installing a rom.
I've tried to restore from philz before but had the same problem. Normally use Dorimanx.
I myself had no probles with Mobile odin pro of CWM in Philz kernals and since Philz kernal this tends to be the normal backup or flashing aid for me. Since I have a Micro SD card install back up and roms are place on this..
by the way Im using SuperSUPro and not Superuser for root.
symondo12 said:
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Click to expand...
Click to collapse
I have a possible solution just flash entire original rom(the one you are going to restore) once, then restore your nandroid backup, clear cache/dalvik, reboot. I have a hunch on the problem that it might be caused by another roms /preload partition data (our nandroid backup won't usually backup it by default so it actually never gets wiped or overwritten)
Edit :I forgot to mention a factory reset at the beginning.
Sent from my GT-I9100 using xda app-developers app

Special Problem with restoring cwm backup

Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
clown85 said:
Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
Click to expand...
Click to collapse
try philz recovery.
sriram231092 said:
try philz recovery.
Click to expand...
Click to collapse
It says in all the steps E:failed archive external sd
is it a problem to rstore from external sd card? so shall I just try to put it on internal?
Worth trying if you have no backup of it .
jje
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
clown85 said:
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
Click to expand...
Click to collapse
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Endiej said:
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Click to expand...
Click to collapse
My phone works just fine. The problem is to flash the cm10.1 nandroid backup successful to get my internal sd memory back.
btw I tried to copy the backup to internal sd but then it says md5 sum mismatch god damn it..... I just wanna have my internal sd card files back. grrrrrrrr
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
slaphead20 said:
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
Click to expand...
Click to collapse
I guess Im just ****ed... I tried moving it with aroma and then it says error again. its just possible for me to restore the nandroid with cwm which I originally had and just from external sd and even then the logfile says everything is fine just restoring system is an error. that sucks cuz I cant boot the phone then to get access to my internal space via usb
or is there another possibility to restore internal card to get access????
Have you changed recovery versions between creating the backup and trying to restore it?
slaphead20 said:
Have you changed recovery versions between creating the backup and trying to restore it?
Click to expand...
Click to collapse
of course not.
its just weird that I can restore everything exept for this cm10.1 backup. I made already a stock jb backup and I could easily restore this one :S but it doesnt help me anymore.....
Endiej said:
CWM doesn't work without root access
Click to expand...
Click to collapse
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
clown85 said:
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
Click to expand...
Click to collapse
You can try.
Sent from my GT-I9300 using Tapatalk 2
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
clown85 said:
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
Click to expand...
Click to collapse
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
rootSU said:
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
Click to expand...
Click to collapse
No it doesnt boot if I try ro restore the backup I end up seeing Samsung Galaxy S3 screen and thats it....
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
clown85 said:
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Click to expand...
Click to collapse
What is "The above problem"? If it restores and boots, its fine.
clown85 said:
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
Click to expand...
Click to collapse
Nandroid backup takes
boot.img (kernel)
system.img (ROM)
userdata.img (Your stuff)
Its okay. Somehow I got the data restored with advanced restoring which didnt work with 6.0.2.7 but with 3.2.
close here.
thanx for your help

More than bricked?

Well i was playing with my phone, flashed a new rom everything was fine but i had no mobile connection. I had an Efs backup already created with Ktool and wanted to restore it. Restored the img. file nothing happened. Restored the .tar file and my phone just broke. It's not even a bootloop the phone freezes on the boot logo. I tried kies recovery and flashing a stock rom with odin but nothing works. The only firmware that works is the stock ICS 4.0.4 and when i instal it the pc doesn't recognize it and i can't access anything else than odin. Someone please help !
If you can get ics to boot then it isn't bricked.
Panic flashing can brick it, however, so slow down and think. afaik JB won't boot if the efs partition won't mount.
Try flashing Philz recovery via odin, use that to restore/fix your efs then factory reset and flash an official 4.1.2 stock rom.
Also, go read the stickied help for efs:
http://forum.xda-developers.com/showthread.php?t=2393289
boomboomer said:
If you can get ics to boot then it isn't bricked.
Panic flashing can brick it, however, so slow down and think. afaik JB won't boot if the efs partition won't mount.
Try flashing Philz recovery via odin, use that to restore/fix your efs then factory reset and flash an official 4.1.2 stock rom.
Also, go read the stickied help for efs:
http://forum.xda-developers.com/showthread.php?t=2393289
Click to expand...
Click to collapse
Well since i already tried to flash a stock rom the efs backup got deleted probably. Could you please explain me step by step the Philz recovery and what to do after.
Sorry, no. You'll have to learn how to install and use it.
I'll just get it to service today, still thanks for your help

[Q] Would this method work?

I have a couple more questions.
1.) I have the brick bug, right?
2.) Flashing a safe kernel and then restoring the backup won't help either I presume?
3.) Would flashing the PIT file from this thread http://forum.xda-developers.com/showpost.php?p=26428986&postcount=1 solve my problem?
thx in advance
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi everyone
first of all, this is my first post so if i posted in the wrong section i am sorry
now here's my problem:
i have a Galaxy S2 (GT-I9100) with rooted stock ICS 4.0.4. I wanted to restore a backup which I created using the Nandroid Backup app on the same day. So i went into recovery mode, flashed a temporary CWM (from this thread http://http://forum.xda-developers.com/showthread.php?t=2327472) then restored the backup from my SD card. if i remember correctly, if the restoration of the backup was succesful the phone should stay in CWM. In my case the screen went black for a few seconds then it looked like it would boot. However it just got stuck showing the Samsung logo with model number, so Samsung Galaxy S II GT-I9100.
I can still enter recovery and download mode. I did a factory reset, wiped cache partition and even re-flashed the stock ROM using odin but to no avail. After flashing the ROM, it didn't work so i did a factory reset again. It still got stuck on the logo so i went into recovery again. In recovery mode it says "E: failed to mount /sytsem (invalid arguement)". i could solve that problem by reflashing the ROM though.
does anybody know what caused this and even more imortantly, how to solve my issue?
On a side note, could be relevant, my phone just froze all of a sudden some times in the past months. i had to reboot my phone everytime it froze
Thx in advance
EDIT: ok, i've re-flashed the ROM again with odin. at first there is the green droid and the blue loading bar right below, but after a few seconds the screen goes black again and it tries to boot and gets stuck. I pulled battery, reinserted it and went into recovery, wiped cache. when i select "reboot" from the menu it says "E: failed to mount /sytsem (invalid arguement)"
Edit2: after flashing the ROM i get this "E: failed to mount /data (invalid arguement)" when rebooting over recovery. I've found a thread where it says i need to flash the dbdata.rfs.tar using odin. i will try that now
Edit3: when i try to flash the file i get a "NAND write start" "fail" error. I've been to a store that will take care of my problem.
bump
-shadow.walker- said:
Hi everyone
first of all, this is my first post so if i posted in the wrong section i am sorry
now here's my problem:
i have a Galaxy S2 (GT-I9100) with rooted stock ICS 4.0.4. I wanted to restore a backup which I created using the Nandroid Backup app on the same day. So i went into recovery mode, flashed a temporary CWM (from this thread http://http://forum.xda-developers.com/showthread.php?t=2327472) then restored the backup from my SD card. if i remember correctly, if the restoration of the backup was succesful the phone should stay in CWM. In my case the screen went black for a few seconds then it looked like it would boot. However it just got stuck showing the Samsung logo with model number, so Samsung Galaxy S II GT-I9100.
I can still enter recovery and download mode. I did a factory reset, wiped cache partition and even re-flashed the stock ROM using odin but to no avail. After flashing the ROM, it didn't work so i did a factory reset again. It still got stuck on the logo so i went into recovery again. In recovery mode it says "E: failed to mount /sytsem (invalid arguement)". i could solve that problem by reflashing the ROM though.
does anybody know what caused this and even more imortantly, how to solve my issue?
On a side note, could be relevant, my phone just froze all of a sudden some times in the past months. i had to reboot my phone everytime it froze
Thx in advance
EDIT: ok, i've re-flashed the ROM again with odin. at first there is the green droid and the blue loading bar right below, but after a few seconds the screen goes black again and it tries to boot and gets stuck. I pulled battery, reinserted it and went into recovery, wiped cache. when i select "reboot" from the menu it says "E: failed to mount /sytsem (invalid arguement)"
Edit2: after flashing the ROM i get this "E: failed to mount /data (invalid arguement)" when rebooting over recovery. I've found a thread where it says i need to flash the dbdata.rfs.tar using odin. i will try that now
Edit3: when i try to flash the file i get a "NAND write start" "fail" error. I've been to a store that will take care of my problem.
Click to expand...
Click to collapse
hey buddy .. just wana know .. all u have done .. I mean to flash CWM ,, backup ,, restore and any stuff ... u performed all of these things using stock kernel .. ???
c0olmad said:
hey buddy .. just wana know .. all u have done .. I mean to flash CWM ,, backup ,, restore and any stuff ... u performed all of these things using stock kernel .. ???
Click to expand...
Click to collapse
yeah, stock ICS kernel and ROM
-shadow.walker- said:
yeah, stock ICS kernel and ROM
Click to expand...
Click to collapse
buddy it is advised to not to perform any thing like .. restore .. flashing etc etc .. as stock kernel is not safe to perform these operations .. whats the progress of ur fone now .. ???
-shadow.walker- said:
yeah, stock ICS kernel and ROM
Click to expand...
Click to collapse
Like c0olmad said, there is a brick bug in ICS. It would be alot better and safer to flash stock jellybean 4.1.2 link below.
http://forum.xda-developers.com/showthread.php?t=1544487
Unsure of why your still on ics but below is a link to get a safe kernal where brick bug has been fixed. Make sure you get the kernal for your build.
http://forum.xda-developers.com/showthread.php?t=1877270
c0olmad said:
buddy it is advised to not to perform any thing like .. restore .. flashing etc etc .. as stock kernel is not safe to perform these operations .. whats the progress of ur fone now .. ???
Click to expand...
Click to collapse
I've been to the store today. He said my case is a bit complicated and he will call me when it' finished.
stonedpsycho said:
Like c0olmad said, there is a brick bug in ICS. It would be alot better and safer to flash stock jellybean 4.1.2 link below.
http://forum.xda-developers.com/showthread.php?t=1544487
Unsure of why your still on ics but below is a link to get a safe kernal where brick bug has been fixed. Make sure you get the kernal for your build.
http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
TBH, I was aware that there was a brick bug but I thought i wouldn't be affected :silly:
And I was happy with ICS so I didn't upgrade. Also there is an app that currently only works on 4.0 or lower, so I didn't bother with upgrading.
the technicians of the store weren't able to repair it. i guess i have the brickbug :crying:

Efs restore help needed urgent

my main problem is my EFS is totally corrupted. i have yellow writing on my ROM which i have read is permanent safe mode and that i need to restore my efs. Sadly i dont think i salvaged enough, i made a EFS backup yesterday (sort of) before i started fiddling around to try and unlock my phone. i have the .img file and .tar file on my PC but i have read you need a gz file?
When making the backup i was on custom 4.3 ROM and im now on stock 4.3 rooted.
UPDATED
i have attempted to restore my efs using a the utility here http://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098
however i get this pop up and when i reboot its just stuck on the blue Samsung logo and wont boot into the rom
http://gyazo.com/e0f93bc00b9355d7e58712f5bd162e53
History of my actions
1) had working rom perfect - made efs backup using galaxasim unlock
2) IMEI corrupt from an update
3) did super wipe on phone and installed stock rom using ODIN, after update phone just got stuck on samsung logo
4) flashed this file which got my rom working again but of course i had a corrupt IMEI https://www.youtube.com/watch?v=xJMJLdzHaAY
5) restored EFS and now phone wont get past samsung logo again (tried clearing cache and wipe data, I also get this error when doing a full wipe from phil CWM [formatting /sd-ext unknown volume for path [/sd-ext]
any help?
ElimElim said:
hi all
after trying to unlock my s3 with constant roms and then imei problems it seems now i am at a dead end needing help
i tried to flash a custom rom and it didnt work.. my phone is at a complete dead end with the whole phone memory erased and im constantly getting message
error mounting /sdcard/.android secure. when doing factory data or clearing cache. the phone just boots to samsung galaxy s3 screen and all i can do is access CWM.
i just want to put stock rom and get it running for now, at the moment it wont mount the SD card for some reason even though my phone has no external sd its using the built in memory.
please help me
Click to expand...
Click to collapse
Have you tried to restore stock rom with ODIN?
gabyif said:
Have you tried to restore stock rom with ODIN?
Click to expand...
Click to collapse
edited op
bump desperate help needed.
ok guys after staring at a screen all day ive got it working
data, calls, imei all recognized after i copied my whole efs folder from backup into the new one
however i still have yellow writing? ive tried editing factorymode to OFF but its still there?
update: fixed it now
ElimElim said:
ok guys after staring at a screen all day ive got it working
data, calls, imei all recognized after i copied my whole efs folder from backup into the new one
however i still have yellow writing? ive tried editing factorymode to OFF but its still there?
update: fixed it now
Click to expand...
Click to collapse
Post how you did it anyway.
Choristav said:
Post how you did it anyway.
Click to expand...
Click to collapse
good point
very helpful page here http://zidroid.com/how-to-exit-factory-mode-for-samsung-galaxy-devices/

Categories

Resources