yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
I am rooted but am on stock recovery. At least I think I am. I boot into recovery and it shows (3e) so it should be stock. What is weird is that the Updater is telling me I am up to date rather than letting me do the update and then failing like it did on 4.1.2. When I went to 4.1.2 I did have a custom recovery and had to revert it back only to discover that my debloating (removing rather than freezing) was also causing the update to fail so I had to go back to stock then update. But in all those tries it failed then let me download again as if it had never happened...this time it is acting like there is no update. I will wait until tonight and try again....Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
It look like we have to stay on 4.1.2 forever
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortydoggg:
4.3 OTA and official firmware, when available, we will probably need to avoid forever.

We just need to avoid the new bootloaders. I think eventually, someone will give us a flash-able Rom along with the modem. It just won't have the bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
But if the tmo version is any indication, not flashing the bootloaders will cause Wi-Fi to not work. I think I'll just stick with Intergalactic 3 until I can get a Nexus 5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
WARNING

I just ran triangle away and flashed back to stock 4.1.1

When it finished starting up it downloaded an OTA.

I let it install thinking it would be the 4.1.2 update.

It went straight to 4.3 so I am unrooted stock 4.3 TW

Just going to stay put for now. Seen too many troubles others have been having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Yes wifi does not work without the new bootloaders. Wifi should probaby work with the mj2 kernel and modem just like with tmobile
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
Wow, I thought I bricked our(My girlfriend and I) GS3's but come to find out this was due to the 4.3 OTA and my attempt to root, re-install CWM Touch, and return to stock(I did this method because Odin was failing, now I see why)? All I wanted to do was negate the 4.3 OTA, as I only downloaded it to try it out, and Odin to stock once I decided that I(we)did not like it. So I could continue to enjoy the art that is created here at XDA. But no, Odin failed so I instead wiped everything using CWM, flashed the zip that returns to stock, and wipes the Flash Counter, tapped "Reboot" in CWM and BOOM! The darkness overtook her device and it was not going to ever see the light again.

Poor girl.

Lucky for her(and me), I was able to replace or GS3's.

Unlucky for me, I did not realize, at that time, that the 4.3 OTA added things that would not allow me to downgrade!

So what did I do when I fired up the two new GS3's? Allowed DM/SW Update to install 4.3 OTA... I allowed it because I thought I had bricked her device and was going to avoid flashing anything, ever again... But a few days later and the flash junky itch came again and I went to root my phone and start flashing... when Odin failed this time, I finally got the wits to go looking for answers instead of following the same walk of death again... If only I were to have looked here before bricking her device and then allowing 4.3 OTA to install on the two new GS3's!

While in Download Mode, My phone says:

ODIN MODE

PRODUCT NAME: SGH-I747

CUSTOM BINARY DOWNLOAD: NO

CURRENT BINARY: Samsung Official

SYSTEM STATUS: OFFICIAL

QUALCOMM SECUREBOOT: ENABLE

Warranty Bit: 0

BOOTLOADER AP SWREV: 2

My question regarding this is: What does "BOOTLOADER AP SWREV: 2" mean? Is it keeping track of my attempts now? Even though Odin failed?! Or is it just the firmware number for the currently installed bootloader?

So there is no way out of this? No way to change the bootloader? No way to banish our GS3's incarcerations in the Stock 4.3 prison?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Thanks for clearing for some.

Just why would they kept 4.1.2 OTA going if there is new update to 4.3? This is how i think. That why i use 4.2.1 update.zip and ADB sideload to my phone.

If someone want 4.2.1 zip file PM me..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Yeah, I know I messed up. I just want to share so no one does the same thing.

I guess I was not expecting it to be able to make the update in a single leap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Phew, big thanks to everyone here. I finally installed CM11 and brought my phone back from the dead. I owe all you guys (loserskater, rdoac, and norbarb specifically) a beer. I am tight on dollars right now, but once I have enough money I will send you guys some beer money. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
For those that are already rooted on 4.3 would you mind pulling the modem?

Just use Terminal Emulator and Copy and Paste this into it

su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096

Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
SW probably stands for Application Processor. So maybe Application Processor Software Revision. Perhaps referring to microcode revision or board revision.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
I tried to Odin to stock and once Odin failed my phone(in Download Mode) had a red lettered message saying something along the lines of a failure. That message drew my attention to the "BOOTLOADER AP SWREV: 2". At that point was a bit worried that even my attempts were being logged.

On a side note, I edited my previous post to remove any discriminating statements, if there were any. ;) I did, after all, know, and have known, the risks involved.

So, is it safe to root now that I'm on 4.3 OTA? If so, I recall the SU Force Closing on the dead GS3, can the SU FC's be resolved? Or would I be best off waiting for a stable fix to all of this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
My stock 4.3 shows SWREV: 2 in it as well, so it is probably just its version number.

As a matter of fact mine looks just like what you posted above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Yeah, I've asked [MENTION=1016795]loserskater[/MENTION] already, but I agree with his "wait and make sure it can be flashed to and from" assessment before making a flashable modem (or bootloader) ZIP. I can't test these things myself (mine's a Canadian model) so I'd rather wait and make sure more phones don't end up bricked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
You went from OTA 4.3 to CM11? Could you post the instructions/ links to do it? Also does everything work?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Yes I did. Long story, but I installed the latest CWM recovery using ODIN flashable tar. I then downloaded CM11 ROM and Gapps, the one specifically mentioned a couple of pages back, since that is the only one that doesn't check for proper bootloader. Flashed it using CWM, rebooted, and working perfectly now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
Awesome. If you can provide a couple of links to the instructions/ROM versions you used? that would be great... I'm a bit surprised all the modems are working. I heard they were broken on CM11. Is there a battery drain problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
In that case, you could probably download the latest CM11 build from the TMO thread (the AT&T version has graphical glitches right now) and remove the asserts from the update_script. This is what most of us running the CM11 builds are doing now, and the dev has said he'll be scrapping the AT&T build entirely and just releasing a single TMO+ATT build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tailgunner9:
Safe to Root

Will someone tell me if it is safe to Root OTA 4.3 with CF Auto or send me a Safe way to root my cell Again. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Cool. I may try it for myself as well. Gonna download the 4.3 Update zip and pull the patch part of the modem from the updater-script and I should be able to get it flashed and working for me to test.

How I did it on my S4 was I found in the updater-script the part for flashing JUST the modem.bin.p and added it to a normal ROM I use updater-script and add the patch folder and the modem.bin.p and was able to get a working modem.bin without flashing a complete ROM and bootloaders. Put the NOW FULL modem.bin I extracted with Terminal Emulator. Added to a flashable zip and it worked with no problems. Was able to flash to ANY of the S4's older modems and back and forth.

The issues with the S3 is the same we are having/had with the bootloaders. Most that had the original bootloaders that WERE locked but had a exploit so we could have a recovery and flash whatever we want never had to flash any bootloaders. Those that went onto the 4.3 leaks and flashed boitloaders were stuck. Their only option at that point was to flash the official firmware and it's boot loader. Now they are stuck without root or recovery at all.

Plus Knox is basically fully removed for flashable Roms (except those that took the OTA update are stuck with it) .

Well once I can get a modem and test I will let you know how it goes. I am planning on staying on MG2 until this all is sorted out. I have learned the hard way you should never flash bootloaders unless there are NO other alternatives.

Sent From My ATT S3 i747 Dark Blue BadAss Theme
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Didn't everyone already have to update bootloaders for one of the recent CM versions?

Has anyone pulled the bootloader part out of the OTA update and flashed everything but the new bootloader? Does 4.3 boot up on the next-newest bootloader just fine?

These are the things that need to be tested, otherwise it might be better to stop offering the bootloaders as separate downloads...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
here you go ... just unzip

BTW... you got command litte wrong should be of=/sdcard0/modem.bin :) there is no sdcard output.

DO NOT FLASH THIS

EDIT: Wrong file atached...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali3n8:
Anyone have the 4.3 stock recovery flashable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
This is the version I used - http://xdaforums.com/showpost.php?p=47680332&postcount=1113

Just follow the instructions on that thread. I did just that. I haven't checked my battery stats yet, just installed the ROM and did a TiBu restore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
These are DEV ONLY! They won't flash through recovery or odin, and are only the necessary files.

Bootloader files: http://www.androidfilehost.com/?fid=23212708291680821

Modem: http://www.androidfilehost.com/?fid=23212708291680823
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I did use the T-Mo version dated 11-19. It seems pretty stable so far, so I am going to stick with that for a while until this whole 4.3 stock ROM thing is figured out. Can't be without a phone again. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Awsome.. I'm happy you get your phone back..:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That's an invalid rip. No amount of compression can turn a 45-65MB file into a 96KB ZIP. ;)

---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------

Thanks, although I'm still not sure I should post them yet until we've figured out what the repercussions of flashing them are... We need a few people that didn't OTA to try flashing these separate from the rest of the 4.3 OTA, preferably devices already running CM10.2 (cause it's stable)

If anyone is interested in being a test-case (AT&T devices only) please send me a PM. Warning: You could end up stuck with only stock 4.3 and the inability to flash other ROMs, although [MENTION=4811327]Evilweasel47[/MENTION] has already proven you can install CM11 after you've OTA'd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
hehehe..u are correct...i zip wrong thing.. sorry..:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Thanks to the awesome community here :good:

Just curious, will I be able to flash the stock 4.3 now? The one that is in this thread - http://xdaforums.com/showthread.php?t=2387423
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Thanks for trying but your modem is still not correct. It is only 512.000k where it should be 60Mb

You were correct I had the wrong block I was wanting to pull from. It should have been using THIS in Terminal Emulator as I just trued it on MG2 and pulled a 60Mb Modem.bin

In Terminal Emulator type in or copy/paste

su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096"

It should come back with a readout like this and put a 60.00Mb modem.bin found in Sdcard

Sent From My ATT S3 i747 Dark Blue BadAss Theme
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
[MENTION=1016795]loserskater[/MENTION] posted a proper rip on the previous page, it's not packaged for flashing though. I'll package it up, but I'm still not sure if I should release it until we've done some more tests.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
I understand that CM11 can still be flashed even after the 4.3 OTA? So with that being said, I'm assuming it should be safe to root and flash CWM from my GS3 w/ 4.3 OTA, then from CWM flash CM11 and Gapps?

I took a look at the thread that this link: http://xdaforums.com/showpost.php?p=47680332&postcount=1113(provided by Evilweasel47) took me to and found nothing regarding whether or not it can be done after the OTA.

I'd like to be extra safe this time around, not interested in bricking another GS3.

Anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
HERE is correct size.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
You'll be fine rooting and installing a custom recovery. Issues only arise when people downgrade bootloaders. You should be able to flash a 4.1.2 rom with the 4.3 bootloaders and be fine, but I have not tested it and won't test it because 4.3 is running just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Why do you want to do it? Stay on what you got.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
So what you're saying is I should just add an assert to the flashable bootloaders to make sure people aren't attempting to downgrade? If so, that'd be a much better solution. (From my point of view, anyway.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I can confirm I flashed 4.4 after the OTA. Here is the screenshot - http://i.imgur.com/NZEm91I.png

You can see it has the latest baseband version from the 4.3 stock.

---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------

I know but I really miss the TW camera. :p

---------- Post added at 05:53 PM ---------- Previous post was at 05:50 PM ----------

In case anyone needs it, I created my own ODIN flashable latest version of CWM recovery since it wasn't available online anywhere. Here is the link to the download - https://www.mediafire.com/?m191fvjujkr1f18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
So, from a rookie perspective, it looks to me that this current issue should be resolvable? It seems to me(from what I've gathered reading along this thread) that the only reason I bricked my device is because I went from the 4.3 OTA to 4.1 Stock + Flash Counter Wipe + CWM Touch + Root. The 4.1 stock included the original bootloader and modem. Hence the paperweighted GS3. The moment I finished the flash of all those zip files and clicked "Reboot" she was a goner.

But, as I said, this is just a rookie perspective and I'm sure it is harder to resolve than just updating the bootloader(s) for every single ROM available for this device.

I have a habit of exposing my green side. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
It might be a good idea. Maybe add something like this to the all the bootloaders except 4.3:

assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
If you downgraded to 4.1.x bootloaders, then you're pretty much out of luck. But if you upgrade to the 4.3 bootloaders you should be able to stay on them while running a 4.1.2 rom. It might not work, as there may be issues with wifi/camera/etc. but in theory it should work. [MENTION=2972841]enewman17[/MENTION] is trying some things with his bricked S3, but it's not looking good.

Also, ROMs dont flash bootloaders, they only mess with the system and boot partitions, which makes them less likely to screw things up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
So being that my GS3 was/is on 4.3 OTA... it should be on the applicable bootloader? Meaning the issue was in flashing the zip that returned to stock and wiped the flash counter. The OP of this thread: http://xdaforums.com/showthread.php?t=2363882 said it also returned the bootloader and modem to stock as well.

Sorry if I'm buggin' anyone, just trying to understand where I went wrong with my last two GS3's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
If the zip you flashed contained the bootloaders for 4.1.x then there's nothing you can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jde984:
Has anyone tried running the 4.3 ota rom with the leaked 4.3 bootloaders? I'm wondering if wifi will work in that case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Thanks Loser. I tried out the modem and put it into a flashable zip. I first was on the MJ2 modem, Flashed the MJB Modem, Then Flashed the LK3 Modem all in TWRP with no issues. I am inside my work which has little to no signal so I will have to check out signal later on. But as far as flashing goes I can flash between any or all modems still.

Sent From My ATT S3 i747 Dark Blue BadAss Theme
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Screenshots

View attachment 2409351

Sent from my Samsung Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gaoqi7:
Can not root by now . I'm failed with CF AUTO .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
Your CWM recovery file is set to private.

Any issues you've run into in the few hours you've used it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Amhed0910:
Hey, been reading this thread for a while, but it seems that no one has asked this (tell me if I'm wrong). How can I update from the leaked 4.3 UCUEMJ2 to the official one? Is there any way to do this? I'm new here at the forum, but can handle android and flashing processes quite well. Can you guys please help me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Don't do it. Your better off where you are now than doing the official update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Amhed0910:
But what if I do want to? You know, the leaked version is very buggy and the battery seems to die very fast. What can I do? If I can't upgrade to the official one, can I get another ROM that works just fine?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
If you simply must have the 4.3 OTA, use an Odin package to restore to Stock 4.1.2 and let the OTA happen normally. If you've read this thread, you'll know what risks you're taking. If you haven't, then read some more. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
I can not install CM11 due to an outdated CWM recovery!

Can't go past Recovery or Download mode...

Does anyone know, or have, a link to a flashable(Odin or Recovery) CWM 6.0.4.3+?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
I think it might work with teamwin too but am not willing to give it a try. Evilweasel47 said he made a flashable tar file for cwm but his file is private. I don't think it's hard to create the tar file yourself but I prefer to wait for someone else to do who knows what he's doing since it can brick your phone.

tmo beta7 seems to have been just posted a few minutes ago and it presumeably supports I747UCUEMJ2. If someone gives it a try it would be great to have some info on how it works...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
You can use your out dated cwm to flash the latest one from your sd card.

---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------

Search in Android development. The thread isn't too buried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
That is the file I'm looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] suprtrukr425:
Just something to think about for people that have updated, or want to update, and are flashing roms and recoveries. With no way to Odin back to stock, if you make a mistake and bork your recovery you are pretty much screwed.

Thank you to all the devs putting in the effort and risking devices for our S3 community.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I am currently outside but will go home and upload it again in about an hour or so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oldbbman:
A prerequisite you must have to be a dev. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Technically, an Odin flashable version of this could be made. But I'm not updating yet to do it, and I'm not asking any one else to do it. Too many things about this update are unknown to try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joehen873:
Didn't note 3 have these problems also??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
Can't the T-Mobile tar be made usable for our s3? Like what enewman17 did with deTmobilized? Saw that they have the 4.3 update on sammobile. I'm not a beveloper by any means so don't know if its possible with all the Knox crap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
From what I've gathered and recall, any Samsung device that officially updated to 4.3 has the difficulties we are now facing here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Something was causing Wi-Fi to not work on the 747 when flashing the tmo version. But be patient. It's only been a couple of days. IF these problems can be worked around/solved, the great group of ppl here can figure it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
This is the fixed link - https://mfi.re/download/m191fvjujkr1f18/recovery.tar.md5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
I want to thank everyone who helped, or tried to help, me today. But I ran out of "Thanks".

I was on 4.3 OTA on 2 GS3's. I ended up rooting via AutoRoot using Odin. Installed the latest TWRP using Odin. And flashed SlimBean 4.3 + Gapps. So all is well. Came from 4.3 OTA to SlimBean 4.3. And it is way easier than I though it would be to come from 4.3 OTA.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gaoqi7:
Cheers!

---------- Post added at 07:41 AM ---------- Previous post was at 07:21 AM ----------

So , is it means that I can use this file to root my s3 which had OTA update to 4.3? And how to use this file .sorry for my newer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperFilapo:
This should help you: http://xdaforums.com/showthread.php?t=2539313