yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
I will be adding JellyBean support to this toolkit in the next week I need to make sure I have all the carriers/builds covered. If anyone is willing to help me collate this information then please let me know via pm as it will make the update alot quicker. I do not frequent the s3 snapdragon forums and do not know all the latest builds that need adding.

Thanks.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the-Mike_D:
Thanks bud. Updating a friend's new 4.1.1 T-mobile S3 and had the sense to check here first because I realized this may be an issue. You're the man =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lilmeanz:
how do i root if im running stock jb 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Datron:
You read a lot and figure it out yourself, especially since there's tons of information available to you.

Unclefest v2 alive and kicking - support SeanZ!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ricsim78:
First off, thank you very much Mark Skippen for making this script. It makes rooting and other tasks a breeze and I highly recommend it.

I used Toolkit version 2.1 and I donated, today I got my unlock code. My Toolkit is saying that I have 2.1 and version 2.3 is available, but then saying I have the latest version already installed? It also is not updating itself as it is supposed to (once the unlock code is entered in from donating.)

No big deal, just a heads up. I will manually download 2.3 and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sid_wisc:
Is the tool now providing the unlock for the SIII? I know that it says in the tool that it is coming but I did not see it the last time i used the tool.

Did you get the unlock from outside source or is the unlock code not available through this toolkit....:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ricsim78:
Hey there.

The way it works is you can (optionally) donate to the Dev, once you do so within 24 hours you will receive an unlock code in an email. This unlock code is supposed to allow the software to automatically update itself and allow extra tweaks.

The problem is even with the latest version and the unlock code entered, I am still asked to manually update the software and the extra tweaks are not available yet. I am not complaining, or regretting the fact I donated at all. I am just trying to make the Dev aware that not everything is working as intended. Also, the serial number of my phone is not showing.

But, as I said I feel this is a must have but I would recommend holding off as far as using this if you are already using (OTA) JellyBean 4.1. I would recommend rooting with this, then downloading a custom JellyBean 4.1 ROM instead of updating using Kies (if on AT&T) or doing an OTA update. That is what I did and my phone is working really well.

Keep up the good work dev!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colddonkey:
Anyone know when the SIM Unlock Feature will be added?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Datron:
.delete.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhoneLine:
So, is it safe to just root and install a custom recovery with this tool on a AT&T s3 with a stock JB rom on it? I read, and some people said they did use this tool to still root JB stock rom Once I get it rooted and can get CWM or TWRP on it, I am good to go, but curious if the current version of the app is safe to just do that part?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrycoffman45:
from the op or first post

IMPORTANT: THIS TOOLKIT IS BEING UPDATED IN THE NEXT WEEK BUT UNTIL IT IS UPDATED IT WILL NOT WORK ON JELLYBEAN BUILDS AND COULD LEAD TO A SOFT BRICK. YOU HAVE BEEN WARNED.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhoneLine:
Thanks. I did read that just wasn't sure if it was for some of the more advanced features only. I'll wait till the app is updated. :good:

Edit: Or actually maybe I will reflash the stock ICS rom in Odin and then I can use this toolkit, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
You can just install CWM with the tool. DO NOT use any kernel or root. Touch recovery is fine. I just did it after rooting with CF-Root. Afterwards if you would like to update CWM, see my post here...

http://xdaforums.com/showthread.php?p=32226847#post32226847
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Killer52:
hello there,

I'm having a trouble with unlocking my SGS3 .... I'm from canada .... I got my phone from Koodo ... here is some info.... I want to unlock it so it can work with my bell sim card .... I tried a lot ... nothing is working ... plz need some help ... thx :)

Phone: Samsung Galaxy s III

Model:SGH-i747M

Android Version:4.1.1

Baseband Version I747MVLDLK4

Build: JRO03L.I747MVLDLK4

got it from Koodo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaeiger:
Hey guys, need a hand hhere.

I used this to first Nandroid back up and back up the apps for my Rogers (747) GS3. After the apps backup in the toolkit, my phone would no longer boot up. From this point on till now, it gets past the Samsung logos, makes the bootup sound, but the screen stays black. The LED notification is a constant blue.

I've tried flashing CWM, CM10, CWM/stock rom, via Odin, and nothing will get it to work. I can't get it fully booted up to where I can enable USB debugging again so the toolkit can't do anything for me anymore it seems. I've wiped everything - data, cache, and dalvik, and every combination of everything I've tried so far has resulted in the exact same thing; what I described above. Any tips or suggestions?

nvm problem solved
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Datron:
How did u solve ur problem?

Unclefest v2 alive and kicking - support SeanZ!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
I am having the same issue!! Koodo 747m, used the toolkit to try the ALLINONE option, says everything worked, but now the screen is black, makes bootup sound, then led is just blue.. downloading the stock images now to reflash.. hoping that fixes, but would like to know how you fixed and if you got your CWM and CM10 working

Edit: Downloaded stock koodo image and flashed via odin fixed my problem.. but now how do I root/etc lol

Edit 2: Gained root via http://xdaforums.com/showthread.php?t=2031840 using the rooted Koodo.. phone up and running again. gonna see about CWMTouch

Final edit... Recoveries are easy, just grab a .img file.. use the option to make Odin flashable from it, and go through Odin... Works beautifully
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whmgreen:
So you just flashed the recovery image through odin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
When you run the toolkit there is an option to make an odin flashable .tar from img file... Grab latest twrp or cwmr/touch and put it in the INPUT folder of the toolkit. Rename it to recovery.img and run the toolkit option to make the tar file. Now load your phone into download mode, run odin and use the same settings/instructions as described in the toolkit, but choose the tar file you just made which is in the OUTPUT folder. Took a couple seconds to flash and the phone rebooted to android. I disconnected it and shut down,then booted to recovery with home + vol up + power.

Been flashing several ROMs, and even gone back and forth from twrp to touch cwm a few times now. Running cm10.1 20121230 nightly now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Flash Counter Reset

Hi mskip,

First of all, this is an awesome tool, I have already donated.

I read all 41 pages of this thread, however it only says that the tool kit has instructions on how to reset the flash counter......

I went trought every option......still nothing found. Am I missing something??

I am on Telus, al least till we have an option for SIM unlock....lol.

Q#1

So choose #11 for telus..... and where from here?

Any help from anyone would help...

Q#2&3

Or possible that the Telus version doen't have a flash counter..... Highly unlikekly... On my phone under status says "modified", would this clear too by resetting my flash counter?

Q#4

Has anyone posted or know someone that made a step by step proces on going back to stock so it's unrecognized by Telus varranty team ;)

Fyi, I have done many mods with my Galaxy S 4G, but now the new one.....

Thanks for any inpute from anyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
For resetting flash counter/custom status, get triangle away from Google play or search on xda. It resets both.

If you want to get your phone back to complete stock, get the appropriate stock odin image from the stickied thread and flash it through odin like normal. Alternatively, see the link in my previous post for a link to the one click Oden flashable for your phone. Get the unrooted version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Thanks a lot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnimeLoverX:
Just got a virgin S3 and tried this root (method 3 all in one)

Phone wont boot up and have a constant blue light...

HELP!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
See my method in http://xdaforums.com/showthread.php?p=36036868 and try the one click odin exe for virgin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TripArtist:
I just did method 2, same result. Now just a blue LED, blank screen. Noticed the kit showed for 4.0.4 instead of JB. Will there be any further updates with the boot image?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duskycub:
Most likely he said he was working on it a few weeks back before the holidays so may be a few more weeks hopefully. Meanwhile u have to use the other root method here http://xdaforums.com/showthread.php?t=1739426. I had that happen and did this method to unstick it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diffstyle:
deleted!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hpka:
Can we confirm if this is still working after the 4.1.1 upgrade on the SGH-i747M, It's likely it would just regard it as a custom rom... but can't hurt to ask.

Great tool btw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
Support for new S3 Toolkit

I have added support for the new 4.1.1 and 4.1.2 S3 builds to the new S3 Toolkit and bought the International and Snapdragon Toolkits into a single Toolkit for both and added ALLOT of improvements but I need the stock and insecure boot images for the US Models flashed to verify the insecure boot images boot properly. The stock image will recover the phone if the insecure boot image gets stuck after flashing.

If someone can do this and verify the insecure boot image works on their build I will be able to add support to the Toolkit and release it tomorrow.

Download the zip file for your model from http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/model_files unzip the contents to your pc and flash the stock and insecure boot images from the root folder using odin. I mainly need the latest builds tested to make sure they work.

Please do not do this if you dont know your way around download mode and odin and dont know how to recover from a bad flash.

If anyone can do this then pm me the results as soon as possible.

I will post more about all the updates to the new Toolkit when it is released tomorrow if all testing goes ok.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mista Panda:
Ok, so understand to an extent, im lost on the files, on the i747.

What is the difference from dlk3 and alg1.

reason i ask is i dont want to screw this up and you didnt address the files inside
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
Those are the build versions that correspond to the build on your phone. ALG1 is a 4.0.4 build and DLK3 is a 4.1.1 build.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mista Panda:
@mskip When flashing the insecure rom, it seems to hang at the Samsung Galaxy SIII screen

Stock image boots just fine, your insecure rom however does not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
The koodo version comes stock with DLK4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CentralMoNexusOne:
If you're like me and can't follow instructions and softbricked your AT&T phone give this link a shot. It worked perfectly for me.

http://xdaforums.com/showthread.php?t=1822308
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
I think I have fixed the reason behind why the insecure image froze, it was with my install of Linux and not the method used. If someone can test a new insecure boot image then please let me know as I cannot release the new Toolkit until images have been tested.

DLK3 is the most recent build I have a boot image for.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] punkyskunky:
Hey. I'm not 100% positive on flashing.

But could I use the toolkit to flash jb? And would I lose all my apps and data?

I never lost them when I rooted via the toolkit and that's why I'm asking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
You will not lose your internal storage or apps if you flash a new firmware via odin.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] punkyskunky:
Can I use the toolkits firmware and odin or should I download firmware to flash?

I just like the basic root features that the toolkit did during root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
I have had my phone brick a hundred times where screen is black but using either S3 TOOLKIT or ODIN

I can conenct to my phone anyways its weird though

It was black screen no boot up nothing but it was in USB debuging mode or ABD mode one or other not sure but i managed flash lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
If you want to download a new firmware then use my new firmware downloader http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/tkfirmware.exe and just type the number associated to your model/build that you want. You can then extract the .tar.md5 file and flash via Odin.

The present Toolkit version does not support any 4.1.1 or newer build, I have the new unified Toolkit ready for release but I need the boot images testing on the various supported models and noone is coming forward to test yet. I have the GT-I9300 and SPH-L7100 images tested but still 9 models to go.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
A hundred times OMG what are you putting your poor phone through lol.

The best thing to do is to open the Device Manager on your pc, connect your phone via usb and hold the buttons to boot to download mode. After about 15 seconds press the volume up button and check if the item appears in the list. If it does then you most likely have a connection and can flash images.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Offer

I could help you out with the Telus SGH I747M model on JB?

I have flashed back to original ICS, than upgraded to JB, but when I flashed the .tar file that had the root imbeded in it, it doesn't seem to work the way i like it.

So if no one helps you by friday, on friday i'll flash back to stock, than you can send me the file for my model.

You may have to walk me trough some things but just pm me..... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
Thank you :)

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Bell I747m test

So here are my exact steps:

1: I was on CM 10.1 so I flashed stock dlk4 via Odin. (Successful boot).

2: Flashed boot-insecure-dlk4-sghI747m.tar (Successful boot). No root achieved, though did not try to install SU

3: Flashed boot-stock-dlk4-sghI747m.tar (Successful boot).

4: Rooted with CF-Root

5: Flashed CWM with MSKIP Toolkit 2.3

6: Nandroid back to normal.

Thanks for your work MSKIP. Let me know if I can do more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
Thanks for testing.

Which exact image did you flash (link)?

Flashing the insecure boot image will not automatically root it you are just given access to perform adb root commands on your device.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Hey I searched forum first before asked this and your thread sir. I have i747 ATT model phone.. yes when I open your program I don't see my specific model... I mean its all android 4.1 im on android 4.2 or am I missing something obvious

If you havn't added my phone yet I be willing to test though let me know

Otherwise Ya I dunno maybe I just use any Att model? is that the deal? I have model number

i747ucdlk3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
I used the link you posted in post #416 http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/model_files

Downloaded the file for sgh-i747m http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/model_files/SGH-I747M.zip

I flashed the insecure first and then stock second.

---------- Post added at 04:58 AM ---------- Previous post was at 04:53 AM ----------

The firmware you listed above is 4.1.1. You are not on Android 4.2 unless you have flashed CM10.1 or AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
The Rom you are using is a Custom Rom with a 4.1 base and 4.2 apps so technically you would choose build 42 from the Model Selection screen. However most custom roms have customised boot images that are linked to that specific rom so I would advise against flashing any kind of boot image from the Toolkit or you may lose functions like wifi and bluetooth. The boot image you are using now should be insecure so if you use any procedures that ask you that question just type 'yes'.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
Great !

Thanks for the updated toolkit MSKIP. Had to flash back from AOKP to stock (Rogers), and then root. Everything went smoothly, no issues.

Appreciate the time and effort,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Getting error for all Nandroid backup options. All other backups and functions seem to work...and my device is recognized. Here is a screen shot of the error message (same message for all Nandroid options, essentially).

Do you need other data I can send you?

Thanks

SOLVED: Flashed insecure boot image from tool and nandroid backup works now. Maybe the tool didn't recognize the insecure boot image I had before.

...carry on...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duskycub:
Re: [SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0] Drivers, Backup, Root, Recovery + MORE [

OK I wish to thank u for the update I can finally root without bugs that the other method had.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
SAMSUNG GALAXY S3 TOOLKIT AUTO UPDATE V7.1.0 [22ND JAN 2013] AVAILABLE!!

Changelog:

+Added support for GT-I9300 build XXELLC

+Fixed US variants versions displayed incorrectly in Model Selection screen

+Added GT-I9300 TWRP Recovery 2.3.3.1 image to Toolkit for easy flashing

+Improved CWM NAND Backup script to make it allot more stable and robust

+Added Insecure Kernel detection to sections requiring Insecure Boot Image

+Added 'Pull Folder' to 'Pull Files' section in Main Menu

+Added 'Fix Internal Storage Permissions' to Mods Menu [folder not showing]

+Minor bug fixes and improvements

[Auto Updates are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the donator features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other donator features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please pm me about them and do not post in the open thread]

Enjoy :)

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spdivr:
Hi Mskip, thanks for putting this together, it looks awesome. I just wan to root my phone to get rid of the bloatware, and this looks like it will do it. The only problem is that when I choose "42" for the AT&T model running Android 4.1.1, it can't connect to any servers to download the images. This happened yesterday and today. Is there something going on?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mletchworth:
spdivr, check your firewall settings, or maybe retry from another internet connection. I tried this at work and my office firewall was blocking access. works fine from home though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lennydude:
Pay Pal Donation unlock number

Was wondering if there is an easy way to retrieve the number MSKIP sent me when i donated.

Typical me, i have lost/misplaced it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Yes- His website has this

http://skipsoft.net/donate/reminder.php
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lennydude:
hmmmmmmmmmm

I donated to him for the S3 toolkit and the Nexus 10. It will only list the code to the nexus 10....................darn it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Mskip I tried to update the toolkit to the latest version which is v7.1 and I keep getting an error that it cannot replace the old files I tried to uninstall the toolkit and re installing it again but it still doesn't work, is there a link where I can download the latest version manually?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chevyman1580:
this does work on mac huh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
Hi Mark, this looks like a fantastic tool. I will definitely also be donating next month. I have reached my monthly app spending limit already and my Visa is maxed. Hah...

Thank you so much... I don't know where we would be without creative and practical developers. :good:

Props.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHourHand:
My AT&T S3 is rooted and I want to restore to stock rom so that the AT&T update will get applied.

My build is UCALH9, but I can't find that on the Stock Rom page (8 -> 1).

What should I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
UCALH9 was an over the air update to UCALG1

You could just update to it and then you should be able to get the update to UCDLK3 that way.

OR

You could just select the UCDLK3 from that same menu to get stock 4.1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reeonimus:
Hey all,

Just picked up a Telus SGIII today and downloaded this toolkit but it does not list my build number which is JRO03L

There is a JRO03C but didn't want to try it.

If anyone can point me in the right direction for rooting I'd appreciate it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
JRO03C works fine. I just came from cm10.1 and used this tool. Option 53 for JRO03c, will get you where you need to be. Beyond that I used #2 'root/ unroot', then #3 'allinone' and everything worked perfectly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
That is just a textual mistake on my part it is meant to say JRO03L so you will be fine. It was fixed a while ago on the Auto Update version but I will be starting on a new round of public builds soon so will fix it on that too.

Mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majikmonkie:
This toolkit looks pretty intense! Thanks for this!

I'm having troubles though and couldn't find it in a search. I have a rooted phone (no recovery), and I tried installing a recovery, unrooting, or rerooting but it keeps giving errors:

error: protocol fault (status read)

and

error: more than one device and emulator

I've enabled USB mode. Can't figure this one out. Any hints?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mskip:
Do you have an emulator installed such as eclipse which would interfere with commands being sent?

Mark.