yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IC-USER1:
Unfortunately, troubleshooting a potentially corrupted OTA it's most definitely not in my skill set. (That's what I think has happened to your OTA that keeps failing. )

But.... I can tell you that IF you are STILL rooted; you can backup all your apps and their corresponding settings including data.

( you can achieve this by making sure your Ti-backup settings ARE set to include all data, external data and possibly their cache )

Once you've backed up your apps take the TITANIUM BACKUP FILE and store on a safe place << not the phone internal memory, not external SdCard, in case you accidentally format SdCard during updating process >> so that you can re-install them later.

Remember that once you restore the TITANIUM BACKUP to its original location. .. AND once you re-install Titanium

< from the market ,maybe? >

It will instantly recognize it's backup file and from there you can restore all your apps and even your preferred settings for titanium backup.

=====%==============%===%===============%================

And, as for your update to UCDMG2 being stuck at 20%.....

I believe you are MUCH better off re-installing your ROM (sort of start fresh if you will) for the sake of reliability and stability.

Since I don't know how your phone is performing as of right now, I cannot tell you if you in fact need to re-flash your Android 4.1.1 or not.

(By the way what software version does your phone displays when you go to settings> > about phone ? )

I guess, re-flashing 4.1 depends on: is it stable, ,is it still usable and stuff like that.

So in the end if 4.1 is working correctly, just work your way up to the newest UCDMG2 4 2 with the process I've described in my prior post.

( you know, the one where you add a custom recovery to your phone, and then flash the ROM no firmware file, and then flash the FIRMWARE no rom file....etc, etc. )

Please note: as I said in the top of this post, I'm no expert so this is just my opinion mixed w/ what little experience I have.

I hope this helps you. Anyway, feel free to ask anything and also cross examine my post against those of members who are "recognized" as very experienced.

Cheers !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dadofsix:
Latest ATT JB Image

I was wondering if there will be any new root options using the latest AT&T image for JB 4.1.2 which downloaded last week? If not, how will flashing this latest JB work since the phone has been updated with this latest OTA update?

Thanks,

Gary
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
So IF I go to stock no root 4.1.2 can I ODIN back to 4.1.1 root and be ok? OR must I wait for the update stock with root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ethere:
I would like to know this as well, as all I'm interested in doing is rooting the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brianray14:
YAAAAAAAAWN!!! This has to be the most painful download of my life. Thanks for putting it up but holy crap androidfilehost SUCKS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I bet its still faster than using the site that a certain firmware site uses :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brianray14:
You are correct sir! However, i get to start my download all over again! Stopped halfway through! ARGH. Good thing i've got nuttin to do today
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gc_geforce:
JB 4.3 Bell ?

Will there be updates when the Bell and Rogers S3 gets updated to v4.3 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
You mean like the update we got today?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
If Rogers and Bell release a full firmware package, maybe. The addition of Knox to the system makes things tricky. But if it can be done, I think mrRobinson can do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tailgunner9:
Mine shows 3 on Flash counter. Explain why I should take a chance with Triangle thing to get rid of it. Does it hurt the phone some way to show Flash counts?? Does not bother me. Phone is out of warranty. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
It is basically a warranty thing. If you send it back and it shows you rooted and or flashed firmware on it they will say you voided the warranty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gc_geforce:
Will there be a "No Tripping Flash Counter + root" version soon?

Thanks

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Satstalker:
Mr Robinson are you there? LOL. Looking forward to your release. Hope its soon.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bass_me:
I finally got tired of waiting to see if there was going to be an update on this thread. Since I don't really care about the flash counter, or sending the phone back under warranty (I can ODIN back to stock and triangle away), I just loaded CyanogenMod Instead.

I now have 4.3.1 without the att and Samsung bloat. My S3 is faster and smoother than ever now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Florad77:
No one cares.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
I flashed this on my wife's S3 rogers 16gb version hoping to go forward with the new 4.3 OTA afterwards. Well i flashed this without keeping root or custom recovery and it still said her device was modified?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snowmangoh:
Soooo... I may be an idiot, but... I just decided to root my daughter's S3. I've rooted a ton of phones before, so I was feeling pretty familiar with the process, but after root, it will either bootloop, or get stuck on the Samsung screen. I just did a wipe in recovery mode, and then reflashed the "root66_ATT_I747UCDLK3.tar.md5", but it's still having issues... any advice? I tried to read through this thread, but 210 pages bogs you down with a 12 year old over your shoulder asking if you're done yet every 30 seconds! Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
Just go into recovery and wipe cache/data/factory reset but do not flash the rom again. Just to the wipe and then reboot. It should boot up after that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snowmangoh:
Thanks, but I did that... I think it's corrupted... I'm going to try reloading from Kies and see what happens. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
thats weird. That usually works for me. No problem though. Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Where is the latest stock image?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Satstalker:
Its on Sammobile site.. Roger SGH I747M Galaxy SIII. Canada Rogers (RWC)

Latest firmware info

SGH-I747M Galaxy S III

PDA: I747MVLUEMK5

CSC: I747MOYAEMK5

MODEM: I747MVLUEMK5

Added: 2013-11-25

http://www.sammobile.com/firmwares/2/

Thanks for your reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snowmangoh:
Yeah... I didn't do Kies. I used a different cable, wiped everything (again) and then flashed again through Odin. thievery is good now! Weird! :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
my bad, was looking for att version. Don't follow the canadian side... I'll update. Doing note 2's first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nwdst:
Thx...me and my friend live off your work. He has T-mobile and I have ATT...so he always updates his first. No worries, thx for your efforts!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
Bell too please whenever it is you have time to get around to it, I'm in no hurry :)

BMC

SGH-I747M Galaxy S III

PDA: I747MVLUEMK5

CSC: I747MOYCEMK5

MODEM: I747MVLUEMK5

Added: 2013-11-25
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] losuma:
Rooting i747 running jb4.3

will root66_xxx_.tar.md5 also work with the new jb4.3 on i747(ATT)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
DO NOT DO IT !

It has the old bootloader in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] losuma:
Thank you!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
ok i'll throw up a rogers test image this weekend. if good bell will be next.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] losuma:
good. will you also do ATT, because that's what I would need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krustyx:
I don't get it... everything went fine, everything is downloaded on the phone, it reboots, and nothing happen.

I'm just unable to root it, i don't get it.

I tried this method and the cf-auto-root, and nothing works.

I need help i think!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djdoubt03:
Sweet I can't wait for the latest ATT No Trip root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nwdst:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Telus Root 4.3

Also Telus, whenever you have time ;)

I know there is not many of us, but the few that are there, we do care for our phones :)

Thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lukesjeans:
you know that moment when you realize your a dummy? I just had that. I tried downgrading to a 4.1.2 pre-rooted odin file from 4.3....it instantly failed. I hear it has a new bootloader. If i get the 4.3 odin file, flash it....will my life be better or am I forever dead? thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Att hasn't released a stock image for mjb. Sorry guys :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krustyx:
Can anybody help me? Here's what happen

I load the phone in Odin no problem.

I load the file in the PDA and click start

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> root66_BMC_I747MVLDMF1.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

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

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

<ID:0/005> sbl2.mbn

<ID:0/005> NAND Write Start!!

<ID:0/005> sbl3.mbn

<ID:0/005> aboot.mbn

<ID:0/005> rpm.mbn

<ID:0/005> tz.mbn

<ID:0/005> boot.img

<ID:0/005> recovery.img

<ID:0/005> system.img.ext4

<ID:0/005> NON-HLOS.bin

<ID:0/005> cache.img.ext4

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

See the little Android robot + progress bar

Reboot

Phone is not rooted, not wiped, nothing. It's exaclty like it was before.

Anybody can help? I also tried with the CF-Auto-Root and it doesnt work either.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Alright, test Rogers image. Someone flash and confirm its rooted, etc. please

Download :: root66_RWC_I747MVLUEMK5.7z
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scyzor:
I had installed 4.1.1 with CWM and decided to go back to original recovery, so had to re-flash it and now I'm stuck on 90% progress bar (system.img.ext4) for about 30 minutes.

Any clue what is going on?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lukesjeans:
Does not root....opened super user and said binary not installed. Root checker said its not rooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
thanks, I have this working on the tmo s3 so have to figure out what is different here. I'll post up another test today. Must be missing something....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
I was just about to give up on this "No Trip Rooting" and just go with CF auto root, but now that I see that there is some progress, I like to stick to something that is actually reliable, and has been working for me ever since I got my S3.

Question.....

I seen threads with root imbedded in them, but some has KNOX and others don't, is that a big deal for later down the road, or just personal preference?

Anyone?

Thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
well its going to trip the knox counter now. I have to remove knox in order for root to work. Also I don't see att posting up full stock images anymore so if you are att you might as well cf-auto root. The variants I'll get up. Posting the next RWC test build in a second.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Test Image 2 for Rogers

Download :: root66_RWC_I747MVLUEMK5_2.7z

If someone could flash this and confirm root is intact after boot or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
No I'm on Telus I747M

I'll just hag tough.

All I need root is for Titanium BU.

Thx

JR
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I'll post others after I get feedback on whether this one retains root or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Who Am I?:
I downloaded root66_ATT_I747UCDLK3.tar.md5 on 12/3/12. 1.11GBs. Im on 4.1.2 ATT right now, should I re-download or is this file fine to root the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
For 4.1.2 use CF AUTO ROOT to root your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
I received feedback via PM this is working. I'll do the other variants over next few days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawen:
So does this rooted 4.3? Can I odin this over my previous rogers 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Florad77:
Yeah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawen:
Cool, can I still install custom recovery and flash the aokp roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Florad77:
Yeah there's another thread somewhere on how to install a custom recovery on 4.3. Im not too sure if the method here still works on 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoryuken_2020:
Thanks. Quick question:

Can this be flashed using Mobile Odin and if so do I uncheck the two options Keep Root, Inject SuperSU since it is already rooted?

Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AceTrader:
You can install ROM Manager from play store and flash CWM if you are already rooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoryuken_2020:
Never mind, I just went ahead and installed using Mobile Odin, unchecked Keep Root and all went well it seems.

Thanks mrRobinson for your work.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawen:
Do u need to install new cwm recovery to install 4.4 roms? Coz I try to use twrp it failed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
You need to use the latest twrp (2.6.3.1). Get it here: http://teamw.in/project/twrp2/104
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawen:
still doesn't work, it gives me bootloader error failed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawen:
nvm, I use cwm recovery 6.0.4.3 seems to work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoryuken_2020:
Since installing the new release by mrRobinson for Rogers, the wifi no longer turns on. Is anyone else having a similar issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Florad77:
Here's another thread that provides a pre rooted stock rom for 4.3 and a few days back I remember a bunch of people complaining about the same issue. Not sure if they found a fix though you might have to do a little searching.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoryuken_2020:
Thanks. It looks like several folks are having a similar problem. Some have resolved it by reflashing (others have fixed it by wacking the back of the phone :))

From what I've read I can't downgrade the firmware, but am I right to assume that it is relatively safe to either:

1) reflash mrRobinson 's latest release using Odin. (desktop version)

Ond/or

2) the original Rogets 4.3 on top of mrRobinson' s using Odin (desktop version)

Thanks.

UPDATE: seems to be working now. I did a factory reset, then went into recovery and wiped cache and all data. Then I went into download mode and reflashed mrRobinson's firmware using the desktop Odin. Wifi is working again for now and hopefully it will stay functional.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Julian713:
Hi everyone, so I wanted to instal a custom ROM on my nephews phone. He has the S3 for AT&T with the OTA 4.3 already on it, however he asked if I could get him a custom ROM on there. So I read everything and figured out I would have to flash one of the files from the first page using ODIN and then get a custom recovery and then flash a ROM. My question is since he's already on 4.3 OTA do I download the 4.1.1 ATT image with root or the Bell 4.3? I noticed some of the custom ROMs say you need to be on the newest 4.3 boot loader/radio, so wasnt to sure exactly what to do. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
1st- you can not downgrade once you have the 4.3, many users have brick their phones for that reason

2nd- if you are on AT&T you do not want the Bell image, they don't mix. If you want root on AT&T, use Autoroot

3rd- and if you want custom ROM, than you will trip the flash counter anyways, so there is really no use of using this method for you. There are many other custom ROMs that already have root in them. And 4.3 just came out for S3 so you may have to wait for roms that are 4.3.

Hope this helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Florad77:
Im on rogers s3 and im on 4.3 and rooted using cf auto root. I flashed some music player mod that I didn't like so I would like to return to the stock one. Would it be ok if I simply flashed the rogers firmware file here? Would there be any risk of a brick ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwnytails:
Hello, I've just rooted my stock 4.3 Bell i747m S3, flashed Dandroid ROM, and now I'm experiencing the same inability to toggle Wifi on/off.

I noticed the bootloaders for 4.3 under Bell have been temporarily taken down while they rebuild due to errors.

Is there a workaround for this, or should I just wait for the new bootloader to be uploaded? Thanks.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Telus and others now up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Is there a 4.3 image for the normal 747 not m version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
I have been using this CM based rom for quite awhile... better than modded stock, aosp and aokp to me (and to quite a few others too) the dev has made a amazing rom better than CM base itself. He has a 4.3 release and a 4.4 beta for the S3. Also I believe that some outside the US (bell, Telus) are using it successfully too.

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

[ROM][KERNEL][4.4.2/4.3] Quantum v3.12 & QuantumKernel 12/21

(DISCLAIMER!!! MAKE SURE YOU READ AND UNDERSTAND WHAT YOUR DOING, YOUR MISTAKES ARE YOUR OWN! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Awesome Job ! ! ! As always.

Works great on Telus

Just one little thing, last time I've flashed your file, it still let me do "OTA" check and update, but this time it doesn't any more. Is there a reason for that?

Also for a Device status it says "Custom" last time it said "Official" I believe or something like that.

Not that it really matters any more, since it's flashed.

I guess Triangle Away should fix that issue??

Thanks again, great job.

JR
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yes there are differences now unlike last time. Last time I simply added root. Rest was completely stock. This time I had to remove knox in order for root to stick. So that is why you now can't get the OTA as you really aren't completely stock like last time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Awesome..... As always :) Thank you for the Sasktel image :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
No, att hasn't released it. Why? No idea.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seaskimmer:
Is it recommended to factory reset before flashing 4.3 (Bell). I'm currently on 4.1.2 and didn't wipe when flashing that but 4.3 seems like a bigger update.

Anybody running Bell 4.3? Stablity, battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
ok...so i have downloaded the sasktel image 7 times from different mirrors...tried different usb ports to no avail...always the md5 check shows up as invalid...is it safe to just delete the md5 extension?? not really wanting to...but seems like may be my only option at this point....:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhiga:
Not a good idea. The md5 checksum is there to prevent you from flashing an invalid or corrupt image that could brick your phone.

Take the safe option, don't flag until you can get a checksum match or further information.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
OK...thank you...i guess ill keep trying...and/or wait hehe :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
Silly question.......

But you do have the newest and the correct drivers installed for your phone model on your PC, right? Also in correct Download mode, and phone left in USB debugging mode in developers option.......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Yes... Followed directions to a T.. Just like the last two times I flashed 4.1.1 and 4.1.2....

I re-downloaded Samsung drivers to be sure.... Did the vol down+home+power for download mode.... Plugged into USB port.... Waited for drivers to recognize phone... Then started Odin (from the link in this post) then when I loaded the tar. Md5 file (from the link on this post) it said that it was invalid....

---------- Post added at 08:47 AM ---------- Previous post was at 08:43 AM ----------

OK... Having said that.... I notice there are two versions of kies.... Would u need the drivers that kies installs..... Or the ones that kies 3 would install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
There is a known issue between Odin and Kies, if you run Odin, make sure that you don't have Kies installed, or be well sure that Kies is not running in the background. Odin is a "big brother" of Kies.

I just downloaded the driver off the Samsung site from the link in the first thread. Although it was for AT&T but worked fine, being the newest one.

Also I always start Odin before I plug the phone in..... once phone <added> than add the file extension in the PDA

These where the only problems that I've even run into so far.

Not to scare you away but, once I had to abort half way trough downloading, cause it was just stuck there and the whole screen went all funky and stripy, I left it there than restarted Odin and it just started all over, but the only thing left on my screen was the blue line, lol. Highly I do NOT recommend unplugging thought download. Just an FYI ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
OK..redownloaded root66_BWA_I747MVLUEMK5.7z (Sasktel)...removed kies from computer...installed drivers from link in first thread....still to no avail...

Would a factory reset first change things? or wipe cache partition? from the android system recovery menu on my phone?

I never had any issue with the last two flashes i did....just this one lol...:silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jrico2:
As long as you are already on the 4.3 prior to flashing, than we would need to ask " mrRobinson " on any known issues.

It's seems odd that it won't go though.

There are a couple of other methods, one is "Auto Root"

And since the file you got, will trip the flash counter, than really not too much difference between flashing methods.