Revert back to S3 ICS - Galaxy S III Q&A, Help & Troubleshooting

I was on Jelly Bean 4.3 but the battery was bad so I downloaded a stock rom of ICS 4.0.4 & cannot get any reception. My IEMI & IEMISV is messed up & is showing 0049 at the start of the IEMI. But if I go back to Jelly Bean I'm able to get reception & the IEMI & SV is fixed but I don't want to do that. I tried restoring the EFS but it didn't do anything. As a lot of features are absent in Jelly Bean & the battery life is horrible. Can anyone help me? Here's the Rom's details
Greece 2012 August 4.0.4
CSC: I9300EURBLH1
PDA: I9300XXBLH1

No, you can't. 4.0 has SDS anyway.

What do you mean I can't? I'm on the firmware right now but just not getting any reception. Why would the rom be up on Sammobile if I wasn't able to go back to 4.0.4?

SmithO77 said:
What do you mean I can't? I'm on the firmware right now but just not getting any reception. Why would the rom be up on Sammobile if I wasn't able to go back to 4.0.4?
Click to expand...
Click to collapse
because it got uploaded when it came arround. with 4.3 Samsung changed the efs partition to efsv2, while older roms / modems uses efsv1 format, thats why there is no signal, some patched modems/kernel may be able to fix.
boomboomer said:
No, you can't. 4.0 has SDS anyway.
Click to expand...
Click to collapse
Partitialy Wrong SDS is caused by the nand´s firmware,while has been "fixed"(i remember they do some sanity checks now instead of fully fixing by upgrading the firmware, as they did on s2) on UK 4.1.2 bootloader or on every 4.3 bootloader, if the phone came with updated firmware, it will run the ics normally(my phone ran ics for about an year with no problems, but it was the 2nd one, my day one crashed twice or more in a day)

Bootloader on the s3 is a separate kernel from firmware, if either is missing the sds fix then sds can occur. If you run any 4.0 firmware then you risk sds, it doesn't matter what the bootloader is.

Hey, thanks for the help. I honestly can't believe Samsung would do this. I'm actually getting good standby time, it's the screen time that's not good. I'm getting about 2 hours & a 1/2 (sometimes 3). Before I was getting worse but since I've disabled google now & location reporting that's where it's at. I don't remember this kind of bad battery life on ICS. I'll be buying another GT-I9300, selling this one, and making sure I don't upgrade. Won't be buying another Samsung device again. Just look at these wakelocks from Jelly Bean. It doesn't matter if I find the culprit that's doing alot of wakelocks as another just takes it's place, it's like an app has to be draining down the battery. Just Crazy!

Try the 4.2.2 leak with patched modem: https://www.dropbox.com/s/geispctijpxqjms/Patched_Modem_I9300XXEMG4.zip?dl=1 I'm getting good performance and battery with this setup
Sent while my supervisor wasn't looking

Related

Stock 4.0.3 to stock 4.0.4 through Kies - 00000000000 serial number issue?!

For the guys who updated to stock 4.0.4 from stock 4.0.3..
I went from stock 4.0.3 to stock 4.0.4 through Kies and I have the 00000000000 serial number issue (as seen with some of the earlier stock leaks).
I am not bothered if the serial number stays like that as long as there aren't anymore issues (i.e. bugs/perks due to bad install etc), so far I haven’t had any issues.. seems pretty smooth and bug free.. time will tell though..
Is there a fix and how can I can re-flash the same firmware just to make sure it wasn't a bad install (without rooting etc)
I have always been completely stock.
How bizarre..
kkh786 said:
For the guys who updated to stock 4.0.4 from stock 4.0.3..
I went from stock 4.0.3 to stock 4.0.4 through Kies and I have the 00000000000 serial number issue (as seen with some of the earlier stock leaks).
I am not bothered if the serial number stays like that as long as there aren't anymore issues (i.e. bugs/perks due to bad install etc), so far I haven’t had any issues.. seems pretty smooth and bug free.. time will tell though..
Is there a fix and how can I can re-flash the same firmware just to make sure it wasn't a bad install (without rooting etc)
I have always been completely stock.
How bizarre..
Click to expand...
Click to collapse
as long as ur IMEI no is intact and ur phone is wrk'ng fine, there is no need to panick ma8.
i have custom rom's running on my s2 right from day one i unboxed the same,rooted and installed custom one's and since then i have serial no unknown. but have no issue so far
Hmm,
Thanks for the prompt reply mate.
I guess I will have to live with it until we get JB.. A few months maybe.
But to be fair, this firmware has been the smoothest version I have used since GB days.
Don't see the need for rooting until JB.
Sent from my GT-I9100
this firmware is smooth but my phone is overheating like mad and also crashes on some games quite a lot. Had to take the battery out loads of times to restart it.

Samsung S2 - Help!

As you can obviously see I'm new here to xda-developers and still don't know my way around the forums and going easy on me will certainly help. Without further ado I would like to ask some questions about Samsung S2 Jelly bean (4.1.2).
I have Ice Cream Sandwhich (4.0.4) stock phone; never been rooted and I do not wish to start now. I want to upgrade to Jelly Bean (JB) but I've heard a lot of complaints of battery not lasting for more than 8 hours or more and phone freezing frequently. Is there anybody still experiencing this problem? (I know it's a bit late asking this question since JB was released months ago I just want to make sure).
I will be updating the phone firmware via Kies.
One more thing how do I make sure that my Samsung S2 is genuine? I'm not keen on putting my IMEI on the internet to check if it's genuine but if I have no choice then I will probably do it. I've also heard that the 8 digit on your IMEI will prove it? Like if you have 00 - Genuine factory.
Thanks in advance.
Read the jb threads, you heard wrong. You can get up to 5 hours screen time or even 2 days out of your battery on JB.
Everyone is gonna tell you to flash it via Odin but I guess you rather do it via kies, which is fine.
IMEI has got nothing to do with your device in terms of originality.
If kies says it's an I9100 chances are it's the real thing.
Sent from...this is not even my S2
gastonw said:
Read the jb threads, you heard wrong. You can get up to 5 hours screen time or even 2 days out of your battery on JB.
Everyone is gonna tell you to flash it via Odin but I guess you rather do it via kies, which is fine.
IMEI has got nothing to do with your device in terms of originality.
If kies says it's an I9100 chances are it's the real thing.
Sent from...this is not even my S2
Click to expand...
Click to collapse
Any chance that you could give me the link to JB threads? I'm new here and don't know where to go.
Why are they going to recommend Odin instead of Kies? Is there any difference? Performance, bugs, etc...?
You can find them in the general forum.
Flashing via odin is just fun as you can flash any ROM you want (either branded or unbranded).
Sent from...this is not even my S2

[Q] Galaxy S3, Android 4.04 ICS

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

S3 4.0.4 stock rom

had installed android 4.3 on s3 but then I installed 4.0.4 after that I had no gsm connectivity see the block sign between battery and wifi. I have gsm connectivity on 4.3 but not on 4.0.4. A guy told me that it has something to do with the bootloader. I wish to install 4.0.4 stock ICS BTU rom if there's a way do tell me. Thanks in anticipation!
Ya i tried this as well because i was really considering downgrading to ICS. IMO it runs way better than jellybean. If anyone knows how to do this, please, enlighten us. For now, just reflash the 4.3 ROM to get your signal back. As i understand it, once you go to 4.3, you need to do a downgrade, you cant just flash the ROM, if anyone can explain the process, that would be great.
For the record, if you have a 16GB S3, i wouldn't recommend the downgrade, the 16GB was subject to a sudden death syndrome and the fix is not included in ICS. If you have 32GB+ then you safe.
I have a 16 GB version of s3 I think then I should go for cyanogen
abubakarsohail said:
I have a 16 GB version of s3 I think then I should go for cyanogen
Click to expand...
Click to collapse
Flash a modem that's MG4 above, this is asked hundreds of times a day, use the search.
9156385854
Better still flash a decent 4.3 ROM. Is there a good reason why you want to go back all the way to 4.0.4? Did you skip 4.1.2 altogether? That was better than 4.0.4, but my brief experience of 4.3, after the initial problems with the disastrous MJ9 release were resolved, is that it's the best yet.

[Q] S3 insane chip phone doing wierd things on 4.3

Hi Folks,
I just bought this secondhand lovely new looking S3 that was still in the box. I was ecstatic, but once I started to use it I realised it is a lemon. It does weird things. Drops calls, gets no reception with full bars showing, drops mic input, won't call, won't receive a call, sound sometimes goes garbled during call. I can't use it.
It is running Jelly bean 4.3. Full details below,
Model: GT-i9300
Android: 4.3
Baseband version: I9300XXUGNA8
Kernel version: 3.0.31-2454463
build no: JSS15J.19300XXUGNB6
getRIL: confirmed RIL/baseband matching
eMMC chip: VTU00M build: 09/2012 FwRev: 0xf1 - confirmed insane
What are my options here? While I could pension it off to the next unsuspecting consumer as was done to me I'm not going to lower myself to that. Is there anything I can do to get this phone working or am I better off just counting my losses and going back to HTC which I've always used and love? This is my first Samsung phone and I"m not impressed. Samsung should recall. Its disgusting and damaging to their image. Well I'm already wiping them from my list of products for life.
thanks
Jimbobtx3 said:
Hi Folks,
I just bought this secondhand lovely new looking S3 that was still in the box. I was ecstatic, but once I started to use it I realised it is a lemon. It does weird things. Drops calls, gets no reception with full bars showing, drops mic input, won't call, won't receive a call, sound sometimes goes garbled during call. I can't use it.
It is running Jelly bean 4.3. Full details below,
Model: GT-i9300
Android: 4.3
Baseband version: I9300XXUGNA8
Kernel version: 3.0.31-2454463
build no: JSS15J.19300XXUGNB6
getRIL: confirmed RIL/baseband matching
eMMC chip: VTU00M build: 09/2012 FwRev: 0xf1 - confirmed insane
What are my options here? While I could pension it off to the next unsuspecting consumer as was done to me I'm not going to lower myself to that. Is there anything I can do to get this phone working or am I better off just counting my losses and going back to HTC which I've always used and love? This is my first Samsung phone and I"m not impressed. Samsung should recall. Its disgusting and damaging to their image. Well I'm already wiping them from my list of products for life.
thanks
Click to expand...
Click to collapse
First thing to try is flash a stock rom with Odin look here for guides >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 << if problems persist after flashing another stock rom then it is most likely a hardware problem....
tallman43 said:
First thing to try is flash a stock rom with Odin look here for guides >> http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 << if problems persist after flashing another stock rom then it is most likely a hardware problem....
Click to expand...
Click to collapse
Thanks for the reply. Won't flashing a ROM risk sudden death syndrome? My understanding of the insane ROM and SDS is that any reflashing could brick the phone immediately. Or maybe I'm not right on that one.
Jimbobtx3 said:
Thanks for the reply. Won't flashing a ROM risk sudden death syndrome? My understanding of the insane ROM and SDS is that any reflashing could brick the phone immediately. Or maybe I'm not right on that one.
Click to expand...
Click to collapse
Lol no I have flashed 100s of times (Lost count I have flashed that many times) and I have insane chip..Only roms you should keep away from is 4.0.4 roms... To be honest I would keep on 4.3 roms because if you flash a rom below this you may run into efs issues which is a separate thing from sds.. Look on sammobile for a 4.3 rom to flash and follow the guides don't forget if you have a bootloop after flashing to factory reset your device.

Categories

Resources