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
Related
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
mad_max911 said:
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
Click to expand...
Click to collapse
CWM version has changed in the CF-root kernal. Many times the backup done with old CWM is not properly recoverable.
Try wiping the data/cache and dalvik cache and recovering nandroid backup.IF this doesnt work , then Best option would be to get your nandroid backup to PC , format the system , flash a stock ROM,root it and try getting to get the backup working again.
Hope this helps!
I think ICS has a different bootloader to that of GB? If so, flash original bootloader from Intratech thread post #2 with Odin in PDA or Bootloader section:
http://forum.xda-developers.com/showthread.php?t=1075278
Then try restore nan-droid backup again.
Maybe I'm wrong, but you won't hurt anything if you follow his Odin flashing instructions.
Sent from my GT-I9100 using xda premium
Interesting... Ill try some off suggestions later. Just to clarify little more: after boot loop i flash kernel trough ODIN, (syah kernel [same kernel that is in recovery]) and everything works (i boot into previously recover system and all fine...), then going into recovery once again after restoring problem occurs again. So problem is not in CWM as kernel itself contains it...
So, maybe better question would be what part of android system does CWM NOT backup... For example, i now that it does not backup camera firmware... What else? It would be great if this backup/recovery would be more complete (including all software/flash/drivers parts of android system...).
Best regards!
Its simple you require the version of clockwork mode recovery on your phone that you used for the backup to recover .
Caught me out last week and took an age to realize the solution .
jje
Yes, backup was created witth syah 2.6.6 and its CWM version... So, i flashed that kernel trough ODIN, booted CWM and recover- stuck at boot once again...
Sent from my GT-I9100 using XDA App
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.
today my battery went down to zero and then my phone stuck on the menu screen.
i rebooted but then my phone got stucked on the samsung galaxy 3 logo.
i tryed to wipe files and catche but it didnt helped,
i tryed to install the ROM again but it didnt helped...
i can get to the recovery and download mode, but my phone still stuck on the stuped logo...
what to do?
sry if i have spelling mistakes...
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
thx but...
boomboomer said:
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
sorry but what "flash a stock firmware means?"
how do i do that?
do you have links?
ty!
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
ok so i should download the firmware achieve from my area
then i just flash original ROM?
this is the instruction page: http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
then im done?
i need to change the recovery thing too?
or i can just start from procces 4?
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
orial10 said:
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
Click to expand...
Click to collapse
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
dxppxd said:
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
Click to expand...
Click to collapse
can you explain or give me some links how to do that?
orial10 said:
can you explain or give me some links how to do that?
Click to expand...
Click to collapse
I mean, go to the stickies in the general section and read. They're there for a reason, including steps before rooting, flashing, information on the efs partition, and pretty much everything else you could have done to avoid the situation you're facing right now.
Hi
I reccently bought i9300 ( hongkong ) and it came with 4.3, i tried rooting it with CF-Root, The process itself completes with no problem but when i open SuperSu, It asks to update binaries but when i do it fails.
All of the fellow xda helpers have suggested to install CWM and than flash Update SuperSU ***.zip from chainfire, I did that as well ( i flashed the latest zip) But the problem is there.
Can anybody help me with that?
The CF-ROOT and flashable supersu i have flashed are:
UPDATE-SuperSU-v1.91
UPDATE-SuperSU-v1.86
UPDATE-SuperSU-v1.10
CF-Auto-Root-m0-m0xx-gti9300
CF-Root-SGS3-v6.4
Now as i am not rooted so i can't backup the EFS (i don't want to take the risk of loosing my IMEI) and flash stock 4.1.2.
-----------------------------
Here are the details of my phone:
Model no: i9300
Android version: 4.3
Baseband: I9300XXUGNA8
Kernel: 3.0.31-i902166 [email protected]#1
Build no: JSS15J.I9300ZSUBNB1
------------------------------
Thanks
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
MD500 said:
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
Click to expand...
Click to collapse
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
predator_b4u said:
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
Click to expand...
Click to collapse
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
tallman43 said:
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
Click to expand...
Click to collapse
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
predator_b4u said:
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
Click to expand...
Click to collapse
If done properly then yes also I would also suggest making another backup with PhilZ recovery there is a option in settings to do that ( you can never have too many backups) also if you want you can do a full nandroid backup which will restore your phone to how it was before you flashed anything.(but remember nandroid won't backup efs you have to do that separately)
For any fellow xdaz who are seeking help in the same case as mine, Let me update on what i did and what went wrong (although i am still not upto the rooting part)
so as i was on 4.3 ( I9300XXUGNA8)- The rom won't let me root, whatever i did, and i am talking about clearing cache, dalvik, cf-root, superSU update, clearing all superSU app and reinstalling via market and odin.
Than i thought i would ditch the rom and maybe downgrade ( for me that was the wrong idea )
along the way ( as suggested by " tallman43 " i did install PHILZ and did custom backup of efs and i made around 4-5 backups, Big thanks for the awesome suggestion ....i suggest you do the same, as trust me i later found out that 1-2 backups have corrupted files ( i don't know why).
i also downloaded neat rom and in that Aroma installer (rom installer) there was an option for efs backup as well, so i did that and installed that rom. Rom installed without any problem, root was also working fine, i personally love the rom but i have to give my phone to someone and i was hoping for total stock whereas in neat rom there are tags here and there, i would love to have em but as i said earlier...
i downloaded Stock 4.1.2 (I9300OZSEMK2) -- flashed it, flashed went fine but now i got 0000 as my imei, i tried restoring through philz but nothing happened
i restored previously made backup of my old 4.3 but now the imei was displaying " NULL "
finally i stopped there and searched the forums and read through many similar problems, i downloaded 4.3 (I9300XXUGNA8) from sam mobile , flashed it and voila the imei and network is back.
I am not sure what fixed the imei and why was it giving problems on 4.1.2 but i am happy with the results.
I will update for the rooting part and that would be my next step.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
duoxx said:
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
Click to expand...
Click to collapse
If you want only to flash a custom rom then you do not need to root custom roms come already rooted (alot of people make this mistake )..Just flash a custom recovery with Odin then follow the procedure in the stickies to flash a custom rom.
Hi All
My phone is now stuck at the samsung logo when booting. I have done everything possible
1. Factory reset.
2. Wipe everything, and install new ROM
3. Use ODIN to flash new stock ROM
4. Lots of nandroid restore with different ROMs
etc
I have taken it to the service centre, and I was informed that the mother board is faulty. But he also told me warranty was void as the flash counter was incremented.
I cannot install triangle away as i cannot boot the phone. My phone works perfectly otherwise in recovery and download mode.
Is there any way to reset the flash counter from the recovery mode so that I can claim the warranty.
Thanks in advance.
If you've got an efs backup, go ahead and try a rescue firmware (multiple files, and pit, + repartition checked in odin).
I the efs gets messed up, restore the backup.
If that fails, game over, faulty unflashable motherboard.
dxppxd said:
If you've got an efs backup, go ahead and try a rescue firmware (multiple files, and pit, + repartition checked in odin).
I the efs gets messed up, restore the backup.
If that fails, game over, faulty unflashable motherboard.
Click to expand...
Click to collapse
thanks for the reply, sorry i've replied late, was travelling.
with so many guides around, i dont want to mess up by following some wrong guide.
please can you post a link that i can follow.. tia.
btw i have an efs backup, though not in the nandroid format. i have it as a file named efs_04Jan2014-1105.tar.gz.
how to restore it?, i guess efs is indeed messed up when i flashed the stock 4.3 rom.