yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
The AT&T logo can pause a long time when first booting 4.3.

After waiting 10 min. it is safe to pull the battery & try for a normal boot.

I reviewed this again for accuracy. The details are all accurate.

Please verify that the details summarized below are what you followed.

Let me know if you find any variation or have questions.

PM me questions if you like.

If no variations, it is also safe to repeat as described.

Wipe data, cache & Dalvik cache

Odin to UCDLK3

Boot 4.1.1, shut down,

flash CWM-Recovery-LTE-SGS3-v5.tar.tar

reboot into CWM

Wipe data, cache & Dalvik cache

flash update412.zip

Boot 4.1.2, shut down,

reboot into CWM Wiped data, cache & Dalvik cache

flash the I747UCUEMJB modem (linked as Radio - loserskater)

CWM Wipe data, cache & Dalvik cache

flash upndown4par's Full ROM

CWM Wipe data, cache & Dalvik cache

flash UCUEMJ2_Insecure_kernel.zip

Boot 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
4.3 ROM & Modem over MJ2 Kernel & 4.1.x Bootloader

You're welcome A!

Mamikemic, I tried flashing the insecure MJB kernel while verifying this upgrade method & so was forced to reenact 18 steps for my own GS3.

The 2 MJB kernels I tested from the dev thread both broke my wifi, so loser's insecure (MJ2) is a must here.

In the process, I recreated the stuck at AT&T logo issue.

I also made some notes that help with the difficult parts.

I have added the missing step 6., 14. & 15 for clarity (the odin MD5 is inside the CF Auto Root zip.)

Step 7. can be done from CWM, but I recommend using Chainfire's excellent Mobile Odin (available here, but why not go Pro!)

In this way, steps 7. - 13. can be handled using Mobile Odin's OTA or load zip methods, with keep root & reinject settings.)

I maintained root throughout (at the expense of my flash counter, since Triangle Away doesn't support 4.3) by Odin flashing CF Auto Root as needed.

When booting each rom flash (steps 3. & 9.) I completed the first use wizard, skipping the Google account & personalization steps, before shutting down. This allowed me to see that wifi is working.

Any "(app) has stopped" messages (including SU) during these sessions are due to missing updates and are safe to temporarily ignore.

Yes, there is a tendency for the new (& less entertaining) AT&T logo to hang here on our phones. It needs to display the "Android is upgrading..." popups to succeed. The also can hang here, once they appear. In either case, rewipe in CWM.

I let it dwell 10 min. the first time, pulled the battery, retried for a minimum of 3 min. & pushed it by redoing the CWM wipes for success. I apologize for making this all appear easier or less intensive than it really is.

In the end, I have repeated the process (forced for me this time by my test of the MJB kernel) much the same as I originally completed it.

Update 1/23/14: Successfully reflashed omitting the 4.1.2 steps as follows. If Samsung logo hangs in Step 15., wait for boot. Ditto AT&T (more than10 mins., rewipe in CWM).

1. Wipe data, cache & Dalvik cache

2. Odin to UCDLK3

3. Boot 4.1.1, shut down,

4. Flash CWM-Recovery-LTE-SGS3-v5.tar.tar

5. Disconnect USB & Battery immediately as Odin resets phone

6. Boot into CWM, Wipe data, cache & Dalvik cache

7. Flash the I747UCUEMJB modem (linked as Radio - loserskater)

8. Flash upndown4par's Full ROM

9. Flash UCUEMJ2_Insecure_kernel.zip

10. Flash CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5

11. Disconnect USB & Battery immediately as Odin resets phone

13. Flash CWM-Recovery-LTE-SGS3-v5.tar.tar

14. CWM Wipe data, cache & Dalvik cache

15. Boot 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kastro1784:
I've had that same problem I wasn't able to fix it tho

---------- Post added at 07:11 PM ---------- Previous post was at 07:07 PM ----------

That happened to me also I sent my galaxy s3 to Samsung support in Texas I told them that my phone was failing to boot up after the 4.3 update they fixed my phone for free it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
The above quote gives some insight on what should be happening after following all steps, then booting from the final CWM wipe dalvik cache.

Namely, the on screen countdown of "upgrading apps". It panicked me when the logo hung & later with "starting apps" but persistence & safe flashing procedures can get past that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vlangden:
I've seen this questions asked several times but no answer, in regards to coming from CM11 back to stock 4.3.

I had the original OTA 4.3, rooted it, removed KNOX, and installed TWRP 2.6.3.1. Then I made the jump to CM11 - but after a few days missed some of the usability of stock 4.3. My CM11 rom is still on the MJB loader (which as the same as the OTA 4.3), so wouldn't flashing the update43.zip from recovery work to get back to stock TW 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lok3sh:
Hey guys,

I have a stock phone on 4.1.1.

I don't have an eternal SD card so I can't install these two updates from there. Is there another (free) way to do it besides the SD card or the OTA?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mexihg:
my s3 go bad

updated my s3 4.3 and since then came the problems, the s3 freezes and restarts every 10 minutes is stressful, try installing others roms 4.3 I found but the problemstill i do not know what more I can do, i reinstall the upgrade and kernel and still the problems

:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElPapiMagneto:
The only thing I can't find here is the prerequisites. I already have a rooted 4.1.2 with TWRP. Do I have to go to 4.1.1 and then back to 4.1.2? I assume I can skip that step.

I also tried the OTA from AT&T but when the phone reboots, TWRP starts and nothing happens. I would love to get 4.3 installed but I can't figure out the steps here.

I just use the 4.3 update zip file from this thread and use that from TWRP?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tokuzumi:
I have a Nexus 5 in the mail, so I wanted to put my GS3 back to stock. I was also having some issues where the phone would not turn off the screen, unless I manually pushed the power button on CM11, so I wanted to start fresh. I went to this thread:

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

and followed the instructions in post 2 of this thread:

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

If you are on AT&T, and want to use the LK3 firmware, the only working link is the Google Drive one. I cannot speak for the LEM and the LG1 links, as I didn't use those.

I ended up going from the LK3, straight to the 4.3 update. I'm not sure what version the LK3 update is. I'm thinking it was 4.1.1, as I recall the 4.1.2 update having a higher bootloader than LK3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
I researched how to get a Knox free stock 4.3 and wound up combining MJB ROM & Modem over MJ2 (leaked 4.3) insecure Kernel & LK3 bootloader. See my update to post #337, this thread.

I have flashed this combo 3x & debloated it's a bug free daily driver with great battery life & App Ops.

Even before I dropped the 4.1.2 steps, I'm pretty sure the bootloader stayed LK3 (4.1.1)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Any chance you can drop some links? I'm having a stupid this morning and I can't seem to remember how to tell what bootloader I have, but I'm on a 4.1.2 ROM (Dandroid.) If I go to the (big) MJB thread (here), and I go to get loserskaters mjb bootloader (here) the link is dead. I'm willing to not upgrade bootloaders if there's not a great reason to do it...I just need advise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
Sure. What I'm running starts with the LK3 Odin flash for Bootloader

Then I747UCUEMJB modem in Loser's hidden link

The ROM d2att_4.3_MJB_Full_Odex_v1.0

The Kernel Insecure Kernel with SE-Linux enforcement disabled (fixes root): in stratatak7's post #3.

Steps are in #337 at http://xdaforums.com/showthread.php?p=49365521#post49365521

I debloated using App Quarantine, stock controls, Startup Manager & App Ops then set SELinux to Enforcing uding Pavel Sikun's app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Diodio26:
I've seen a bunch of topics about people wanting to revert from 4.3 to 4.1.2.

Is it 4.3 so bad? I'm currently on 4.1.2 which I updated using the OP method. I decided not to flash 4.3 due to everyone wanting to roll back.

What's so bad about 4.3 aside from not being able to roll back and Knox?. I don't have a problem with that.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
I have been running 4.3 since mid-December & I definitely don't want a lower ROM. The 4.3 OTA ROM*, Modem & leaked kernel** combine over the 4.1.x stock bootloader on my phone for a great 4.3 experience. Fast & stable with all the benefits I wanted & none of the unwanted restrictions.

That is because our devs designgears, upndwn4par, loserskater, stratatak7 & others took the bite out of 4.3 for us. These devs put the resources out there for others to work with and the resulting forum activity showed me I could have & enjoy 4.3 as I am. Details are in this thread, in my previous post, directly above yours.

*deKnoxed **insecure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
pc103,

Firstly, I'd like to say thanks for your efforts here. You have taken the time to explain well how to upgrade to 4.3 over the DLK3 bootloader. This really makes things quite easy to go back to stock.

I do have a question, where you say flash the modem, ROM & insecure kernel, I'm assuming your using pc ODIN. Do you flash the above from PDA?

Also, are you flashing each step separate, rebooting, clearing data/cache/Dalvik & rebooting before flashing the next step?

Thanks! for your efforts!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidBH:
How add languages on this stock rom? Croatian?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
You're welcome sailindawg! As you know, I've posted about this method a few times. By now I've stepped through it 3x on my GS3 for various reasons. Here are the latest steps, with comments to answer your questions:

1. Wipe data, cache & Dalvik cache

2. Odin to UCDLK3

3. Boot 4.1.1, shut down,

4. Flash CWM-Recovery-LTE-SGS3-v5.tar.tar

5. Disconnect USB & Battery immediately as Odin resets phone

6. Boot into CWM, Wipe data, cache & Dalvik cache

7. Flash the I747UCUEMJB modem (linked as Radio - loserskater)

8. Flash upndown4par's Full ROM

9. Flash UCUEMJ2_Insecure_kernel.zip

10. Flash CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5

11. Disconnect USB & Battery immediately as Odin resets phone

13. Flash CWM-Recovery-LTE-SGS3-v5.tar.tar

14. CWM Wipe data, cache & Dalvik cache

15. Boot 4.3

Steps 2, 4, 10 & 13 are Odin PDA flashes.

Steps 1, 6 - 9, & 14 were done via Clockwork Mod Recovery.

The wipes were done as noted; steps 1, 6, & 14, plus a follow-up round after appearing to hang at either logo for at least 6 minutes on the first full 4.3 boot.

Additional details & links are in my final post of 1/24/14 in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
Thanks again pc103! Your efforts are much appreciated. Reading your post #337 you mention that the modem, ROM & insecure kernel can all be flashed by way of Mobile ODIN. I may try this with MO Pro. That Chainfire is one crack dev! As I'm learning about MO, I'm liking the fact that not only can root be re-injected with each flash, but you can set to wipe data/cache/dalvik. It's a pretty comprehensive tool. It's good to know how to flash ODIN PDA files with pc as well. Regarding your comments about the device hanging after flashing, the solution there seems to reboot to custom recovery and wipe data/factory reset. You indicate that after 6-10 minutes, the device should complete or it is hanging. You have made this first time noob flasher's experience a bit less white knuckle! It's always exciting to jump into that abyss after clicking the start flash button!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
Probably all 3 sgs phones I've had were prone to the hanging logo after a rom flash.

Letting the background process complete some, then rebooting with cleaner caches can usually get past that.

+1 on MO Pro. Chainfire's awesome like that.

I should warn though, I had problems recovering from recent nandroids. I've switched to TWRP to try the difference, but for now I'll just keep enjoying 4.3 since it's stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
What kind of problems? I've only used TWRP these past few weeks. I have not had a problem recovering a restore or a part of a nandroid like Data, yet. These past few weeks has been my only experience though. What I have noticed about TWRP nandroid recovery, it will not touch a bootloader. That's how I got the 4.1.2 bootloader with a 4.1.1 nandroid restore. The camera stopped working withn that combo. ODIN back to stock 4.1.1 solved that, camera now working with full 4.1.1 bootloader again. That's what I have found so appealing about your method. A way back to a stable system that I think performs well enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
That was the appeal for me in flashing 4.3 also. I did not want to lose "downflashing" ability or accept Knox restrictions. I wanted App Ops and don't want to lose it. Lack of permission filtering is my biggest disappointment with Android.

After long success with restoring CWM nandroids; including from 4.3, my recent CWM nandroids would restore, but give a 2 vibration boot loop at the Samsung logo. I can still browse them, but I was more interested in reimaging from scratch than troubleshooting nandroid those times. I took the radical step of switching to TWRP to try working around the problem.

Nandroid from any custom recovery never includes the bootloader; only the ROM, Kernel, data, caches & sometimes Recovery. Note that the Radio or Modem is not included. So the camera problem you experienced with 4.1.1 nandroid should have another explanation.

I did some research to verify why my 4.3 method results in an LK3 bootloader and help determine if you actually handled a 4.1.2 one. The short answer is booltoader changes probably come via OTA push & Odin, and not via custom recovery flashes. The most informative piece I found on this is under Functionality of the Bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] serstylz2:
so if i did this method, and am having problems now, i cannot flash back to 4.1.1 and repeat the process can I?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
If you followed the method listed 5 posts earlier here, flashing back & repeating are no problem.

The method uses LK3 bootloader + MJB modem + MJB rom + MJ2 insecure kernel.

The bootloader is 4.1.1 & the modem, rom & kernel are 4.3.

The resulting Android image runs great once you get past the logos on first boot.

I have flashed this combo three times with the same great result.

Other times I used alternative stock kernels & found wifi disabled.

What problem were you having?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] serstylz2:
Sorry, I should have specified I followed the OP directions. Not the updated directions, which look awesome. My phone is completely dead at this point, not even a red LED when plugged into PC or wall so I think it was a hardware failure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
That is sad news &I hope it works out better. Have you checked out the unbricking for 4.3 downgraded thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
[MENTION=531042]pc103[/MENTION]

I finally flashed 4.3 using your method. I followed your directions to the letter. However, my first attempt with upndown4par's rom from this thread resulted in a hang on the AT&T boot page. No matter how much I wiped data, cache, Dalvik, I would get the same hang at the AT&T boot logo. I let the phone sit for 15 minutes the first time, pulled battery & rewiped to no success. Tried this for the better part of an hour and a half. No go with upndwn4par's rom. I had read a post from that thread that indicated such a thing and to use loserskater's rom from thread. I odined back to stock, wiped, rebooted back to stock and flashed TWRP via odin. I booted to TWRP and flashed the MJB modem, wiped, flashed loserskater's rom, wiped and flashed the MJ2 insecure kernel, rewiped. Before flashing the insecure kernel, I let the phone boot to the newly flashed 4.3 rom. No hangs. Went to the AT&T logo for about 3-5 minutes, then booted the OS. I did notice that after the 4.3 rom flashed on the LK3 kernel, I had no wifi. After flashing insecure kernel, wifi worked. I was surprised to see after flashing the MJB modem onto the 4.1.1 LK3 build, wifi and LTE both worked. Been running the phone for the past few days and the phone runs well. I find the battery life no better / no worse than where I was with 4.1.1. I have loaded my Tasker profiles onto the new install and I'll see how that works with Greenify. 4.3 runs pretty smooth. I use APEX launcher. Where I used to get a bit of lag changing screens, the transitions are now smooth.

Many thanks to you, loserskater & upndwn4par for taking the down sides to the official 4.3 update out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
Awesome news 'dawg! I'm glad to hear you can finally get the best of 4.3.

We'll never know why loser's rom fared better on your phone, but your efforts paid off, cause the process is reversible.

A few apps I'd like to recommend:

App Opps Starter

SELinuxModeChanger

App Quarantine

Startup Manager

Enjoy!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
Is startup manager by ES? I have always used ES FileManager & found they also made a start up manager as well. Been unsing that one. I pretty much installed your list, but the quarantine manager. I started using Titanium Backup.

Yes, what I like about this method of up grading is the ability to go back to an official stock rom / stock state. I'm hoping for a way to do the same with kitkat when available. Plus no KNOX.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
This Startup Manager's by Imobilife.

I liked ES too, a project made me search up fx & I stuck with it.

+1 on finding a similar approach to KitKat. I wouldn't want to lose App Ops though. Excess permissions are my least favorite part of Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hadrons123:
I have flashed boot_CWM_I747UCUEMJB bootloader,d2att_I747UCUEMJ2_root_noknox, d2att_I747UCUEMJB_modem, UCUEMJ2_Insecure_kernel on my i747 galaxy s3 at&t. If I wanted to move to 4.3 Official ROM can I just flash it with update43.zip and if I moved will I loose the root, TWRP recovery ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Slemgen07:
I'm having a status 6 error

I tried installing it and it gave me the "(status 6)"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brownhonky:
Can i root my SGH-i747 on Ver 4.3 OS

PLEASE TELL MY YES :crying: SGH-i747 ON VER 4.3....

Allso is there any way to unlock network sim so i can use it on metropcs since i can not downgrade?

Or can i downgrade please help this :eek: NOOOOB :rolleyes:.....

I will be ever so great full for any input thank you........... :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kastro1784:
No way to unlock network sim sense you updated to 4.3... you should have unlocked it when it was on 4.1.1.. but yiu should be able call the services provider and ask them for and unlock code because you travel a lot its not impossible to to downgrade to a lower android version but it became difficult to do so because of the 4.3 boot loader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brownhonky:
:good:thank you:good: . just one more :confused: if i downgrade to a early version like 4.1.1 can i unlock it then? I installed TWRP and removed knox.:rolleyes::silly::(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
From what I understand, downgrading to 4.1.1 from 4.3 will brick your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
Read: http://xdaforums.com/showthread.php?t=2529200
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alltroy:
Please help revive the AT&T Galaxy S3-i747

Please help revive the AT&T Galaxy S3-i747

I made a mistake somewhere: set according to the instructions as stated here rose 4.3 without problems, the phone booted I did backup in CWM 6.0.2.3. Over 4.3 I tried to install CM11night, but got an error (status 7) I did FR / Cash

after reboot goes into CWM. I, did to restore but before reaching the AT&T icon hanging on it more than half

Please advise as to try to revive the device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pc103:
In CWM wipe data, cache & dalvik. Try booting & waiting 10 - 15 mins at logo if necessary, then pulling battery if still hung, re-wiping & booting.

You are trying to advance to the "Android is upgrading xx/yy apps" and "Starting apps" pop ups. The technique can help anytime it falls short.

You can later advance restore data from a nandroid if you like.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaCotyaa:
Status 7 error usually means your using and out of date recovery. Just flash the latest version of CWM, and then flash the rom again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alltroy:
Thank you all responded, the problem was solved so:

Nandroid restore, but the phone refused to boot the system and hung on the logo (at&t)

I flashed in CWM UCUEMJ2_Insecure_kernel + cleaning cache/FR + ATT_I747UCUEMJB_S3Rx_3.0_AROMA_1-27-14

S3 booted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kastro1784:
Hopefully it will be 4.4 kitkat manual update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabrielcab:
Thanks for this guide, I managed to update my i747 to 4.3 using this guide, but now I have no data. The WiFi is working but not the data.

I'm on T-Mobile

---------- Post added at 03:22 AM ---------- Previous post was at 03:00 AM ----------

There where some errors on the APN settings so I fix them and now i'm good to go. Thanks again for this guide.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] david240894:
Anyother link i try to download of androidfilehost and will stop every time before 25minutes of downloading.

Mediafire? Mega? A server with resume download?

Enviado desde mi SAMSUNG-SGH-I747 mediante Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n0013z:
I have a friend whose phone is still on 4.0.4.

I already have the files for 4.1.1, 4.1.2 and 4.3, can i flash 4.1.1 through the recovery or do i have to use odin first?

just dont want to brick his phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
This is what I did. It should be noted that I cleared the flash counter with Triangle Away while still on 4.0.4.

Clear flash counter

Factory reset from settings menu

Flash 4.1.1 with Odin

Verify flash counter is still reset to 0

Use dialer code method to unlock phone

Install 4.1.2 ota from external sd in stock recovery

Install 4.3 ota from ext sd/stock recovery

At this point, I just let the 4.4.2 ota happen on its own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjroberts98:
Where was the file when you installed from CW recovery? I downloaded the OTA, then it rebooted to TWRP. I chose install, but I can't find the downloaded file to try and install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tailgunner9:
Getting it Rooted

I went back to stock 4.1.1 then installed 4.1.2 OTA. So have no root now. What is easy & Best way to get phone Rooted Again so I can install Rom Manager? Thanks guys...;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
So you are going to post a flashable zip from an OTA that you haven't tested yourself? :confused:

See step #4 in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Yes, I'll add it to the other 10 in the modem thread. It obviously works, considering it's shown working in your screenshot and has been pushed by AT&T to all devices.

Don't worry about it, I'll get it from Samsung. This one is just a diff anyway.