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.
Related
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.
I already posted in the wrong place one... I hope this is the right place.
------------------------------------------------------------------------------------------------------------
Hi,
I have a problem with my S2 after flashing to new firmware. This is the story:
- I purchased a S2. Everything worked fine. This was the data before I did something I shouldn’t have done:
PDA: I9100XWLQ2
PHONE: I9100XXLQ6
CSC: I9100DBTLPO
Sales code: DBT (only)
Android 4.0.4
Baseband version: I9100XXLQ6
Kernel version
3.0.15-1157945
[email protected] #3
SMP PREEMPT Fri Oct 26 16:17:36 KST
2012
Build number: IMM76D.XWLQ2
Kies worked fine (updated to the above).
- The only problem is that the firmware was DBT (German). The UI was in English but some applications were German. Nothing against Germany but I’m UK based.
- I decided to update to a new version using Odin, so I flashed:
I9100XWLPT_I9100XXLQ6_I9100XEULPA
This is where all the problems started:
Every time I boot I got a message saying the process android.(...).acore stopped
Clearing contacts cache/data did not address the problem
I read in this thread that this was due to instability of LP9 and it was advisable to use LP8.
- Flashed using Odin
Kernel_I9100XWLP8.tar.md5
I9100XWLPT_I9100XXLQ6_I9100XEULPA
- Now I have UK applications (which is good) but:
a) Every time I boot I get the message "Unfortunately, LogsProvider has stopped"
Clearing contacts cache/data doesn’t help.
b) When I try to use the phone (e.g. dial a number) I got a black screen for a minute or so and then the LogsProvider message. After that the phone application closes.
c) Kies stopped working with the message:
Your device's current firmware version is not supported to update firmware via Kies
Current firmware version: PDA:LPT / PHONE:LQ6 / CSC:LPA (DBT)
- Flashed I9100XWLPT_I9100XXLQ6_I9100XEULPA_HOME
Same problems
Now internal data is:
Android 4.0.4
Baseband version: I9100XXLQ6
Kernel version
3.0.15-I9100XWLPT-CL941023
[email protected] #3
SMP PREEMPT Fri Jul 27 18:08:15 KST
2012
Build number: IMM76D.XWLPT
In ideal world I would like to have an UK, unbranded, S2 and use Kies for future updates. Having said that, considering that the phone is almost dead any suggestion to bring the S2 back to life would be great.
I’m a little bit desperate... help... please
Thanks
~sf
P.S. I did search and read post, guides, notes, comments and info. I am not sure I understood all of it but I did try - I promise.
Well....why don't you just flash an unbranded stock ROM then? You could always update it via kies or OTA.
Should get 4.0.3 tho, dancing with 4.0.4's kernel might brick your device.
what you mean by "bring back to life", It is still working right?
gastonw said:
Well....why don't you just flash an unbranded stock ROM then?
Click to expand...
Click to collapse
This was the plan:
- Install an unbranded version
- Update via Kies
I didn't work
Do you have any suggestion for a UK-unbranded fimware version (4.0.3) that should work. My understanding is that it should be
a) for GT-I9100 (obviously)
b) XEU version (aka UK)
c) Android 4.0.3
Apart from that, is there any other important requirement?
Would this be ok: http://forum.xda-developers.com/showthread.php?t=1604254
gastonw said:
Should get 4.0.3 tho, dancing with 4.0.4's kernel might brick your device.
Click to expand...
Click to collapse
Ok - Message received. I'll use 4.0.3.
gastonw said:
What you mean by "bring back to life", It is still working right?
Click to expand...
Click to collapse
Well, not exacly. I can't make calls...
Don't worry about either your country or your calls. Search for an unbranded samsung official stock 4.0.3 ROM, flash it, check it out (smoothness and all) and then try to make a call. If it doesn't fly, just flash another modem
gastonw said:
Don't worry about either your country or your calls. Search for an unbranded samsung official stock 4.0.3 ROM, flash it, check it out (smoothness and all) and then try to make a call. If it doesn't fly, just flash another modem
Click to expand...
Click to collapse
I flashed
XEU 2012 April 4.0.3
I9100XWLP7_I9100XEULP5_I9100XXLPS\I9100XWLP7_I9100XXLPS_I9100XEULP5_HOME.tar.md5
I got the following messages:
"Unfortunately, Messaging has stopped working"
"Unfortunately, the process androind.process.acore has stopped"
"Unfortunately, LogsProvider has stopped"
I still can't make calls (black screen + above messages)
:crying:
factory reset & reboot maybe?
those are simple android errors.
gastonw said:
factory reset & reboot maybe?
those are simple android errors.
Click to expand...
Click to collapse
Good news. It looks like the situation has improved after the factory reset.
I'll go to sleep now (it's 2:50am here in London/UK). Tomorrow I'll check all the functions and but it looks like I'm going are in the right direction.
I'll post tomorrow about the results.
Thanks for your help gastonw - it is really appreciated. :good:
np, go get some rest now.
[Q] Brand new S2. After flash: errors, slow... (more questions)
Bingo! The factory reset worked. Everything back to normal. I have my UK application and Kies update to:
Android version: 4.0.4
Base version: I9100XXLQ6
Kernel version: 3.0.15-I9100XWLPT-CL941023
[email protected] #3
SMP PREEMPT Fri Jul 27 18:08:15 KST
2012
Build number: IMM76D.XWLPT
The only odd thing that the "About phone screen/Status" shows serial number 0000000000*. Not the end of the world.
Just a few additional questions
Now, before I make the same mistake again (do something I shouldn't, panic and ask for help)... If I want to root:
a) Can I do it without risking to brick?
b) Can I still use Kies after rooting?
c) Is there a recommended procedure that I should follow?
*update about it the next post.
Quick update about serial number 0000000000. Apparently, it is a 4.0.4 bug. The serial number is stored correctly internally but Android UI shows 0000000000.
The majority of people here probably already know that but just in case...
~sf said:
Now, before I make the same mistake again (do something I shouldn't, panic and ask for help)... If I want to root:
a) Can I do it without risking to brick?
b) Can I still use Kies after rooting?
c) Is there a recommended procedure that I should follow?
Click to expand...
Click to collapse
I manage to find the answers to my own questions :silly:
a/c) I followed the procedure described here. It worked great.
b) Yes. Kies doesn’t seem to care that the S2 is rooted
Result:
- 4.0.4 generic/unbranded/XEU firmware
- Updated and recognised by Kies.
- Rooted successfully.
- So far everything works smoothly and fast
Lesson learned:
- Factory reset after firmware flash resolved the problem.
I couldn’t be happier :good:
~sf said:
I manage to find the answers to my own questions :silly:
a/c) I followed the procedure described here. It worked great.
b) Yes. Kies doesn’t seem to care that the S2 is rooted
Result:
- 4.0.4 generic/unbranded/XEU firmware
- Updated and recognised by Kies.
- Rooted successfully.
- So far everything works smoothly and fast
Lesson learned:
- Factory reset after firmware flash resolved the problem.
I couldn’t be happier :good:
Click to expand...
Click to collapse
Happy to hear that, It's good to find answers just by reading a couple of post or googling around.
Now, I'd like you to read a little more about the brick bug and 4.0.4 ICS.
In the meanwhile, enjoy your device.
gastonw said:
(...)
Now, I'd like you to read a little more about the brick bug and 4.0.4 ICS.
Click to expand...
Click to collapse
I heard of it - although I don't know the details. The 4.0.4 Brick Bug is the reason why I flashed to 4.0.3 instead of 4.0.4.
The Samsung Update application updated to 4.0.4. It wasn't, strictly speaking, my direct choice. I could have ignored the suggestion of updating but I though that, since the update was coming from Samsung and it was applied to stock firmware, it was a safe choice.
gastonw said:
(...)
In the meanwhile, enjoy your device.
Click to expand...
Click to collapse
This sounds a little bit scary Should I be worried about something?
Lol, I remember you were on 4.0.4, told you It would be wise to go 4.0.3 and kies threw you back at 4.0.4.
Download gotbrickbug app from the store and check your chip (just for kicks). If it's insane, well...you can always go back to 4.0.3 and wait for the Jelly Bean update thru both Kies & OTA (Over The Air).
The thing is, you're completly safe whereas you don't flash any ROM or custom ROM, and perform things like wipes thru recovery and what not.
If you want to go in a flashing frenzee, then you might flash a safe kernel (like Siyah), but I think it's not the case, you seem to love Kies updates
The important thing is that your device is running smoothly on ICS; so, enjoy.
gastonw said:
Lol, I remember you were on 4.0.4, told you It would be wise to go 4.0.3 and kies threw you back at 4.0.4.
Download gotbrickbug app from the store and check your chip (just for kicks). If it's insane, well...you can always go back to 4.0.3 and wait for the Jelly Bean update thru both Kies & OTA (Over The Air).
The thing is, you're completly safe whereas you don't flash any ROM or custom ROM, and perform things like wipes thru recovery and what not.
If you want to go in a flashing frenzee, then you might flash a safe kernel (like Siyah), but I think it's not the case, you seem to love Kies updates
Click to expand...
Click to collapse
Hi gastonw,
Thanks again for you useful comments.
I suspected your comments about 4.0.3 vs 4.0.4 were related to my previous attemps of flashing 4.0... and your advice of staying away from it.
I run gotbrickbug and I'm happy to say it reports "Brick Bug? NO. Sane chip" - which I guess is good news.
gastonw said:
The important thing is that your device is running smoothly on ICS; so, enjoy.
Click to expand...
Click to collapse
I haven't tried all the functions but, so far, it works smoothly.
Well, ain't this a good weekend for you? lol
gastonw said:
Well, ain't this a good weekend for you? lol
Click to expand...
Click to collapse
Intense but rewarding :laugh: lol
Hello there!
First of all I am a complete noob when it comes to the Galaxy SII and pretty much know nothing about it apart from navigating my way around the device. Previously before I got the SII I successfully rooted and updated an LG Optimus One P500h to Android 4.1.2 via Clockwork Recovery and that went very smoothly however I managed to "Soft Brick" it as I forgot to perform a factory reset when flashing CM10 :laugh:. I used a bit of common sense to fix this by reflashing CM after a factory reset and a dalvik cache wipe.
Anyway I recently purchased a Galaxy S2 because it seemed like a powerful phone with a large screen at a price that wouldn't put a heavy duty dent in my wallet. I had the intent of rooting the phone but soon discovered after I purchased it that the phone had a "superbrick" bug thanks to Chainfire's Got Brickbug? app. I've read quite a few posts on the forum regarding people's phones motherboard being burnt out when they performed a factory reset with CWM Recovery. I am very keen to root my phone and have an alternative to CWM Recovery installed so in the future I can flash CyanogenMod and not have any issues regarding the superbrick bug. Is there any "safe-ish" root method and recovery that won't cause the superbrick bug?.
Here are some specifications for my device that might prove useful:
[From Chainfires Got Brickbug? App]
eMMC chip:
Type: VYL00M
CID: 15010056594c30304d19b62b3054bf7b
Revision: 0x19
Verdict: DANGER! This eMMC chip is *KNOWN* to have the brick bug!
[From About phone]
Model number: GT-I9100T
Android version: 4.0.3
Baseband version: I9100TDOLP4
Kernel version: [email protected] #3
Build number: IML74K.DOLP7
Any links, posts etc will be greatly appreciated!.
Thank you very much for your time
Matthew McLean
New XDA member
mmclean said:
Hello there!
First of all I am a complete noob when it comes to the Galaxy SII and pretty much know nothing about it apart from navigating my way around the device. Previously before I got the SII I successfully rooted and updated an LG Optimus One P500h to Android 4.1.2 via Clockwork Recovery and that went very smoothly however I managed to "Soft Brick" it as I forgot to perform a factory reset when flashing CM10 :laugh:. I used a bit of common sense to fix this by reflashing CM after a factory reset and a dalvik cache wipe.
Anyway I recently purchased a Galaxy S2 because it seemed like a powerful phone with a large screen at a price that wouldn't put a heavy duty dent in my wallet. I had the intent of rooting the phone but soon discovered after I purchased it that the phone had a "superbrick" bug thanks to Chainfire's Got Brickbug? app. I've read quite a few posts on the forum regarding people's phones motherboard being burnt out when they performed a factory reset with CWM Recovery. I am very keen to root my phone and have an alternative to CWM Recovery installed so in the future I can flash CyanogenMod and not have any issues regarding the superbrick bug. Is there any "safe-ish" root method and recovery that won't cause the superbrick bug?.
Here are some specifications for my device that might prove useful:
[From Chainfires Got Brickbug? App]
eMMC chip:
Type: VYL00M
CID: 15010056594c30304d19b62b3054bf7b
Revision: 0x19
Verdict: DANGER! This eMMC chip is *KNOWN* to have the brick bug!
[From About phone]
Model number: GT-I9100T
Android version: 4.0.3
Baseband version: I9100TDOLP4
Kernel version: [email protected] #3
Build number: IML74K.DOLP7
Any links, posts etc will be greatly appreciated!.
Thank you very much for your time
Matthew McLean
New XDA member
Click to expand...
Click to collapse
Just flash siyah Kernel and you'll be safe from brick bug. You are on 4.0.3, that means you are off the hook as well (BrickBug only affects 4.0.4's stock kernel).
Learn more from your device.
Here you can find your model's Q&A. If you wanna root it, search the thread for the "root" word (or go to the last page).
So this means that I can use ClockworkMod Recovery and not run into any brickbug problems with factory reset?.
If you do so while on 4.0.3 or after you've replaced the stock kernel with a custom one (siyah, dorimanx, etc), yes.
Sent from my GT-I9100 using xda app-developers app
Hello guys. How are you?
I have a Samsung Galaxy S3 I9300 (Baseband version: i9300UBELL1 /// Kernel version: 3.0.31-789635 [email protected] #1 SMP PREEMPT Fri Jan 25 00:23:01 KST 2013 /// Build number: JZO54K.I9300UBEMA2) from Movistar Argentina. A couple of months ago, my phone got SDS (sudden death syndrome) and lucky for me it was during the warranty period. After getting a new board (from the outside is the same phone), Samsung guys upgrade the system to the one I have mentioned.
Last weeks, I rooted my phone and installed SuperNexus 3.0 (build 1). The experience was incredible: greatest speed ever, smooth interphase, clean system, faster connection and re-connection to 3G networks. Everything was amazing, until my phone started to freeze. At first I thought, it was part of the ROM development because this was build 1, but day after day the freeze got worse (like the symptoms I experienced before SDS). As my phone still is a SDS candidate (checked with eMMC), even that SuperNexus 3.0 (b1) has the kernel patch sudden death fix, I changed to SuperNexus 2.0. To make the long story short, the freeze problem continued so I've restored to factory state for warranty purpose... just in case...
I would like to optimize my S3. What do you recommend me to do? Does someone has the same phone model rooted with a good ROM without the freezing issue? What ROM do you recommend me to install in i9300UBELL1? By knowing that my phone is a SDS candidate, is there any risky to try different ROMs?
Thanks!
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
What rom best rom posts are not allowed .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
This has been discussed in detail here:
http://forum.xda-developers.com/showthread.php?t=2133401
**Ultimate Galaxy S3 Unusual Freezing Thread**
bishop0102 said:
Hello guys. How are you?
I have a Samsung Galaxy S3 I9300 (Baseband version: i9300UBELL1 /// Kernel version: 3.0.31-789635 [email protected] #1 SMP PREEMPT Fri Jan 25 00:23:01 KST 2013 /// Build number: JZO54K.I9300UBEMA2) from Movistar Argentina. A couple of months ago, my phone got SDS (sudden death syndrome) and lucky for me it was during the warranty period. After getting a new board (from the outside is the same phone), Samsung guys upgrade the system to the one I have mentioned.
Last weeks, I rooted my phone and installed SuperNexus 3.0 (build 1). The experience was incredible: greatest speed ever, smooth interphase, clean system, faster connection and re-connection to 3G networks. Everything was amazing, until my phone started to freeze. At first I thought, it was part of the ROM development because this was build 1, but day after day the freeze got worse (like the symptoms I experienced before SDS). As my phone still is a SDS candidate (checked with eMMC), even that SuperNexus 3.0 (b1) has the kernel patch sudden death fix, I changed to SuperNexus 2.0. To make the long story short, the freeze problem continued so I've restored to factory state for warranty purpose... just in case...
I would like to optimize my S3. What do you recommend me to do? Does someone has the same phone model rooted with a good ROM without the freezing issue? What ROM do you recommend me to install in i9300UBELL1? By knowing that my phone is a SDS candidate, is there any risky to try different ROMs?
Thanks!
Click to expand...
Click to collapse
try sotmax rom v19:good:
JJEgan said:
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
What rom best rom posts are not allowed .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
Sorry JJEgan. It won't happen again.
shar1r said:
This has been discussed in detail here:
http://forum.xda-developers.com/showthread.php?t=2133401
**Ultimate Galaxy S3 Unusual Freezing Thread**
Click to expand...
Click to collapse
Thanks shar1r. I have read this forum before. I will give it a try and write some feedback later.
fantasmanegro said:
try sotmax rom v19:good:
Click to expand...
Click to collapse
Hello fantasmanegro. Do you have the same phone model (I9300ubell1 from South America)? How does it work on your device? Any freeze issues? Thx.
bishop0102 said:
Do you have the same phone model (I9300ubell1 from South America)? How does it work on your device? Any freeze issues? Thx.
Click to expand...
Click to collapse
The i9300 is the i9300. The rest of it means nothing. The i9300 is international so everyone who posts here has an i9300 or an i9305. Infact only our "general" section is shared with i9305, our q&a, where you now know this should have gone - is ONLY i9300 users. UBELL1 means nothing
bishop0102 said:
Sorry JJEgan. It won't happen again.
Thanks shar1r. I have read this forum before. I will give it a try and write some feedback later.
Hello fantasmanegro. Do you have the same phone model (I9300ubell1 from South America)? How does it work on your device? Any freeze issues? Thx.
Click to expand...
Click to collapse
yup, i have it... or i used to have it... XD... now i'm with sotmax rom v19...
but... my stock rom is bell1...:good::good::good::good::good:
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