yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
So no problems getting ViperXl up and running BUT now I really want to try Cyanogenmod but its not a Sense ROM. So I started monkeying around with S-off and no luck. I tried this method:

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

and I also tried the All In One Kit here:

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

Two odd things happen. After I flash the zip file I get FAILED (remote: 99 unknown fail). According to what I read I should be getting error 92 supercid etc etc

My SuperCID is 1111111 by the way

Also, when I get to the last three steps in the process, where I have to execute three individual commands once I have booted into android, I get no prompts in SuperUse to grant permissions. So when I reboot, S-on is still the situation

Anyway, that's my situ.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Go to the s-off thread and search for a fix for the "error 99" problem posted by Chongodroid, it's on about page 17 if I remember correctly.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
.

Found it. I'll get it a shot. Much thanks
[AT&T, Rogers HTC One X, Telstra One XL] exad:
All you really need to do is simulate a battery pull by pressing and holding power until the phone shuts off and then try again until it gives error 92,, Usually doesnt take more than a few tries,
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
I ran through Chongdroids steps to no avail and quite frankly his method is alot of steps to do over and again.

Exad: at what point do I do this simulated battery pull? Prior to starting the Facepalm method starting from step 1?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm pretty sure you simulate the battery pull when you get the error 99.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Exactly! If you get error 99 simulate a battery pull and try again. When you manage to get error 92 then continue with the rest of the process.
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Ok just to be clear, here's what I am hearing with respect to the steps you've outlined. Sorry - I am an engineer. I like a good process plan :

1. Flash the zip in fastboot

2. Error 99 pops up.

3. "Pull the battery" BUT keep the command line window open

4. Reboot it into bootloader holding power and volume down button at the same time

5. Once the phone reboots into bootloader, do I need to send the command "fastboot oem rebootRUU" or can I just go ahead and flash the zip again?

One more dumb question: according to the instructions in the Facepalm, once I flash the zip, and I get that error, I am to immediately run the command "adb reboot bootloader." If I get to the white boot HTC screen before the command executes, did I not run the command in time?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
1. Make sure you give the command " fastboot oem rebootRUU" while in bootloader, let it boot to the black HTC screen, then you flash the zip.

2. Yes.

3. Yes.

4. Yes.

5. You need to give the command "fastboot oem rebootRUU" before you flash the zip.

The other question, you don't give the command "adb reboot bootloader" after flashing the zip, you're supposed to give the command " fastboot oem boot" so it should boot to the OS, not the white bootloader screen.

Then you can give the last three commands (make sure adb debugging is turned on in developer settings though).

PS. You need to follow the instructions exactly, make sure you give the exact commands in the exact screens. Don't deviate from the instructions whatever or it'll fail.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] exad:
After simulating a battery pull, you'll want to start over from step 1(if you boot to the android os) or step 2 (if you boot right into fastboot).

I hope this is all making sense.....
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Yeah I meant fastboot oem boot on step 5. My bad.

Ok this is all making sense. I'll give it another try a little later and report back.
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
BAM!! WORKED!!! I am going to downgrade the touchpanel firmware and give cyanogen a try

THANKS THANKS THANKS

Thats not to say I wont have questions about the touchpanel downgrade:)
[AT&T, Rogers HTC One X, Telstra One XL] exad:
You only need to downgrade your touch panel firmware for AOSP roms that are not on the 3.4 kernel.
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Uh oh. I downgraded the firmware. Is this reason why GPS no longer works? Should I just go ahead and go back to the old firmware?

According to my phone I have kernal 3.0.51

This the thread I used to perform this operation:

http://xdaforums.com/showthread.php?t=2159863&page=2
[AT&T, Rogers HTC One X, Telstra One XL] exad:
No and no, a downgraded ts firmware will work on any Rom it's just not required for most.
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Os so any clue why my GPS is kaput? I spent about 30 minutes this morning looking for a fix and most of what I came across is for the nightlies or the experimental. I have the 10.0.0 stable release? I saw a few posts about installing a third GPS manager. I'd have to think that there has to be something native in the phone that wouldnt require me to resort to a 3rd party?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Have you tried flashing another radio?
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Hehehe if I knew what that meant I would do it. I did come across some posts about radios and I figured this has something to do with my issue. I just havent had any time to do some research. I am open to any suggestions/ tips etc. I'll keep reading in the meantime. Thanks
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
The radio is the firmware which controls all wireless activity on your device. You just flash the zip in recovery like you would flash a ROM. Wipe cache and dalvik cache to be safe.

There's a thread here which lists all of them. If you're running CM10 though, only pay attention to the CM10 part of the list.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Flashing a radio refers to writting a new radio driver to your phone for use by the android OS. It is important to note that Sense and CM look to different locations for the radio driver so flashing a sense radio on CM or vice versa will have no effect.

That being said: http://xdaforums.com/showthread.php?t=1671237

Scroll down to radios, click the link and you will see a division of CM radios and Sense Radios. If I am not mistaken Sense radios require S-OFF to flash and CM Radios do not. Do not quote me on this, I can't recall exactly.

---------- Post added at 11:20 AM ---------- Previous post was at 11:20 AM ----------

Beat me to it :(
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Thanks Fellas. I am heading over there now...

Out of curiosity, alot of the research I've done points to alot of people using the 10.1 Nightly Build. Any particular reason that I shouldnt give the 10.1 a try? How unstable is it in reality?
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Me too :P

The radio thread is well written. The top post explains the concept quite well.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Lol sorry man it's 2:24am, can't sleep, ain't got nothing to do except linger here :p

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Yep, reading it now. I have Redpoint's Index bookmarked. I am familiar with this page.

Holy Smokes there's a lot of radios listed. Which one do I want? ATT 3.18: http://d-h.st/DcT?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
CM 10.1 is pretty stable, with the occasional random reboot. If you want complete stability, go with a Sense ROM, but it's not like you'll be getting reboots every 20 minutes or anything like that.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
The one for your carrier "should" work best. You can try them all if you like. Monitor heat, speeds, signal and use the best one for you.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
There is no definitive way to answer that question. Everyone has different expectations, preferences and requirements for what they consider "stable" or reasons why/why not to try out a ROM. Read through the CM10.1 thread, and see if any of the common issues are deal breakers for you. Otherwise, if it intrigues you, just flash it and give it a try!

Really there is no good reason

not

to try out a ROM. Half the fun is in the experimentation.
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Gotcha. I'll stick with 10.0.0. When I get bored I'll try 10.1
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
Got the radio to work. Thanks Gentlemen
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
I flashed to the CM 10.1. Installed the same radio I used on the 10.0.0 and the wifi sucks

Can I use one of the sense Radios on this build? Or I have to specifically use the radios that are list as specifically for 10.x?
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
You can flash the Sense radios bit they won't do anything. The CM10.x ones are the only ones that affect CM10.x ROMs because they store radio in /system instead of a special radio partition like Sense ROMs.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What he said. But keep in mind you don't need to stick to the radios for your carrier, any of those cm10.x radios will work. Best idea is to experiment a little and see what works best.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Fivetenfrank:
I couldnt get the Rage ROM to boot/ Very Strange. Would boot to the setup page after booting into Android. three steps in - when i get to the page that allows me to find my wifi network and then pop my password in - poof! It reboots. I have tried a full wipe, the whole nine yards. Same thing.

Any suggestions? I used TWRP 2.3.3.1 by the way

Edit: nevermind. Figured it out
[Sprint Samsung Galaxy S III] seb0910:
Hi. I tried following a simple guide to rooting my S3, but it failed horribly. I followed the steps (download Odin+this file, load the file into Odin, hit Start and bam your phone's rooted) but it failed. Here's the log from Odin.

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

Now my phone won't run properly, it says to run Kies in recovery mode or something but I don't understand. In retrospect I should've downloaded Kies onto my computer first, as well as SU onto my phone, and I probably should've found out my model number, but here I am.

I'm not trying to install a custom OS, I just want root access so I can use root-only apps. Can anyone tell me how to save my phone?
[Sprint Samsung Galaxy S III] jdelano:
if you have a custom recovery installed go here

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

if you need to use odin to restore your phone to proper working order go here

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

good luck, make sure to read everything about what you attempt to put on your phone going forward :)
[Sprint Samsung Galaxy S III] CNexus:
You may just have bricked your phone, because that package was for the international variant.
[Sprint Samsung Galaxy S III] seb0910:
relieved

Wow, thanks a lot man! I will be sure to!
[Sprint Samsung Galaxy S III] jdelano:
You're welcome, if you have bricked due to the fact that you flashed the international version, there is an older thread that describes how to recover from that here.

http://xdaforums.com/showthread.php?t=1727171
[Sprint Samsung Galaxy S III] CNexus:
If it's a true brick then that won't work, because in a real brick the phone doesn't even turn on. When that thread refers to a brick, it's really referring to a soft brick which is easy to recover from.
[Sprint Samsung Galaxy S III] jdelano:
yes, I am assuming soft because the OP said "Now my phone won't run properly", not it won't turn on. I know its bad to assume but I took the leap any way :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayemprady:
Hi guys,

My beloved S3 is is > 1 year old now.

I was always afraid\skeptical of rooting it as it lead to void warranty

Since it is already > 1 year old and warranty does not come into picture now, I thought why not give it a try now..

I see many S3 users are more than efficient after root.

Should I go for it ?:confused::confused::confused::confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markdexter:
Yes, unleash your device!! It's easy, and opens up a whole new way to interact with your phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Yes, root to experience the full capabilities of your phone.

Please be sure to read all guides and FAQs and be familiar with GS3 terminology.

Read tons....i mean TONS!! :)

Search and reading will be your besfriends.

Root, experiment, enjoy greatness :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackmoor2000:
Root and unleash the chains that bind you.

Take it from a noob, read, read and re-read.

Easier to read about potential problems before they arise than after.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
i can has root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
Rooting is a must. I went for root the day i got the phone and went reading up on rooting the S3, roms, etc. before i even got the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i root SGH i777:
first thing i did when i got my s3 in april was root it. and my dad has the same phone i have, and i have to say having mine rooted vs his stock, mine gets so much better battery life. and is just one of the perks of rooting other than overclock and underclock and custom roms and stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
...and Sammy phones are fairly fool proof when it comes to rooting and flashing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayemprady:
Yes, it seems like we have many 1 click tools to do this.

I just want to go slow, I want to unlock the boot loader first & then uninstall all the att crap..

that should free up some space n RAM..

Later on I can install custom ROM's and Kernels if need be..

This can be done right...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knucklesmckay:
First thing you should do is make a backup of your stock unmodified system before you remove or erase anything or install roms. And also make a copy of the backup to a second location like a computer.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
S3 doesn't have a locked bootloader. Reality just have to flash a rooted stock firmware in Odin and you are good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayemprady:
yes,,

1) unlock boot loader

2) take backup of everything using titanium

3) then uninstall all the useless apps which came along with att

4) if required i will flash custom rom and kernel else i will stick with everything stock..

The reason I want to stop at unlocked boot loader is that as of now I already have 4.1.1, and I have read everywhere that 4.1.2 isn't much of a revolution so why flash a custom ROM. People might not agree with this but I tend to think so...

Obviously any suggestions are appreciated....:fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
No

Don't even think about touching anything dealing with bootloaders.

The i747 comes with an unlocked boot loader, the only one that is locked is the Verizon S3.

There have been various bricked S3 by trying to "unlock" something that isnt locked.

Read read read and search and research.

Before you wind up with a paperweight ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knucklesmckay:
No I am not talking about just backing everything up with titanium backup. I am talking about backing up your stock untouched system with a custom recovery like twrp or clockwork recovery. After root you will most likely have a custom recovery installed like twrp. You can boot into this custom recovery and backup the entire system in its current state, because sometimes when certain system apps are removed you will get force closes and bootloops and the only way to restore your phone is by restoring a backup, flashing a rom or pushing a system to your phone via odin.

Removing stock apps that came with your phone can be risky at times because they are often tied to other systems. Search to see what apps are safe to remove and a system backup is probably good.

http://xdaforums.com/showthread.php?t=1746665
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Do not attempt to unlock the bootloader! It is unlocked already. Your proper plan of action should be:

Backup everything possible (MyBackup is what I used)

Root phone (several methods available, choose one)

Install custom recovery. Rom Manager can install CWM for you, while goo manager can install TWRP (I prefer twrp)

Follow instructions for installation off any Rom you download (found in the first post of that Roms thread, usually before you get to the dl link)

Before flashing or attempting any mod, make a back up of everything. And read the directions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Mine is still under warranty and its rooted. Open its can of whoop a** :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bubba Fett:
The cool thing for you will be all the awesome tweaks and mods that have out in the last few months because you device is a little elderly. Check out the definitive mod thread in the T-Mobile S3 forum. I forget which thread its in. You can atleast double battery and speed and 20x the customization options. Once you flash a new rom it becomes a habit called flashaholism so be aware. My name is Bubba Fett and I'm a flasaholic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayemprady:
Finally I did it,, My Galaxy S3 is rooted successfully..

Thanks to you guys & online sources..

-Root is done

-Backup using CWM is taken, a copy is there on Internal Memory, External Memory Card and My Computer

Next step-

-Remove bloatware and free some storage..

-Any idea which is the best stable ROM as of now for 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmccool80:
There is no best ROM it all depends on the user. Feel free to try any of them. Just make a Nandroid backup each time before you flash a new one and follow the devs installation instructions. Good luck and have fun!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hw4ng3r:
I've tried Cyanogenmod, PAC, and AOKP in the past week. All three are butter smooth and stable. You will have to cycle the battery a couple of times for it to fit in (I noticed upon initial flash, battery life was terrible).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yes. Battery stats usually take a bit to calibrate themselves. That is why it is good to test a bunch of roms out and don't judge them right away, sometimes it takes a while for things to settle in. We have a great set of roms for the GS3 both AOSP and TW based. Its an awesome device for rooting and romming.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scotteb:
One could compare not rooting a phone to an IPHONE, but once rooted........it becomes an OMGphone!!! Android all the way!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Whoa whoa whoa buddy.lol

Android can do WAY more out of the box than iPhone. Even with out root, icrap doesn't compare.

Galaxy S3 / AoCP / V4A / Turbocharged
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deathsting_50cal:
I would suggest that you do... but only if you're comfortable around computers... lol Yes there are simple "1" click rooting software out there, that's not the issue. The issue is when it doesn't work the way it was intended.. it's the troubleshooting steps that you have to take into consideration. Flashing rom is a like an addiction. Once you flash a rom, you want to know what the other does better, and so on... and eventually you will land on a rom that soft bricks (Worst case: hard brick) your device..

So is it worth it to root your s3? YES!

Just be willing to spend some time on forums if something goes wrong...

Best of luck!

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
I agree that while rooting has its advantages, you need to invest the time to read up on it. You will need to understand the good, the bad, and the caveats. It cannot be stressed enough that you need to be willing to spend a lot of time working towards fixing problems when and if they occur on your own. By this point, most issues that could occur have already been addressed so you need to be able to search and read a lot.

Sent from my SAMSUNG-SGH-I747
[Transformer TF300T Q&A, Help & Troubleshooting] samus88:
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.

EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!

i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
[Transformer TF300T Q&A, Help & Troubleshooting] samus88:
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
[Transformer TF300T Q&A, Help & Troubleshooting] noahvt:
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?

Sent from my ASUS Transformer Pad TF300T
[Transformer TF300T Q&A, Help & Troubleshooting] samus88:
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
[Transformer TF300T Q&A, Help & Troubleshooting] noahvt:
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://xdaforums.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!

EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!

Sent from my ASUS Transformer Pad TF300T