yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nubreed000:
I dunno about that man...I rooted, and after a few days it's been nothing but problems. Phone would restart randomly, go into a boot loop, screen would turn itself on and the power menu would appear all on its own before the phone restarted again. I flashed Carbon after that to see if it would help, and it didn't.

Went back to stock ROM...and the first day it was unusable. It seems to have gotten better. Today is the first day in 3-ish weeks where the phone has managed to stay on all day.

Moving on though: how come there isn't a way to root via ODIN anymore? Is it in the works or have people given up on the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Root (or towelroot) couldn't have been the cause of your issues. All it can do is allow apps root access to your system. Something else must have gone wrong, especially if you had trouble on multiple roms.

Development on root66 stopped because it really wasn't needed with towel root making things so easy. Plus there is no NE4 firmware to inject root into.

Since the later 4.4.2 builds are patched against it though, he might be willing to do those for you guys. But I can't speak for him, so don't expect it. He's moved on from the S3, so I really don't know how much time he would have to devote to it now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Here is my first try at 4.4.2 - Rogers

root66_RWC_I747MVLUFNF2.7z
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Has no one given this a try???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adizzzle:
Waiting for the Telus - root for 4.4.2

I747MVLUFNK2

Edit: Tripped the counter but am now rooted!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moiz Ahmed:
Bell Anyone?

can you do one for I747MVLUFNK2 BELL?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] badbambam:
Bell 4.4.2?

Hello, I was just wondering if there are any new updates to this OS coming? I's running 4.4.2 an I updated over one of your rooted 4.3 I think and now it's not rooted properly.

At least root checkers report back as such. Now just wondering if I should wait for an update without flashing back to 4.3 rooted version.

Thank You

BBB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you still have a custom recovery (CWM, TWRP, or Philz) on your device you can root by downloading the SuperSu.zip from Chainfire's thread, place it on your phone, and then flash it from recovery. This is how many are restoring root when updated to 4.4.x or 5.0.x.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoonus:
I have an ATT Galaxy S3 (SGH-i747).

I am running CM11 Android 4.4.4 Baseband I747UCDMG2.

I need to go back to stock to SIM unlock the phone.

Can I odin and use ATT stock rom 4.1.1 (root66_ATT_I747UCDLK3.7z) with baseband I747UCDLK3?

Will downgrading from 4.4.4 to 4.1.1 (Baseband downgrade from I747UCDMG2 to I747UCDLK3) brick the phone?

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I think I saw a reply to you in another thread, but in case I didn't:

The bootloader and modem versions will determine if it is safe to make the downgrades.

For this device, if the versions are MJB or newer, downgrading the bootloader and modem can cause a brick.

Stock ROMs from the OEM will change the bootloader and modem to match the ROM version. Do not use them if your bootloader and modem are MJB or newer and the ROM you want to flash is older. Some of the stock images in the forums are just that, they are close to exact copies of the stock ROM. Some of these will also flash bootloader, modem, and stock recovery. Read carefully. Others do not change the bootloader and modem. You need to be sure what you have in hand.

Custom ROMs do not install bootloader and modems, of course now that I have said this one of us will probably find an exception. This is why your ROM version does not have to match your bootloader and modem versions, you are a case in point.

To be certain of your bootloader and modem versions, if you have any doubt, there is a 'Samsung Info' app in the PlayStore. Personally, I determine this using these terminal emulator commands:

getprop ro.bootloader

getprop | grep version.baseband

If you are truly on the MG2 bootloader and modem it is safe for you to downgrade to LK3 in the way you asked. This is what I did to use the free unlock.

Long winded, but I wanted to be clear, especially if someone else comes across this in the future.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoonus:
Thanks for the detailed answer. It really helps to get a long answer.

I am helping a friend over phone to unlock S3. Since he is on CM11, it doesn't take the unlock code. I need to flash with stock first.

Thanks for telling the way to determine bootloader and baseband.

I will have him install 'Phone Info' and get details. https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

I will update the post on how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoonus:
update

Update:

Using the play store app and manual commads, I confirmed bootloader and baseband are I747UCDMG2.

That's the good news.

I will update how flashing 4.1.1 stock ROM goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I hope all goes well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoonus:
Thanks all for the assurance and support.

I was able to ODIN to stock ROM and SIM unlock the phone.

Background: My ATT S3 i747 was running CM11 Android 4.4.4. Baseband and Bootloader was I747UCDMG2.

Steps:

1. Flashed rooted stock ROM (root66_ATT_I747UCDLK3.7z) using odin. Followed the steps in OP.

After flash ODIN showed PASS and phone rebooted. It was stuck in Samsung logo. I booted into recovery. Performed a wipe cache and factory restore.

Phone rebooted successfully after that.

2. Inserted non-ATT SIM and it asked for the unlock code. I had obtained the code from ATT before. Used the code and phone was unlocked.

The same code did not work while I was running CM11.

NOTE: When running stock ROM you can follow steps in below threads if direct unlock did not work for you.

1. http://xdaforums.com/showpost.php?p=58671214&postcount=152

2. http://xdaforums.com/showthread.php?p=38767845#post38767845 This works only with stock 4.1.1 image (LK3 modem).

See http://xdaforums.com/showpost.php?p=59029460&postcount=323

NOTE: If you need TWRP recovery, search for "Odin Flashable TWRP Recovery" in OP. You can download ODIN flashable TWRP from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StarFire_MK2:
I have a Rogers S3. I have tried both the Rogers 4.3 and 4.1.2 JB ROMS listed here, using Odin 3.07 and following the OP. On all attempts at flashing, I get a fail message. I now cannot boot into recovery or into the phone. I can still boot into download. Any suggestions would be appreciated. The phone was running KK4.4.2 prior to my flash attempt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Don't flash those anymore.

Odin is saving you from bricking your phone. You are trying to downgrade your bootloader and modem if you flash a 4.3 or 4.1.2 stock rom. If you had succeeded you would have probably been looking for a jtag service to help you. At the least you would have been learning to boot from a debrick image on an external sdcard.

I haven't reviewed this thread in a while, but see if he has posted a 4.4.2 version. Otherwise you will need to find another method to root. ( I think you could actually use Odin to flash TWRP, and then use TWRP to flash a rooted ROM. Check to make sure.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
I am currently on 5.1.1 Dirty Unicorn, and I want to go back to stock TouchWiz 4.3 with TWRP Recovery.

My phone shows that my bootloader is I747MVLUEMK5. Can I use Odin to flash the tar file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Mk5 is for the i747m. You can flash the stock rom from sammobile.com but the rom must be mk5 or higher.

Flashing stock rom from sammobile.com will replace twrp with stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazeazn:
That Long-winded answer was what I was looking for! Thank you so much, now I can stop hunting around XDA to see if I can unlock my two GS3s. (bc i cant!):good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
The unlock that needs the downgrade to 4.1.1 is to unlock the sim to make the phone open to use on various carriers. Once you are on the 4.3 or newer bootloader the only way I have heard of sim unlocking the phone is a paid method from a third party provider. (I've seen references to ones on EBay but I don't have a name. [MENTION=4673498]audit13[/MENTION] may be able to help.)

People at times talk about locked bootloaders and methods to unlock them. I have two SGS3 phones, an i535 (Verizon) and an i747 (AT&T). The i535 has a locked bootloader in the strictest sense if you upgrade to the NE1 bootloader: You can not install a custom recovery nor can you change the kernel.

Some refer to the i747 as having a locked bootloader. In the true sense of locked, it does not have a locked bootloader. You can install custom recoveries and change kernels no matter the bootloader installed. What you can not do is downgrade bootloader once you are on the MJB bootloader or newer (which causes you to be unable to downgrade for the free sim unlock). BTW, once the phone is on the NE4 bootloader, or newer, the bootloader and modem versions must match.

Sorry about getting long winded again, I did so hoping to clarify any lingering questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazeazn:
[Oops posted in a different thread: basically I have 2 ATT GS3s both running on NJ2 with CWM 6.0.4.7 and CM 10.2.1 I needed to unlock so I can use T-Mobile and I found your thread]

You're amazing! Last question though, If I download these:

http://xdaforums.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

Flashable S3 Stock recovery AND Flashable Rooted NJ2 system.img and boot.img and install in that order would that put me back to complete stock? I'm confused as to how to install a stock recovery back onto a custom recovery (as I've never got this way) viz the recovery as it seems those files arent installed via Odin...

or can I pull the stock recovery from here:

http://galaxys3root.com/galaxy-s3-t...l-stock-recovery-and-update-ota-on-galaxy-s3/

and then install NJ2 system.img and boot.img from the above zip

I'm still an AT&T customer (more than 15 years) so I can technically request up to 5 unlock codes a year. I was under the impression that the phones needed to get back to their "original" state, [root or no root?], for me to input the unlock code.

Thanks a bunch!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
The unlock code must be entered into the stock dialer. So some custom TW roms will work, provided the dialer hasn't been changed.

The flashable system and boot images from enewman17 will bring you back to stock with root. If you are just wanting to unlock it using the dialer code, you don't need to worry about the stock recovery.

If you need stock recovery, the one in enewman17's thread should be just fine. Just flash in your current recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
My understanding re: the unlock codes from AT&T is that you must be fully stock. I seem to recall that root is okay as long as you are on the stock ROM with stock recovery. I think AT&T provides you with one code that is valid for 5 attempts to unlock. So if you remain rooted and attempt the code and the unlock is unsuccessful do not give it more than maybe two attempts before unrooting.

Flash the NJ2 system.img and boot.img from your custom recovery first. Based on the NJ2 thread you linked, after flashing the above, unroot and then flash the stock recovery from within the custom recovery. enewman17 had those instructions in one of his threads, but I can't seem to find them now. I would get all of the files from enewman17's NJ2 thread rather than the galaxyS3root site, just my preference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazeazn:
perfection!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Glad its working for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crazeazn:
for future reference if anyone is going the opposite direction like I am, you do not need to unroot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OneLonelyPolka-Dot:
What image should I use for AT&T running 4.4.2?

My build is UCUFNJ2 and I can't find an image for anything later than 4.3.

Someone made a brief mention of another method for rooting using CWM, but didn't elaborate. Point me in the right direction?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you already have a custom recovery installed (CWM, TWRP, or Philz) there is a flashable zip in the SuperSu stable thread. I don't know if that method will trip flash counter or not.

To me it's not a worry if flash counter is tripped, any warranty period on my device is long over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heliumballoon:
Need help please...

Hi,

Can anyone please help with this (I already posted this on a different thread, but since it's an old device, I'm not sure ppl are still looking at it...sorry):

My friend has AT&T galaxy S3 and got an OTA update and now on: I747UCUFNJ2.

Since the update, settings application crashes, like others had here. I suggested root, then custom recovery then flash either the stock rom provided by enewman17 or the rooted stock by enewman17 , but he did not want root, just everything fixed on the stock rom, no rooting.

I downloaded the stock rom by enewman17, then wipe cache, wipe data/factory reset in (stock) recovery, then flash from sd card (the stock NJ2 rom provided by enewman17). It failed with signature verification error.

Now I can get into download mode and also stock recovery. The phone boots up into the OS, but cannot get past the setup process as settings app keep crashing.

I tried using odin to flash CWM (latest) but even though it succeeds, on boot to recovery it always goes back to stock recovery. So I can't get into CWM to disable signature verification.

Also tried to flash 4.1.1 from sammobile, but it failed doing check version, saying the rom im flashing is older. (maybe that's a good thing, since it might have bricked it if it did...)

Tried using "SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9" from here in XDA, but it seems to require the OS to be up and running, but now I can't get there...

Any ideas how to install the CWM and prevent the stock recovery from running on boot?

Thanks for any help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Check the NJ2 thread you posted in for a reply by me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Hope this helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
You are exactly right. I just installed busybox and my device status still read normal. I then rebooted my phone and quickly jumped into settings. Sure enough I read "scanning." I waited a few seconds and then it switched to modified. I am almost positive now that it only checks this after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
interesting. this "scan" should be something we can kill...

though again it doesn't really matter. You still flash to stock before any warranty return/repair and as long as the counter didn't trip you'd be fine. Just be interesting to see what process is scanning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] terrymc:
There is an app called (root) triangle

Away. It removes the triangle and counter on "Some" Samsung phones , read details carefully can potentially brick phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Doesn't work yet for our phones. Read the fine print...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Well here is our "evil" service identifying busybox as DANGEROUS. Indeed.

I/SysScopeService( 861): add service
I/SysScopeService( 861): registerAlarm, interval:86400000
W/SysScopeService( 861): onCreate
W/SysScopeService( 861): onStart Intent { cmp=com.sec.android.app.sysscope/.service.SysScopeService }
W/SysScopeService( 861): onStart Intent { act=com.sec.intent.action.SYSSCOPE flg=0x4 (has extras) }
I/SysScopeService( 861): periodic:true
W/SysScopeService( 861): setState state=1
V/AlarmManager( 534): waitForAlarm result :8
W/SysScopeService( 861): handleMessage
W/SysScopeService( 861): current state = SYSSCOPE_STATE_INIT, next state = SYDSCOPE_STATE_RUN
W/SysScopeService( 861): setState state=2
W/SysScopeService( 861): handleMessage
W/SysScopeService( 861): current state = SYDSCOPE_STATE_RUN, next state = SYDSCOPE_STATE_DONE
W/SysScopeService( 861): OnJobProgressListener.onStart: total = 5, listener=0
I/SysScopeDiagnosisManager( 861): SysDiagnosisManager > call storeResult2
I/SysScopeDiagnosisManager( 861): SysDiagnosisManager > storeResult:1
W/SysScopeService( 861): OnJobProgressListener.onFinish: true, info = Sat Jun 30 14:27:47 EDT 2012
W/SysScopeService( 861): DANGEROUS_FILE_DETECTED: /system/bin/busybox
W/SysScopeService( 861): setState state=3
W/SysScopeService( 861): handleMessage
W/SysScopeService( 861): current state = SYDSCOPE_STATE_DONE, next state = SYDSCOPE_STATE_NULL
W/SysScopeService( 861): setState state=0
W/SysScopeService( 861): handleMessage
W/SysScopeService( 861): current state = SYDSCOPE_STATE_NULL, next state = SYSSCOPE_STATE_INIT
D/SysScopeService( 861): SysScopeService : send status Intent
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I uninstalled busybox so status went back to normal. Then removed SysScope.apk and now it says Modified. My thought is without SysScope the system just marks it as modified, with sysscope it'll scan and look for stuff?

W/SysScopeVerifier( 965): Exception: java.io.FileNotFoundException: /system/app/SysScope.apk: open failed: ENOENT (No such file or directory)
E/SysScopeVerifier( 965): parse error
E/SysScope( 965): SysScope service has invalid signature
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lensgrabber:
Even set to start at boot and after a phone restart?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
That did it, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krynn!:
Ha! So busybox is dangerous, but su isn't? Nice! I think someone at Samsung has their priorities a little screwed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Yep. But I had some other mods was messing with so looks like one of these guys may be indeed the culprit..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
My brain is completely fried today. When you guys are referring to the modified status showing up where are you seeing this? On the about phone in settings or somewhere else? Could someone with the status take a quick screen shot, because for the life of me I can't find it and I have both Busybox and LBE privacy guard enabled on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
Settings>About Device>Status>Device Status (on the waaaay bottom)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Gotcha. Didn't go into the Status submenu. Never noticed that before, but I believe flashing back to stock reverts this correct? So probably won't worry about it too much...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Correct. Nothing to worry about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
Yes, going back to stock will make it say "Normal", even if the flash counter was tripped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cushcalc:
Clarification of instructions for ADB Shell

I'm glad you showed your Code output - I completed the instructions prior, then didn't know what my status was - so then I typed in

"reboot recovery" after the line: shell@android:/ #

and then phone rebooted to CWM Recovery!

Thanks! (maybe add that line to your instructions?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PensFan66:
Hey All -

I used to use Custom ROMs on my Sensation - now I have my S3, and right now - I just want Rooton the stock. So Ill follow the first few steps for that - I do understand correctly that this wont trip the meter and to go back to regular stock I would just needto reflash with the stock image to remove root?

Thanks for any help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Confirmed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PensFan66:
Thanks ... It looked like it, but since its so new - wanted to make sure 110%
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
The reboot recovery is actually an optional step :-). You can manually turn off and boot into recovery if you want as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stan.s:
Well, now that you answered that question, I have one. Where do you see the download count?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
When you are in download mode, look at the top left of the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I just dd'd in the new v4 recovery.img from here.

Seems to work fine in case anyone is wondering since they only tested on Sprint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
sorry for the noobish question - but is an sd card required for this?

been with the iphone since 2007, but used to flash a lot before that when i had tons of windows mobile devices.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freakboy13:
Nope. In fact I just got my gs3 Friday eve,

used this exact method to root sat. morn.

no sd card installed!

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Just curious - if you go into the APN list and hit menu, return to default, then reboot and wait 5 minutes, doesn't that do it as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
great! thanks for the info.

yeah, you're right - super easy method. ive rooted, flashed cwm, and ran the debloater.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
Works great!!!!! Thanks for your hard work!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robstunner:
After doing this last night I've been getting allot of wake locks and wake ups. Dunno if it's related but battery life has just tanked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Crap - help!

Mine failed.

Not sure what to do I'm leaving everything the way it is right now

Got through to system.img.ext4 part in odin and it hung for a long time and then reported FAIL! at the top. What should I do????

using v4 and odin 3.07 samsung usb 1.4.6

---

Well, hot shart in ma pantz.... checked the thread and someone else had the same damn problem. Took forever for odin on my system too, not sure why, but this time it did work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinichi21:
Hi just want to ask where can I find the cmw nandroid backup? i have look on ny sdcard and ext sdcard can anyone point me where the nandroid is being stored thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsxx:
should be at /mnt/extSdCard/clockworkmod
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] creepyncrawly:
@MrRobinson, Pinoymutt,

Done. Posted. Thanks for your help.

btw, I wanted to put busybox into the system along with root, but I couldn't figure out how to install it in the ubuntu environment so it would be correctly installed on the phone. I just don't know linux that well yet, and I couldn't find a recipe anywhere. Have you thought about how that would work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
What was posted? I must have missed something or forgot.

busybox install a lot of bins and a bit of symlinking too. personally I would prep the system manually but would take some time, I'd rather use the busybox installer and keep it updated that way. you mention recipe, that's funny. been writing a lot of recipes in opscode chef lately....I doubt you meant it that way but just what i thought of.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
Finally! This worked great, but now my counter is at 6, oh well.