Root for Verizon GSIII

[tayswg20]

Sure did take a while but thank you for the help. I more than likely would have given up and spent another day trying to figure it out.

S3nt from Galaxy S3

Anytime

 

[anon(859166)]

Hey all, I'm new to the forum.

I took the root method described in the rootzwiki link and successfully obtained root. After rooting I noticed that I'm having some problems. I rooted right out of the box so I don't know if this was a general VZW GSIII issue or related to the rooted image.

1. T9 trace no longer works. It traces the path, but won't enter any words or show any predictive options.

2. I don't seem to have s-voice

I did a search on google and came up with nothing. Does anyone else have these problems? Can anyone help shed some light on the situation?

btw, thanks to the guys who do all the hard work making root possible.

 

[Cyber Warrior]

Hey all, I'm new to the forum.

I took the root method described in the rootzwiki link and successfully obtained root. After rooting I noticed that I'm having some problems. I rooted right out of the box so I don't know if this was a general VZW GSIII issue or related to the rooted image.

1. T9 trace no longer works. It traces the path, but won't enter any words or show any predictive options.

2. I don't seem to have s-voice

I did a search on google and came up with nothing. Does anyone else have these problems? Can anyone help shed some light on the situation?

btw, thanks to the guys who do all the hard work making root possible.

Did you use the stripped ROM in the first link? or the Stock version in the second link?

 

[anon(859166)]

Did you use the stripped ROM in the first link? or the Stock version in the second link?

Cyber warrior, thanks. I realized I used the stripped and flashed the regular one. Got all the bloat back, but my T9 trace still doesn't work. I gave up and installed Swype beta. I miss stock swype and my DX but this sgs3 is badass.

Anyone run into T9 trace issues? It won't even let me trace now even though the option is checked.

Sent from my SCH-I535 using Tapatalk 2

 

[Ricky Babalu]

It seems there were several issues with the Root method you selected and addressed in the below Post.

Originally Posted by open1your1eyes0 View Post
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.

I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.

Here is the link to the complete thread ( a long read, but well worth it Link), I would suggest that you flash "Route66" to have a stable ROM (see Post #1 for complete step by step instructions).

 

[npo]

So now that I'm rooted, will Verizon's updates cause problems? Not sure whether I need to be worried about disabling auto updates, etc. Thanks!

 

[Cyber Warrior]

Yeah.. You don't want to accept OTAs while rooted.. 90 percent of the time it will break root access. Devs will put out a rooted version of the OTA for you to flash manually.

 

[npo]

You don't want to accept OTAs...

Thanks! So I take that to mean that when an OTA is available I'll be prompted and can decline. That's how it worked on my BB, but just making sure it's the same for Android phones -- i.e. not automatically pushed and loaded by Verizon.

 

[Ricky Babalu]

Thanks! So I take that to mean that when an OTA is available I'll be prompted and can decline. That's how it worked on my BB, but just making sure it's the same for Android phones -- i.e. not automatically pushed and loaded by Verizon.

That is not the way it worked on my now retired Droid X, it eventually will get pushed. I am confident it will be the same on the S3.

The only way to avoid this was for me to "freeze the updater". I did this using TB and was able to stay on "Froyo" and not get the pesky notices.

 

[AdamHLG]

Quick question about that XDA thread (I just read all 40 pages).

I am on a rooted GNex now. My SGS3 arrives Friday. I'll still keep the GNex also by the way as I am in love with it.

Anyway... If I install CWR after root, will it work the same as on the GNex, i.e., once it's all installed, can I simply boot into recovery , make the same nandroid backups, flash mods, etc? Is it all the same? Also, will I be able to boot into recovery direct by holding up/down vol + power and then select boot into recovery?

I'd ask on the XDA thread but I'm not allowed to post in that thread because I don't have 10 posts on XDA :-(

 

[Cyber Warrior]

Yes it's the same.. ClockWorkMod Recovery.. It's volume up + Home button + Power button until you see the white Samsung letters.. Takes you right into CWM Recovery where you can make nandroids, flash ROMs, etc..

 

[AdamHLG]

Thanks.

Sent from my Galaxy Nexus using Tapatalk 2

 

[inm8num2]

So, I'm a bit confused. I know the phone has been rooted and even a kernel has been loaded using some workaround methods.

How does the future of the development on the phone look? Are devs going to move to the Samsung variant or stick with the Verizon version?

My primary concern is, will people with the Verizon encrypted GS3 be stuck waiting for Samsung/Verizon OTA updates to new versions of Android, or is the rooting access enough such that we'll be able to load custom ROMs from developers to avoid the wait?

 

[AdamHLG]

Just a note that I rooted my SGS3 within 2 minutes of activating it! Went without a hitch - works perfectly and rooted. Anyone scared to pull the trigger have no worries. It was easier to root this phone than it was to root my GNex!

 

[sicario666]

I just got an s3 replacement today. My box had an updated sticker on it. Here's a screenshot of the phone details. I'm curious to know if I can use the same root method or is the version that hasn't been cracked yet.

Sent from my SCH-I535 using Xparent Green Tapatalk 2

 

[jshannon]

So i'm trying to root my S3 and when I power it up with Odin it just sits on the "Downloading...Do not turn off target!!" screen. I'm not sure what I'm supposed to do here.

 

[sicario666]

So i'm trying to root my S3 and when I power it up with Odin it just sits on the "Downloading...Do not turn off target!!" screen. I'm not sure what I'm supposed to do here.

have you installed the device drivers and downloaded the tar file needed?

S3nt from GalaxyS3

 

[sicario666]

I can walk you through this. Its simple. Once you get the needed tar file which is the rooted version. Download the stock rooted version. Not the stock rooted debolat. I had problems with the debloated version.

The stock rooted tar file is huge. 1.5gigs. Once that is downloaded and drivers are installed. Go back into download mode. Plug the S3 back into your comp. Open Odin and click the PDA field. Then navigate to the folder where you have the tar file located. Double click the tar file then hit start. Be patient and let the comp do its thing. Then you can flash recovery. Backup. Download a rom and flash that.

If you need more help. Let me know.

S3nt from GalaxyS3

 

[sayheysarah]

So i'm trying to root my S3 and when I power it up with Odin it just sits on the "Downloading...Do not turn off target!!" screen. I'm not sure what I'm supposed to do here.

My GS3 was at this screen for quite awhile, then it did its stuff and it was all good.

 

[jshannon]

Thanks for the help. I've never used Odin so I missed the part about launching that on my computer.

How do I know if it worked? It rebooted but I don't really see anything different.