yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] DowntownRDB:
Sandman, same here today. AVG picked up 4 Trojan Horse BackDoor.Generic15.CMTQ threats after a fresh download from media fire and clean install. Also downloaded from Dev-Host with same results. Ran Malware Bytes and it picked up 2 Trojan Horse. I uninstalled AVG and installed Norton AV and it picked up 3 Trojan Horse threats. So just wanted to let you know that you aren't the only one having this problem and I don't think AVG, Malware Bytes and Norton can all be wrong.
[Sprint Samsung Galaxy S III] RegnierD:
This is a common problem with root exploits and antivirus software. The problem is that it is a string of code designed to take over the operating system. The antivirus programs recognize that as a threat, because it is. It's just being used to root your phone, and not maliciously.
[Sprint Samsung Galaxy S III] therockk:
Can i use Feature No:#9 of this toolkit to create an Odin flash-able .tar from a CWM .img BUT for other phones like the Galaxy S2 i727, or Google Nexus?? I downloaded this tool, and already tried to convert a CWM img to .tar and i was able to successfully create the .tar, But when i compared the MD5 of the tar with a copy i downloaded from someones post (which i successfully flashed onto my S2) the MD5's didn't match, HOWEVER, the MD5's of the .imgs inside both .tars matched, My question is that am i able to flash the .tar i converted with this tool to my S3?? Any help would greatly be appreciated.

I am basically looking for a method to convert CWM .img files into Odin flash-able tars not just for my S3, but for my friends phones too like the Google Nexus, or S3 i747 or T999, or Galaxy S2 etc Thanks again!
[Sprint Samsung Galaxy S III] sandman512:
Running AVG.

Ran MBAM and cleaned up everything.
[Sprint Samsung Galaxy S III] wwjoshdew:
How To Flash Stock Video

http://www.youtube.com/watch?v=ukDpzfsoKQk

[YOUTUBE]ukDpzfsoKQk[/YOUTUBE]

I used your ToolKit mskip. Let me know what you think! :D
[Sprint Samsung Galaxy S III] saynotopunx:
This stumped me for a while, but I installed the newest version of ClockworkMod from Rom Manager and it flashed perfectly. This happened to me on two different GS III phones.
[Sprint Samsung Galaxy S III] mskip:
Added to the OP :)

Mark.
[Sprint Samsung Galaxy S III] obender:
Can the devices running Jelly Bean be rooted with this toolkit?
[Sprint Samsung Galaxy S III] Anon9mouz:
Plus one on this??

__________________________________________________
[Sprint Samsung Galaxy S III] mskip:
The only stock image available is the original 4.0.4 image. I need a stock boot image to be able to add support in the Toolkit. CWM root option will still work perfectly for you but if you can flash custom recovery, make a nand backup in tar format and send me the boot image then I can root it and add it to the new version im currently working on.

Mark.
[Sprint Samsung Galaxy S III] biglos201:
hey guys, I need some serious help. I just tried to root with the updated jelly bean and i'm am now stuck at a blue light with a black screen. I can hear the sprint boot but it doesn't boot up - blue led and I can hear the sprint boot but can't see it. I was attempting to root using this tool but then it didn't work. did I just **** up my phone?
[Sprint Samsung Galaxy S III] Jamin13:
Sounds that way. I don't believe the toolbox has been updated to root Jelly Bean. Try ODIN'ing back to stock.
[Sprint Samsung Galaxy S III] wwjoshdew:
That's because of the boot.img that's meant for Android 4.0.4. This happened to me earlier today. You are going to have to use Odin (or if you created a nandroid) and go back, or flash the latest 4.1.1 and start restoring stuff with Titanium Backup.

http://xdaforums.com/showthread.php?t=1951885

I'm not a developer, I think if you just replace the boot.img with the original one you had before, it will boot up just fine. You're experiencing a soft brick that can easily be fixed.
[Sprint Samsung Galaxy S III] dbpaddler:
Anyone know why I'd get:

I'm on Windows 8, run the program anyway then get that error. I've redownloaded it multiple times with the same results.
[Sprint Samsung Galaxy S III] geolemon:
I used a tool similar to this for my Nexus 7. However, this one is a little scary, by contrast to that one, which gave a smooth experience.

I'd previously rooted my GS3 without issue using the TeamEpic 'root from recovery' process (the one in the thread stickied "easiest root method"), but had subsequently unrooted for a few reasons. Now I want to root again, installing TWRP this time to satisfy a requirement in a custom ROM (Sonic FreeGS3)... which is how I found this thread.

Following the instructions in the video exactly, including deleting the existing Samsung drivers to start with, after running option 1, I couldn't get my phone to show in "attached devices" list, even after rebooting my computer.

I decided to run option 1 a second time- this time was prompted with a Windows dialog "Drivers already installed - are you sure you wish to proceed?" I clicked "yes" and on completion my phone appeared in the toolkit.

Moving on to rooting, again following the instructions in the video exactly, I selected the 'boot-insecure-spr-l710palen-cwm.tar' in ODIN, and after rebooting my phone, I saw I believe 6 messages along the lines of "error: device not connected" or simillar, then the script proceeded through, and when it said things like "you should see '/system/xbin/busybox', below that it gave an error along the lines of 'path not found' (I didn't capture the exact text). Same for 'you should now see a list of all busybox commands'. Scary.

So - again - I selected option 2 a second time (when returned to the main toolkit menu). Second time through, I received the responses I should have, and it appeared to complete successfully. But that doesn't leave me with a lot of confidence.

I also wasn't prompted at any point to choose whether I wanted to install CWM or TWRP (I also looked for an alternative file, named 'boot-insecure-spr-l710palen-twrp.tar' or similar, but one did not exist). Option 5 on the main menu "Flash Custom Recovery" also shows "[CWM]"

As mentioned, I chose this method over the tried-and-true because this thread said there was a TWRP option, so this is also disappointing, because I'll need to perform extra steps - I could have used the tried-and-true method and installed TWRP after the fact, but I chose this one because I was seeking a clean and integrated method.

Note I did not skip the update option - I checked for update on first launching the toolkit.

What went wrong here - and where are these TWRP options, if supported?

Please advise, thanks.

EDIT:

Even worse, I can't boot into recovery. It behaves as though there's no recovery at all on the phone.

I get a little "vibrate" when the phone gets to where recovery should be, then the Samsung logo appears a second time, and the phone boots into Android.

EDIT2:

Same with fastboot. Phone ends up booting into Android.
[Sprint Samsung Galaxy S III] snailer88:
This is the easiest and most useful tool I've ever used! Thank you SOOOOO much! Worked like a charm first try!

Edit: Noob question - After rooting can I apply OTA updates safely or will that remove root?
[Sprint Samsung Galaxy S III] BiggieD:
Jellybean issue

Gents, I used the tool kit to root my stock some time ago it worked great, i used voodoo to unroot and took the jelly bean update through kies, it went well and i was able to re root with tool again, however i know have issues, seems some of what is to be in jelly is not on my phone, some are like vpn client and the added screen dimmer in notifications, however the camera is still same and shoots and plays everything upside down, i know a full wipe and reload is going to be my answer and i have all backed up via 3 or 4 different apps, however I’m worried i may not be able to re root and won’t be able to restore due to no root, any advise or suggestions to my issue?
[Sprint Samsung Galaxy S III] dbpaddler:
Even if you started from scratch via Odin, you'd be able to get root again and restore your backups.
[Sprint Samsung Galaxy S III] BiggieD:
should i download a rom or should i do a factory wipe? if i do a factory wipe via the phone will it load what i have now or rebuild the jellybean rom i installed from kies? thanks for your help
[Sprint Samsung Galaxy S III] dbpaddler:
If you factory reset, you get a clean slate of the rom you currently have installed.

You can Odin back to stock and rooted Jellybean. or you can flash this through CWM and get back to unrooted stock. Then you can go through the toolkit to root again.
[Sprint Samsung Galaxy S III] yowhatup:
Does this utility work on Android version 4.1.1? I see the menus say 4.0.4, but I also get update server unable to be accessed (from my work).
[Sprint Samsung Galaxy S III] Jamin13:
No, not yet.
[Sprint Samsung Galaxy S III] yowhatup:
Thanks!
[Sprint Samsung Galaxy S III] highcheef13:
I'm running Jellybean and tried using this toolkit. It seemed to go okay, said it was successfully rooted, but after everything was finished and the phone re-booted, the LED was blinking blue and the screen wouldn't turn on. I tried re-rooting, the toolkit said it was already rooted. When my phone would re-boot, it would show the Samsung boot animation, I would hear the Sprint boot-up sound, but the screen stays black and the blue LED keeps blinking.

I'm trying to un-root and return to stock using the toolkit, but I'm not an expert with this stuff.

Any idea what happened or what I can do?

EDIT: I tried option 8 (Download, Extract, and flash stock ROM) from the Sprint device menu in the toolkit, but after the stock ROM downloads, it says "file not found." I looked in the folder the toolkit says to check, and the file is there. I tried option 7 (Reflash stock recovery VIA odin), but it hangs at "Waiting for USB debugging to be enabled".
[Sprint Samsung Galaxy S III] sinsit3r:
i did the same thing to my phone earlier today. didnt realize its not working on jellybean yet. im still waiting for a fix on this as well!
[Sprint Samsung Galaxy S III] highcheef13:
I'm surprised there hasn't been more chatter about this. I mean, I know I'm a noob, but I did read around and never saw and warnings not to try it while running JB...

I'll keep trying and update if I find a fix.

Please do as well!

EDIT: FIXED IT!

Here's what I did...

Downloaded one of the .tar files from this link http://xdaforums.com/showthread.php?t=1941546

Sorry I can't remember which one (but I'm assuming the full wipe one because I had to go back and re-sign in and re-install everything after), but download one of those official JB .tar files.

Open ODIN and load the .tar into the PDA slot

Boot into download mode (from powered off, hold power button, home button, volume down until the little android shows up)

Volume up to continue

Plug in phone to computer

Start ODIN

It took like 10minutes but re-booted and now works! I think I'm rooted, too!
[Sprint Samsung Galaxy S III] sinsit3r:
Wow good find... im going to give this a shot when I get home from work and ill update this than. also if you want to check if your rooted just trying installing something like setcpu or whatever that asks for root.

EDIT... was wondering if it stayed on setup connection in odin for awhile?
[Sprint Samsung Galaxy S III] firestetz:
I development still going on with this, will there be an update so that it works with jellybean?
[Sprint Samsung Galaxy S III] xxdjvalexx:
Quick question. Will this work with the Cricket SGS3?? It has a similar model number as the Cellular one SGS3, The only difference is the "C" at the end (SCH-R530C)

:good:

Thanks in advance
[Sprint Samsung Galaxy S III] mskip:
Yes development is still active and yes there will be an update as soon as possible with jellybean support as long as I can get the required boot images.

Mark.
[Sprint Samsung Galaxy S III] Buddlespit:
http://xdaforums.com/showpost.php?p=28807761&postcount=1

http://xdaforums.com/showpost.php?p=32913815&postcount=1

I can pull the boot.img from either, if you like. You'll have to give me time to ask permission first. Even tho both kernels fall under the GNU GPL, it's only good form.
[Sprint Samsung Galaxy S III] firestetz:
Could you use a copy of the pushed update to get the boot image from?
[Sprint Samsung Galaxy S III] das_webos_transformer:
you should state it doesnt work with jb

i also used this thinking ehh itll work, doesnt say anything against it. buuut i was wrong.

STATE THIS ONLY WORKS ON JB PLEASE

to confirm flashing

http://xdaforums.com/showthread.php?t=1956392in

in custom recovery WILL fix your problem.

flash that and wipe cache and dalvik cache.

so to clarift:

1. reboot to recovery hold vlolume up, homebutton and power when the blue text in top right shows let go

2. use CWM recovdry to flash kernel (agat 0.3.2) {NOTE] this has to be on a sd card for cwm to see it.

3. clear cache and dalvik{dalvik is in advanced}

4. reboot!

you will have all your data intact. although you will have no root.
[HTC One S] mvmv:
Hi guys, specification of the display is 960x540, but if I run Quadrant or Antutu they report a resolution of 540x888. Is this normal?

Thanks
[HTC One S] k1llacanon:
I got 540 by 960 WTF? Quadrant
[HTC One S] mvmv:
I tried to download 3 differents apps to measure display resolution: 2 are giving 540x960 and one is giving 540x888.

If I take screenshots with [power]+[home], the image files are 540x960.

This is something I don't really understand, I've sent an email to HTC support for clarifications, waiting for the answer.
[HTC One S] opiswahn:
It has something to do with the 3-Dot menu. AnTuTu somewhat doesn't calculate the space of that button, other apps(wich maybe doesn't use this button) have the full resolution.
[HTC One S] k1llacanon:
But I'm on custom Rom and don't have the 3dots tell me what they say when they reply pls
[HTC One S] mvmv:
Today I received a call from HTC support, it was a short and funny call:

HTC: "Try to see if the problem persist after removing the battery and reinserting it".

ME: "How do I remove battery, with a hammer?"

HTC: "Why? I don't understand..."

ME: "It's a unibody shell"

HTC: "OK, so push power button for ten seconds, then please contact us again if the problem persist"

I've tried but, as expected, nothing changed. I don't think I will contact again HTC support.

BTW, I noticed that if I run Quadrant in portrait mode I got 540x888, if I run it in landscape I got 540x896.
[HTC One S] eagle63:
Is this because of the Pentile screen perhaps? Doesn't that mess with the actual resolution?
[HTC One S] k1llacanon:
Lol what idiots
[HTC One S] dementor123:
This definitely has to do with 3 dot menu. All the apps that don't implement the menu, OS gives them only 540x888 to render the UI and reserves 960-888 for the menu. The screenshot (power+home) has access to the full screen.
[T-Mobile, Samsung Galaxy SIII] mskip:
*reserved if needed*
[T-Mobile, Samsung Galaxy SIII] darren.wlsn1:
thanx op for all your work and helping us tmo peeps.

EDIt: works as advertised, no issues.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Hey, congrats on finding everything you were looking for and getting the Toolkit up and running for the US variants!

Thanks for the great tool.
[T-Mobile, Samsung Galaxy SIII] mocsab:
Thanks!

Awesome and thanks! I used the GNEX Toolkit you put together and I assume this is very much like that one - I do apprecaite the effort and time you put into this - thanks a lot!
[T-Mobile, Samsung Galaxy SIII] kscasper13:
well done mate! everything seems to work perfectly. thanks Mark
[T-Mobile, Samsung Galaxy SIII] overground:
Donation sent.

Thanks, Mark! :good:
[T-Mobile, Samsung Galaxy SIII] mskip:
Thanks mate hope everything works as it should. If you spot anything that needs fixing please let me know. The Snapdragon Edition benefited from a few script upgades over the International version ;)

Mark.
[T-Mobile, Samsung Galaxy SIII] overground:
Well, there's a problem with build.prop push/pulls, at least on this ROM: http://xdaforums.com/showthread.php?t=1728255

Any changes fail to boot...even after restoring backup in recovery.

Seems to be a permissions problem as indicated in this thread (towards the end): http://xdaforums.com/showthread.php?t=1735128
[T-Mobile, Samsung Galaxy SIII] mskip:
Is that s problem with the ToolKit or with the build.prop changes from the thread you linked to. Its never a good idea to edit too much in the build.prop as it can soft brick your device.

Mark.
[T-Mobile, Samsung Galaxy SIII] overground:
I'm not sure at this point. All I did was use your tool to disable boot ani.

But it's not inherently the tool's fault because it happens if manually done also.
[T-Mobile, Samsung Galaxy SIII] gharris040604:
Use the toolkit to restore back to stock for some odd reason my Internet isn't working any ideas

Edit problem solved had to pull some and reboot thanks for this wonderful tool
[T-Mobile, Samsung Galaxy SIII] Davidion:
Just upgraded to an SIII from a G2 and boy, when did rooting get so easy? Thank you for this fantastic tool; your work saves everyone a ton of headaches.
[T-Mobile, Samsung Galaxy SIII] anthonykash:
Recovery

Does this recovery support external sd card and if it does do the backup and restore work? I know there was one posted, but restores did not work. The recovery in the root tutorial woks with backup/restore but it's internal storage support only.
[T-Mobile, Samsung Galaxy SIII] garz:
Just used This toolkit to root my device. Worked flawlessly. Thanks, bro!:cool:
[T-Mobile, Samsung Galaxy SIII] C_LosEvo:
I would also like to verify this?
[T-Mobile, Samsung Galaxy SIII] kharnage:
I got everything to work except installing superuser. I passed ODIN and then when I try to flash superuser, it flashes but when I restart my phone I don't have superuser.
[T-Mobile, Samsung Galaxy SIII] kscasper13:
go to the market and download superuser, and busybox.
[T-Mobile, Samsung Galaxy SIII] mskip:
The ToolKit uses Team Epic's v4 cwm Recovery which from their changelog supports external sd cards and has no mention of restores not working so I would think its safe.

You can see Team Epic's Changelog *HERE*.

Mark.
[T-Mobile, Samsung Galaxy SIII] darknessxyz:
All the happened after you update the OTA from Tmo?
[T-Mobile, Samsung Galaxy SIII] EL_REY666:
actually no.. i havent done the update from tmo yet..

just plugged in the s3 and it didnt recognize it to go into the sd/memory

the toolkit also doesnt display the serial # of the phone as it did when i rooted

checked and the usb drivers are installed and i reinstalled them just to make sure and nada
[T-Mobile, Samsung Galaxy SIII] sofia-captivate:
if i root my phone and get clockwork using this method. if i ever want to go back to orignal samsung software would i be able to? i am with wind mobile.
[T-Mobile, Samsung Galaxy SIII] iwillkillyou:
Pretty standard stuff, thanks OP, sticky well deserved.
[T-Mobile, Samsung Galaxy SIII] cheapshot789:
I need help i dont know if i bricked or what, i did the all in one root i was on the ota jelly bean evrything went trought except on the part for busy box it said fualt then gave a bunch of codes the exited out to the main menu phone restarted intial galaxy s3 boot came up after that the led blue turns on have a black screen an phone vibrates stuck on that, i can get into cw i tried to install a custom rom but says failed, anyone help!
[T-Mobile, Samsung Galaxy SIII] GrandMstrBud:
Another awesome toolkit. Not sure why but I can't get the stock odin image to flash. I click start it goes for a second and then fails. I have since installed CWM and rooted it and put a custom ROM on it so not a huge deal and I'm downloading the stock image from another thread on here not sure if I'll bother or not.

Here is the odin message

<ID:0/041> Added!!

<ID:0/041> Odin v.3 engine (ID:41)..

<ID:0/041> File analysis..

<ID:0/041> SetupConnection..

<ID:0/041> Initialzation..

<ID:0/041> Get PIT for mapping..

<ID:0/041> Firmware update start..

<ID:0/041> amss

<ID:0/041> NAND Write Start!!

<ID:0/041> FAIL!

<OSM> All threads completed. (succeed 0 / failed 1)
[T-Mobile, Samsung Galaxy SIII] EL_REY666:
ok i have done the updates and have andriod 4.0.4 now but i guess its several updates... i was able to boot into cwm and did a dalvik wipe and i cant remembert what else but before i did the wipe it wold update android, but cwm would show the doid with an electrical bolt thing then cwm has something that says : e invalid command; finding update, opening update, verifying, e:failed to verify; e:sign varification failed; installation aborted.. and it shows the droid with a red triangle knocked over

dont know i might try and just go back to stock rom with no root if im having problems now with my computer not recognizing my phone and etc...

im a noob with this samsung stuff as i came off the hd2.. is there a link that shows the steps we use to flash back to stock with no triangle and 'modified' status?

thanks.

ahh just saw #5 to flash stock image.. will thuis erase everything on my phone/sd?
[T-Mobile, Samsung Galaxy SIII] freska8:
This is an amazing Tool. I am looking forward to the GSM Carrier Unlock feature. Thank you to all that are contributing to create this tool and make it better. Thanks for the hard work.
[T-Mobile, Samsung Galaxy SIII] EL_REY666:
its looking like you CANT do the ota update from TMo

i have downloaded it and installed.. what happens is that CWM is not letting it update

after you download it, the phone boots into i would assume the update and it shows the android with a little electrical symbol or something; then after a while it fails and it does what it does what it says in my last post..

dunno.. its working fine with the root so far, but i guess i dont want to always have this update thing that always fails..
[T-Mobile, Samsung Galaxy SIII] anyuser2004:
Same here. Can't get past CWM on the TMo OTA update. Also noticed that the flash counter was tripped after running the all in one. Any tips on getting back to stock and resetting the flash counter? I'd like to have everything back before TMo drops Jellybean.
[T-Mobile, Samsung Galaxy SIII] nygmam:
Not sure what you are both dooing, if you are taliking about the T999UVLH2 upgrade. I downloaded it and flashed it in Odin, then I went and used this tool to root and install CWM, then revert to the stock kernal. I will admit I did extract the kernal from the new ROM, and did not use the stock Kernal as provided in the kit, but I now have the T999UVLH2 running, Rooted, with stock kernal and CWM. I did have to use Triangle Away, which works just fine to clear teh flash counter, so I am not sure what you are trying to do. The OTA Ubdate I had came in a Zip, but not CWM flashable, I had to extract the md5 file from the zip, and used that in ODIN (PDA Option).