UPDATE EDIT: I have had some progress since my original post. Could you please read my latest posts, maybe you could help me out
Samsung S3 GT-I9300 purchased in the UK.
Its my sisters mobile and i think its soft bricked. She told me it just happened and she done nothing. I received the phone in stock condition.
The phone was orignally stuck solid on the first startup title screen and would not go any further. This is what i have done so far:
1. booted the phone into recovery mode which shows E:failed to mount /efs (invalid argument)
2. wiped cache partition
3. wiped data/factory reset
4. Installed Odin3-v3.04 and downloaded I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar
5. Connected phone to Odin and flashed the above .tar file which completed sucessfully.
The phone rebooted and it still got stuck on the first startup title screen.
I then looked for a different version and downloaded I9300XXEMF1_I9300EVREMF1_I9300BVEMF1_HOME.tar
this version also installed sucessfully onto the phone after repeating what i had previously done.
The phone reboots and now gets past the first title screen to the animated samsung logo but then keeps looping the animation.
The blue led in top left corner is on and is pulsing from dim to bright constantly while it loops.
Getting a little progress with the 2nd version i kept this on and patched CF-Auto-Root-m0-m0xx-gti9300.tar ontop of it.
Still the same looping when it gets to animated samsung logo
I dont know if this would of helped but i then tryed downloading the NV Generator to make a new IMEI file but cant get
the phone to respond to NV reader writer program.
Iv downloaded Adb and tryed to push the IMEI file onto the phone but it fails with error E: Signature Verification Failed
Im a beginner and this is the first time iv tryed to fix a phone and iv hit a brick wall and not sure now if im wasting my time.
can anyone help me get to the next stage?
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
JJEgan said:
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
I don't have a backed up EFS. its my sisters phone. with no backed up EFS is the phone unfixable then?
ardensedvirens said:
no backed up EFS is the phone unfixable then?
Click to expand...
Click to collapse
Correct, needs Service centre repair
Kalyan_121 said:
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
Click to expand...
Click to collapse
is cwm and twrp options in the recovery menu? where do I look to see?
the recovery menu only shows:
Android system recovery <3e>
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
sorry if this is not what you meant. im not sure what cwm and twrp is short for.
rootSU said:
Correct, needs Service centre repair
Click to expand...
Click to collapse
really? dam. how much would it cost to fix this problem?
JJEgan said:
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
ardensedvirens said:
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
Click to expand...
Click to collapse
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Glebun said:
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Click to expand...
Click to collapse
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
iv just flashed ODIN_CheckROM_V4_XXBLG8
it gives alot more options to fiddle around with. I think I could fix this phone to be honest if I keep looking into it.
OMG!! after installing the rom I just posted the phone has booted up and im in
I don't know what to do now.
is the efs fixed? should I make a backup?
how did this fix the phone?
ardensedvirens said:
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
Click to expand...
Click to collapse
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
ardensedvirens said:
is the efs fixed?
Click to expand...
Click to collapse
you tell us - is the IMEI back?
make ioudedi
Glebun said:
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
you tell us - is the IMEI back?
Click to expand...
Click to collapse
Ok sorry I didn't know, I just thought it was just a missing folder that could be copyed.
the phone has now booted up
[Resurrection Edition] CheckROM EvoHD™ V4 [ODIN ROM]
this is what I flashed and it seems to have fixed it?
can anyone explain what has happened, I would like to understand what this rom was able to do that the others I flashed before couldn't.
if it booted it doesn't mean that EFS is okay
Glebun said:
if it booted it doesn't mean that EFS is okay
Click to expand...
Click to collapse
do you know what I could do from here to fix the efs?
should I try and pull anything from the phone onto my computer now that its booted?
when I goto status it says IMEI unknown
I know my imei number is behind the battery, how do I register it?
the fact that it booted changes nothing.
you can't repair the EFS if you don't have a backup
what is EFS? is it a folder? a file?
can anyone else explain a little more?
it is a folder.
to explain a little more - you need a new motherboard because every EFS folder is device-specific
I cant get the phone to connect to my wifi. Kies is not picking up the phone either.
is there a way I can download apps to my pc and load them onto the phone? I would like to try and get root explorer installed to see if there is an efs folder.
i tried EFS PRO. it has generated an efs.img file, is it useful?
this is what i done to get it, im not sure if its correct. can anyone tell me?
i went into Backup and selected Device Filter: International Variants
i ticked the block device box and clicked the backup button.
the operation was successful and it created the zip file with the efs.img inside it.
i have pulled this zip from the phone using QtADB_0.8.1_
does anybody know if this file can be used to fix the problem? or has it made a backup of a corrupt efs folder?
Related
As the topic states, I am in a big need for some seriously help with my S3 and that ASAP!
I flashed the InsertCoin ROM for our lovely Galaxy S3 some days ago and the installation / flash procedure went fine, and today, I did an hell of a serious failed mistake..
The thing is that I played around with the application ES Filemanager (ticked ROOT access, ofc) and deleted every folder on internal SD card. And I was so stupid that I also tried to delete the folders above the SD card (where you can find folders like system, etc and the build.prop) and after that - my phone started to act strange and rebooted itself and that gived me some serious panic and my first thought was that the phone was killed for good. Well, it was bootable but the booting was failed when the screen arrived on launcher / home screen and everything was force closed etc etc.
My first solution was to re-flash stock, untouched Samsung firmware and that worked fine like butter. I also accessed stock recovery after this procedure to wipe data/factory reset and wipe cache, that worked fine too. But when booting the phone at last again - I got this weird picture on screen and my signal is killed (only Emergncy Mode-calls is possible), and I am in a panic at the moment because the Galaxy S3 is the only phone I have that supports micro-SIM cards..
Please, can someone help me ASAP - you guys would save my day! :/ see attached picture below for more information on my problem...
this thread any help to you, seems to be similar prob
http://forum.xda-developers.com/showthread.php?t=2071052
[email protected] said:
this thread any help to you, seems to be similar prob
http://forum.xda-developers.com/showthread.php?t=2071052
Click to expand...
Click to collapse
I didn't find any good solution at all :crying:
for solution I went to efs / factoryapp / factorymode and changed the text inside to ON from OFF)
Do you happen to have an EFS backup, perchance?
If everything in / was getting recursively deleted, then /efs (which would be before etc, alphabetically) would most likely have been hit also, IMO
EDIT: If it is your EFS, the log inside /efs will tell you if it's been regenerated (and if so, check your IMEI as if it's not correct, then it would explain your inability to connect to networks)
Please check your IMEI number. if it is starting from "00" than your IMEI number is screwed and you can fix that only if you have EFS folder backup...
qwerty12 said:
Do you happen to have an EFS backup, perchance?
If everything in / was getting recursively deleted, then /efs (which would be before etc, alphabetically) would most likely have been hit also, IMO
EDIT: If it is your EFS, the log inside /efs will tell you if it's been regenerated (and if so, check your IMEI as if it's not correct, then it would explain your inability to connect to networks)
Click to expand...
Click to collapse
No EFS backup, damn.. And the IMEI number is starting with 00, see quote below..
Chaitanyapatel8880 said:
Please check your IMEI number. if it is starting from "00" than your IMEI number is screwed and you can fix that only if you have EFS folder backup...
Click to expand...
Click to collapse
I just checked the IMEI number of my phone and it does start with 00.. Any solution to get everything back to stock or is my phone screwed for good?
If you have no backup, then the only way that I am aware of to get your IMEI back is to send it to Samsung :/
Sent from my GT-I9300 using Tapatalk 2
I think Samsung will deny me warranty rights because the flash counter on my S3 is over 20 and I don't know how-to reset it.. :/
Sent from my LT18i using xda app-developers app
Destroyedbeauty said:
I think Samsung will deny me warranty rights because the flash counter on my S3 is over 20 and I don't know how-to reset it.. :/
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Do you not think triangle away will work?
WTVTom said:
Do you not think triangle away will work?
Click to expand...
Click to collapse
Does that even work on the S3? It's not like it got any triangle thing to remove, haha..
Sent from my LT18i using xda app-developers app
Destroyedbeauty said:
Does that even work on the S3? It's not like it got any triangle thing to remove, haha..
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
The triangle will show in download mode.
Bx2
BenjaminX2 said:
The triangle will show in download mode.
Bx2
Click to expand...
Click to collapse
So, if I reset the counter to zero and re-flashing stock Samsung FW - I will get full warranty back so I can send it in for recovering my IMEI number and everything, right?
Sent from my LT18i using xda app-developers app
Destroyedbeauty said:
As the topic states, I am in a big need for some seriously help with my S3 and that ASAP!
I flashed the InsertCoin ROM for our lovely Galaxy S3 some days ago and the installation / flash procedure went fine, and today, I did an hell of a serious failed mistake..
The thing is that I played around with the application ES Filemanager (ticked ROOT access, ofc) and deleted every folder on internal SD card. And I was so stupid that I also tried to delete the folders above the SD card (where you can find folders like system, etc and the build.prop) and after that - my phone started to act strange and rebooted itself and that gived me some serious panic and my first thought was that the phone was killed for good. Well, it was bootable but the booting was failed when the screen arrived on launcher / home screen and everything was force closed etc etc.
My first solution was to re-flash stock, untouched Samsung firmware and that worked fine like butter. I also accessed stock recovery after this procedure to wipe data/factory reset and wipe cache, that worked fine too. But when booting the phone at last again - I got this weird picture on screen and my signal is killed (only Emergncy Mode-calls is possible), and I am in a panic at the moment because the Galaxy S3 is the only phone I have that supports micro-SIM cards..
Please, can someone help me ASAP - you guys would save my day! :/ see attached picture below for more information on my problem...
Click to expand...
Click to collapse
____________________________________________________________________________
Reflash ROM and Modem via ODIN then flash CWM recovery and Flash your new ROM, Wipe data and cache and Dalvik and then reboot and install Triangle Away and reset counter! Good Luck
bunglebp said:
____________________________________________________________________________
Reflash ROM and Modem via ODIN then flash CWM recovery and Flash your new ROM, Wipe data and cache and Dalvik and then reboot and install Triangle Away and reset counter! Good Luck
Click to expand...
Click to collapse
I don't know how that can make me get my IMEI number and network / cell access back :/ I am kinda stuck with no possibility to send text messages, call someone or anything :/
bunglebp said:
____________________________________________________________________________
Reflash ROM and Modem via ODIN then flash CWM recovery and Flash your new ROM, Wipe data and cache and Dalvik and then reboot and install Triangle Away and reset counter! Good Luck
Click to expand...
Click to collapse
Quick update..
It didn't work, so I am stuck right now with no other possibilites than reset flash counter and leave the phone for warranty..
I must have wiped the EFS folder in CWM not realising it's important. If I do a factory reset or wipe "data" in CWM, the phone IEMI code is lost and it only allows emergency calls. Only a restore from the image brings it back to a usable state.
I have a image backup, so I'm sort of ok. So it's running ok, but that means I cannot sell the phone off, as I cannot do a reset without bricking it (and I cannot delete accounts)
Is there anyway of recovering IEMI, NV_DATA.BIN?
I wouldn't be fiddling with this phone if I had enough RAM in the first place. I have tried QPST but I cannot communicate with the phone, it just says not found.
Is there any other way of copying NV_DATA.BIN modded to my IEMI to EFS folder?
Is it a simple fix?
Berties123 said:
I must have wiped the EFS folder in CWM not realising it's important. If I do a factory reset or wipe "data" in CWM, the phone IEMI code is lost and it only allows emergency calls. Only a restore from the image brings it back to a usable state.
I have a image backup, so I'm sort of ok. So it's running ok, but that means I cannot sell the phone off, as I cannot do a reset without bricking it (and I cannot delete accounts)
Is there anyway of recovering IEMI, NV_DATA.BIN?
I wouldn't be fiddling with this phone if I had enough RAM in the first place. I have tried QPST but I cannot communicate with the phone, it just says not found.
Is there any other way of copying NV_DATA.BIN modded to my IEMI to EFS folder?
Is it a simple fix?
Click to expand...
Click to collapse
Use galaxy toolbox to restore imei and search the thread how to use it.
will it recover iemi from a nv_data_bin that I don't have?
tried it, still does not work. EFS partition file is about 1MB when backed to micro sd card. Is this right?
does anyone have a backup of theirs and could they edit iemi for mine?
I've been having wifi problems too, it keeps on dropping out with the wifi address. This one of the problems with lost efs/iemi?
getting it looked at by phone shop, I've restored the image, done a factory reset, unrooted it, do I need to do binary counter reset?
IMEI partition is very small, that's right. On russian 4pda.ru some people repaired their IMEI by installing stock rom via odin. (that, wich comes with 4 files.)
I have downloaded the single file and repacked versions.
Which version of Odin should I use? I cannot get odin to communicate with the phone, is there another way of flashing the phone?
phone FIXED! Managed to unzip the repacked files, used odin 1.85, flashed the three files, rebooted, then reset to factory defaults, and can now dial out!
hi
Berties123 said:
I have downloaded the single file and repacked versions.
Which version of Odin should I use? I cannot get odin to communicate with the phone, is there another way of flashing the phone?
phone FIXED! Managed to unzip the repacked files, used odin 1.85, flashed the three files, rebooted, then reset to factory defaults, and can now dial out!
Click to expand...
Click to collapse
Hi, I've had the same problem, I want to install jelly bean ROM on my galaxy ace s5830i, but tried it before and I only read a forum about backing up efs folder afterwards, so it was too late! Now I have an imei number but the efs folder is empty, so there's no way of installing a ROM like jelly bean without being able to recover the imei number later, EVERY TIME I INSTALL JELLY BEAN IT KNOCKS OUT THE IMEI! Does anyone know how to recover the details in the efs folder if you have accidentally wiped them?
johnnyboy86 said:
Hi, I've had the same problem, I want to install jelly bean ROM on my galaxy ace s5830i, but tried it before and I only read a forum about backing up efs folder afterwards, so it was too late! Now I have an imei number but the efs folder is empty, so there's no way of installing a ROM like jelly bean without being able to recover the imei number later, EVERY TIME I INSTALL JELLY BEAN IT KNOCKS OUT THE IMEI! Does anyone know how to recover the details in the efs folder if you have accidentally wiped them?
Click to expand...
Click to collapse
1. You don't install Jelly Bean. You install themed Gingerbread ROM
2. You won't see anything in EFS folder ever. If you can't see anything in it, doesn't mean it's empty.
3. You didn't search correctly, answer is right here - http://forum.xda-developers.com/showthread.php?t=1968360
hi
iamareebjamal said:
1. You don't install Jelly Bean. You install themed Gingerbread ROM
2. You won't see anything in EFS folder ever. If you can't see anything in it, doesn't mean it's empty.
3. You didn't search correctly, answer is right here - http://forum.xda-developers.com/showthread.php?t=1968360
Click to expand...
Click to collapse
Yeah, I'm stuck!! I installed galaxy toolbox, made a backup of the efs, moved it to my computer! I took a screenshot, I've attached! but now I'm stuck on what to do next, this ain't exactly my neck of the woods, cheers!
johnnyboy86 said:
Yeah, I'm stuck!! I installed galaxy toolbox, made a backup of the efs, moved it to my computer! I took a screenshot, I've attached! but now I'm stuck on what to do next, this ain't exactly my neck of the woods, cheers!
Click to expand...
Click to collapse
You haven't read the guide correctly till now
Read it twice
Saw something about 0x80000?
And if you even read the replies there, your problem will be solved
And that ain't anybody's neck of wood until they try it for first time
iamareebjamal said:
You haven't read the guide correctly till now
Read it twice
Saw something about 0x80000?
And if you even read the replies there, your problem will be solved
And that ain't anybody's neck of wood until they try it for first time
Click to expand...
Click to collapse
Sorry, I meant to put in the reply that I wasn't sure where to put the 0x8000, but I'll read through the replies and see where I can get to! cheers!!
---------- Post added at 07:33 PM ---------- Previous post was at 06:55 PM ----------
johnnyboy86 said:
Sorry, I meant to put in the reply that I wasn't sure where to put the 0x8000, but I'll read through the replies and see where I can get to! cheers!!
Click to expand...
Click to collapse
Alright, yeah I worked it out, thanks! I've found the imei number in the program! in the post it says click on the number, I can't exactly click on it, do I highlight it and then save, I'm not sure what to do next!! I'm reading the comments but cnt find anything :/
I was running CyanogenMod 10.1 ROM with SiyahKernel v-1.9.1. My phone ran out of battery, so I went to charge it, I turned it on and it became stuck at the ''SAMSUNG S3 GT-I9300'' logo. I left it there for 30 min. nothing happened, I took the battery out and the same thing. So I decided to flash again the Stock Firmware with ODIN (obiously ), It flashed it with no problems, but it is the same. I tried so many things and searched in so many posts and nothing helped me. Sorry for writing long and for bothering! Thx!
Plenty of reasons why your phone won't boot, running the battery until shut down increases the risk of corrupting files or even partition. If the stock rom flashed via odin successfully then there should be nothing wrong, you did factory reset and clear caches before you booted, right?
factory reset from recovery
boomboomer said:
Plenty of reasons why your phone won't boot, running the battery until shut down increases the risk of corrupting files or even partition. If the stock rom flashed via odin successfully then there should be nothing wrong, you did factory reset and clear caches before you booted, right?
Click to expand...
Click to collapse
Yeah I did it nothing happened... But when I put it into Recovery its says E:failed to mount /efs (Invalid argument) it has something to do with it?
yes. restore your backed up EFS folder.
Or if you didn't back it up, then send it to service. Use search for loads of similar posts.
Glebun said:
yes. restore your backed up EFS folder.
Or if you didn't back it up, then send it to service. Use search for loads of similar posts.
Click to expand...
Click to collapse
Oh god so there is no way I can fix it? Here the Samsung service is soooo expensive :crying:
If you didn't read the instructions that said you should back up the folder before doing anything, then no
Glebun said:
If you didn't read the instructions that said you should back up the folder before doing anything, then no
Click to expand...
Click to collapse
I just got an EFS file that I got from my father's phone, is there a way to take out the file that contains his IMEI and recover mine with other things? It is possible?
juanca530 said:
I just got an EFS file that I got from my father's phone, is there a way to take out the file that contains his IMEI and recover mine with other things? It is possible?
Click to expand...
Click to collapse
NO
jje
juanca530 said:
I just got an EFS file that I got from my father's phone, is there a way to take out the file that contains his IMEI and recover mine with other things? It is possible?
Click to expand...
Click to collapse
maybe, but you won't get any support on xda about that, because it can be used for illegal purposes
Glebun said:
maybe, but you won't get any support on xda about that, because it can be used for illegal purposes
Click to expand...
Click to collapse
Thx for the help guys! I'll keep investigating.
Guys. i got some ladys number last night.
This morning I was going to do a NANDROID backup before i rooted. I'm on stock. with a secure boot image
so using the S3 toolkit I chose the backup option flashed an insecure boot image.
From now on my phone is stuck on the samsung galaxy siii screen with a ! in the corner, but it wont go pass this.
I want to get back into my stock rom to get this number before i start messing around again
anyone got any ideas?
I've tried flashing recovery/stock-bll3 in odin
cramhead said:
Guys. i got some ladys number last night.
This morning I was going to do a NANDROID backup before i rooted. I'm on stock. with a secure boot image
so using the S3 toolkit I chose the backup option flashed an insecure boot image.
From now on my phone is stuck on the samsung galaxy siii screen with a ! in the corner, but it wont go pass this.
I want to get back into my stock rom to get this number before i start messing around again
anyone got any ideas?
I've tried flashing recovery/stock-bll3 in odin
Click to expand...
Click to collapse
stock-bll3?
Whats that? What phone have you got? you dont need to flash an insecure boot image on the i9300
rootSU said:
stock-bll3?
Whats that? What phone have you got? you dont need to flash an insecure boot image on the i9300
Click to expand...
Click to collapse
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
cramhead said:
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
Click to expand...
Click to collapse
if i re-installed stock would all my contacts still be stored as long as i didnt wipe the partition/catch etc?
cramhead said:
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
Click to expand...
Click to collapse
Thats for a different phone! i9305 is not the same as the i9300
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
cramhead said:
if i re-installed stock would all my contacts still be stored as long as i didnt wipe the partition/catch etc?
Click to expand...
Click to collapse
If you flash a genuine i9300 rom from sammobile.com to as close as possible as what was on it before without wiping, you may be OK...
Some report sometimes it wipes but others not.
If you flash a custom recovery (Philz / CWM / TWRP) for the i9300, you can take a nandroid backup then if the worst comes to the worst, you can use a nandroid backup explorer to extract the data.
Here's a tip for future... Take a number and say "hey let me ring that quickly to test it", then it appears on your mobile phone bill / history
Or better yet, use google contacts
Caveman method write it on the back of your hand .
jje
rootSU said:
Thats for a different phone! i9305 is not the same as the i9300
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
If you flash a genuine i9300 rom from sammobile.com to as close as possible as what was on it before without wiping, you may be OK...
Some report sometimes it wipes but others not.
If you flash a custom recovery (Philz / CWM / TWRP) for the i9300, you can take a nandroid backup then if the worst comes to the worst, you can use a nandroid backup explorer to extract the data.
Here's a tip for future... Take a number and say "hey let me ring that quickly to test it", then it appears on your mobile phone bill / history
Or better yet, use google contacts
Click to expand...
Click to collapse
went back to stock and the NUMBER IS STILL THERE!!!! YESSSSSS Sexy time
cheers m8 x
Hi,
I have got an Galaxy S3 from a friend. It was stuck on the Samsung animation and it would not boot.
Animation - black screen - animation.
I thought well, its gonna be a simple matter of reflashing the os with odin. But I was wrong.
I tried a buch of Jelly Bean Versions and even clockworkmod recovery and CM10.1. It still refused to boot.
So I reflashed stock recovery and took a closer look. In stock recovery i spotted the line "failed to mount /efs partition".
A quick research confirmed my first thought. It refuesed to boot because the imei partition is damaged.
Luckily i found this useful forum thread here http://forum.xda-developers.com/showthread.php?t=2403903 i tried the ICS rom and it booted.
That is the point i am at right now. And I could need some help :good:
IMEI is now null/null *lol* and baseband is unknown, so there is certainly something going on there.
The phone had no custom binaries so there is no /efs backup i would know of. Oh and there is another little problem, the phone somehow does not have a sticker below the battery (dont ask me why. I do not know) which could tell me the imei and my mate does not have a receipt or the box to tell me the right imei.
I think it would be a good idea to try to backup the damaged partition and try to extract the data from it and then format it and merge the files with a "clean /efs folder" somehow like this http://forum.xda-developers.com/showthread.php?t=1264021 here.
Or is there a "repair partition" function like scandisk for windwos included in android to take care of that?
If anybody has any thoughts on this please let me know!
Thanks a lot!
playitlouder said:
Hi,
I have got an Galaxy S3 from a friend. It was stuck on the Samsung animation and it would not boot.
Animation - black screen - animation.
I thought well, its gonna be a simple matter of reflashing the os with odin. But I was wrong.
I tried a buch of Jelly Bean Versions and even clockworkmod recovery and CM10.1. It still refused to boot.
So I reflashed stock recovery and took a closer look. In stock recovery i spotted the line "failed to mount /efs partition".
A quick research confirmed my first thought. It refuesed to boot because the imei partition is damaged.
Luckily i found this useful forum thread here http://forum.xda-developers.com/showthread.php?t=2403903 i tried the ICS rom and it booted.
That is the point i am at right now. And I could need some help :good:
IMEI is now null/null *lol* and baseband is unknown, so there is certainly something going on there.
The phone had no custom binaries so there is no /efs backup i would know of. Oh and there is another little problem, the phone somehow does not have a sticker below the battery (dont ask me why. I do not know) which could tell me the imei and my mate does not have a receipt or the box to tell me the right imei.
I think it would be a good idea to try to backup the damaged partition and try to extract the data from it and then format it and merge the files with a "clean /efs folder" somehow like this http://forum.xda-developers.com/showthread.php?t=1264021 here.
Or is there a "repair partition" function like scandisk for windwos included in android to take care of that?
If anybody has any thoughts on this please let me know!
Thanks a lot!
Click to expand...
Click to collapse
Where are you?
Some people have had luck with efs restore while going from a lower android version to higher version
sent from the state where Marijuana is NOT illegal !
playitlouder said:
Oh and there is another little problem, the phone somehow does not have a sticker below the battery (dont ask me why. I do not know) which could tell me the imei and my mate does not have a receipt or the box to tell me the right imei.
Click to expand...
Click to collapse
Hmm, very strange indeed. A repair shop won't even be able to help you with that phone.
it is possible fixing efs partition with dd backup restore command for dev/mmcblk07 from another i9300. but you need an efs backup. if you have a backup i can send an empty backup from mmcblk07. efs will mount success
Sent from my GT-I9300 using xda app-developers app
zuluman said:
it is possible fixing efs partition with dd backup restore command for dev/mmcblk07 from another i9300. but you need an efs backup. if you have a backup i can send an empty backup from mmcblk07. efs will mount success
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
In the I9300 efs is partition number 3, 7 is the radio.
wangdaning said:
In the I9300 efs is partition number 3, 7 is the radio.
Click to expand...
Click to collapse
you are right sorry. alot of think of my mind
I tried flashing XXEMC2_I9300 but no luck it doesn't want to boot
Going back to ICS again now. (and going to root it).
Is there a command to force android to mount the partition even tho its damaged? (trying to copy data from it)
(Or a command to get the data bit by bit to seek for something on the pc maybe...)
With a "clear" image of /efs could I simply enter an imei from an old Samsung Phone(nobody is ever going to use again) ?
playitlouder said:
I tried flashing XXEMC2_I9300 but no luck it doesn't want to boot
Going back to ICS again now. (and going to root it).
Is there a command to force android to mount the partition even tho its damaged? (trying to copy data from it)
(Or a command to get the data bit by bit to seek for something on the pc maybe...)
With a "clear" image of /efs could I simply enter an imei from an old Samsung Phone(nobody is ever going to use again) ?
Click to expand...
Click to collapse
Flash omega Rom, you will find the baseband has been upgraded to XXEMG5, as such you can only flash roms with new base band you cannot go back even with odin, thats your problem, hope this helps !
swukjay said:
Flash omega Rom, you will find the baseband has been upgraded, as such you can only flash roms with new base band you cannot go back even with odin, thats your problem, hope this helps !
Click to expand...
Click to collapse
Youc an flash any rom so long as you flash mg2 or mg4 baseband again afterwards. These are available in:
general > sticky roll-up thread > imei / efs - know this stuff
I tried CM 10.1 and it wouldn't boot.
Omega seems CM based, so I don't get why it should boot.
And in recovery there is a red line of text saying E: Failed to mount /efs (invalid argument).
I dont think this is just a matter of flashing another rom. Or am I wrong?
playitlouder said:
I tried CM 10.1 and it wouldn't boot.
Omega seems CM based, so I don't get why it should boot.
And in recovery there is a red line of text saying E: Failed to mount /efs (invalid argument).
I dont think this is just a matter of flashing another rom. Or am I wrong?
Click to expand...
Click to collapse
Omega is Sammy based ROM not cm based !
Also there option to remount efs in recovery.
sent from the state where Marijuana is NOT illegal !
playitlouder said:
I tried CM 10.1 and it wouldn't boot.
Omega seems CM based, so I don't get why it should boot.
And in recovery there is a red line of text saying E: Failed to mount /efs (invalid argument).
I dont think this is just a matter of flashing another rom. Or am I wrong?
Click to expand...
Click to collapse
Omega is stock sammy based so should work !
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
chris_marsh said:
Omega is Sammy based ROM not cm based !
Also there option to remount efs in recovery.
sent from the state where Marijuana is NOT illegal !
Click to expand...
Click to collapse
Thanks mate, great minds think alike that's why i suggested omega, its a bloody good ROM too !
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
playitlouder said:
I tried CM 10.1 and it wouldn't boot.
Omega seems CM based, so I don't get why it should boot.
And in recovery there is a red line of text saying E: Failed to mount /efs (invalid argument).
I dont think this is just a matter of flashing another rom. Or am I wrong?
Click to expand...
Click to collapse
Look mate it cannot mount and write to efs because the partition is now in a different file format, it changes the entire format of efs which is why its failing, flash the omega rom ! you have asked for help and we have given you the solution, if that dont work come back and tell us
So im going to flash that rom now. Correct?
http://forum.xda-developers.com/showthread.php?t=1720628&highlight=omega
playitlouder said:
So im going to flash that rom now. Correct?
http://forum.xda-developers.com/showthread.php?t=1720628&highlight=omega
Click to expand...
Click to collapse
Not that one. They said Omega is Sammy based but they forget there are 2 omega roms. That is teh AOKP based one (Similar to CM). You want the Samsung based one. Its usually on page 1 of "Android development"
playitlouder said:
So im going to flash that rom now. Correct?
http://forum.xda-developers.com/showthread.php?t=1720628&highlight=omega
Click to expand...
Click to collapse
no this one
http://forum.xda-developers.com/showthread.php?t=1663656 xxemg5
link to download centre and rom http://omega-roms.net/blog/?page_id=723
playitlouder said:
So im going to flash that rom now. Correct?
http://forum.xda-developers.com/showthread.php?t=1720628&highlight=omega
Click to expand...
Click to collapse
Not that . this one : http://forum.xda-developers.com/showthread.php?t=1663656
sent from the state where Marijuana is NOT illegal !
The omega rom is great and should get you up and running , once that is done and it boots and is working boot back into recovery and use the installer again to back up the efs, then you should be flying job done simples !
Installed Omega, and now I'm stuck on the first Samsung screen again.
I still think there is an EFS problem...
EDIT: Installed it again. Now I get blue LED and spinning omega Logo. Its stuck there...
playitlouder said:
Installed Omega, and now I'm stuck on the first Samsung screen again.
I still think there is an EFS problem...
EDIT: Installed it again. Now I get blue LED and spinning omega Logo. Its stuck there...
Click to expand...
Click to collapse
Boot into recovery and wip all the partions, system preload etc all of em then try again to install, I have seen this happen before when it wouldnt boot as a wipe wasn't performed before install, then get back to us
Also what recovery are you using?