yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noahattic:
Sorry to be redundant... but is it safe to say this is the rooting method without losing IMEI or any other important stuff??? I'm so tempted to root my phone as I got fed up with Rogers bloatwares and the native clock app seems broken already....... But after reading the "IMEI losing" post, I am back off... I cannot afford to brick my $700 investment.

I'm currently using the Rogers model.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I've been following the IMEI thread, and I personally don't think anybody understands what is causing the problem. There's lots of supposition in that thread, but it's really to hard to draw any scientific conclusion based solely on reports from people that have had a problem. Who knows? Maybe there's lots of other people who have done exactly the same thing and have not had a problem?

Personally, I made a dd clone of all my block devices. If I lose my IMEI, I'll first try restoring those. If that doesn't work, I'll spend $30 and try MobileTechVideo.com's IMEI repair service.

Just my $0.02.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Does anyone know if mobiletech IMEI fix works with our variant of the SGS? I haven't seen anyone here succesfully find the IMEI, so I'd be surprised if they could (would be awesome if they could though). I'm refraining from flashing anything else (I've done SU and CWM as well as the stock Deodyxed version so far), but since I flipped my flash counter to 1 I'm not sure if AT&T would exchange it if the IMEI is gone.

I'm looking forward to Triangle Away, or the root cause of lost IMEI's so I can feel more comfortable flashing without fear of a paperweight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm not sure what you mean by Team Epic's "Sprint" v4 CWM. Right now they have two downloads on their CWM site: CWM-Recovery-LTE-SGS3-Sprint-v5.zip and CWM-Recovery-LTE-SGS3-v5.tar.md5. Both contain exactly the same recovery.img file. The zip file is meant to be flashed in CWM to update it. If all you did was extract the recovery.img file from that zip (or the v4 version) and the copy it to your recovery partition to dd, you should be just fine.

As far as I know, the Team Epic's recovery works just fine on AT&T (and Rogers) phones. The only slight issue is that it reports that the phone is Sprint (technically, getProp("ro.product.device") returns d2spr instead of d2att, for example). This isn't normally a problem, but it has tripped up some people trying to apply the CM9 nightly and it does prevent applying the AT&T LG1 OTA upgrade, because in both cases the updater script checks that the phone is AT&T and fails to continue if it isn't.

I personally am using the clockworkmod.com v5.8.5.4 touch recovery and like it very much. Beware of later versions (at least for AT&T) because they don't support installing zips from, backing up to, or restoring from the external SD card.

---------- Post added at 04:37 PM ---------- Previous post was at 04:34 PM ----------

I've never used them, but I watched this video of theirs and was impressed. Seems like they can do a full JTAG repair and recover anything short of a phone with actual physical damage. That said, I'm sure you could shoot them an email and ask. If you do, please share the response. I'm sure lots of people here are very interested!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
Thanks, that's a great way to remember :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thank you, For some reason I thought the .tar and .zip files on team epic's page contained different recovery images. As they are the same I am fine then.

I really miss 4ext recovery (http://4ext.net/) from my old device, just so much better than cwm. Hopefully one day the dev will support this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zaghy2zy:
oops, sorry, XD was really thinking of down.... XD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockstarbrad04:
I have tried swapping USB cables and ports. I deleted and redownloaded the stock software. I am stumped! :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
What error are you getting in Odin?

I don't know if this is relevant, but I'm running Win7 x64 and I press PDA and choose a .tar.md5 file, I get this pop-up with Korean in it. I used Google Translate and it translates to "An invalid argument was encountered". I discovered that if I run Odin in compatibility mode for XP SP3, I don't get that. Now, I've never tried flashing a file after getting that pop-up and I have not seen anyone else mention it. But if you're seeing the pop-up, it might be worth trying it in compatibility mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockstarbrad04:
<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> aboot.mbn

This is as far as it goes and it hangs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm sorry, but I'm out of ideas. All the solutions I've seen posted for Odin flashing problems involving trying different cables, reinstalling drivers, rebooting the computer, etc. I'm pretty sure that being on LG1 doesn't cause this, because I updated to LG1 myself and have successfully gone back to LEM, as have several others.

If you get completely stuck, maybe the folks at mobiletechvideos.com can help. (I'm not affiliated with them, nor have I used them, but they offer services for issues like this.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockstarbrad04:
Here we go.. this is if I wait 10 minutes

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> aboot.mbn

<ID:0/004> __Xmit Write fail

<ID:0/004> XmitData Fail..

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
try these drivers:

http://www.xda-developers.com/android/universal-naked-driver-gets-face-lift-adds-new-devices/

and make sure kies is not installed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockstarbrad04:
Completely uninstalled all samsung software including kies. Installed the drivers and tried again... same thing.

I am thinking its this phone :(

---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------

Update: After completely removing all samsung software and redoing drives, I again tried a different USB port and its working now!! Its flashing as we speak.

Thank you guys for the help. Very excited about getting the modded camera put on here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
It seems to be a temperamental phone... i blame it more on the drivers, they seem to be crap... I always use the same USB port for all my devices... never seem to have any issues... and I use the cable that came with each device...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WTFsandwich:
Should I avoid the OTA update if I use this method?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You should read this thread and others, and your question will answer itself. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Check out this thread: http://xdaforums.com/showthread.php?t=1768826
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevenca:
Successfully rooted my bell i747m , thanks guys for your hard work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anethema:
The answer is no to pretty much everything you asked unfortunately. Not positive about triangle-away but you def cannot reset your counter. Flashing back to stock ROM will not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] coolzy:
Worked on Rogers Stock SG3, thanks a lot! used Odin 3.04
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EthanMG:
i am new to adb on android, with my previous phone (captivate) i never had to use it. it seems simple enough, but i cant tell if my phone is in usb debugging mode, which i believe you have to be in in order for adb commands to work. i have it checked under developer options on my phone, but when i plug my phone into my computer, it still reacts the same as if i hadnt checked usb debugging (defaults to 'connected as media device (mtp), with the option to switch to camera (ptp)). is there a way to know if i am in usb debugging mode? as far as i can tell, it is not, and that just boggles my mind, as i have it ticked to be in it. thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You need to do some reading on ADB (always a good idea anyway) - it's easy enough to tell from the ADB shell whether you're connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
Quick question. Could you still use this root method even if you installed the new software update that broke the search bar?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Not this method, no, because it uses a root-injected version of UCALEM, the version before your software update. You can do that if you want, but then you won't have the update.

But Chainfire has updated Triangle Away for our devices, so you can now reset the flash counter. This means you can use the toolkit to root, which should work even if you're on LG1. (The reason is it flashes a custom recovery using Odin, then uses that to apply root.) If you do that, you're flash counter will be 1, but now that it can be reset, this is no big deal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
you can use this but it will put you on the orig version. There are ways to upgrade keeping root. One being voodoo ota rootkeeper which is free as opposed to paying for triangle away to reset your counter. You can also use this then flash the upgrades that are out via cwm which also have the benefit of keeping the system search or not flashing the bootloader. With triangle away we now have more options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
When i select touch recovery got att s3, i get this big long page. I'm confused about how to use this. Dl and rename, then use adb?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
Not sure if i should post this here or cwm thread.

I was stock rooted via OP.

I installed root keeper and did the OTA update. All went perfect.

i decided to install the att specific cwm (non touch) in order to debloat via Aroma (I've done all of this before but this is my replacement phone). i installed cwm per adb instructions after saving cwm recovery image and aroma installer to my internal sd. all went perfect after running adb shell commands on my pc and booted into cwm recovery and flashed aroma and debloated just fine.

now the only thing is anytime i boot into recovery the device boots into the stock recovery. The cwm recovery is still on my internal sd card and i can get to cwm but only if i do adb commands via adb shell. anytime i simply reboot recovery, the stock recovery loads. do i need to remove the stock recovery some how?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Try removing /etc/install-recovery.sh or something like that (I'm away from my computer.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
Went to factory recovery again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Also remove /etc/recovery.img or /recovery.img.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
I don't find either of those with the paths u've given. I do find /system/recovery-from-boot.p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
You can remove that file, too, but it's not the problem. Forgive the stupid question, but did you reflash CWM after removing install-recovery.sh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
Not stupid at all. Just realized that would be a good idea. It's working mint now. Thanks for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
It appears that UCALG1 is now available as a full ROM on Kies. Can we get an updated rooted tar with the newer version ?

It's on www.samsung-updates.com
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
Why? Do you want the neutered Google search?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'll add the rooted UCALG1 to the OP tmr.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
No I I'm already on UCALG1 stock so I'd rather just Odin same version over it but with root. Saves some time/trouble. Also with all the lost IMEI stuff that's ongoing, I'm trying to avoid using CWM and just use Odin. This would be the quickest way to get root on my current ROM. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I'll be mirroring the rooted UCALG1 tomorrow too. :)

(And might as well link to the non-gimped universal search apk (system/app/GoogleQuickSearchBox.apk), or the CWM-flashable version, because there's really no point otherwise, imo.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Well as much as the whole point of this is to be "stock". i don't see the point in even using the one with universal search removed. I just root injected UCALG1 and also used the univeral search GoogleQuickSearchBox.apk. Uploading now....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Awesome thanks. Only problem I can think of is any future OTA updates would fail since the assert on GoogleQuickSearchbox would fail but I guess you wouldn't be using OTAs anyway.

I'm assuming if I flash this over my stock LG1 I'll end up with rooted LG1 and no other changes to data/etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yea good point. Unless the OTA doesn't touch that. We could always provide the LG1 apk.

Edit: OP updated with link. Let's see how many people care for an image with the crippled search. ATT typically isn't too quick with the OTA updates and eventually we should get full image of it anyway like we just did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
root69_ATT_I747UCALG1.7z mirrored here - and I guess you can call it a perm mirror instead of temp, since the previous didn't hit my bandwidth as hard I was expecting (403 attempted downloads, and ~150GB xfer'd)

md5sum: f9a8516fc16b81c1caad0459a4e1bcaf root69_ATT_I747UCALG1.7z

sha256sum: 2ef6c13a2c0362ace20ce48535408ad8c446d2d6710f10111b176b6184890687 root69_ATT_I747UCALG1.7z
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mordred69:
Hi all,

I am a new one with S3, just moved off HTC EVO and the rooting is different, of course. I am a bit at a loss, and since I don't post too much so as to not interrupt your fine work, I have gathered my questions here. The others I had I was able to search for them and get my answers.

First off, thanks for your hard work!

Second, I was trying to stay off the rooting for a while so I could enjoy my phone, sock, as much as possible, but I am in need of WiFi Tethering for next week... so I guess I will root.

Now, coming off HTC EVO 4G, I am a little lost, so I'm posting here so I can get the story straight from the horse's mouth. Thanks in advance.

1. Will rooting my phone (currently UCALG1 Stock, OTA) cause me to not be able to OTA anymore, or will next OTA break root?

2. In case of me being root, will I have to update through ODIN every time if I want to stay stock and root? I assume the image would have to be..."injected"? is that the term?

3. Will I be able to tether wirelessly? and if so, would there be an external.3rd party app for it?

4. The OP says the counter will NOT trip with this method. What happens if the counter reaches a certain number?

Thanks guys, for your hard work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
1. it will but only because I used the non-stock google search that retains the universal search they removed from the update. I could always post a stock rooted so you can OTA update and retain root with voodoo ota rootkeeper.

2. When the ota update comes out as a full rom you can always flash that in odin with root injected. That just entails waiting a week or two for the update to be released as a full rom.

3. yes just have to flash some changes or do it the stock way.

4. nothing. And you can now reset the counter with a play store app or an adb shell command line. Tripping counter voids warranties that's why people cared. Using this you won't have to worry about reseting the counter though as it will never trip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Thanks. That is actually more than I'd have thought being listed 3rd in the list. Now you are the only one but the initial rush is prob over and now some who would've flashed this in odin might just flash the cwm recovery, trip counter, then reset it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mordred69:
Thank you for your quick reply! Yes, if I can get a link for the stock rooted, I would be most grateful. That way, if I want to OTA update, I'd just do it.

Thanks again! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
OP Updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] McAwesome:
So does anyone have the issue that after running the adb commands and booting to recovery from shell it boots into CWM but then after I reboot phone and load it up again if I reboot into recovery again it goes to stock recovery.

2992
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the1stSecond:
@mcawesome

Ya...me yesterday...like one page back..

Try this:

Remove /etc/install-recovery.sh

Then

Reflash cwm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bluezz:
Phew, I thought I messed my phone up - it was stuck on Samsung screen but I wiped data and cache in recovery and phone boots ok now :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
So this worked fine but now how do I block future OTAs? I know this last one if you deferred too many times it just installed by itself. Any ideas? I can't disable AT&T Software Update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Get Titanium Backup from the market and freeze AT&T software updates
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Meh. Just realized that's not even needed. If it tries to update it'll just fail because I have CWM and not stock recovery. I'll leave it be for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevenca:
I rooted my bell i747m with this method , worked fine thanks BUT when I go to about phone, status at the bottom it says Device Status - Modified. Does that mean it can be detected if I need to have it warrantied or will that disappear when I unroot it before sending it in ? thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kssxs:
Yes, it will disappear. It was confirmed earlier in the thread. It can't be detected if you re-flash to stock ROM before sending in for repair.

Don't worry about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Rooted and CWM installed on Rogers SGH-I747M very quick and easy!

Thank you mrRobinson! much appreciated for this versatile post with very simple and easy to follow instructions on the many carrier variants of the phone, to root and install CWM Recovery. I'm no noob anymore but no veteran yet either and this post was great. Quick and easy, no modified count increase and device status normal. Rooted and working perfectly. Just got phone a few hours ago.

Thanks again. This should be stickied...and really appreciate the Canadian variants files and info all in one place!

Now have to see what mod to flash first...not a ton of choice yet either but i'm sure there will be many to come soon with this new SGS3...i would assume...

any thoughts or preferences anyone on stable new release ICS roms? thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kssxs:
Not to discourage you from flashing or anything, since it is entirely up to you and is your own risk to take, but... check out this thread before you decide to flash any MOD's. There is a potential for IMEI corruption that would disable your voice/data ability on your new phone, and has no fix at this point in time, except to attempt a return to your carrier.

Again, up to you. Good luck!

http://xdaforums.com/showthread.php?t=1753833
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sentry07:
OP you originally had links to updated mods for native tethering coupled with some others, is there a reason you removed them? I'm mostly interested in the only the tether mod as I just reflashed my phone again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mordred69:
I installed Android-wifi-tether and it's working fine for me. Just be careful what you download because I believe, if you are on AT&T, they will track you.

To everyone else,

My Device Status says "Modified". Could it be because I installed BusyBox?

What I did:

Followed this procedure to the T.

Installed CWM Touch Recovery

Updated SuperUser App (but Binaries will NOT update, for some reason)

Installed BusyBox from Market.

Aside from this, I have not installed anything else.

My warranty allows for me to exchange my phone at no cost or deductibles, and I have EVERYTHING synced...so if I need to send my phone for repairs, I'll just bash it with a hammer and get a new one, no need to reflash... but because I am somewhat picky, I'd like to get rid of the "Modified" label.

Thanks, all!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krynn!:
Yeah, that's exactly it. There's a watchdog program that scans the system for 'busybox'. Not sure if it scans the whole file system or just /system/bin and /system/xbin. Kinda funny that it flags 'busybox' as a dangerous program and not 'su'.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sentry07:
I installed everything per this thread and my status says normal.

Which version of cwm did you install? I used 5.8.4.5 touch
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I never had that? you must be thinking of a different thread. I recall seeing tether stuff in the themes/apps section?

yes exactly. and even if you delete the "watchdog" it will still say modified. this is no big deal cause if you need to return the phone you can just flash back to stock and modified won't be there anymore. or just remove busybox as being rooted doesn't seem to trip this just busybox. So you can just run rooted without busybox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
I rooted with another method two days ago and it wiped my imei number and had to get my phone replaced. Rogers i747m model. I'm scared now but has it been totally confirmed this doesn't occur using this method? Just a little paranoid over here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
No one has figured out the cause of the imei problem, so there are no guarantees. I haven't heard of anyone losing imei rooting with this method but you never know. I personally am holding off on everything until the imei issue is figured out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pachi72:
You just rooted only?

Nokia 3650>Nokia 3660>Nokia 6630>SE W800>SE W810>SE K790>Nokia N95-1>Nokia N95-3>Nokia N95-4 8gb>iPhone 3G>iPhone 3GS>iPhone 4>GS Capitvate>Galaxy S2 i9100>Note N7000 32gb> Galaxy S 3 i747 32gb