yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ckelly33:
Trying to follow the instruction on OP. I'm on 4.0.4 stock. I downloaded the Samsung drivers, put in Debugging mode, check to allow for unknown sources, and connect my phone via the Samsung USB. It recognizes my phone, installs drivers but the last one fails and gives the following error: "SAMSUNG_android_sch-i535 device driver software was not successfully installed"

I reinstalled the drivers from the OP but nothing helps. I get the same results. Any help on this?
[Verizon Samsung Galaxy S III] wooddale:
I had same thing happen I had to switch ports for usb connection or it could be cable
[Verizon Samsung Galaxy S III] ckelly33:
I triedg a second cable in another port . Reinstall the drivers (again) first.... same result.
[Verizon Samsung Galaxy S III] wooddale:
When you click on computer is it showing as a devise sometimes its there but still saying it isnt.
[Verizon Samsung Galaxy S III] lohp75:
Install drivers with "run as administrator".
[Verizon Samsung Galaxy S III] ckelly33:
No. Always there.

---------- Post added at 11:44 AM ---------- Previous post was at 11:26 AM ----------

Didn't work. I uninstalled, ran as administtrator, restarted the computer (for good measure), connected, the device was recognized and successfully installed 3 of 4 drivers.

I tried to run Root debug, FS anyway and it never recognized the phone (in debugging mode)

Do I have to have Kies installed? I have Security -> Device Administration -> and Unknown sources checked as well. As far as I can tell I'm following the directions accurately

Thanks for the suggestions....any more?
[Verizon Samsung Galaxy S III] lohp75:
Do u also have usb debugging ticked on in developers options?
[Verizon Samsung Galaxy S III] ckelly33:
Yes.

While it is checked, some of my devices have read in the notification bat that they are in debugging. This only says it is connected as Media Device.

I went into regedit and removed two things that I saw as Samsung drivers. Seems like I removed others in the past prior to a reinstall but I can't remember what they were. Anyway, after uninstalling through regedit and re installing then connecting.....same result. one of the drivers doesn't install.

Is Kies required?
[Verizon Samsung Galaxy S III] lohp75:
I didn't see which OS your running?
[Verizon Samsung Galaxy S III] ckelly33:
Windows 7 Professional

---------- Post added at 12:19 PM ---------- Previous post was at 12:15 PM ----------

Well! I went into device manager and chose to update the driver manually. It seemed to have worked. I'm in the process of rooting now.....

Thanks for your help!! (I may be back, LOL)
[Verizon Samsung Galaxy S III] lohp75:
Well because I'm not home with my family on this day I will do my best to help. If your following the OP to the letter then you shouldn't be having a lick of issues? So I'm gonna keep asking stupid questions to try and help. Have you rebooted your phone and unlocked it to the launcher then plugged it in? (not necessary but another way for device to be fully seen). I used win 7 ultimate and went like butter a few months back.

---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------

I didn't get this post until I posted my last one (slow ass 3g where I'm at). Right on. Happy holidays and happy rooting!
[Verizon Samsung Galaxy S III] Gervin:
I used the image in section 5 to flash root, installed three OTA updates which got me to stock jellybean.

Then rooted and unlocked.

Great so far.....

But now using Rom Toolbox to customize, and developer said I need drodexed ROM.

Can I convert what I got, or need to stay from scratch from a deodexed Rom.

Or... better way I should be customizing my status bar icons? (I know off topic).
[Verizon Samsung Galaxy S III] waffleb051:
Ok so I know this won't get answer until the morning but I used Voodoo root keeper to keep root through the OTA to JB, can I just use EX unlock to re unlock my bootloader?
[Verizon Samsung Galaxy S III] BigErnM:
Yes you can. Make sure you use version 1.2. Also click lock and then unlock again if it says you are unlocked the first time you open it, because sometimes it doesn't know the bootloader has been relocked.
[Verizon Samsung Galaxy S III] droidstyle:
this! although im not sure why anybody wants to ota. you can simply flash pre rooted VRBLK3(same as the ota) from section 5 and be on the latest stock rooted jellybean in 8 minutes.
[Verizon Samsung Galaxy S III] Rushead:
While I'm no dev, I can't understand why so many people are interested in the ota. Granted, this phone is super easy to unlock. On most/many phones, the ota is avoided b/c of the possibility of losing root.

Besides, once the ota is out, the devs will have a rooted rom available. To take the ota just convolutes the entire process. Just flash a custom rom based on whatever current version is out.

Sent from PAC-land
[Verizon Samsung Galaxy S III] droidstyle:
bingo!
[Verizon Samsung Galaxy S III] lennie paz:
Anyone have an alternate download link to "Official VRBLK3 4.1.1" ? The Hotfile link is super slow and taking forever.
[Verizon Samsung Galaxy S III] lexluthor:
Do EZ-unlock and EZ-Recovery that are linked in the OP still work to unlock and install recovery when used from LK3?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you've rooted VRBLK3, yes.
[Verizon Samsung Galaxy S III] droidstyle:
x2!
[Verizon Samsung Galaxy S III] neh4pres:
Droidstyle, Hello old fascinate friend, is there no need for a pit file on this phone? I'm having trouble with gps and am going to odin stock to see if that resolves it. I want to make sure it's done right though.

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] NITRO_2:
Have to send in phone tomorrow after I get my replacement s3 in the mail, following section 5 should get rid of all traces of rooting/roms, correct?
[Verizon Samsung Galaxy S III] Madmanmoose:
Verizon GS3 4.1.1 keeps resetting during Odin Root

I have been following the XDA directions for rooting a Verizon GS3 with the OTA 4.1.1 firmware update. The phone is brand new (today), was just activated and had the OTA firmware update to Jelly Bean 4.1.1

As soon as I start the 1st Odin session (VRALEC bootchain), it starts to process, and after about 10 seconds, it reboots itself

I have attached a screenshot of Odin at the point it always fails

I am using a Windows 7 64-bit laptop

After programming in my Google account, and having my apps restored, I did the following:

1) Downloaded all the software in the links on the XDA directions

2) Put SuperUser on my micro SD care on the GS3

3) Installed the Samsung drivers

4) Extracted all the Odin files into the same folder

5) Turned off the GS3, then restarted it into Odin Mode and then connected it to its USB cable

6) I opened Odin, made sure that Auto Reboot, F. Reset Time and PDA are the only things checked

7) I click the PDA button, and select the VRALEC.bootchain.tar.md5 file

8) I click the Start button, the VRALEC starts to process...and, then the GS3 reboots

I have tried it on 2 other Win7 32 bit machines, and also tried it again right after a factory reset.

In every case, the exact same thing happens.

I have no doubt that despite looking at the pix and reading the text, I have made a goof somewhere .

Can you PLEASE give me some direction, here? I am desperate to get Titanium Backup, all my app data, etc. from my Droid X installed on this device.

Thanks, as always!

PJ Arts
[Verizon Samsung Galaxy S III] Droid2drummer:
I just went from stock unrooted refurb to rooted stock by just odining the root 66 vk3 then used ez unlock app and gooim to flash twrp. I always use this method but I guess some want pure unflashed stock. But seems overkill for end result if only wanting root to flash a backup or rom...idk still good write up
[Verizon Samsung Galaxy S III] Legato Bluesummers:
It is supposed to reboot. Hence it saying "reset" in the box. Don't touch it til it says "passed". It needs to reboot to make sure what it flashed worked. That is normal. Sometimes it says passed as soon as the phone boots. Odin my wife's phone today and it took 3min after boot to say passed. Just wait and be patient

Sent from a GlaDos Baked Potato
[Verizon Samsung Galaxy S III] NITRO_2:
Anyone have the answer to this? Thank you
[Verizon Samsung Galaxy S III] Legato Bluesummers:
Yes it will make you fully stock with no trace of root. The only thing that could make it known as previously rooted is if you flashed a custom OS or Recovery through Odin. As that trips the flash counter. Stock OS and recovery are fine. Its the custom stuff that increments the counter. You can use "triangleaway" app from the market on from here on xDA to get rid of that counter. But you must be rooted on a stock ROM to use it.

Here is the free version for XDA users. http://db.tt/aFarzsar you can buy it for $1.49 in the market if you want to support the dev

Sent from my GlaDos Baked Potato
[Verizon Samsung Galaxy S III] NITRO_2:
Thank you!!! Quick question if you don't mind and I know this is a bit off topic so I'm sorry but for triangle away, if it says "current status, counter: 0, binary: official", does that mean I'm good to go and do not have to bother using the app?
[Verizon Samsung Galaxy S III] Legato Bluesummers:
Yep. You are good to go. If the counter said anything above zero you'd us the app to clear it back to zero. Since you are already at zero. Odin away and get that new phone. :)

Sent from a GlaDos Baked Potato
[Verizon Samsung Galaxy S III] slick_shoes:
I'll be getting my replacement phone tomorrow and will need to root it right away so I can restore the ROM I was running. Where can I find the root66vk3 file so I can flash through odin. I'm assuming that's all I need to do and then flash twrp through goo manager and use ez unlock for the bootloader. Am I missing something else or do I need to root it a different way?
[Verizon Samsung Galaxy S III] Droid2drummer:
Flash root 66 no wipe 7zip. You'll find it here in the forum under odin files stock files etc. Then prepare your phone as usual check boxes etc. Dl mode. Then in odin flash the root 66 file. From there. I did.

1 playstore dl ez unlock goomanager and that's it. I unlocked and then flashed twrp. Then I backed up. However. I think at one point I wiped or the new twrp won't reach my back ups from before. But I haven't looked too hard. Lol Just wasn't there at first glance but all my dl roms and all are good. So not sure there. But yes just backup once you hit recovery. Then you'll be good. Might have to find your back ups
[Verizon Samsung Galaxy S III] droidstyle:
Yes..................................................................................................
[Verizon Samsung Galaxy S III] droidstyle:
wrong thread...if your going to use open1your1eyes method then post in his thread not here :silly:
[Verizon Samsung Galaxy S III] irl5fan:
I tried rooting via section 1, but had no success. I have jellybean 4.1.1, so it looks like i should be able to follow instructions in section 5 and that will work? Is that correct?

The main reason i'm trying to root my GSIII is to try some new radios. My cell service seems to be pretty dismal at this point. Is this even worth doing or should i just trade in for a different phone (still under the 14 day return period).
[Verizon Samsung Galaxy S III] wooddale:
Getting new radios is probably not gonna do the trick if your in a bad service area. Moto radios are a bit better than Samsung for data.
[Verizon Samsung Galaxy S III] irl5fan:
Thanks. Any recommendations for a different phone?
[Verizon Samsung Galaxy S III] wooddale:
Well I had an S3 and now I have a Note2 there was nothing wrong with the S3 I just wanted bigger. The Note is probably the best phone I ever had. If your wanting to get away from Samsung my choice would be the droid Razr Maxx HD. It doesnt have all the whistles and bells of the Sammys but its a good sturdy phone. IMO
[Verizon Samsung Galaxy S III] Rword69:
I don't really understand why someone would flash a new radio. Can someone explain why you would want to do this to me?
[Verizon Samsung Galaxy S III] wooddale:
Radios (Modems) are what give us our signal strength. We are always looking to better that. Radios are weird as some work better with different phones. So we try and find the one that works best with our phone. I am currently testing the new radio so far no difference.
[Verizon Samsung Galaxy S III] droidstyle:
This! As always mileage may vary from device to device so having different modem options is a good thing. Just make sure you only flash I535 s3 radios or you will bork data.
[Verizon Samsung Galaxy S III] lennie paz:
I followed the instructions in section 5 because I need to return my phone to Verizon. I flashed the factory BLK3 combination ROM that is supposed to return to stock and lock the bootloader. I'm not sure my bootloader is locked though. When I boot the phone up, the Samsung logo only flashes on the screen for about 1 second, and I checked a bunch of YouTube videos of the S3 unboxing, and the logo stays on for about 3 seconds. How can I truly tell if it's locked?
[Verizon Samsung Galaxy S III] Biker1:
I believe if you go into your Bootloader screen, you can tell where it says custom and status.

Power off device.

Press Power, volume down and home button at the same time.

You will see the Bootloader screen,

See what it says under:

Custom binary

System status

To get out of Bootloader,

Pull battery and restart device.

Also, the fact that the splash screen was only a second is indicative of an Unlocked bootloader, I believe.

Check your phone status also in Settings to see that everything installed
[Verizon Samsung Galaxy S III] lennie paz:
Here's what it says on that screen:

Custom Binary Download:No

Current Binary: Samsung Official

System Status: Official

Qualcomm Secureboot: Enable
[Verizon Samsung Galaxy S III] Biker1:
That's exactly what you want it to say when you return the device, and if they check it.

I would say that you're good to go.

While I'm not sure the above is indicative of the status of your Bootloader, one way or the other, the above settings on your Bootloader is what the tech will want to see, if they look at all.

After reading through some posts, a one second splash screen is indicative of a locked bootloader.

Someone can chime in with more knowledge.

Your successful ODIN flash should ensure that your Bootloader is Locked also.

At this point, with your above Bootloader screen settings, again I'd say you have nothing to worry about.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I agree too, if it flashes by super quick then it's still unlocked. There's no real concrete way to check if it's still unlocked other than that. If it really bugs you reroot, lock your bootloader with EZ Unlock, then Odin flash the stock image again. But I agree with the above post, it definitely checks out fine.
[Verizon Samsung Galaxy S III] Biker1:
@ SlimSloopOS

If the splash screen is one second or so, it is indicative of the Bootloader being 'Locked' ;)

And as you say, he can always Root his device, install EZ Unlock, lock his device if it isn't already, and use ODIN again, But I also think that is completely unnecessary, as the ODIN install already Locked the Bootloader, if the program ran correctly which it did by seeing PASS on the ODIN screen, and by the current Bootloader stock settings.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea and I do agree lol
[Verizon Samsung Galaxy S III] Biker1:
I concur, also lol :)

@ lennie paz

As per the info you provided, I'd say you're good to go, and there's not much more to verify,if anything.

The rep will look at your Settings menu, (check that as I mentioned earlier) if at all.

He or she may even look at your Bootloader screen, if at all.

Everything will be in order, and your exchange can commence......

Imo ;)
[Verizon Samsung Galaxy S III] lennie paz:
Here's a video of the phone booting up. Does it look like the Samsung logo is going too fast, or is it me?

http://www.youtube.com/watch?v=nWfLXEi6J7M
[Verizon Samsung Galaxy S III] Biker1:
That's indicative of a locked bootloader.

I think you're thinking too much about this.

I know you want to make sure your Bootloader is Locked but unless you want to:

Root

Install EZ Unlock

Lock if Unlocked

ODIN

Which I think is entirely Overkill from what you've shown me and verified so far, I wouldn't worry about it.

You will be fine ;)

Edit:

Btw, you answered your own question, as a fast boot up/splash screen is indicative of a Locked Bootloader, so if you think it looks too fast, that's good.
[Verizon Samsung Galaxy S III] lennie paz:
I just don't want Verizon to charge me full retail for my replacement phone. I think it's weird that it's going past the logo so fast, when I know I flashed the stock image through Odin, and also that the info in the recovery screen points to it being locked.
[Verizon Samsung Galaxy S III] Biker1:
You lost me.

If it going fast, that's what a Locked Bootloader will do.

If your Bootloader was unlocked the splash screen would stay on longer.

As I mentioned, you can Root and install EZ Unlock, check it out as we mentioned before, and ODIN again.

Even though I don't think it's necessary, that doesn't mean you don't, and may feel the need to go that route.

At this point, that is what you may have to do to have piece of mind.

EZ Unlock will let you know if you were Locked or Unlocked, but you have to go through the Rooting process again.

The Rep, if at all, will:

Check your Settings Menu

Check your Bootloader

The above checks out fine for a stock device.

But go the Root/EZ Unlock route if you feel the need to ;)

Edit:

Remember that even if you go the Root/EZ Unlock route to check your Bootloader, and then ODIN again, you will come full circle, and may be uncertain again, and want to do the Root/EZ Unlock route again, and you will be caught in a vicious circle, so to speak.

TRUST the ODIN program you flashed, and Trust your Settings, and you'll be fine.

As per my example, at some point in time, you'll need to trust that what the Rep will see, if checked, will ensure the return of your device as Stock with Locked Bootloader.
[Verizon Samsung Galaxy S III] lennie paz:
You are confused. When it flashes quick, it means it's still UNLOCKED. If it was locked, the logo would stay on for about 3-4 seconds.
[Verizon Samsung Galaxy S III] Biker1:
I believe it's Locked.

But as mentioned, you can:

Root

EZ Unlock

Check out if the ODIN program Locked your device.

If it did, then you know that the ODIN program worked, and you can be assured.

Then ODIN again.

If it didn't, Lock the device and then ODIN again.

As I said before, you still may have doubts after doing the above, and may feel compelled to start again and again.

As long as you flashed the property ODIN program, and it installed the boot.img I believe it is, you're fine.

But if you want to be sure, go the Root/EZ Unlock route, and see if ODIN Locked the Bootloader.

If it did, then then odds are it will Lock it again when you flash it again.

Edit:

As per the op --

" *These are full wipe versions that will format the internal sd and lock bootloader!!

Official VRBLK3 4.1.1"

If it didn't, there'd be many complaints, and it would be looked into if need be.

With the above being said, you can always Root and EZ Unlock, then ODIN again.

---------- Post added at 02:36 PM ---------- Previous post was at 02:12 PM ----------

I just checked my 'Samsung' splash screen, on my Unlocked S3, and it appears for ms, and looks to be twice as fast as yours, at least.

If I blinked, I'd miss it.

Yours is 'slow' compared to mine ;)
[Verizon Samsung Galaxy S III] Rushead:
Holy redundant posts, Batman.
[Verizon Samsung Galaxy S III] lennie paz:
I'm trying to root my son's S3, but the guide doesn't make sense to me. His phone is on 4.1.1 , and the guide says this:

"*However RootdebugFS does not work for 4.1.1 JellyBean. If you want Stock rooted Jellybean then there are 2 options! .

*Option 1 is to proceed to section 5 and use odin to flash a Stock pre-rooted Jellybean rom. Then follow steps 8-12 from this section for unlocking and flashing a custom recovery.

*Option 2 is to complete this section 1, then proceed to section 2 and flash a Jellybean rom via CWM or TWRP recovery."

Option 2 says to use RootdebugFS, and it clearly says RootdebugFS does not work on 4.1.1. I know I can use option 1, but was just curious about option 2 maybe being a mistake?
[Verizon Samsung Galaxy S III] lennie paz:
For anyone who was following my posts, about me not being sure if my bootloader was locked, because the Samsung logo was flashing fast, I installed the Official VRALG1 4.0.4 file using Odin just for the heck of it. When the phone booted, the Samsung logo stayed on for about 4-5 seconds, which was twice as long as when I flashed the Official VRBLK3 4.1.1 file. After accepting the factory updates on the phone, that put me on VRBLK3, I noticed the Samsung logo was only on for about 2 seconds. I've come to the conclusion, that older firmwares, make the Samsung logo stay on for about 4-5 seconds, and the latest firmware, only stays on for about 2 seconds. Just thought I would pass this along in case others weren't sure if their bootloader was locked when they send the phone in for warranty.
[Verizon Samsung Galaxy S III] sideoutjj:
I want to root my sons phone as well, just to get rid of the bloatware. He too has the 4.1.1 version, so I look forward to seeing what the answer here is.
[Verizon Samsung Galaxy S III] lennie paz:
I just used option 1. It was simple.
[Verizon Samsung Galaxy S III] ReFLeX135:
Hey guys. I am completely new to Samsung phones. I've rooted several different models of HTC phones without ever having issues. I tried to figure out the root process for the GS3 back in August. I've come to absolutely hate Odin. I followed guides and couldn't get it to work right with my device.

Since then I've reinstalled Windows on a new SSD and motherboard. I hope to successfully root this time.

I'm on the correct version of android that this guide applies to. I've not taken any ota updates.

my question is: Should I follow this guide's first post, or is it easier to take the JB ota and root that instead?

thanks for your help!

edit: I should probably mention that I intend to have the ability to flash custom roms. and yes I'm on Verizon.
[Verizon Samsung Galaxy S III] Rushead:
This is the simplest process I've ever encountered with a phone. For the life of me, I can't figure out why you guys are making it so complicated. This phone is virtually brick-proof.

Just follow whatever instructions you choose to the letter. It will work.
[Verizon Samsung Galaxy S III] ReFLeX135:
I appreciate the encouragement. It isn't so easy if Odin doesn't work no matter what you do...

And my reason for not just being flash happy before asking is that a friend bricked his GS2 and replacement, and wouldn't have if he had asked first.

And I don't have insurance.
[Verizon Samsung Galaxy S III] droidstyle:
What does not make sense? You download root66 vrblk3 put it in the pda function of odin and flash.
[Verizon Samsung Galaxy S III] lennie paz:
He's referring to my question I asked about using option 2.
[Verizon Samsung Galaxy S III] droidstyle:
i just told ya what to do....
[Verizon Samsung Galaxy S III] lennie paz:
I never said I don't know what to do. I said I was curious as to why the guide says to use option 2, when it clearly says option 2 won't work on 4.1.1
[Verizon Samsung Galaxy S III] dyskinesia:
Any news on 4.1.2 anytime soon?

Saw there was a leak a while back.

Not sure if we need or even want it
[Verizon Samsung Galaxy S III] edthesped:
root 66 version of the leak can be found here...

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

My opinion after 1 day...

- Better battery life (may be my imagination but I don't think so)

- Better GPS performance

- Super smooth, but so was 4.1

- Personalized text notifications.
[Verizon Samsung Galaxy S III] ravinaziankid:
Does anyone know where to get the Samsung drivers? The link in the OP is dead. Thank you.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It downloaded just fine using Dolphin Browser and Chrome. If that doesn't work for you, download it from Samsung's official website.