Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

 Samsung Galaxy S III I9300 Official Thread V25, Samsung Galaxy S series sold over 100m !

views
     
tigerporc
post Jan 9 2013, 07:54 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(nokia6280 @ Jan 9 2013, 04:55 PM)
Too bad there isn't any Changelog for every release but I suspect some fixes to this round. Since Samsung start S3 release hoping we received xxla or higher not like others still ll4 or 5. Hope Malaysia is this round...
*
Strange no one reply to you yet, the GSIII Sudden Death fix is in the XXELLA kernel (not bootloader) and if you're on custom kernel, Perseus is the first to have the new fix.

Source: http://forum.xda-developers.com/showthread.php?p=36459955

This post has been edited by tigerporc: Jan 9 2013, 07:54 PM
tigerporc
post Jan 9 2013, 08:26 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(waveweaver @ Jan 9 2013, 08:15 PM)
If you read case 2 in LordDenning post #1366...you'll see that the guy phone went dead eventhough his phone was unrooted and on stock rom XXELLA firmware  doh.gif
*
Yupe, I myself am not too sure about XXELLA kernel, still unclear from reading the various dev posts... so I flashed perseus kernel earlier today anyway instead while still on stock Msia JB blush.gif
tigerporc
post Jan 9 2013, 09:56 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(noobandroid @ Jan 9 2013, 09:40 PM)
droidtrix it is due to an eMMC failure in the memory chip, whatever it means dry.gif
*
Very good analogy of the wear leveler problem described here
http://forum.xda-developers.com/showpost.p...&postcount=2841

And very good explanation of why the workaround fix can work from the dev Entropy512
http://forum.xda-developers.com/showpost.p...&postcount=2903

This post has been edited by tigerporc: Jan 9 2013, 09:58 PM
tigerporc
post Jan 9 2013, 11:50 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(nokia6280 @ Jan 9 2013, 11:44 PM)
Not sure only 4.0.4 facing SDS problem or after upgrade to 4.1.1, any idea? hmm.gif
*
It is 100% confirmed that stock ICS 4.0.4 also had SDS and JB 4.1.1 of coz.
JB 4.1.2 is unfortunately not confirmed yet to have the fix as there as still some cases of SDS.

Like I mentioned before for me, just get Perseus 1st since nothing to lose while waiting smile.gif
tigerporc
post Jan 10 2013, 08:23 AM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(nokia6280 @ Jan 10 2013, 08:07 AM)
Just to clarify the Perseus is custom kernel? hmm.gif
*
Yes, get it here
Perseus Kernel (XDA)

Just flash it, and use Triangle Away to reset the flash count. On stock Msia JB, you just have to reset the flash count once. In download mode, your binary will still be official. But to get back the stock kernel, you have to reflash the whole stock rom again (or restore from nandroid)


Added on Jan 10 2013, 09:30 AM
Seems that Entropy512 thinks 90% chance that Perseus fixed it and 75% chance for XXELLA/4 to fix it
Source: http://forum.xda-developers.com/showpost.p...&postcount=2905

This post has been edited by tigerporc: Jan 10 2013, 09:31 AM
tigerporc
post Jan 10 2013, 09:15 AM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(waveweaver @ Jan 9 2013, 08:15 PM)
If you read case 2 in LordDenning post #1366...you'll see that the guy phone went dead eventhough his phone was unrooted and on stock rom XXELLA firmware  doh.gif
*
A WTF update from the fella today, now claims a jig saved his phone doh.gif
source: http://forum.xda-developers.com/showthread.php?t=2089302
tigerporc
post Jan 10 2013, 10:55 AM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(nokia6280 @ Jan 10 2013, 10:41 AM)
Hey Bro, just to confim few things just in case i want to flash it.

1. Flashing using PC ODIN and place the file in PDA?
2. Any 4.1.1 can be flashed?
3. Need to root first before flashed or this will flash and root together?

Thanks! notworthy.gif
*
1. Correct, just tick PDA.
2. Yes, the latest perseus can be used on any JB ROM. In future, if you flash any full JB ROM, this perseus kernel will be replaced...
3. If you have rooted before, flashing this new perseus kernel will not impact it, you will still be rooted.

Follow the steps here for ODIN (Yes, I know it is Note 2, but just showing you the steps which are the same)
http://www.androidauthority.com/galaxy-not...-kernel-143983/

After that, remember to reset flash counter using TriangleAway

This post has been edited by tigerporc: Jan 10 2013, 10:59 AM
tigerporc
post Jan 10 2013, 01:53 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(danleongwz @ Jan 10 2013, 01:23 PM)
just flashed it last night and its awesome! but then there bugs with the camera and brightness while no photosphere tongue.gif anyway, anyone noticed that red dot on the galaxy boot screen ?
*
You are using the XXELLA or later bootloader. The red dot (exclamation mark) indicates that your device is modified. 'Fixing' needs some skillz as unfortunately flashing older bootloader not possible due to blacklisting
See this
http://forum.xda-developers.com/showthread.php?t=2081748

For other ways, see this
http://forum.xda-developers.com/showthread.php?t=2083860

This post has been edited by tigerporc: Jan 10 2013, 01:55 PM
tigerporc
post Jan 10 2013, 02:26 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(danleongwz @ Jan 10 2013, 01:59 PM)
i see. i'll try it out and tell you guys later. any of you guys having the same problem as me ?
*
I think most people here flash 4.1.2 via mobile ODIN so did not face this problem cool2.gif
tigerporc
post Jan 10 2013, 05:27 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(ranc79 @ Jan 10 2013, 05:16 PM)
which one is the bootloader that we are using now for stock malaysia rom 4.1.1?
*
Can also check by using terminal (you also need busybox)

CODE

cat /proc/last_kmsg | grep bootloader


Mine is (stock Msia JB 4.1.1); updated last year using Kies
android.bootloader=I9300XXALEF

This post has been edited by tigerporc: Jan 10 2013, 05:28 PM
tigerporc
post Jan 10 2013, 05:33 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(XeactorZ @ Jan 10 2013, 05:28 PM)
huhu same with me
you got OTA update ?
*
Updated my post. Last update to 4.1.1 was via Kies.
No longer will do that though, as next update (4.1.2 Msia) I will flash using Mobile ODIN to not update the bootloader.
tigerporc
post Jan 10 2013, 06:20 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(nokia6280 @ Jan 10 2013, 06:10 PM)
No... what bro tiger telling is he will download malaysia 4.1.2 from Sammobile and remove the bootloaderr then use mobile odin to flash without the bootloader...

Bro tiger, correct? hmm.gif
*
Actually XeactorZ is right (OTA is the one that probably updates the bootloader as well), my last 4.1.1 update using Kies did not seem to update the bootloader (his and my bootloader is still ICS Msia version). I am not very sure if Kies will be successful in updating my Msia 4.1.1 to Msia 4.1.2 as my device shows modified now (and also worried bout bootloader downgrade hassle; so to be safe I will update 4.1.2 using Mobile ODIN when Msia 4.1.2 is available from Sammobile) biggrin.gif
tigerporc
post Jan 10 2013, 06:47 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(waveweaver @ Jan 10 2013, 05:03 PM)
I didn't make that bootloader into flashable zip...i get it from xda thread  laugh.gif
*
The person who created that flashable zip has written comments (or rather print output) in the code in italian biggrin.gif

That particular flashable zip is actually doing the operations described here
http://forum.xda-developers.com/showthread.php?t=2081748

BTW - Guide to creating flashable zip is here
http://fokke.org/site/content/howto-create...datezip-package

This post has been edited by tigerporc: Jan 10 2013, 06:57 PM
tigerporc
post Jan 11 2013, 04:07 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(eszol @ Jan 11 2013, 02:22 PM)
sorry cannot give exact number because so hard to count everybody phone  tongue.gif

but mine still alive n waiting patiently for newer siyah that can fix SDS issue

found in xda that perseus got bug that cause slow charging rate

n the latest siyah i use now also got bug. cannot transfer file from computer using usb cable n will cause reboot
*
Using PerseusAlpha v31 I don't find much difference in charging (Using Battery Monitor Widget), it charges roughly the same time as the 4.1.1 Msia stock kernel. (Stock cable + stock 1A charger)
=> Reading the thread, Andrei is supposedly aware of slow charge issue but I am inclined to think it may be due to some app/stweak issues as well

On the stock kernel 4.1.1, the slow charge I sometimes get once in a while is because of the charging suddenly gets dropped to 499mA instead of the expected 999mA; if you notice it; plugging out and in again would solve the problem.
=> Have yet to experience it on perseus.

I will still stay on perseus anyway for the moment flex.gif
tigerporc
post Jan 12 2013, 06:32 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(xinghuei @ Jan 12 2013, 06:20 PM)
Yesterday night I cleared my i9300 Google Map app cache (very regret I did this),
this morning my phone start to go haywire, Google Map App failed, and went into boot loop, after awhile, it stuck in Samsung Boot Screen,
1/ I tried press Vol Up + Home Button + Power Button it refuse to go into recovery mode, it keep stuck at Samsung Boot Screen
2/ If I press Vol Down + Home Button + Power Button it can enter into download mode.
My phone is not rooted and running Android 4.1.1 (last update 2mth ago via Kies)
Any solutions? Thank you.
*
Unlikely just clear Google Map cache can damage your phone...
What is the download mode status? If blank, and status modified, could be just bad luck and hit Sudden Death issue

If not that, possible just reflash stock ROM with PC ODIN will get your phone working again.
tigerporc
post Jan 12 2013, 06:43 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(xinghuei @ Jan 12 2013, 06:39 PM)
Below is what appear in my Download Mode:

ODIN MODE
Product Name: GT-i9300
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
*
It seems ok, so should not be SDS issue, maybe other hardware issue; which you may have to bring to SC.
For now, just try reflash back stock ROM with PC ODIN.
Good Luck!

tigerporc
post Jan 12 2013, 06:48 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(xinghuei @ Jan 12 2013, 06:44 PM)
Is there anyway to perform backup before I reflash with PC ODIN? Thanks
*
As far as I know, only if you can boot to recovery.
Once in recovery, you can use ADB shell to backup and copy the files to your PC/Notebook or if you have CWM, then can do backup with CWM to your sdcard.

If you reflash ROM, data is not affected, but normally recommended to wipe data.
tigerporc
post Jan 12 2013, 07:33 PM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(Kelvin8998 @ Jan 12 2013, 07:12 PM)
Is the galaxy s3 I9300 version actually compatible with LTE?
*
Your question is not clear, you're in luck - just search for LTE in this thread and start reading from 1st page of the posts found. rclxms.gif
Covers LTE flame war, coverage and models supported

QUOTE(xinghuei @ Jan 12 2013, 07:13 PM)
Ok. Can you help verified if below steps are correct

1/ Download stock rom Sammobile
2/ Enter download mode
3/ Download and run odin3v1.85.exe
4/ At ODIN, check PDA and Click PDA button, and select rom MD5 file
5/ Click Start

Thanks. smile.gif
*
Yes; but I prefer ODIN 3.07, go search Jayce Ooi blog for some vids if you need more help.
tigerporc
post Jan 14 2013, 11:03 AM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(soupdragon @ Jan 14 2013, 10:52 AM)
Thanks but what I really want to know is the 32GB at the same risk of sudden death as the 16GB version ??
*
No same sudden death issue for 32GB as the eMMC firmware is different. FYI - it seems, the 16GB eMMC for Note2 is the same as SIII as well so that is why there are some cases of sudden death as well.

If worried about SIII sudden death, read this to mitigate your risks
http://forum.xda-developers.com/showthread.php?t=2091045
tigerporc
post Jan 14 2013, 11:47 AM

Casual
***
Junior Member
391 posts

Joined: Jan 2003


QUOTE(wilsonjack228 @ Jan 14 2013, 11:44 AM)
Using mobile odin to flash the newest firmware that suppose to fix the SDS does not flash the bootloader ?
so thats mean I'm still not secure yet ?  tongue.gif now rooted on the UK JB 4.1.2  hmm.gif
*
Yes, mobile ODIN is unable to flash bootloader.
At this time, the new bootloader is not required. Not yet any good reason to flash it.
At the moment, what is known is that you do not need the new bootloader to be secure against SDS.
The stock 4.1.2 kernel is enough, so you're good.

2 Pages  1 2 >Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0511sec    0.33    7 queries    GZIP Disabled
Time is now: 3rd December 2025 - 01:34 AM