I recently tried to downgrade my Galaxy S3 from Jelly Bean 4.1.2 to ICS 4.04 using Odin and a ROM file downloaded from Sammobile.
The installation was succesful and after doing a factory reset and clearing cache the phone booted up ok. It connected to my network provider for several seconds and then disconnected.
After several attempts at this process using different files, I noticed that the IMEI of my phone was no longer correct. At this point I thought I had bricked my phone by somehow corrupting the IMEI.
In an attempt to put it right, I reloaded Jelly Bean 4.1.2 and my phone now works fine again. Please can someone advise what I am doing wrong with this process and why the IMEI gets corrupted as this is obviously why the network rejects my phone when I install ICS.
If you would look here: http://forum.xda-developers.com/galaxy-s3/general/ref-galaxy-s3-modem-radio-collection-t1740061 you will found this link for ICS ROMs: https://www.wuala.com/UpInTheAir/SGS3/Modems/I9300/ICS/?key=n0KVwtIMZPE8 . From here, select CWM folder if you want to flash the modem via recovery, or the Odin one if you want to flash it with Odin. Choone one of the file, download it, and then flash it via the method you want.
QuickQuestion: Why would you wanna use ICS when it has been released 4.3 for our device, and 4.4 it is said to be released in the following weeks (Hope so! ). If you want, you can answer, if not, it'ss not a big problem
Thanks for the reply. Is this the reason my IMEI is corrupted when I flash a PDA from Sammobile? I am new to using Odin etc and followed the instructions on the website.
There are some features I liked in ICS that were removed in Jelly Bean, such as direct access to words in the custom dictionary and the 3 x 4 keypad that was removed in 4.3. I already downgraded from 4.3 to 4.1.2 but wanted to try ICS 4.04. So far I can install it but cannot get a network connection for more than a few seconds.
#EDIT: After further research this problem appears to be an issue with the phone's EFS data. I have now used EFS Professional to back up this important area. What I don't know is can I restore this backed up EFS data to correct the problem I'm having when I downgrade Jelly Bean 4.1.2 to ICS 4.04?
andyb1712 said:
Thanks for the reply. Is this the reason my IMEI is corrupted when I flash a PDA from Sammobile? I am new to using Odin etc and followed the instructions on the website.
There are some features I liked in ICS that were removed in Jelly Bean, such as direct access to words in the custom dictionary and the 3 x 4 keypad that was removed in 4.3. I already downgraded from 4.3 to 4.1.2 but wanted to try ICS 4.04. So far I can install it but cannot get a network connection for more than a few seconds.
#EDIT: After further research this problem appears to be an issue with the phone's EFS data. I have now used EFS Professional to back up this important area. What I don't know is can I restore this backed up EFS data to correct the problem I'm having when I downgrade Jelly Bean 4.1.2 to ICS 4.04?
Click to expand...
Click to collapse
If you have a 16GB s3, u might want to keep JB, 16GB ICS S3 has the possibility for sudden death. But, i too am considering going back to ICS, Jellybean is a joke, it lags way more than ICS does. Trying to force the system to constantly render at 60FPS is hardware demanding and was probably a temporary approach. Its unfortunate that ICS ROMS are no longer available for download. Also, i doubt kitkat would be released for our phone.
My S3 is 16Gb and was originally shipped with Jelly Bean. I watched a Youtube video comparing ICS and Jelly Bean and ICS was faster responding in virtually every test, despite the guy doing it being pro Jelly Bean.
I don't know much about the 'sudden death' problem with ICS on 16Gb models but from what little I've read, I thought this was more of a hardware issue due to defective memory chips and/or main boards?
My S3 updated to Jelly Bean 4.3 last December and I wasn't happy because they had removed the 3x4 Samsung keypad that I like to use. I tried a number of different keypads from Play Store but in the end decided to downgrade to 4.1.2, which went without a hitch.
My attempts to do the same with ICS 4.04 did not go so well and I'm still not sure why the IMEI was corrupted or even more surprising, that it was corrected when I re flashed 4.1.2
andyb1712 said:
My S3 is 16Gb and was originally shipped with Jelly Bean. I watched a Youtube video comparing ICS and Jelly Bean and ICS was faster responding in virtually every test, despite the guy doing it being pro Jelly Bean.
I don't know much about the 'sudden death' problem with ICS on 16Gb models but from what little I've read, I thought this was more of a hardware issue due to defective memory chips and/or main boards?
My S3 updated to Jelly Bean 4.3 last December and I wasn't happy because they had removed the 3x4 Samsung keypad that I like to use. I tried a number of different keypads from Play Store but in the end decided to downgrade to 4.1.2, which went without a hitch.
My attempts to do the same with ICS 4.04 did not go so well and I'm still not sure why the IMEI was corrupted or even more surprising, that it was corrected when I re flashed 4.1.2
Click to expand...
Click to collapse
Not sure exactly how the sudden death works, i just know it affects 16GB s3 variants. I know the video you are referring to, i watched the exact same one. I think most people got caught up in the hype of JB and forgot how good ICS was.
Havoc-X said:
Not sure exactly how the sudden death works, i just know it affects 16GB s3 variants. I know the video you are referring to, i watched the exact same one. I think most people got caught up in the hype of JB and forgot how good ICS was.
Click to expand...
Click to collapse
The Youtube video made me laugh as it was supposed to encourage you to want the Jelly Bean upgrade, when all it did was make me want to run ICS even more! I tried a friend's Galaxy S2 with ICS the other day and it was smoother and faster responding than my S3.
I hope to have another go at getting it working but also I am concerned I probably came close to bricking my handset last time because I do not know enough about the process. This wouldn't be good as I still have another year on my network contract to go.
Do post here if you succeed in downgrading to 4.0.4 as I am also looking for it but it's not working
And best of luck
Unless you have a backup of your efs folder, from before firmware EMG4 then you cannot downgrade.
EFS format was changed at EMG4 to v2, earlier roms are incompatible with v2 and later roms incompatible with v1 so IMEI will be corrupt.
Sent from my GT-I9300 using Tapatalk
Thanks for the info.
My S3 was shipped with EMG4, so unfortunately I don't have any efs data that I can use with earlier ICS firmwares. I was trying in vain to load BLG8 but it just resulted in a corrupted IMEI and no network.
Unless there is some way of converting saved v2 efs data to the earlier format, then I will have to stick with the Android version I have.
Why are you not trying 4.3 or custom rom mate? My god if your phone is giving u problem u should try to tame it. Very smooth, the nb6 firmware. Or at least let yourself try a custom rom for instance temasek.
Sent from my GT-I9300 using XDA Premium 4 mobile app
I have tried the Official Samsung 4.3 release but didn't like that they removed the 3x4 Samsung Keypad, which I prefer to use. I've tried custom firmwares on my old phone (Galaxy Ace) but never had much success with installing them or getting things to work properly after.
My S3 is still under contract for another year and my skills in this area of modifying are beginner level at best, so I plan to do a lot more reading on here and a lot less messing around with the phone firmware until I know more about it.
andyb1712 said:
I have tried the Official Samsung 4.3 release but didn't like that they removed the 3x4 Samsung Keypad, which I prefer to use. I've tried custom firmwares on my old phone (Galaxy Ace) but never had much success with installing them or getting things to work properly after.
My S3 is still under contract for another year and my skills in this area of modifying are beginner level at best, so I plan to do a lot more reading on here and a lot less messing around with the phone firmware until I know more about it.
Click to expand...
Click to collapse
Your phone lag is because of Samsung bloatwares, get rid of it and you would be fine. Temporarily suggestions would be hang on 4.12 and try greenify. U don't need root but root would give you he best out of it. Look up cf autoroot and begin your journey.
:thumbup:
Sent from my GT-I9300 using XDA Premium 4 mobile app
First, I have a Galaxy S4 i9505 (4G), the problem does not affect my device, but the device's my cousin who is a Samsung Galaxy S4 i9500 (3G).
He recently purchased the unit from another person, the unit worked well, but had a small defect in the charging connector ...
He asked me to sell one of my cases and battery why his battery was apparently bad, why was not possible give loads on the battery, I managed to solve this problem.
The problem came when he asked me to update the device to Android 4.4.2 KitKat by several improvements, I downloaded the latest firmware available at SamMobile site and after that did the flash using Odin.
Knox had in 0x1 (the unit had been modified) and I read on some forums that night, that when doing upgrade directly from 4.2.2 version, especially XXUBMGA the EFS partition changes shape, thus having little network problem and signal.
Link : http://www.grupoandroid.com/topic/83400-modem-mg9-y-posteriores-modifican-la-efs/
My questions are, it is possible to resolve this situation? I read previously that the IMEI is restored from a backup made previously it is possible to recover the network signal, but made no backup of EFS ....
I also read a long time ago that it is impossible to downgrade to ROM's with lower versions if there Knox installed.
I did the update of Android 4.2.2 to 4.4.2 using Odin.
If possible downgrade, any of you can share the ROM XXUBMGA 4.2.2 for S4 i9500? Or tell me some possible solution installing another ROM / modem?
I am currently trying different modems and using the OmegaROM in my cousin's S4.
Hi.
EDIT: My phone is a GT-I9300 bought in Denmark (So I guess International).
So yesterday I installed this custom rom from Android 4.3 to Unofficial Cyanogenmod 12.1 (Here is the article: http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864). I got it installed with no problems but then I discovered that I had no 3G (data connection). My IMEI and APN was fine and it could recognize my carrier (Telenor Denmark). I tried installing more than 5 different flashed modems but with no luck. So, today I installed the stock Android 4.1.2 official ROM and the 3G was working perfectly again. I then tried installing CM 12.1 again, but the same error occurred. I have no problems making calls and sending text messages, and WIFI works too.
Could someone lead me in the right direction to solving this error?
Thank you in advance.
Andreas B. Ostergaard
If you had official 4.3 in the beginning there is no way you can get a signal or 3g if you go back 4.1.2 except somewhere in the past you restored your old 4.1.2 efs backup. If you have signal in 4.1.2 this means you still have efs v1. Since cm12 doesnt change your efs or modem you may still have network. Your 3g problem may be efs v1. Install official 4.3 first and update your efs to v2 then install a clean cm12 and try again.
thewalekk said:
If you had official 4.3 in the beginning there is no way you can get a signal or 3g if you go back 4.1.2 except somewhere in the past you restored your old 4.1.2 efs backup. If you have signal in 4.1.2 this means you still have efs v1. Since cm12 doesnt change your efs or modem you may still have network. Your 3g problem may be efs v1. Install official 4.3 first and update your efs to v2 then install a clean cm12 and try again.
Click to expand...
Click to collapse
Hi. Thanks for your answer.
I know this is a stupid question, but how do I update my EFS?
Thank you.
Andreas.
If you install official 4.3 through odin, it will update automaticly.
thewalekk said:
If you install official 4.3 through odin, it will update automaticly.
Click to expand...
Click to collapse
Okay but then I don't really understand because I have already updated once to 4.3 OTA (or via Kies maybe) before I began installing custom roms. Shouldn't that be the same as using Odin?
Best regards.
Andreas.
I never updated via ota or kies before and never even used kies before (no needed). Also I use my s3 rooted since day one. So maybe (i say maybe because i really dont know) ota updates might keep your efs unupdated. (Since it is an update not the whole package).
Download an official 4.3 from sammobile.com and try and see. (Nothing to lose anyway)
---------- Post added at 09:22 PM ---------- Previous post was at 08:59 PM ----------
https://www.dropbox.com/s/qzgn1abhr4qcmls/Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3.zip?dl=0
https://www.dropbox.com/s/f1zbm0tvsvh5ww5/MegaWipe_-_GS3.zip?dl=0
And also these are the cleaning scripts for s3. They will wipe clean your entire phone even the system and any kernel leftovers. Use them before installing any custom roms because cm and sammy roms are completly different roms and any leftovers can make problems to your system..
@AndreasX12: Failing 3g-access has nothing to do with IMEI/efs-issues, but may be a CM-issue. So, if you've still your correct IMEI and network access with 4.3-firmware, (backup your efs-data and the whole system and) try simply another AOSP-ROM, Omni or Euphoria fe.
Recommended updating path from stock 4.3 leads through 10.2, 11 and ad last 12.1.
If you have stock 4.3 download stable cm10.2 and flash it through recovery twice and reboot. You can skip cm11 than and flash cm 12 or cm12.1.
Cm10.2 is the first one cyanogenmod which change partition layout a bit.
Converting between efs 1 and efs 2 is possible and recommended on stock firmwares by flashing corresponding modem version by Odin. It also have place while flashing whole rom through Kies, Odin or Heimdall.
To omit future 3g errors flash roms without sim card onboard.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Thank you all for your answers.
Special thanks to rp158. I have installed OmniROM instead so it was a problem with the CM12.1 unofficial build.
Best regards,
Andreas.
Recently, I have a rooted Note 2 , which is the phone became not registered on network after updating 5.1.1.
I've returned to 4.1.2 for flashing Ariza Patch and BusyBox but nothing seems to work.
I did flash GT-N7100 Model ND3 for fixing it and I've tried a few other sims from different network, but it doesn't work either
This is the first time I've used Android OS so that it's little bit difficult for newbie as me
Anyone can solve it? Just help me
Thank you guys so muchhh!
Check you IMEI in device settings. This sometimes can be wiped out by flashing roms, that is the reason it is posted to back up your efs folder. Without a backup you may end up having to send it in for a new board.
Hi xda
I am new to this site, so sorry in advance if this thread is posted in the wrong section of the forum. Please let me know if Im doing something incorrect.
Anyways, my problem is, that I have two SGS3's both flashed to cm-13.0-20160217-NIGHTLY-i9300 (older versions have been tried out as well), where one of them can't make or recieve calls. Everything else works on it - send and recieve texts, mobile data etc. (the IMEI and serial number are both original and intact). Both the phones were originally running the Android Jellybean 4.3 Nordic version (I9300XXUGND5_NEEGND1_Nordic_4.3), and both were flashed using twrp 3.0.0.1 (and running GAPPS 6.0 pico).
I find it strange, that the phone is able to make and recieve texts and access the mobile network, while not being able to make or recieve calls. Anyone got any idea as to why this is a problem?
It should be noted, that the phone has no trouble at all when running the stock Android 4.3 or CrDroid Android 5.1.1.
The two phones are completely identical, and only one of them has trouble with calls on cm-13.0-20160217-NIGHTLY-i9300 (and any other version of cm for that matter).
Hope somebody knows what the problem is.