yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tillithz:
I think what he means is two parts.

you will be able to adb in. (if you continue on)

you will be able to use su to take root. (when you boot into phone)

IF you are just doin root, you are done at that point. that is just an informational note if anything, i think. If you read the next step thats where you use adb.
[Verizon Samsung Galaxy S III] cmg5461:
Thank you for the clarification!
[Verizon Samsung Galaxy S III] thekendog:
invisiblek, I love you. Been using your nightlies on the Inc, and now you saved me. I didn't even have the phone 5 minutes before doing this. Worked like a charm. Woo!
[Verizon Samsung Galaxy S III] psalm462:
I am having problems with Titanium Backup. I see it on the SD card as a file and all the apps are there, but when I load the program and look for the restore, it doesn't see the apps from when I was on my Charge.
[Verizon Samsung Galaxy S III] johnjay829:
You have to change the backup location under settings it is looking on the internal memory which is listed as sdcard. Just detect on the phone should find it
[Verizon Samsung Galaxy S III] Tekn010933:
Great Work EK! But I will disagree on the boot.ani, I hate it more than you do :)
[Verizon Samsung Galaxy S III] tprouty:
Worked amazingly. did realize that they had the "stock" version rooted, just thought it was "stock" with no root. very good work here.
[Verizon Samsung Galaxy S III] s197:
Those having issues or are trying to use a Mac might want to try using Heimdall instead of Odin. Not sure if anyone has actually tried that yet, but it may be an option to explore.
[Verizon Samsung Galaxy S III] pozer69:
It is split into two parts, one for root and one to instal CWM Recovery.

If you want to install the recovery to do a backup, after the phone is booted into the OS (NOT ODIN), enable "USB Debuging" in settings, then plug in your usb cable, then from your command prompt you can adb into the phone to install the recovery.

If you do an

adb devices

You should be able to see your phone.
[Verizon Samsung Galaxy S III] BungeBash:
Can I get some clarification from the mod on several issues I'm noticing with this root.

1. The keyboard issues I stated before. The stock keyboards functionality ceases to work correctly. I.E - The auto correct and punctuation do not work. The stock swype will not work. The 3x4 Keyboard will not work.

2. This build has Sprint references in it, and does not match my BaseBand Verision of I535VRLF2. You have listed as using I535VRALF2. Why is this different. Is this why I have the Sprint references and odd options within settings.

3. NONE of my apps that are not by default landscape, will rotate into landscape anymore. I find it hard to believe I'm the only one who notices this. Open up music player, or google music or your browser. None will rotate into landscape anymore.

This is just to start. But it appears that I will have to revert back to stock to fix issues created. However, can I trust that the "stock" I535VRALF2 is actually Verizon's stock image. I would love for this thread to stay on topic about developments and issues for this image.
[Verizon Samsung Galaxy S III] elvenlemming:
I'm not sure about the other issues, but I believe the difference here is that the baseband version is I535VRLF2 and the build version is I535VRALF2. They are different because they refer to different things, despite being extremely similar. The Sprint references are likely from Samsung reuses parts of a single build to create the separate Verizon and Samsung builds.
[Verizon Samsung Galaxy S III] themusicmonkey:
Try toggling the Screen Rotation back on in your notification bar. I personally use SwiftKey, which works fine, but I keep getting a nagging notification to choose my keyboard.
[Verizon Samsung Galaxy S III] Coderedpl:
I installed the driver package Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0 but when I connect my galaxy s3 it still doesnt get detected by windows to install the drivers?

still says unknown device and i cant access the internal storage of the phone at all either

EDIT: I'm not using the supplied usb cable but another one I have that always worked with galaxy nexus, could this be why.

EDIT#2: wow, I switched USB ports and it detected and works, guess my computer is acting up now
[Verizon Samsung Galaxy S III] BungeBash:
I have. I have also tried rebooting the phone with screen rotation off, then booting up and turning it on. No change. Screen rotation = Dead. I have since done a factory reboot, lost messaging abilities, and my stock keyboards funtion worse.
[Verizon Samsung Galaxy S III] themusicmonkey:
I just noticed this. I went into the SQLite Editor app to get rid of that ongoing WiFi nag in the notification bar.

Normally it's here: Setting storage>settings.db>secure

When I tried to locate this, “wifi_networks_available_notification_on" on line 86, it wasn't there.

Anybody know why? What's up with all the missing lines? Could this be why we're having setting related issues?
[Verizon Samsung Galaxy S III] BungeBash:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Agreed. I'm sure it would be great if we can request someone of knowledge of this guide to remake the rooted system.img for us.

Link Here
[Verizon Samsung Galaxy S III] BungeBash:
****, so going back to stock I now get this CONSTANTLY:

process com.google.process.gapps has stopped
[Verizon Samsung Galaxy S III] Cicatrize:
Ehh ignore my post. Sorry. :-)
[Verizon Samsung Galaxy S III] themusicmonkey:
I got that on stock too, so I don't think that's anything new.
[Verizon Samsung Galaxy S III] open1your1eyes0:
I made a request thread here for any developer or user interested in helping us recreate the rooted system image. Would be of great assistance. :)

Link to Thread
[Verizon Samsung Galaxy S III] BeavermanA:
Thanks for the great work!
[Verizon Samsung Galaxy S III] droidstyle:
is this root.img different than whats packaged in the stock rom root/debloat package? Just wondering because I flashed that and everything works flawless for me, unless Im missing something?
[Verizon Samsung Galaxy S III] lynseyw:
Anyone able to tell me how to root using a mac? I also have parallels.
[Verizon Samsung Galaxy S III] minmongoblin:
If this isn't the thread for discussing how to use ADB on the phone...where is the thread? I tried owenbeal's method ( http://xdaforums.com/showthread.php?t=1759980 ) and the link to his YouTube leads to a Java method of installing, and it's broken. Basically the Java will not finish the install of the SDK even when I install the Java JDK that he tells us to. So honestly I'm hoping that's not the only way, because it's not working for me...

EDIT: I did root perfectly fine, however. Thanks for that portion of the post, Invisiblek!
[Verizon Samsung Galaxy S III] drmanhattan:
rooted no problem i cant get into twrp though just stock 3e recovery clockwork mod recovery works fine though... any ideas ?
[Verizon Samsung Galaxy S III] psalm462:
I rooted and everything is working great. I could not get ADB working either so I just skipped it. I spent more time trying to work on the ADB then I did rooting. Odin was really simple, but I had experience with it from my charge.
[Verizon Samsung Galaxy S III] minmongoblin:
Yeah, Odin was incredibly easy. I used it in my Fascinate days *shudder*

I guess I won't really worry about ADB access until more things start coming out for the Verizon S3...
[Verizon Samsung Galaxy S III] aj8600:
Jelly bean source nwas released! It's possible :)
[Verizon Samsung Galaxy S III] BKinney:
Was wondering if light flow is working on anyone's rooted S3?
[Verizon Samsung Galaxy S III] aj8600:
Is twrp installed the same way? Adb?

Or can we flash of cwr
[Verizon Samsung Galaxy S III] cadams122593:
really wanna try to root this phone on a mac since its the only thing i have right now. can anyone confirm that the mac versions that are hacked work with the s3 yet? or will heimdall work? open for anything. feel free to PM me.
[Verizon Samsung Galaxy S III] chickenmon:
seems like patience is a virtue.

After reading all 30 pages of this post I am left with this process has screwed up swype and texting for several users. And the stock recovery image is missing a A in the filename so its not really the true stock recovery image at least not for all. And when loaded shows radio freq screens not normally available so the stock image is probably from samsungs engineers. So for the time being this method of unrooting is probably not ready for prime time but only for those willing to screw up a $650 dollar phone and know how to recover if things go bad. Thanks to the devs and the guinea pigs. After destroying my samsung vibrant with a deleted internal sd card ICS encryption unsuccesful problem I learned my lesson. Dont be a noob and read all the post.
[Verizon Samsung Galaxy S III] C0mbe:
Really don't understand all these problems. I am rooted, and haven't seen any sprint elements, no FCs, and it's completely stable.
[Verizon Samsung Galaxy S III] themusicmonkey:
The main error I'm getting is the MAPSamsungService failing. That could be unrelated. And the database for setting storage is missing lines.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
Rename .tar files??

Getting ready to root SGS3, but am a bit uncertain about using the downloaded ...img.tar files, as I had none of these when rooting my Inc2.

Do I just delete the .tar and use the files as .img files? I looked at extracting them, but didn't think that gave the right file either.

How about the extra file Samsung-Updates.com-SCH-I535_VZW.zip that is mentioned...what to I name change this to, or do I do something else to it before using it?

Thanks.
[Verizon Samsung Galaxy S III] jdubau55:
No leave them as they are. The full image with be a .tar and the stripped image is zipped and needs to be extracted. It comes out as a .tar.md5 this tells ODIN to do a checksum on the file first.
[Verizon Samsung Galaxy S III] Gamer113:
It is located on line 10 in the rooted version
[Verizon Samsung Galaxy S III] themusicmonkey:
Thank you. Do you know where the keyboard ongoing notification line is? I'm not sure if anyone has ever found the appropriate line for that. I WANT to use SwiftKey, so I don't know why it keeps popping up after I've already selected something.
[Verizon Samsung Galaxy S III] jdubau55:
Mine doesn't do that. What do you mean popping up?
[Verizon Samsung Galaxy S III] ShadowMN:
Which system.img did you use? Stock or Stripped?
[Verizon Samsung Galaxy S III] psalm462:
I am using the stock version and I have had only one problem and that was the swype function on the Samsung keyboard. I downloaded the new Swype and it is ten times better. I have had no problems since. I have not frozen anything either with Titanium and my battery lasts all day. I am very happy.

Sent from my rooted SIII
[Verizon Samsung Galaxy S III] jackdubl:
Landscape works fine for me. And I use Swiftkey X, which also works fine. Not having any issues as long as I don't factory reset.

Also froze most Verizon and Samsung apps in titanium with no issues.
[Verizon Samsung Galaxy S III] pdinphx:
Does anyone know if a custom recovery image can be pushed via Root Explorer or ES File Explorer?

Pj

Phoenix, AZ
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
I am now rooted and have recovery! Many thanks to the OP and the guy who made the walk-through YouTube video.
[Verizon Samsung Galaxy S III] Gamer113:
I used this and all I can report is swype gone.

I didn't do a factory reset as others are reporting they did and having these other issues.
[Verizon Samsung Galaxy S III] jonhern:
how do i get the phone to connect to adb? there is no option for usb only, just connects as media device, nor can i eject the drives like i did with my razr to get adb working.

Edit: found this app and it worked perfectly, adb wireless, first time i used it, got TWRP installed. nice guide here http://www.androidegis.com/how-to/now-connect-your-android-device-through-adb-wirelessly-how-to/
[Verizon Samsung Galaxy S III] ScottIsMyName:
You have to enable debugging mode.
[Verizon Samsung Galaxy S III] jonhern:
i did have it on, would just connect as a media device. used adb wireless instead.
[Verizon Samsung Galaxy S III] raisins:
I was getting a com.android.phone has stopped constantly after I removed the ongoing wifi notification. So I reflashed the stripped version through Odin.

Unfortunately, my computer decided to blue screen in the middle of the process. Once it came back I reflashed again (I did not restart the phone though). It finished this time, but it gets stuck on the boot animation when it says "Samsung Galaxy SIII".

Right now I'm reflashing through Odin again... Hopefully it boots up this time

EDIT: Well it finished flashing, but now this time it's stuck on the Samsung logo with the blue LED

Any Idea what I should do?
[Verizon Samsung Galaxy S III] ssmaster:
My serial number is coming up as 000000000000000 under about phone -> status......
[Verizon Samsung Galaxy S III] preusstang:
reflash the stock rom mentioned in OP
[Verizon Samsung Galaxy S III] open1your1eyes0:
Hey guys. Don't mean to piggyback on this thread but in an effort resolve most of your issues with the rooted system.img you guys have used here, we have successfully created a PROPER factory stock image (with root) that is confirmed to have no keyboard issues, no crashes, no Sprint elements, and works identical to factory image. Highly advise to take a look at our thread if you are experiencing issues with the ROM posted here.

[SOLVED] PROPER Remake of Rooted Stock Image
[Verizon Samsung Galaxy S III] mangler1055:
Will this work using Heimdall or is Odin required? I've seen the question asked, but not answered.

Thanks!
[Verizon Samsung Galaxy S III] maplewood:
How does one confirm which build they have (i.e. does their just-delivered phone have that updated OTA or not?)
[Verizon Samsung Galaxy S III] BungeBash:
OTA's tend to not be with shipped phones for a month or so. Especially with the phone still in its early shipments, it is 99.9% doubtful that it would be shipping with the OTA installed. You can always check the software version on your phone by going to 'Settings > About Phone' if you would like to compare to this thread and double check.
[Verizon Samsung Galaxy S III] td911:
Can't get it to work.

Tried before the info about disabled apps, anyway got stuck on S3 Logo Screen.

Flashed Stock Rom, Reset system, Flashed Rooted img and still gets stuck on S3 logo screen.

Anyone else NOT able to get this done?

Just tried again.

Used the DDL image instead of the torrent, and it's all good.

It's butter!

Thanks
[Verizon Samsung Galaxy S III] Tbenson:
I have asked the same in the heimdall thread but have not got confirmation. I had to dig up an old windows box until confirmed.
[Verizon Samsung Galaxy S III] eastwood1:
Is there a way to get a recovery without having a sd card? My phone didnt come with a sd card. Im curious if im out of luck until i buy one or can i install a recovery without a sd card ? why cant i just flash a recovery using rom manager?

Thanks for any help.
[Verizon Samsung Galaxy S III] sincerity:
^just use adb to flash the recovery...I did with cwm and twrp and no problems.....easy as well...there are detailed guides.

Now accessing internal memory via said recovery is another battle.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
Not working...neither ClockworkMod nor Tether

Just got phone today and rooting went well. In fact it all seemed to go well.

BUT, two big things that I cannot get working are ROM Manager full backup, or any tether program. ROM Manager says that "You must have ClockworkMod Recovery installed before continuing". When I hit "install", it wants me to pick a phone...none of which are Galaxy s3's or even close.

Have I missed something, or can we not yet do ROM backups with ROM Manager?

The other problem is that I have tried four different tether programs, all which seem to work fine, but my laptop does not see any of these?!?! Setting are all the same as with my HTC Incredible 2 that worked flawlessly.

Thoughts and help appreciated.
[Verizon Samsung Galaxy S III] s197:
Look in the apps section. There's a thread on Wifi Tether with a link to the apk and also the settings you need to use for Verizon.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
Great help on the tether...

I just had to set

device profile to generic ics

. I was able to keep the setup method as

auto

and did not need to change to netd master.

Any feedback on the ROM Manager issue?
[Verizon Samsung Galaxy S III] sincerity:
you have to adb to get recovery installed right now....it's not that bad just follow the guide...
[Verizon Samsung Galaxy S III] babydreamer1520:
Thanks buddy!

Now Im working on how Tether. No apps working atm so maybe SQlite?
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
I do have ADB. I followed all the steps and did indeed get to the recovery mode on reboot. I've used two different recovery.img files, TeamWin and CWM.

Things seem as they were with my Inc2 (fully rooted and ClockWork Modded), but ROM Manager wants me to select a phone for the install...and none of my choices are ones I trust. I'm running CWM 5.0.0.8 which claims to be the latest version. I don't want to choose the wrong phone and have it mess things up.
[Verizon Samsung Galaxy S III] eastwood1:
Ok but what commands do i use for internal. The commands i see are sdcard and ill be using internal storage.
[Verizon Samsung Galaxy S III] sid8911:
if ur adb isnt working for the recovery try this

http://xdaforums.com/showthread.php?t=1764398
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
My ADB is working great, and I reboot in recovery mode to CWM 5.5, so I have CWM on the phone.

BUT I still cannot get ROM Manager to accept this fact and allow me to do a ROM backup. Is this a known issue for all of us, or just a problem for me.

Am I missing a step or a setting regarding the program or the phone. Why does it as to "Confirm Phone Model" and not give me the SGS3 choice?
[Verizon Samsung Galaxy S III] silasrye:
I was going through and disabling apps from starting up automatically using Rom toolbox and ran across FWUpgrade. You might want to think about disabling or freezing or uninstalling it as it might cause us update problems.

edit: and SysScope (i don't like the permissions or the name, full disclaimer, I don't know what it does)
[Verizon Samsung Galaxy S III] AndyMan386:
Is there an issue with the video camera in this? I rooted with the first thing keeping some off the stuff. Out at the bar and tried told record video, it looks like it recorded but when i try told watch it wont load..

Hate the autocorrect too.... cant type to without it changing told told, what a pain in the ass
[Verizon Samsung Galaxy S III] yukonhijack:
Works on mine. Looks like it drops the videos in the camera folder of the gallery.
[Verizon Samsung Galaxy S III] minmongoblin:
This doesn't work for me. I did manage to install the SDK on my computer but I still get ADB errors like "Yadda-yadda is not an internal or external command", that whole mess. Same with just trying to initiate the ADB by opening a command window in the same folder as the recovery .img

I'm seriously on my last leg here and am about to just give up on recovery entirely. Someone please help me. I installed the 4.1 SDK first by accident, then I installed the 4.0.3 SDK which is what I figured I needed. Still nothing working. Please help
[Verizon Samsung Galaxy S III] tekhna:
So having CWM should prevent any future update from installing, correct? It'll fail because the recovery is different?
[Verizon Samsung Galaxy S III] ZachPA:
Is ADB in your path? You can either set it in your environment variables for all CMD windows, or you can set it on the fly. Assuming you installed the SDK into the default location, which is c:\users\YOUR_USERNAME\AppData\Local\Android\android-sdk:

PATH=%PATH%;"C:\Users\YOUR_USERNAME\AppData\Local\Android\android-sdk\platform-tools"

I suspect for simplicity you'd want to just set that in the environment variables. Do that by going to control panel, system, advanced system properties, environment variables button, then under system variables, find the path variable, edit by putting a semi-colon and then the path to your adb.

Always worked for me.
[Verizon Samsung Galaxy S III] minmongoblin:
Okay, I at least got this far and got something when I typed "adb devices". I assume that's my phone.

Now, when I try to type "adb push recovery.img /sdcard" I get this in response: failed to copy 'recovery.img' to '/sdcard': Is a directory

What do I do to fix this?

Thank you for your help, by the way, those directions of yours got me closer than ever.
[Verizon Samsung Galaxy S III] AndyMan386:
so when i opened the songs when in astro the load fine, but yet from the gallery, they wont work
[Verizon Samsung Galaxy S III] Marcismo55:
Man..you couldnt have made this any easier. Rooted and running CWM now.

Thank you!
[Verizon Samsung Galaxy S III] tekhna:
FWIW, in what I am sure is an unrelated coincidence, after flashing CWM my phone's data connection has simply stopped working, even after reseting and toggling airplane mode numerous times. On all apps.
[Verizon Samsung Galaxy S III] ZachPA:
If that's what you typed, you're leaving off the trailing slash. There is one key difference between the linux command prompt and the Microsoft command prompt: the linux command prompt is absolutely unforgiving when it comes to case and location. If you type /sdcard, it assumes you mean a file, where if you type /sdcard/ it assumes you mean a directory, which is completely different from /SDcard/ and /sdcArd/.

Rooting this way by using adb and these instructions really requires one to be at least a bit familiar with both microsoft and linux command prompts. If you aren't readily able to diagnose why something may not be in your path, or why adb isn't pushing properly, I strongly urge you to step back for a moment and think about what you're doing. Do this wrong, and you stand the chance of bricking your new $600 device.

I definitely convey the above with the utmost respect and without any malice toward anyone (in other words... not a flame...). If you are ok with your knowledge at this point, you should be ok if you follow each instruction and command perfectly. Before you hit enter, you should make sure you have typed it correctly, too.
[Verizon Samsung Galaxy S III] minmongoblin:
Wow, I don't know how that last slash did not copy over when I copied Invisiblek's original commands. User error, indeed. Thank you for being patient with me! Everything's working perfectly now
[Verizon Samsung Galaxy S III] xformulax:
everything? try using swype on the stock keyboard?
[Verizon Samsung Galaxy S III] TheBiles:
Download the vastly superior Swype Beta.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
ROM Manager app does not work

Sorry to repost this, but it was never answered. Should my ROM Manager (latest version) app not work?

I tells me I need to "have ClockwordMod Recovery installed". I do have this v5.5.0.4 in recovery mode.

To install it at the app level, it wants me to choose a phone...none of which are Galaxy s3's.

Known problem with this app on SGS3's or error on my part?? Do I need to buy the pro version to resolve?

I've always had this work on my Inc2 with no problem in the past.

Thanks.
[Verizon Samsung Galaxy S III] Sniper_5:
sys = system, normal permissions for this.

Sent from my Droid X until I get my SGS3
[Verizon Samsung Galaxy S III] C0mbe:
Rom manager doesn't work because the VZW S3 recovery is unsupoorted. That said, boot into the recovery by powering off phone and holding vol up+home+power. You can create backups from here.
[Verizon Samsung Galaxy S III] toosurreal01:
Anybody else's serial number reading as 00000000000?

Menu>Settings>About Device>Status
[Verizon Samsung Galaxy S III] minmongoblin:
No, because I'm using Swype Beta :highfive: