yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingwp1:
I just redid the whole process up to the point of having CWM installed. I had a nandroid backup from earlier take care of the rest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
MrR - sent you a PM :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingwp1:
Well, my suspicions were confirmed. Because of problems arising from that tether hack, I restored from a nandroid. Now my system status is back to Modified.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Fixing system size issue. Everyone go thank pinoymutt now for the PM which confirmed my suspicions. I encountered 3 problem areas doing this and pinoymutt confirmed /system had no space which was one of them so I have to redo the resize.

I won't be able to test myself till 10am est.

I'll need one or two more tries to get it perfect. (but i'll know before i post it so if try 1 works you'll see it earlier if i have to go through the injection again it'll need another half hour) You'll have to go through the process again but your counter won't increase still.

my thought is those who didn't see issues were de-bloated enough they had space left for stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastarifla:
Fantastic job!

The only issue I had was installing busybox, otherwise very straightforward!

Miles better than dealing with HTC phones

Thanks again!

PS. Is there any way we can get SuperSU instead of just SU? Sorry if I'm being picky >.<
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
wow feels good to be rooted.

but i am experiencing the system size problem..not a big deal but certainly looking forward to the fix :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Yea..my phone didn't want to boot after I installed busy box with the regular program...I think I tried installing/uninstalling and it gave me warnings about system stability.

I then restored to my nandroid backup. I then installed Busybox installer and now it said /System had room on it. Not sure if its because of Busybox installer or that I reverted back to my Nandroid backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sennant:
yea, just install it from the Market

---------- Post added at 08:06 AM ---------- Previous post was at 07:53 AM ----------

Nevermind. It installed SuperSU but doesn't get rid of the other.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frelnik:
Has anyone tried this with a Canadian (Bell/Telus/Rogers) i747M?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
One quick "search thread" for Rogers got me this: http://xdaforums.com/showpost.php?p=28030079&postcount=68

And if you're in the XDA app, you can still use the browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Ok guys, OP updated with new download. I checked system size and installed busybox and adway updated hosts no issues.

If you had used the old one your system size is at its limit of capacity so unless you remove bloat, as you install things into system you will run out of space.

I strongly recommend reflashing with Odin this new download. counter won't increase and nothing will get wiped that you have so should be a win/win for you except for the time spent which I'm sorry about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdbx18:
Thanks! Rooted and installed CWM on our two SGS3s inside of 30 mins.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
First Samsung phone so Odin is new to me, but why would you recommend we use Odin to flash it? Would CWM recovery not be sufficient?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
you can't flash it with cwm. its an odin tar and you need to use it first to not increase the flash counter or show system as modified.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
I see. Still too early this morning. Forgot it was a tar and not a zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lensgrabber:
One thing I noticed late last night was the Samsung T9 trace stopped working. Some times it will trace but nothing shows up as being typed. Most of the time it just acts as if trace is turned off. It's not a huge deal since I installed Swype (like it better anyway) but thought I might mention it to see if others have the problem. This was from the root tar yesterday. I'll flash the new one from this morning for the space fix when I get home.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altitude909:
Will reflashing the new one with Odin require CWM to be installed again? Also, after I did my initial nandroid backup, I cleaned house with titanium, installed busybox, etc and now my device status shows "modified" and the download mode shows "custom" (but counter still at zero and everything else is official), is that just a result of cleaning up the system apps? Will it go back to "normal" if I flashed the official rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wraithdu:
@mrRobinson

First, thanks for the work on this, very cool. When you have time, do you think you could post a step by step of how you created the image? I've read the linked threads, but you said there were tweaks and such you had to do to get it all working - I'd love to have a full guide to follow.

Keep it up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Same thing happened to me. If you flash the new file, it all comes back. Need to reinstall anything that went into /system though (like busybox)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
Do you think flashing the newer version will allow me to restore my nandroid? It starts to restore /data but fails a minute or so in. I soft bricked from forcing a build.prop that was too big into /system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hunter99507:
How do I get the latest attention firmware rooted. I don't see the latest update on the first page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hunter99507:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
power off, boot into recovery (hold power down + vol up), do a factory reset then reflash odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hunter99507:
I cant get into recoevery, I pulled the battery, then held power up + vol up key, it flashed samsung then samsung galaxt s3 logo, then went black screen. I held for over 30 seconds and when i let go it rebooted like normal.

I can get into download mode though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I thought you had to hold Home, too. I do it by holding home and vol up, then holding power until the phone vibrates. I release power at that point and wait until the Samsung logo flashes with some little blue text in the top-left. Then I release all the buttons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garbageguy:
newer baseband: I747UCLH9

i just got an at&t s3 and it was updated to the baseband: I747UCLH9 which is newer i believe than the one in the OP. to the OPoster, can i still use the one in the OP or should i wait for an updated version to be available? and if yes to the first question, would an OTA update wipe out root ?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
You are right. Forgot that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
you can flash the stock image in the op..then afterwards if you like you can flash the updated or most current modem..check in this section for the thread on cwm flash able modems..also if you accept an ota while rooted more then likely it will wipe out root..but if you use supesu instead of superuser it has a feature to protect root when accepting or doing an ota update..I have tried and it works fine..but keep in mind the ota will not work if your using a custom recovery..you will need to flash back to stock with stock recovery or it will fail when trying to flash itself..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sy007:
wtf.

ok not sure whats gone on i just rooted my telus s3 with everything downloaded from op it all went ok got super user etc. but my device status says modified! and i can no longer access my internal sd card though my pc i downloaded all drivers i got all 4 green ticks but still nothing? i know it worked as right b4 i rooted i put music on my phone though pc.. help any 1?

edit deleted drivers now cant access samsung mobile mtp.. tried kies tried the registry fix wiped cache done permissions done every thing i can find on this forum.. should i try flashing again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] damon412:
Not sure this will help but worth a try. My phone would never show up on my PC when I connected it(had Kies drivers installed and everything). I just went to the USB PC connection option that pops up when I connected my phone, swapped from MTP to PTP a few times and it showed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garbageguy:
thank you for your reply ! i haven't done this before on samsung phones (coming from atrix) - as for now i don't intend to go non-stock just yet... i just want to have stock + root and this seemed like a perfect solution... you make mention of flashing latest modem... i am assuming you mean via computer and not via a custom recovery right? (i don't intend on flashing a 'custom' rom yet) - and if yes, wouldn't that trigger the flash counter ?

and also, i imagine something like rootkeeper would work too if i ever get ota ? that's what i used on my asus tablet and it kept root from ics to jb... now if using rootkeeper + supersu to preserve root while the OTA installs, woulnd't the OTA bring in the new modem drivers ?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vanisleguy1976:
Just picked up the Roger's version of the S3! So happy to see the level of development and support!

I'll miss my HTC EVO3D but I'm really looking forward to my newest toy :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
it may be possible to flash a modem via Odin..but I myself haven't done so yet..someone with more experience would have to say for sure...the modem thread has cwm flashable modems..but you would need a custom recovery to flash one..the method in the op will not trip the counter..and you could flash stock touchwiz via odin all day long with out worry of tripping the counter..I have never tried root keeper..but I have tried the supersu feature I was speaking of..it works great and will do the trick for you..as far as I know the ota's that get pushed out have the new modems included..and if you decide to use cwm or twrp you can check out the modems thread in this section..grab one and flash it..the most current modems you can find there..hope this helped you out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Flashing anything via cwm will not trigger the counter. Flashing non stock things with odin does.

exactly. if you flash this then get an ota, just use rootkeeper to preserve root through the process. and yes the OTA would bring the new modem that is with that OTA. Sometimes even newer modems leak that aren't a part of any OTA and those you'd have to flash in CWM or fastboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sy007:
i dont have that option to as nothing shows on phone???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krazex2005:
I had the latest ota, completely stock, I installed the image in this thread and now my phone crashes when i get to the lock screen? any help? Im completely stock no CWM or anytihng just ODIN. So i need to find the same stock image I had to reflash with ODIN,can anyone help me out with some links I cant use my phone as of now. ALl the phone does is this ---> Starts up normally then gets to lock screen and tell me touchwiz stopped and that android.process.acore has stopped. I cant get passed the lockscreen, is there any way to flash something else with ODIN that helps corrects this issue. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Going from LH9 (the latest OTA) to LG1 (the version in the image in this thread) requires a factory reset. You can do that in recovery, but beware -- the stock recovery will wipe your entire internal SD card, including all photos, music, etc.

Another way to recover is to flash a custom recovery using Odin and then flash a rooted LH9 image with the custom recovery. You can follow the instructions in this post to flash TWRP (steps 1 and 5-11). Once you get to recovery, make a nandroid backup and then do a factory reset. Then, to go back to LH9, boot into the ROM (LG1) and download all the files in the PIECES section of this post. Then go back to recovery and flash them all before rebooting, making sure you flash the kernel after the ROM. After you do the flashing, you can restore just the data from the nandroid.

At the end, you'll be on LH9 with root and no lost data. You will have tripped the flash counter, but you can reset that with Triangle Away from the Play Store.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garbageguy:
it worked as you said, and you're awesome ! thank you for your hard work !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phat_cow:
I can't seem to get LTE when I flashed with this rom. I'm with Rogers. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
Failed at rooting.

I was already at the latest update, used the AT&T Image provided in first post. Flash went fine, but when phone rebooted got stuck in the loop of:

android.process.acore has stopped

and

Touchwiz has stopped.

Had to do factory reset to get back to stock and get phone to work again. What I would like to know is how did it go wrong; The odin flash went without a hiccup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Nothing went wrong, it's just that downgrading from LH9 (the latest release) to LG1 (the image you flashed with Odin) requires a factory reset.

There are some instructions for rooting LH9 directly without flashing the LG1 image here. My post two or three above this one describes how to recover from flashing the root-injected LG1 image without doing a factory reset.

By the way, you are now on LG1 and not LH9. If you want to get back to LH9, you can follow the instructions here. The easiest method is to download all the files in the PIECES section, flash them all in recovery before rebooting, making sure to flash the kernel after the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
Thanks, that's what I thought was happened. I think I am going to wait for the Jelly Bean release and grab a stock rom from that. Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
OK Got my phone rooted, but can't get the recovery installed. I am using the AT&T suggestion and downloaded the recovery-clockwork-5.8.4.5-d2att.img file

Put the file on my sdcard, and extSdCard and tried to install from both locations (I verified that the file was visible with an ls /sdcard and ls /extSdCard.)

shell@android:/mnt # dd if=/extSdCard/recovery-clockwork-5.8.4.5-d2att.img of=/d

ev/block/mmcblk0p18

ckwork-5.8.4.5-d2att.img of=/dev/block/mmcblk0p18 <

/extSdCard/recovery-clockwork-5.8.4.5-d2att.img: cannot open for read: No such f

ile or directory

1|shell@android:/mnt # dd if=/sdcard/recovery-clockwork-5.8.4.5-datt.img of=/dev

/block/mmcblk0p18

work-5.8.4.5-datt.img of=/dev/block/mmcblk0p18 <

/sdcard/recovery-clockwork-5.8.4.5-datt.img: cannot open for read: No such file

:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Grab goo manager or rom manager and install recovery that way. Will be easier for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
Thanks, downloaded and added recovery!:victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] docent000:
thanks for this

This is a very clear and good instruction.

I've got my SGS3 last Friday and rooted the same night using the OP.

Next day I updated to LH9 by following one of the instructions (with pieces to flash separately).

All good now. CWM was installed via Rom Manager - this is the easiest way, no dealing with ADB and the command line.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] runtohell121:
I probably messed up my phone by using the LG1 package over my updated LH9. Right now my phone is having "unfortuately, the process android.process.acore has stopped" and "TouchWiz home has stopped" Whats the fix for it? Sorry for not searching.

Didn't have a chance to install CWM yet

edit: can't even get into download mode.

edit2: unable to get into stock recovery also. Been trying to enter into stock recovery to do wipe.

edit3: nevermind, finally got it into recovery and doing wipe.

edit4: all fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xkam8x:
Looks like I made the same mistake and am stuck as well. If you get a chance, do you mind explaining how exactly did you fix the issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I described a way to recover from this without having to do a factory reset in this post. If you already have a custom recovery installed, you can skip the first Odin step.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] supermartin73:
Thank you! Rogers S3 rooted perfect!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synyster06Gates:
I really need to read before doing stuff. I ended up installing the older software over the newer software. Can I just use OTA updates and be okay? or do I need to download a ROM from here? I just want the stock software. Also, I'm on ATT here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
There are ways to install the OTA directly, but you have to take some steps to protect your root and you may need to install the stock recovery. I can't remember. If you don't want to be bothered with that, I suggest you download all the files in the PIECES section of this post and install them all in recovery before rebooting, making sure you install the kernel after the ROM. Make a nandroid first, of course, in case something goes wrong. At the end, you'll be on LH9 (the latest) with root and with the original Google Search from LEM (with the universal search still intact). You won't lose any data either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synyster06Gates:
How do I install the stock recovery? I think I'm going to start over from point 1. I have only had the phone since Monday so I didn't lose much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] runtohell121:
Stock recovery comes with Samsung phones already. You go into stock recovery by powering off the phone. Press and hold down the volume up + home + power button until screen shows the Samsung logo, let go of the buttons immediately when you see the logo though or at least that's how I go into recovery usually, might take a few tries at first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synyster06Gates:
Even if I flashed CWM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] runtohell121:
Same goes for CWM recovery. It's one or the other. So if you flashed CWM, you will boot into CWM Recovery. If you haven't flashed anything on it, it will go into stock recovery. Same procedure to get into recovery though. vol up + home + power
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
You can flash the attached zip in CWM to get back to the stock recovery if you really want to do that. Seems the hard way to me, but your call of course.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yami951:
about to root my friends at&t gs3, and this seems a little more complicated than doing the bootloader and rooting my gnex. will the OP be updated with the latest files and maybe the things to watch out for? I dont want to read all 122+ pages to find out what I should do with a phone that is updated to LH9, when the files should be available in the OP for that update. Helpful thread, but everything just seems spread out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
This post gives some directions for rooting LH9: http://xdaforums.com/showthread.php?p=32218479

The OP for this thread will be updated for LH9 as soon as the full ROM is released by AT&T. Until then, the method in the OP can cause problems if you are already on LH9 since it does a downgrade to LG1, which requires a factory reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Guess I'll update the op since all these latest questions are similar. Thanks for replying so quickly to everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synyster06Gates:
I just re started at point 1, flashing the stock rooted ROM, then flashed the 4 zips for the update. Easy enough!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lillejord:
I had the same problem with "android.process.acore has stopped" and I followed the above direction, sort of. I was still able to install Clockwork ROM Manager from the play store and install Clockwork Recovery from ROM Manager. It was somewhat painful with all the error messages but it did finally work. I went into recovery and made a backup and did a factory reset. I then downloaded the suggested files and flashed them. When I restored my backup I accidentally restored the ENTIRE backup, not just the data. So I immediately re-flashed everything, with out restarting the phone. When I restarted I had everything, apps and data. The Flash Counter, as far as I can tell has not been tripped, but the phone does say it has been modified. So, with this method, I don't think it is necessary to do a factory reset. Just flash over what you have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Right. The factory reset is only necessary to get your phone working with LG1 if you came from LH9. I only suggested doing that so you can get your phone running again in order to get the zip files for LH9 on to it. If you are sufficiently skilled to get them on in some other way (e.g., through adb while in recovery) or can suffer through the error messages long enough to get the files on your phone, you don't need to do the factory reset.

The primary problem here is that something in /data from LH9 causes the "android.process.acore has stopped" errors in LG1. Factory reset wipes that bad data from /data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trujap:
I wanted to know if I could use the same instructions to root my bell gs3 if I updated to jb already using the steps I found in the general forum?

Or do I need to find the stock rom and go back to that first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
You should be able to use the toolkit to root or the instructions here: http://xdaforums.com/showthread.php?p=32218479. Both will trip the flash counter, but you can use Triangle Away to clear it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trujap:
Awesome. I will have to look into this. Love using jb but the boatwear and battery draining is driving me mental. I usually root and install custom roms but wasn't going to do it on this device yet. That changed quickly hahaha

---------- Post added at 06:55 PM ---------- Previous post was at 06:50 PM ----------

Awesome. I will have to look into this. Love using jb but the boatwear and battery draining is driving me mental. I usually root and install custom roms but wasn't going to do it on this device yet. That changed quickly hahaha

The baseband I'm on is mvllh1 the instructions so for another number. Is there anything I need to be worried about doing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
No, the instructions are pretty generic and are essentially what the toolkit does (at least one of its rooting options). The only thing you might want to change is the recovery you're flash. The one I mentioned is TWRP for the 747. If you'd like to use a different one, just download the img file for it, rename it to recovery.img and replace the file in the twrp-2.2.2.0.tar.