Hi,
I have a Chilean Entel PCS i9100. Looking at the data below it looks like the firmware is pretty old and based on KE1.
There is no problem in changing to the latest generic XEU, e.g. KF2.
XEU is generic Europe; What about the CHE CSC?
*#1234#:
PDA: I9100UHKD7
PHONE: I9100UHKD7
CSC: I9100CHEKD7
Build Info: Wed May 4 13:33:54 KST 2011
Kies DeviceDB registry:
ProdCode: GT-I9100LKLCHE
HIDSWVER: 9100UHKE1/I9100CHEKE1/I9100UHKE1/I9100UHKE1
Thanks,
zyxeu
P.S.: The original Chilean firmwares can be found at Intratech's [ROM + Guide] threads:
Branded stock firmwares, e.g. CHE, CHT, CHL:
http://forum.xda-developers.com/showthread.php?t=1113928
Unbranded stock firmware, e.g. CHO:
http://forum.xda-developers.com/showthread.php?t=1075278
Chilean CHEKE1 CSC now available to download.
The mans just posted .
jje
Download the Frankenstein XWKE7 firmware package and instead of using the multi-CSC package included with it download and use the CHEKE1 CSC.
Thank you very much Intratech.
Hi zyxeu,
I have the same Chilean Entel firmware. Have you managed to update the firmware to KE2 or KE7? and if so did you use Odin?
On other post you mention upgrading the firmware through Kies using "Check Fus Downloader"
Saludos,
Mguel
Hi mguel,
Yes, I changed my Chilean Entel PCS SG2 to XE7 generic XEU and it works.
I did not change the CSC to the Chilean one.
I upgraded the firmware using the Intratech way with his instructions, tools(Odin), and firmware, which he provides in this thread:
http://forum.xda-developers.com/showthread.php?t=1075278
In my case after the first firmware download using Odin the device got stuck with an endless Samsung logo boot. This happened to me twice or thrice during firmware downloading. To get around this I always used the following method from post #7 here:
http://forum.xda-developers.com/showthread.php?t=1104515
This three firmware download always got the device back to working state!
The order that I have used to update, root, simunlock:
1.) Updated to XWKE7 XEU generic (http://www.multiupload.com/IBRBHDUDXI)
2.) Had to fix the endless loop with the "3 file" method then I did the step 1.) again and it worked
3.) Removed SD and SIM card and then did a full reset *2767*3855# to reset the internal CSC to XEU
4.) Did step 1.) again as recommended to ensure CSC setting really gets changed and everything is in sync
5.) Rooted the device using Chainfire's CF-Root 3.5 KE7 kernel from his thread: http://forum.xda-developers.com/showthread.php?t=1103399
6.) Back up your /efs folder as mentioned in this thread: http://forum.xda-developers.com/show...&highlight=efs
7.) Unlocked the simlock using Chainfire's unlock app and from android market that uses Odia's method, a Movistar/Claro SIM, and had to do it like this: http://forum.xda-developers.com/showthread.php?t=1106496
So far everything went well and if a problem occured I just used step 2.) to go back to a working system and did all the steps again.
If you are using Chainfire's CF-Root 3.5 KE7 kernel and plan to use a corporate Exchange Activesync account this thread will interest you to fix the boot endless loop that results: http://forum.xda-developers.com/showthread.php?t=1107457
Basically you overwrite Chainfire's CF-Root 3.5 KE7 kernel with a KE7 stock kernel. Root and Busybox are still working afterwards but I do not recommend the use of CWM, because I do not know how far it is anchored with Chainfire's kernel.
I recommend you to download all files mentioned above beforehand (and the Chilean UHKE1 files just in case).
NEVER USE PIT OR REPARTITION IN ODIN!
As long as you can get in the "firmware download" mode your device can be saved and is not bricked.
There is a way to reset the custom firmware download counter and remove the yellow "!" with a micro USB connector and some resistors (look at intratech's ROOT AND ROM GUIDE thread).
And finally if you need your original Chilean firmware for warranty issues (Claro/Movistar/Entel) check post #10 here http://forum.xda-developers.com/showthread.php?t=1098738
The efs backup is necessary, e.g. if you end up with a bad IMEI and/or ProductCode, which seems to be fixeable: http://forum.xda-developers.com/showthread.php?t=881162
Wow, thanks a lot for the detailed answer!!
Although I rooted and flashed my previous androids, the infinite loop you got 2 or 3 times scares me a bit... so I'll study thoroughly the method before, wainting if entel releases a firmware update in the meanwhile... but as I read somewhere entel is not too active in releasing updates :/, and I like to test different ROMs. Although with the hardware aceleration features of the Samsung firmwares and the fact that I like how it work in general (hated motoblur on my previous phone), I'm not sure if I will test many ROMs but certainly I like to keep my phone updated.
Thanks again for the answer!
Mguel
PS: we should start some sort of chilean SGS2 community.
Dear friends,
I had a Chilean´s movistar version and come with the following firmware:
PDA:UHKE4
PHONE: UHKE2
After read a lot in the forum, i decided and flashed to a custom rom ( VillainRom 1.1 and later to kernel CF-Root 3.5 KE7), all going very charming and rooted everything. I do it following with a youtvbe video ( if you need, plese PM)
Hope it´s usefull your
mguel said:
Wow, thanks a lot for the detailed answer!!
Although I rooted and flashed my previous androids, the infinite loop you got 2 or 3 times scares me a bit... so I'll study thoroughly the method before, wainting if entel releases a firmware update in the meanwhile... but as I read somewhere entel is not too active in releasing updates :/, and I like to test different ROMs. Although with the hardware aceleration features of the Samsung firmwares and the fact that I like how it work in general (hated motoblur on my previous phone), I'm not sure if I will test many ROMs but certainly I like to keep my phone updated.
Thanks again for the answer!
Mguel
PS: we should start some sort of chilean SGS2 community.
Click to expand...
Click to collapse
I think I have had bad luck and got problems, because I tend to reset to factory settings when upgrading the device.
So you can see that even if there are problems, like in my case, you can bypass them and get everything working. That is what makes me really happy and confident about the SGS2.
It looks like there is now a boot loop sticky thread with different instructions by pulser_g2: http://forum.xda-developers.com/showthread.php?t=1108499
Ok, so far so good.
I'm doing step four of your sequence...
I didn't get any loops, but I got stuck on factory reset until I realized that I should have removed the SD-Card and the SIM-Card :/... after that the factory reset went smoothly, and now I'm with the "vanilla/stock/entelless" firmware!!!
Happy to see the samsung boot screen animation and not the dull and flat entel logo.
If I do a *#1234# I get:
PDA: I9100XWKE7
PHONE: I9100XXKE4
CSC: I9100XEUKD1
Build Info: Wed May 18 16:08:22 KST 2011
So I suppose I did it fine
Now I'll root it.
Thanks again zyxeu
Now also rooted!
So I'll be able to install Titanium Backup!! I was missing it (3 days without it )
Now I'll add Entel's APN, add google account, reinstall apps... etc (with frequent CWM backups)
Edit: strange... the APNs are there... the same that where set when just bought the phone: bam.entelpcs.cl. OT: do you know the difference between using the bam.entelpcs.cl or the imovil.entelpcs.cl (with my previous phones I use the imovil. I believe with my first android I used the bam one until on the browser I start having a sort of entel toolbar on top all the time and on all pages... switching to imovil solved that issue)
mguel said:
Now also rooted!
So I'll be able to install Titanium Backup!! I was missing it (3 days without it )
Now I'll add Entel's APN, add google account, reinstall apps... etc (with frequent CWM backups)
Edit: strange... the APNs are there... the same that where set when just bought the phone: bam.entelpcs.cl. OT: do you know the difference between using the bam.entelpcs.cl or the imovil.entelpcs.cl (with my previous phones I use the imovil. I believe with my first android I used the bam one until on the browser I start having a sort of entel toolbar on top all the time and on all pages... switching to imovil solved that issue)
Click to expand...
Click to collapse
Congratulations, now others can follow your steps too.
It looks like BAM is for WAP devices and IMOVIL for devices which browser can handle full HTML, e.g. look under "¿Qué es una APN?" here:
http://ayuda.entelpcs.cl/PortalAyud..._nfpb=true&_pageLabel=P4801255431229114952095
zyxeu said:
Congratulations, now others can follow your steps too.
It looks like BAM is for WAP devices and IMOVIL for devices which browser can handle full HTML, e.g. look under "¿Qué es una APN?" here:
http://ayuda.entelpcs.cl/PortalAyud..._nfpb=true&_pageLabel=P4801255431229114952095
Click to expand...
Click to collapse
You're right thanks again!
PS: I would suggest (for reference for others) to edit the post where you number the steps you used, and add something like:
3.) Remove SD and SIM card and then did a full reset *2767*3855# to reset the internal CSC to XEU
Click to expand...
Click to collapse
or add it at the beggining, but I at least, couldn't do/finish the factory reset until I removed both cards.
mguel said:
You're right thanks again!
PS: I would suggest (for reference for others) to edit the post where you number the steps you used, and add something like: or add it at the beggining, but I at least, couldn't do/finish the factory reset until I removed both cards.
Click to expand...
Click to collapse
Done.
Thanks for the comment.
Great!
By the way having the XWKE7 should make future update process easier I believe… It won't be necesary to wipe user data/factory reset since we will be keeping the same CSC, or not?
mguel said:
Great!
By the way having the XWKE7 should make future update process easier I believe… It won't be necesary to wipe user data/factory reset since we will be keeping the same CSC, or not?
Click to expand...
Click to collapse
Yes, you are right.
Chainfire has found a Samsung bug ("To those interested, the problem was faulty filesystem creation in init.rc ... in other words, Samsung made this issue.") that leads to the loop. He fixed the issue in his CF-root latest v.3.7 kernel: http://forum.xda-developers.com/showthread.php?t=1103399&page=34
kei_kusanagi published also the remaining Chilean firmware version codes:
kei_kusanagi said:
EntelPCS Chile:
I9100UHKE1/I9100CHEKE1/I9100UHKE1/I9100UHKE1
ProductCode=CHE
Movistar Chile:
I9100UHKE4/I9100CHTKE3/I9100UHKE2/I9100UHKE4
ProductCode=CHT
Claro Chile:
I9100UHKE2/I9100CHLKE3/I9100UHKE2/I9100UHKE2
ProductCode=CHL
Chile Unbranded:
I9100UHKE2/I9100CHOKE1/I9100UHKE2/I9100UHKE2
Product Code: CHO
Click to expand...
Click to collapse
http://forum.xda-developers.com/newreply.php?do=newreply&p=14465711
http://forum.xda-developers.com/showpost.php?p=14688503&postcount=43
zyxeu said:
Chainfire has found a Samsung bug ("To those interested, the problem was faulty filesystem creation in init.rc ... in other words, Samsung made this issue.") that leads to the loop. He fixed the issue in his CF-root latest v.3.7 kernel: http://forum.xda-developers.com/showthread.php?t=1103399&page=34
Click to expand...
Click to collapse
So maybe that was the cause of the problems I had on the Factory Reset step, instead of not having removed the sd & sim card...
The bug has to do with the "Factory Reset problem"... so if I'm not planning to do another factory reset (at least before updating to a new firmware to come)... is there a need to flash the same firmware version?... do the bug causes any other problem? (I searched and I didn't find info on other problems that it could cause)
thx for the guide!!! it helped me a lot,
i didnt had the bootloop all worked fine and fast
PDA: I9100XWKE7
PHONE: I9100XXKE4
CSC: I9100XEUKD1
Build Info: Wed May 18 16:08:22 KST 2011
Bacán ver chilenos aquí....
Nice to see chilean out here!!!
lauchon said:
Bacán ver chilenos aquí....
Click to expand...
Click to collapse
Estamos bien los 33 en el refugio con una galaxy s2 ctm!!!!
jajajaja
PS: Chilean joke
Related
Button Combos:
Download Mode: Volume Down+Home+Power
Recovery Mode: Volume Up+Home+Power
Once in recovery use volume keys to navigate, home button to select and power button to go back
Official Firmware Version
PDA: I9100MUGKG2
Phone: I9100MUGKG2
CSC: I9100MBMCKG2
Product Code: GT-I9100LKMBMC
Unlock
Galaxy_S Unlock App by Helroz found here https://market.android.com/details?id=com.helroz.galaxysunlock&feature=search_result.
Rooting
CF-Root Thread: http://forum.xda-developers.com/showthread.php?t=1103399
We do not have a CF-Root version of our kernel so just flash any kernel using the instructions provided in the link and flash the stock kernel back (found below). Root will remain as well as the CWM app but you will loose clockwork mod recovery.
Alternative method:
Zergrush exploit: http://forum.xda-developers.com/showthread.php?t=803682&highlight=zegrush
Yellow Triangle Removal
Tutorial can be found here: http://forum.xda-developers.com/showthread.php?t=1193091
Alternatively you can use a Jig as it also resets the custom Rom counter
I9100 Secret Codes
http://forum.xda-developers.com/showthread.php?t=1193285
All links below are for Gingerbread 2.3.3 MUGK2
Stock Bell/Virgin Modem
Directions: Use Odin and place .tar file in "phone" section
Download
Mirror: Download
Stock Firmware
Download
Mirror: Download
Stock Kernel
Directions: Place .tar file in PDA section using ODIN
Download
Mirror: Download
Bell CSC
Directions: Flash with Odin in CSC section
Download
Mirror: Download
Additional Modems:
Some users are experiencing better Gps/Reception with the KH3/KI3 modem
Directions: Unzip file and flash modem.bin with Odin under "phone" section
I9100XXKH3-Download
I9100XXKG6-Download
I9100XXKI1-Download
I9100XXKI3-Download
I9100XXKI4-Download
*CWM Compatible Modems can be found here
Flashing Instructions
How to install the latest firmware on your phone. This will also get rid of Bell's bloatware:
1) Make sure you have working drivers installed on your computer. If you do not, the easiest way is to download Kies and it will install it for you.
2) Install Odin 1.85 on your computer (attached at the bottom of this post)
3) Pick any firmware version you would like to flash from Intratech's thread linked here. The firmware is arranged from oldest to newest so the last ones are obviously going to be the newest.
4) Start Odin in "administrator" mode and make sure Kies is not running in the background. Use task manager to check
5) Place your downloaded firmware .tar or .md5 file into the PDA section in Odin. Make sure re-partition is not selected. Auto reboot and reset time should be selected by default.
6) Remove any external sd cards and the sim card from your phone (precaution) then reboot into download or hold volume down + home + power key. If a warning pops up press the volume up key to continue.
7) Connect your phone to the computer with the USB cable. You should see the I.D:Com port turn yellow.
8) Once you are certain everything is where it should be, select START. Once the process has completed your phone will re-boot. Exit out of Odin. That's it!
Optional (Rooting)
9) If you wish to root your will need to download a cf-root kernel that matches the firmware you just flashed from here. For example if you flashed XXKI4 then you will need to download the cf-root kernel that ends with XXKI4
10) Restart Odin and place the kernel .tar file in the PDA section, connect your phone and press START.
Alternative TWlaunchers
Since upgrading to 2.3.4/2.3.5 firmwares, some (including myself) have noticed some lag/stuttering when flipping through homescreens. I find that this gets worse when using the program monitor widget. I put together some alternatives that I pulled from the US variants of the Galaxy S2.
I have tested them and they have pretty much eliminated the issue. I personally find them much smoother. These are stock Twlaunchers with no mods. The files can be found at the bottom of this post. Requires Root.
Directions: These files a deodexed but will work with Odexed Firmwares (I tested on 2.3.5) Make sure to download another launcher and use it as your primary. While using an alternative launcher, back up the twlauncher.apk and .odex files under system app then the libglcanvas.so under system/lib. Then delete twlauncher.odex. Boot into CWM recovery and flash the new twlauncher. If you do not have CWM recovery you can also unzip the file and drop the .apk into system/app and the .so into system/lib.
AT&T
App version: 2.3.4
Features: Long press on menu button brings up search. Endless scrolling through home screens. Option to set app drawer alphabetically.
Epic 4G Touch (Sprint)
App version: 2.3.4
Features: Option to set app drawer alphabetically.
T-Mobile Galaxy S2 (Hercules)
App version: 2.3.5
Features: Long press on menu button brings up search. Endless scrolling through homescreens and widget selection screen. Option to set app drawer alphabetically.
credits: Intratech, x-cimo
Is there a way to turn off the sound (music) when the SGS2 starts?
mpsrent said:
Is there a way to turn off the sound (music) when the SGS2 starts?
Click to expand...
Click to collapse
There is no sound when the phone is in vibration/slient mode.
How to root sgs2 from BELL (GT-9100M)?
details steps plz for a beginner
turki_00 said:
How to root sgs2 from BELL (GT-9100M)?
details steps plz for a beginner
Click to expand...
Click to collapse
-Download and install ODIN on your PC.
-From XDA, download the kernel CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip(ZIP.File)
-unzip the above file and it will unzip itself to CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.tar (TAR File)
-Fire up ODIN and under 'PDA' browse to the above mentioned .tar file.
-Place your phone on download mode (either USB jig, or boot it up while holding vol down+home+power)
-once in download mode, plug in to the computer.
-everything should be default settings in ODIN,butmake sure repartition and flashlock IS NOT ticked.
-click start
http://forum.xda-developers.com/showthread.php?t=1075278
DONE
BTW, Im not sure if this is just for Rogers users but I tried disabling 'fast dormancy' and it actually slowed down my upload link connection. Not sure about Telus, or Bell users but it would be worth a shot to test as it helps drastically with battery life.
SMS Time Stamp Fix
I'm sure most already knows this but just I just wanted to post this here.
For anyone on the Rogers network (or any network that is affected) that is experiencing their text messages coming in 4 hours behind, download this free app in the market called time stamp fix and set the offset hours to 4. Link: https://market.android.com/details?id=com.mattprecious.smsfix&feature=search_result
KayvinM said:
http://forum.xda-developers.com/showthread.php?t=1103399
Currently the best 3 choices that is closest to our firmware version are:
CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip
CF-Root-SGS2_JP_XSG_KG2-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KG2-v4.1-CWM4.zip
Note: You will not be able to revert back to the stock kernel until Samsung releases our Firmware
Click to expand...
Click to collapse
CF-Root-SGS2_XX_OXA_KG2-v4.1-CWM4.zip is not even close to our version of android. It is a 2.3.4 kernel. Just because it says KG2, doesn't mean it's the same. That only refers to a single geographical area's release for a month. I'll explain:
The rom letter versions are actually based upon 5 letters, not 3. There are several variants of KG2. Basically, the Samsung naming convention is as follows:
Model name: I9100M
Provider/Area: UG (Bell/Virgin/Sasktel)
Rom Version: KG2
Now, the rom version can get broken down into each letter as well...
K = 2011
G = July
2 = 2nd version that month.
All area's roms are developed completely separate from each other...
Ours is UGKG2. Which is unavailable for download from the Samsung servers, so we're not able to actually get back to stock, or make any kind of custom firmwares/kernels based upon it.
All the other ones, including ZS, JP, and XX are completely different roms and kernels than what we have on our Bell phones.
The KG2 that either of those 3 kernels are based on are either 2.3.4 roms or different 2.3.3 roms. So, matching that is no different than installing a KG1 or KG3 or any KF* CF-Root kernels. ChainFire has not made a CF-Root based upon UGKG2 yet, so no matter what one you install, it's not based upon our rom, meaning you can basically install ANY CF-Root Kernel and as long as your phone still works with it, it doesn't matter. All the roms are completely different and the naming convention has nothing to do with each other unless all 5 letters/numbers match up.
Lesson of the night???? Just because a pile of uninformed people on a forum agree about something, it doesn't make it correct...
KayvinM said:
I'm sure most already knows this but just I just wanted to post this here.
For anyone on the Rogers network (or any network that is affected) that is experiencing their text messages coming in 4 hours behind, download this free app in the market called time stamp fix and set the offset hours to 4. Link: https://market.android.com/details?id=com.mattprecious.smsfix&feature=search_result
Click to expand...
Click to collapse
I have also found that upgrading KG3+ will solve the issue.
Electroz said:
CF-Root-SGS2_XX_OXA_KG2-v4.1-CWM4.zip is not even close to our version of android. It is a 2.3.4 kernel. Just because it says KG2, doesn't mean it's the same. That only refers to a single geographical area's release for a month. I'll explain:
The rom letter versions are actually based upon 5 letters, not 3. There are several variants of KG2. Basically, the Samsung naming convention is as follows:
Model name: I9100M
Provider/Area: UG (Bell/Virgin/Sasktel)
Rom Version: KG2
Now, the rom version can get broken down into each letter as well...
K = 2011
G = July
2 = 2nd version that month.
All area's roms are developed completely separate from each other...
Ours is UGKG2. Which is unavailable for download from the Samsung servers, so we're not able to actually get back to stock, or make any kind of custom firmwares/kernels based upon it.
All the other ones, including ZS, JP, and XX are completely different roms and kernels than what we have on our Bell phones.
The KG2 that either of those 3 kernels are based on are either 2.3.4 roms or different 2.3.3 roms. So, matching that is no different than installing a KG1 or KG3 or any KF* CF-Root kernels. ChainFire has not made a CF-Root based upon UGKG2 yet, so no matter what one you install, it's not based upon our rom, meaning you can basically install ANY CF-Root Kernel and as long as your phone still works with it, it doesn't matter. All the roms are completely different and the naming convention has nothing to do with each other unless all 5 letters/numbers match up.
Lesson of the night???? Just because a pile of uninformed people on a forum agree about something, it doesn't make it correct...
Click to expand...
Click to collapse
Lesson learned and post edited. Thank you for bringing it to my attention.
I have a friend with a Bell branded GS2 which he unlocked by buying a code to use on the Telus network. He wants me to upgrade it to 2.3.4 for him this weekend, but doesn't want it rooted.
I have an international unbranded GS2 and have flashed numerous firmwares. I have kept mine unrooted and have only flashed official leaked firmware via Odin (no custom ROM's). Can I update his the same way without rooting? I realize his model number will change (GT-I9100m to GT-I9100) and that he won't be able to go back until the Bell ROM is posted. I'm just not sure if there is any difference because his phone is branded and mine isn't.
No difference at all. Go ahead and install 2.3.4. Our phones are exactly the same as the international version. It's an I9100M due to Bell's firmware.
Sent from my GT-I9100M using XDA App
I am a TELUS customer with a Bell SGS2, and everyone I call or who calls me experiences an echo on their end. I did some research and found that it was actually my phone that was the problem. People said they were able to rectify the problem by disabling "Noise Cancellation", however, the only way I've been able to find to disable it is within the call itself, which means I have to disable it in every call.
Does anyone know how to disable Noise Cancellation permanently? Thank you!
Hi KayvinM and Electroz, I'm from Canada and I ordered my S2 from Newegg.ca, so my phone came factory unlocked and right now I'm running it on the Telus Network.
My phone is running on the UK firmware but I would like to use a North American firmware.
My questions is that would I be able to run any firmware from any region I want without damaging my phone?
And witch firmware is the latest one for the Canadian region?
Here's the details for my SCS2:
PDA: I9100XWKF3
Phone: I9100XXKE7
CSC: I9100XEUKD1
I posted a thread about this yesterday but I didn't get much help, so I really appreciated if you guys can help me.
Thanks in advance.
Sobai said:
I am a TELUS customer with a Bell SGS2, and everyone I call or who calls me experiences an echo on their end. I did some research and found that it was actually my phone that was the problem. People said they were able to rectify the problem by disabling "Noise Cancellation", however, the only way I've been able to find to disable it is within the call itself, which means I have to disable it in every call.
Does anyone know how to disable Noise Cancellation permanently? Thank you!
Click to expand...
Click to collapse
Weird thing is I had this exact issue a couple of days ago. What kernel do you have installed at the moment?
id_mew said:
Hi KayvinM and Electroz, I'm from Canada and I ordered my S2 from Newegg.ca, so my phone came factory unlocked and right now I'm running it on the Telus Network.
My phone is running on the UK firmware but I would like to use a North American firmware.
My questions is that would I be able to run any firmware from any region I want without damaging my phone?
And witch firmware is the latest one for the Canadian region?
Here's the details for my SCS2:
PDA: I9100XWKF3
Phone: I9100XXKE7
CSC: I9100XEUKD1
I posted a thread about this yesterday but I didn't get much help, so I really appreciated if you guys can help me.
Thanks in advance.
Click to expand...
Click to collapse
Hey id_mew, you can run any firmware you would like without damaging your phone. Just make sure you read up lots and you are comfortable with the process and using Odin. Also avoid using any .pit files when flashing unless it's called for. All the firmwares can be found in this thread http://forum.xda-developers.com/showthread.php?t=1075278 As off right now the latest canadian firmware is bell's/virgin UGK2 which is 2.3.3 based. Problem is if you are not currently on this firmware, you wont be able to flash it because it hasn't been released yet. As to my knowledge the latest official firmware is XXKG5 (poland based) and KG7 (Brazil) which was released earlier this month. Here is one the threads I found regarding ithttp://forum.xda-developers.com/showthread.php?t=1200044 As far as I understand there is no difference between the European and the Canadian version of the sgs2. Both phones make use of the same cell tower frequencies, meaning you should have no issues running a european based firmware here in canada. It just comes down to personal preference. Hope I was able to help
KayvinM said:
Weird thing is I had this exact issue a couple of days ago. What kernel do you have installed at the moment?
Click to expand...
Click to collapse
PDA: I9100XXKG5
PHONE: I9100XXKG5
CSC: I9100OXAKG5
Kernel: [email protected] #20
I only flashed the kernel yesterday which made my battery life so much better (20 hours of use with data/wifi/gps turned off most of the time) but still had echo problems before flashing the Kernel. I know its the noice reduction feature because when I disable the feature the person I'm speaking to no longer hears the echo. I just wish I knew how to disable it for good, rather than every time I answer a call.
As many of us is waiting for UGKG2 the stock bell rom, will it be available eventually? Quite a few people I know need that rom to revert so the phone can be send back for repair if need be.
Sent from my GT-I9100M using XDA Premium App
shuweee said:
As many of us is waiting for UGKG2 the stock bell rom, will it be available eventually? Quite a few people I know need that rom to revert so the phone can be send back for repair if need be.
Sent from my GT-I9100M using XDA Premium App
Click to expand...
Click to collapse
It's whenever Samsung plans to make it available. They might someday, or they may never. Other cellular firmwares are readily available, so I don't see why the Bell firmware won't. My guess is that the firmware will probably be released when Bell releases a new firmware with 2.3.4.
So where is this site or server that I can go check for firmwares
Sent from my GT-I9100M using XDA Premium App
Hey everyone,
First post, n00b question - please be gentle.
First, I'll start with a positive. I have come from using an iPhone, and I was quiet comfortable with jailbreaking and cydia. I now have a Samsung Galaxy S 2 / II (GT-I9100T). I am from Australia, and on the Telstra network. Whoever is in the same boat would know it is quiet an adjustment, but you can root! (if you wanted to know).
I followed this persons 3 part guide and with sucess:
I cannot post the link but it is on YouTube and the video title is:
How To Root The Samsung Galaxy S II - Part 1
How To Root The Samsung Galaxy S II - Part 2
How To Root The Samsung Galaxy S II - Part 3
Username is mattj101101
I had Android 2.3.3 installed.
Second part is a question, is there any debranding roms / kernals that is ok for the GT-I9100T? I have tried the *#272*IMEI# but it only had 'Preconfig - TEL'
My phones info:
PDA: 19100TDVKF4
PHONE: I9100TDVKF2
CSC: I9100TTELFK3
My Kernal version, after the root is 2.6.35.7-I9100XWKDD-CL161513root<insertATsymbol>DELL103 #2
Hopefully with these answers I can help other fellow people out with this particular model (that are sold in Australia). Also if someone has the stock Telstra rom for re-flashing (if needed for warrenty) please point me in the right direction.
Thank-you.
Hey,
Ive got the GT-I9100T from Vodafone (both can run on the telstra bandwidth now ) and have had no issues flashing most roms. Only thing you may notice is the new modems aren't as good as the stock ones you currently have, so you may need to reflash the original modem through odin to get the best support.
Before you do flash though, make sure you back up your /efs folder, it contains the bin files for your IMEI for your phone, and people have reported flashing a rom can change that, so beware! also, before you do flash, try find the stock telstra rom for your phone incase you need to reflash. There are a few threads about it all, so good luck
The i9100T can use i9100 roms, but it will change the product code to i9100.
Easiest way to root is using CF-root, match the part of the version number in bold "PDA: 19100TDVKF4"
My phones info:
PDA: The rom/kernel
PHONE: The modem/radio, responsable for signal quality and speed, you dont need to match this to rom version, and the best way to find a good one is to test different ones.
CSC: APN settings and bundles apps, no need to match this, but if you do chose to all you may have todo is enter your APN settings for internet and MMS manually.
You can flash any rom onto any SGS2 via odin, see this guide, that will debrand etc.
Also, you rooted using a very old insecure kernel, people have had random reboots with that one, I suggest you flash back your stock kernel (you will keep root) or flash a version of cf-root (you will gain clockworkmod recovery, a way to flash roms/etc from your phone, and nandroid, a whole phone backup system, like snapshots)
I would recommend flashing DarkyRom2 on your S2. Runs fast, stable and great battery life. It roots your phone as well and changes your kernel to SuperCore which has a lot of optimisations.
Instructions:
Since you're not rooted (stock firmware/kernel)
1. Flash SuperCore_1.7.tar with Odin (put in PDA and do NOT tick repartition)
2. Get DarkyROM2 Tool and Superuser from market
3. Upload DarkyROM2_XXKH3_Base_R2.zip to SD-Card (INTERNAL)
4. Open DarkyROM2 tool. Accept SuperUser access request notification (this confirms you are rooted.
4. Under the DarkyRom tab, be sure "Wipe User data" is selected AND "INSTALL MODEM" is NOT SELECTED. (this will wipe everything from your phone but keep your stock KF4 modem. Any other modem causes signal problems for our I-9100T. )
5. No need to select "Install Kernel" Since SuperCore 1.7 is already installed.
5. Go back to the General Tab and use "Flash/Install File from SDCARD" to browse to and install DarkyROM2_XXKH3_Base_R2.zip
6. Wait for the phone to reboot and flash the new firmware
Get the files here:
http://www.darkyrom.com/community/index.php?threads/rom-cwm-sgs2-darkyrom2-kh3-base.4950/
I modified the instructions given on that link and posted it above for you since it's a little different for our I-9100T phones.
more info on I-9100T here:
http://forum.xda-developers.com/showpost.php?p=16824749&postcount=10
Interestingly, I just purchased a SGS2 here in Thailand (I'm also an Aussie) and the model of the phone is GT-I9100T.
Unfortunately I cannot seem to find a KL2 kernel for CF-Root to patch it with... any suggestions?
Also, the site that held all the OEM kernels (MultiUpload) for download is now showing a "Shut down by the FBI" logo : )
As long as you're certain you've got a I9100T, use the KL1 CFRoot kernel. Will work fine.
ApriliaM3 said:
Interestingly, I just purchased a SGS2 here in Thailand (I'm also an Aussie) and the model of the phone is GT-I9100T.
Unfortunately I cannot seem to find a KL2 kernel for CF-Root to patch it with... any suggestions?
Also, the site that held all the OEM kernels (MultiUpload) for download is now showing a "Shut down by the FBI" logo : )
Click to expand...
Click to collapse
My phone details are as follows:
Model: GT-I9100T
Android: 2.3.6
Baseband: I9100TDCKL1
Kernel: 2.6.35.7-I9100TDCKL2-CL767350 [email protected]#2
Build: GINGERBREAD.DCKL2
This is not an Aussie phone such as the Telstra I9100T that I see spoken about.
I purchased this phone here in Thailand 3 days ago and I have a few questions.
1. Is there a way to backup the original kernel before rooting?
2. Will the KL1 kernal make me lose things such as Thai language options etc?
3. Any way to restore the KL2 kernel in the future?
Thanks for taking the time to reply!
MistahBungle said:
As long as you're certain you've got a I9100T, use the KL1 CFRoot kernel. Will work fine.
Click to expand...
Click to collapse
1) Doubt it. And the only link for DCKL2/Thailand in Intra's official firmware thread is dead as it was MegaUpload, and he more than likely won't have a backup (you could always ask him tho). Search around elsewhere online, you might find a copy of this kernel somewhere.
2) I don't know for certain, but I don't think so. I would have thought something like language would be more firmware-related.
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service from Samsung, all you'd need to do is flash the most recent firmware available for your phone (for all they know you could easily have got this from an OTA update via Kies), do a factory reset/make sure there's no apps left on your phone that could tip off whomever repairs it that the phone was rooted, and use a jig to reset the flash counter. Obviously there are no rolled gold guarantees with getting warranty service once you've voided same by rooting the phone/running non-stock firmware firmware on it, tho.
ApriliaM3 said:
My phone details are as follows:
Model: GT-I9100T
Android: 2.3.6
Baseband: I9100TDCKL1
Kernel: 2.6.35.7-I9100TDCKL2-CL767350 [email protected]#2
Build: GINGERBREAD.DCKL2
This is not an Aussie phone such as the Telstra I9100T that I see spoken about.
I purchased this phone here in Thailand 3 days ago and I have a few questions.
1. Is there a way to backup the original kernel before rooting?
2. Will the KL1 kernal make me lose things such as Thai language options etc?
3. Any way to restore the KL2 kernel in the future?
Thanks for taking the time to reply!
Click to expand...
Click to collapse
I was just worried it might stop future updates to ICS or similar via Kies.
At least I think I've managed to find another copy of the latest kernal on a site other than MegaUpload...
It's at 50% and counting : )
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service
Running a CFRoot kernel over stock firmware should still allow you to receive OTA updates via Kies. If you find it doesn't, simply use Checkfus (search for it on here), it allows you to find/download the latest firmware for your phone/country that you'd normally get via Kies.
Really ? Cool Might wanna post a linky to your source over in Intra's thread. I'm sure there will be other people who might need it at some stage.
ApriliaM3 said:
I was just worried it might stop future updates to ICS or similar via Kies.
At least I think I've managed to find another copy of the latest kernal on a site other than MegaUpload...
It's at 50% and counting : )
3) Refer to 1) I don't see why you'd need to ? In order to get warranty service
Click to expand...
Click to collapse
Ok so would you believe...
I ran the guide from Intra.
Installed an insecure ROM and then ran SuperOneClick and was rooted.
I restored the OEM kernel that I found online and BINGO - UNROOTED!
I repeated the procedure just to check everything again... same deal!
Phone is currently unrooted again...
MistahBungle said:
Running a CFRoot kernel over stock firmware should still allow you to receive OTA updates via Kies. If you find it doesn't, simply use Checkfus (search for it on here), it allows you to find/download the latest firmware for your phone/country that you'd normally get via Kies.
Really ? Cool Might wanna post a linky to your source over in Intra's thread. I'm sure there will be other people who might need it at some stage.
Click to expand...
Click to collapse
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
There's a procedure for removing the yellow warning triangle at boot in the CFRoot thread & also retaining root, but I found it too fiddly when I first rooted my phone so I simply bought a jig & did it that way.
I can't speak for anything to do with SuperOneClick as I've never used it.
ApriliaM3 said:
Ok so would you believe...
I ran the guide from Intra.
Installed an insecure ROM and then ran SuperOneClick and was rooted.
I restored the OEM kernel that I found online and BINGO - UNROOTED!
I repeated the procedure just to check everything again... same deal!
Phone is currently unrooted again...
Click to expand...
Click to collapse
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
MistahBungle said:
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
QUOTE]
Click to expand...
Click to collapse
As I said, I have no idea whatsoever about anything to do with SuperOneClick. If you want a rooted phone minus the yellow warning triangle at boot without fiddling around, root it with a CFRoot kernel, buy a $3 jig from eBay, done.
So far as Kies not working, you could try uninstalling/reinstalling Kies, or simply use Checkfus as I've said previously. Me, I'd use Checkfus. Quick, easy & like the paragraph above, no fiddling around.
Edit to add - Yes, obviously Kies won't work if you're running an "insecure rom" as per your post above. I presume you mean a custom rom you found somewhere on here or elsewhere ? One of my earlier posts did say Kies should (not always) work if you're running a rooted kernel over a stock Samsung rom. If you're running a non-stock rom Kies won't work.
ApriliaM3 said:
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
Click to expand...
Click to collapse
ApriliaM3 said:
Apparently so... now I'm confused about what the guide was trying to achieve.
Also, Kies now tells me it's not compatible with my device... Perfect!
MistahBungle said:
Yeah, if you flash an original (unrooted) kernel over your rooted kernel you'll lose root.
QUOTE]
Click to expand...
Click to collapse
Ditch Kies there is a better alternative out there. MyphoneExplore, do a seach via google. You'll also need to get the app client software from the android market. I use it to synch my work Outlook Calendar to my phone. You can also back up your contacts, sms and call records.
Click to expand...
Click to collapse
Edit: I tried CF-Root KL3 (wanted KL2) and it seems fine so far.
I have root and everything else seems the same (Thai language support etc.)
I'll keep you posted : )
Thanks for taking the time to deal with my issues!
Hope I can do the same for some others on this Forum in the future.
I'd not heard of Checkfus so I'll give that a try, thanks : )
There's no CF-Root to match my phone exactly but I guess there's nothing to lose now by trying something close : P
I ordered the jig almost a week before getting the phone but it seems the postage to Thailand is sloooow.
I'm running a stock ROM and unrooted but Kies is still misbehaving.
MistahBungle said:
As I said, I have no idea whatsoever about anything to do with SuperOneClick. If you want a rooted phone minus the yellow warning triangle at boot without fiddling around, root it with a CFRoot kernel, buy a $3 jig from eBay, done.
So far as Kies not working, you could try uninstalling/reinstalling Kies, or simply use Checkfus as I've said previously. Me, I'd use Checkfus. Quick, easy & like the paragraph above, no fiddling around.
Edit to add - Yes, obviously Kies won't work if you're running an "insecure rom" as per your post above. I presume you mean a custom rom you found somewhere on here or elsewhere ? One of my earlier posts did say Kies should (not always) work if you're running a rooted kernel over a stock Samsung rom. If you're running a non-stock rom Kies won't work.
Click to expand...
Click to collapse
Something may have borked so far as the CSC goes (which tells Kies, the Market, etc where you are). I did say you should be able to use Kies, you're not the first person to have problems with it after rooting
Personally speaking, I've never used Kies & almost certainly won't use it. Ever. Custom roms/kernels are a piece of you know what to flash via CWRecovery (or Odin for that matter), and official firmware updates are easy to get with Checkfus & flash via Odin if I ever have to go down that path for warranty purposes or whatever.
Kies is a truly awful piece of software
Edit to add after your edit - No worries
ApriliaM3 said:
I'd not heard of Checkfus so I'll give that a try, thanks : )
I'm running a stock ROM and unrooted but Kies is still misbehaving.
Click to expand...
Click to collapse
Yeah Kies is dodgy...
When I got home I plugged it into Kies on the home PC and everything was fine!
Have you experimented much with any Custom ROM's?
MistahBungle said:
Something may have borked so far as the CSC goes (which tells Kies, the Market, etc where you are). I did say you should be able to use Kies, you're not the first person to have problems with it after rooting
Kies is a truly awful piece of software
Click to expand...
Click to collapse
Hi Guys,
My Galaxy S2 came with KE7 I bought it in the UK and it's not branded to any network, I flashed CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 and then the stock kernel and all was good.
A while later I tried to flash the clockworkmod from http://forum.xda-developers.com/showthread.php?t=1118693 ... that flashed OK but I couldn't get into the CWM recovery so I flashed the CF-Root back.
The recovery menu now works, but I still have the warning triangle on boot (I have tried reflashing the stock kernel again). This in itself doesn't bother me too much - I did this a month or 2 ago.
I've been told by someone that there is an upgrade available via Kies, however when connecting the phone Kies on Windows just tries to connect for ages and then gives up. (I have disabled USB debugging). Not that it should be relevant but I have previously removed Kies.apk, KiesAir.apk and kieswifi.apk using g-script but I put these back before trying to do this.
My phone currently reports:
Android: 2.3.3
Baseband: I9100XXKE4
Kernel: 2.6.35.7-I9100XWKE7-CL215725 [email protected] #2
Build: GINGERBREAD.XWKE7
Looking at these values, is the mix of XX and XW correct? (It's possible that I might have downloaded the wrong CF-root version the second time)
All I would really like to do is get the official version Samsung version and then root the phone. I believe that the Kies upgrade would still keep all applications.
Any help would be much appreciated.
You can find official, stock roms in the development threads
Sent from my GT-I9100
Thanks.
I've seen the thread http://forum.xda-developers.com/showthread.php?t=1075278 but I'm not sure which is the correct stock firmware for me.
Given the other issues I've described above I'm a bit 'concerned' that I've already done something wrong :S
EDIT:Re-editting my post cos Im blind and cant read good
Sorry dude I got all screwed-up there I have ta apolagize.Anyway you can download the one i told you and all will be cool as its a UK+Europe generic as stated and its XWKF3 but you are indeed on KE7 and you will find it here
http://forum.xda-developers.com/showthread.php?t=1075278
its XWKE7 ,Build Date 18/05/2011 generic XEU
.TO root go to this link.
http://forum.xda-developers.com/showthread.php?t=1103399
its a kernel flash via odin that takes,from hitting the start button,about 10 seconds to complete.It roots and puts CWM on your phone.The kernel you want is one of the first ones (xx-xeu-ke7).You Cant go wrong its all explained.
EDIT: You can also check to see if it really is unbranded by checking your product code by typing this number and checking the last 3 letters of your code *2767*4387264636#
Thanks very much. The PCode I have is GT-I9100LKAXEU.
I'm going to try the latest KI3 and see how that goes, failing that I'll reflash the I9100XWKE7_I9100XXKE4_I9100XEUKD1 I've just got (I note that this lists KE4 and KE7 in the filename, which does match the version I currently have).
The important part about your code is the XEU which is your local CSC.this is recognized by kies when you connect.The first thing Kies does when you connect is rcognize this code to identify the phone and look for the appropriate firmware update.When you flash a new firmware if its not official obviously kies wont understand it cos it doesnt register.Your Product Code says your phone is a UK model (XEU) so for example if you flash an official firmware and by default the phone sets KOR then kies has 2 conflicting CSCs and thus might decide not to connect.If you want your phone to work properly on kies then when you flash an official FW make sure you have XEU selected as your CSC marking *#272*(IMEI)# this will then reboot your phone although its always good to do a factory rest too.Do this anyway although not on an official FW as it might not always set the CSC to your area so it pays to check.
This is what Kies looks at for an upgrade .
http://forum.xda-developers.com/showthread.php?t=1089874
Spoof FW Check Fus may be worth a search also.
jje
so the long story well done to the short version is I just bought the galaxy S2 in China. It was supposed to be a European version. But the manuals were from the Arabian Peninsula and it is not in the original configuration. the question is: can I easily get it back to its original configuration and is it worth doing so?
It's been flashed or routed I'm not sure what the differences with the combination of English/Western-based programs and Chinese-based programs. It doesn't suffer from the afflictions of the legit Chinese copies that don't have the Google apps, although they have been blocked. ( just came to Hong Kong for a few days so I know that they working)
What is missing: Swype ( the manuals mention this) and other Samson apps. I honestly don't know what I'm missing out on widgets etc. because they're not there. Samsung app store is only in Chinese
What's extra: a bunch of Chinese bloatware/crapware and an app called "super share" that the antivirus program LookOut labels as malware. this really concerns me considering how linked the phone is with Google. it cannot be uninstalled even with other uninstaller programs. this goes the same for many of the Chinese apps including the Chinese version of Opera.
I wrote a post about it here (edit it won't let me post a link. Just search metafilter.com for "newbie Samsung android astrill" to find the post)
I'm incredibly naïve about all of this and of devoted as much free time as I can to try to solve this problem. the phone also has the clockwork mod and Odin. As outlined in the linked post I tried Odin but then it just froze for several hours. I looked online and it looks like I am supposed to something my computer also but it's so incredibly complex I'm afraid to mess it up.
Should I try the clockwork mod to restore to factory defaults? Will it?
Before I do this , is there any easy way to get any pictures/videos I've taken off of the phone and or otherwise backup the apps? (I've purchased a few.)
finally, as a side note the battery only seems to last for about five hours under sustained use. Was I taken in that they switched out the battery?
sorry for so many questions. Spent a total of 20+ hours on this now with no good results and only going deeper and deeper in the rabbit hole. I just wanted to avoid going to iPhone, but didn't imagine it would be so difficult. I was expecting that I was going to get a true European version of the phone when I bought it.
Should I try the clockwork mod to restore to factory defaults? Will it?
Factory defualts = last firmware flashed not original firmware .
Before I do this , is there any easy way to get any pictures/videos I've taken off of the phone and or otherwise backup the apps? (I've purchased a few.)
Pics Video copy and paste through the usb cable mass storage mode .
Apps are downloaded again if they are bought market apps .
You need to confirm what product you have product Code under the battery .
Firmware dial *#1234#
also settings about phone .
I was expecting that I was going to get a true European version of the phone when I bought it.
Thats what you need to find out first .
jje
thanks for the fast reply.
I'm googling for USB mass storage right now and will try that.
underneath the phone:
model: GT-I9100
SSN:-I9100GSMH
Information from typing in *#1234#:
PDA: I9100ZCKI2
phone: I9100XXKF1
CSC: I9100ZHKI2
build info: Mon Sep 5 13:02:24 KST 2011
2011universal said:
thanks for the fast reply.
I'm googling for USB mass storage right now and will try that.
underneath the phone:
model: GT-I9100
SSN:-I9100GSMH
Information from typing in *#1234#:
PDA: I9100ZCKI2
phone: I9100XXKF1
CSC: I9100ZHKI2
build info: Mon Sep 5 13:02:24 KST 2011
Click to expand...
Click to collapse
I would say on that that it would accept any European firmware exact same model as Europe version according to the figures but with China Firmware on it . ZC KI2.
International firmware here .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
This is guesswork from the codes posted your choice as to flashing a different firmware . I think i would want advice from China user who has gone the same route to be 100% sure .
jje
jje
JJEgan said:
I would say on that that it would accept any European firmware exact same model as Europe version according to the figures but with China Firmware on it . ZC KI2.
International firmware here .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
This is guesswork from the codes posted your choice as to flashing a different firmware . I think i would want advice from China user who has gone the same route to be 100% sure .
Click to expand...
Click to collapse
Thanks, but I am confused. If it can take same firmware as Europe, why use a Chinese firmware? This was an illegal import as far as I know, so it shouldn't have the same problems as the "Chinese" models right? I also read the post about "ZCKI2 now available on KIES server" and it refers to ones "sold in China". I am assuming that means the official ones.
2011universal said:
Thanks, but I am confused. If it can take same firmware as Europe, why use a Chinese firmware? This was an illegal import as far as I know, so it shouldn't have the same problems as the "Chinese" models right? I also read the post about "ZCKI2 now available on KIES server" and it refers to ones "sold in China". I am assuming that means the official ones.
Click to expand...
Click to collapse
It sounds like it is a legit euro version just been taken to china and flashed with a Chinese rom for the Chinese user.
You say you have clockwork recovery on it yes? what version is it? (boot into clockwork recovery to find out)
if you have clockwork you have a few options,
You say odin keeps hanging but you can get rid of the Chinese firmware via flashing a rom thru clockwork.
Imho the best thing to do is backup your rom with clockwork, wipe data, cache + dalvik cache under advanced then flash Villain rom through clockwork (closest to stock but optimized)
http://forum.xda-developers.com/showthread.php?t=1198334
and you should be on Euro region firmware with root and a clean slate to start from.
hope this helped, if you need any more info just let me know
I think i would want advice from China user who has gone the same route to be 100% sure .
That was in regards to Modem and CSC to use .
jje
@mnissteve
CWM is 4.0.0.2
I can't even understand the link you linked to. Never flashed before and I don't know the terminology referenced, but I could give the link to someone who can perhaps do the flashing.
Would there be any reason that a stock rom (saw the thread) would be bad for my phone? (Assuming that I can get the place to do it)
Somebody here has managed to use cyanogen mod on there sgs2 with the same rom as you
http://forum.cyanogenmod.com/topic/32284-help！my-sg2-dont-boot/
so i assume it will work but as jje said your best to check and get advice from China user before trying this! also and if your determined to fix this you need to understand some terminology!
As long as it is an orig euro sgs2 this will work.
-Download Villain zip and place on internal memory card
-boot into clockwork.
-go to backup and restore and do a backup
-go bk to main clockwork menu
-wipe data
-wip cache
-wipe dalvik cache advanced
-instal zip from sd
-pick Villain zip
-reboot when complete
-????
-profit
Make sure this really is orig euro sgs2 before doing this!
Hi all....
I am an infrequent user of this site, the last time I pored over the information housed in here was a couple of years ago when I found the site and various threads invaluable for me when rooting my old and trusty HTC Desire.
I am now the owner of a fab and groovy galaxy S3 which I aquired in the UK from carphone warehouse.
I am using Vodafone as a carrier, but my understanding is that the stock phone was not tied in any way to a carrier.
It didn't take me long to root the phone, I only rooted the device because I wanted to get rid of various bits of samsung/bloatware, not in order to Flash a new rom to the phone.
I was more than happy with this until I received a notification that there was an OTA update, this I deemed to be the JB OS, which of course would not install due to the fact the phone was rooted and was using cwm etc.
After a week of cancelling the update and being reminded of it every three hours I decided that it was maybe time to update, I discovered that in order to do this I needed in effect to put the phone back to its factory state, soo I completed a factory reset on the phone and in no time at all I was up and running again with an unrooted S3....however, despite this in the last three weeks I have seen hide nor hair of the update that seemed to be banging at my door for so long!
My question therefore is:
is there something I am unaware of that is now stopping my phone from receiving the OTA update via settings/about device/software update/update(check for updates)?
To help those of you that know about this stuff here are the details from the phone that may help you to help me...and anyone else not in the know enough!
Device Status = Normal (while rooted this obviously showed as being modified)
Model Number GT-19300
Android version 4.0.4
baseband version - 19300XXLG8
kernel version - 3.0.15-928452-user [email protected] #1 SMP PREEMPT Thu Jul 26 12:06:08 KST 2012
Build Number IMM76D.19300XXBLGB
In addition prior to unrooting the phone the foillowing info was parsed and returned :
AP: 19300XXBLG8
CP: 19300XXLH1
CSC: 19300OXABLG8
Following unrooting and completing a factory reset.....the same process returns this information.....
AP: 19300XXBLG8
CP: 19300XXLG8
CSC: Unknown.
My apologies for the length of the post for what is probably a trivial matter, but as a Phone noob (but a systems pro) you can never have too much info!
many thanks in anticipation!
It's because your CSC was lost when you unrooted and hence OTA won't work. You would have been better off using the toolkit (see original development forum) to simply download and flash the JB ROM yourself, then no need to unroot etc.
You can still do this and you'll also get updates usually faster than OTA.
Regarding your bust CSC, try:
http://forum.xda-developers.com/showthread.php?t=1845103
Hmmm...well...
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
I'm not quite sure why you want to fix it, flashing jb yourself is much quicker, but a quick search found:
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Good luck.
I can....
...find all of that myself, It doesn't really help much if the person searching amongst the huge amount of disarticulated information liberally strewn around this forum is faced constantly with broken links or unhelpful replies and threads that vanish up their own orifice.
In order to decorticate that information it helps if some form of standardisation or common language is employed.
I have my reasons for asking the original question.
I am facing a problem and asking for advice and help in order to rectify the issue.
I have tried to flash the JB ROm myself, I am despite what you may consider not stupid, however, I am receiving errors when flashing the rom from the 'update' menu from the recovery menu within the phone.
Elsewhere on this forum I discover that it may be an issue with the csc being in an unknown state, hence my post in the first place, If I was able to follow the instructions and all was working as it should I would not bother anyone here or indeed waste my time doing so.
by querying the csc by using the dial pad it shows me that the correct one is still there, so installing it seems pointless, however, as stated at the very beginning of the question, when parsing the phone for detail info it tells me that the csc is 'UNKNOWN'
Greywolf907 said:
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
Click to expand...
Click to collapse
Try installing this from the Android Market
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&
Run it and update your CSC to your correct one
EDIT :- Just looked at your phone info in post 1 again, this relates to UK unbranded version so your CSC should be BTU
You shouldn't normally have a problem updating a rooted phone to newer versions provided the base rom is still stock I have never had a problem with mine but everyone is different I guess, I did mine via Kies then just re-rooted afterwards.
...well...
ag4751 said:
Try installing this from the Android Market
Run it and update your CSC to your correct one
Click to expand...
Click to collapse
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Greywolf907 said:
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Click to expand...
Click to collapse
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1#firmware
......not
ag4751 said:
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
....that version no........I did d/l and try this version
United Kingdom 8 Sep 2012 4.1.1 I9300XXBLG8 I9300XXDLI4 283.2 MB Download
which seemed to be relevant to my original build, this is the one that I have been having issues with.
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
I am as I type sucking the file you suggest down and as soon as hotfile finishes dribbling it into my machine I'll give it a bash and let you know what happens.....many many thanks for taking the time to help me and do it with such good grace and civility, it's refreshing.
Cheers for now!
PS: I tried Kies, on three different machines, two running XP and one running Seven, each time it just doesnt want to know that the phone is even connected...ie. it knows its there, but just doesnt want to actually connect to it...just whirrs and clicks until I get fed up and unplug it....hence the grief I am having one way or another trying to update the O/S...so I can root it again!
Click to expand...
Click to collapse
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
Click to expand...
Click to collapse
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
mucho...
ag4751 said:
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
Click to expand...
Click to collapse
yes I understand all that bit, I didn't make myself clear maybe....The problem I had was that the file I had downloaded seemed to be a zip file containing the whole system, i.e a cloned image, it didn't work...however, the link you so very helpfully provided was just waht i was looking for and couldn't find myself, a single tar/md5 file which has been downloaded, installed and is up and running....I now have JB, but still the csc is classified as unknown...anyhow, that doesn't matter much until the next time I need to update.
My very best regards to you and huge thanks.
have a good 'un
:good:
Got there eventually, strange abut the CSC
If you want to root your phone use this thread, 3rd post if you don't already have it
http://forum.xda-developers.com/showthread.php?t=1957273
Then install this for easy access to recovery
http://forum.xda-developers.com/showthread.php?t=1768142