yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
As far as i know there is no odin tar for the att 4.3, not official anyways.

if your bricked look here

http://xdaforums.com/showpost.php?p=47911843&postcount=165

I have posted a debricking file for the I747U as well as I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
My issue is that i do not have a 4.3 OTA odin package for i747 AT&T to restore to. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
thats why i posted if you're feeling adventurous flash a 4.3 ATT flashable zip via recover after you boot the bricked device. thats really the only option for ATT right now. Odining back to the 4.3 rom would be preferred. but not an option yet for ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
I was under the impression the OP had an odin flashable 4.3 bootloader link before it was temporarily removed. How else could I flash a 4.3 recovery compressed zip, the external SD card is being used as it's bootloader at the moment.

My goal was to flash and recover the bootloader via ODIN and get the device to boot on its own, then finally load the flashable zip via external SD

card. Correct me if i am wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
theramsey3 was in the same situation you were in. possibly reading his post will help. http://xdaforums.com/showpost.php?p=47959048&postcount=183
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
I wrote a how to in the Q&A section it is still a work in progress so if I have left something unclear or unfinished please send me a pm I will be glad to clear it up to the best of my ability. See link below.

http://xdaforums.com/showthread.php?p=47984104
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
I figured it out finally :)

Just had to swap to an alternate SD card with the 4.3 bootloaders.

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

Yes, I was trying to do something similar to what you did and finally got the device to boot on it's own.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Are there any plans to update the OP with the downloadable zip bootloader files again? This thread has been quiet for the last couple of days. I understand the issues and am willing to accept the risk that downgrading the bootloader will result in a borked phone. I already have my phone unlocked and have no desire to ever downgrade.

I'd like to update but don't want to do all the back to stock to get it done. Already flashed the modem from the modem thread.

I'm looking for the 4.3 M variant one. I747MVLUEMK5 Can anyone point me to another thread or PM me with a link?

I'm also working on getting it added to the CM assert but need to verify it works and is stable. Should be good to go though. The AT&T ones have already been added.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I've been busy with work and family over the past few days and will update the thread within the next 12 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I never meant to imply that I am ungrateful or that you didn't have life getting in the way. Was just wondering if they were still in the works or not as it has been quiet for a while.

Thank you it is much appreciated. Also thanks for your hard work on the modem thread. I've been referencing that thread for quite a while now.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhomiec:
please correct me if i'm wrong, as i understand it, the updated Bootloader is only required for TouchWiz-based 4.3, right?

or is it required for anything 4.3 and up?

i'm currently on CM10.1.3 (aka 4.2.2). but when i flashed CM10.2 RC1 (aka 4.3.1) last week, the flash process worked, but when i'm actually using the ROM, i get about 2-3 random reboots an hour. this also happened to me with SlimBean 4.3.

but from what i remember on the previous Bootloader update, you had to update it otherwise you would get the "Status 7" error in recovery when trying to flash any ROM 4.2 and up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
OK so im trying to flash tasks rom but in the OP says you have to update the bootloader http://xdaforums.com/showpost.php?p=41535366&postcount=26684 and im not sure what to do some say you do some say dont.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That was old news when LK3 was the latest release. As long as you have at least that you are fine. For newer ones just make sure its in your ROMs assert.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
ROms assert

http://xdaforums.com/showthread.php?t=1781242&page=816 I made a post here # 8159 its my log that im having errors
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
What is your bootloader revision? Download root checker from the market to see. Note that baseband and bootloader are NOT the same and don't assume that if one is one revision that the other is the same. Another bit of helpful information would be what stock version were you on? 4.3 or 4.1?

Post back here once you find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
ok stand by

D/L root checker verified and Baseband I747UCUEMJB

And I was on 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Did you double check that? That doesn't look like an official revision that I've seen. I'm on the M variant though.

Also I wanted the bootloader number not the baseband number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Double check what.? My baseband yes I went into settings and the info on root checker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Once again, I want the boot loader revision NOT the baseband revision. They are 2 very difference things.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Honestly im working on something right now so I cant boot my phone but when I tried 2 different root check apps 1 of them just said root verified and the other same thing but gave me info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
We aren't checking if you have root, we are using the root checker app to get your bootloader revision. That information cannot be obtained from the ROM menus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
I got you Ill check again and see when I ran root check to look for the bootload revision I didnt see anything.. But thanks for helping this much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
So I did some looking around. Seems like you have a fairly new bootloader and it hasn't been added to the asserts yet for Task's ROM. So you will have to wait until he adds them or pick a different ROM like the latest CM nightlies that already have it added.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks for that.. well I was trying a few things and as a result my phone now wont turn on at all this was the last thing I was doing http://xdaforums.com/showthread.php?t=2498233
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You are on your own for that one bud.....

Your bootloader one was an easy one. Should have just held tight and waited for a responce. Either way best of luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
LOL yeah its cool live and learn.. But again thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pitbullmommy45245:
i'm in the same boat as the other guy except i didn't brick my phone. i want to flash either dirty unicorns 4.3 rom or beanstalks 4.3 rom but i get a failed each time i try. here is a screen shot of my info on root checker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Ask in the ROM thread; All that's needed is for the ROM installer script to allow that bootloader version. You can't flash another bootloader over that one, it's the newest one and downgrading will brick it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Also, quick update to those waiting for ZIPs, I'll be posting them on Thursday. Sorry again for the wait.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pitbullmommy45245:
so do i need to flash a new bootloader or just wait for them to add it. i just posted in the rom thread (dirty unicorn and beanstalk) and asked if they can ad it. do i just wait for them to? sorry for the noob questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
DO NOT FLASH

any other bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pitbullmommy45245:
k lol. i'll just wait for them to hopefully ad that bootloader variation to their site. my goal is to flash beanstalk or dirty unicorn lol haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Sorry for the delay in getting the new links up everyone, I'm uploading the M-variant versions now and will do the AT&T versions next. It's been a busy week... :rolleyes:

EDIT: Some versions are now available in my Dropbox!

You will not be able to downgrade your bootloader using these packages;

Upgrades only!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
Can't flash bootloader from current bootloader version

Hi there,

I was just trying to flash one of these bootloaders, but it stops and I get the message

I've probably caused whatever problem this is myself, but does anybody know how I can flash a new version?

Thanks,

-- b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eigenket:
I have the same problem with I747UCALG1. I was hoping my problem might be solved by the new ZIPs for the AT&T variant, and was going to sit tight and wait for them before reporting the problem, but it appears you're having this issue with the I747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You likely have a newer bootloader installed. Rolling your bootloader backwards can cause major problems and these zips protect users from that.

Use the app root checker to check your current version and see what it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
Thanks. In my case, Root Checker doesn't provide any further info--for "Bootloader", it lists the same version string as my post above, "I747MVLALH1".

-- b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
What boot loader are your trying to flash and did you get the correct one for your phone? AT&T or Canadian Variant?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
Hi there,

The phone's an SGH-I747M, so it's the Canadian variant. I've been running the Cyanogenmod d2att 10.0 ROM for as long as it's been out.

I was trying to flash 'boot_CWM_I747UCDMG2.zip' (an ATT version) in order to satisfy the Cyanogenmod d2att 10.2 zip which insists on one of several specific bootloader variants in order to install. That flash fails on this line:

assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");

Possibly this is all a dumb idea :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
I'm currently running 1747UCLG1 on my SG3. If I flash the file found in the Drobox a few posts up: boot_CWM_I747UCDLK3.zip, will I be all good? Currently trying to flash 10.2 but need that updated baseband first. I think I will be okay but I want to triple check before I brick my only phone....

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
No no no. Never flash an AT&T bootloader onto an M variant of the S3. If the checks weren't in the flashable you would have bricked your phone. You owe dstruct2k a big thanks for adding the check that prevented you from flashing that file earlier.

If you look at the list of acceptable bootloaders that you listed, you will notice they either start with I747U or I747M. If you have the M variant pick a bootloader with the I747M at the start. Those are the ones for our Canadian versions of the phone. Same goes if flashing a modem. Pick the ones that start with I747M not I747U. I recommend you flash I747MVLDMF1 for now. That way if you ever need to go back to stock ROM you wont have any issues. That bootloader won't cause you any problems and will give your freedom to flash pretty much anything that's out there as that bootloader is currently in all asserts.

Cheers and good luck.

---------- Post added at 10:35 PM ---------- Previous post was at 10:27 PM ----------

Dstruct2k, I think it would be useful, based on the confusion seen in the last couple of pages, to explain the difference between the U and M variants as well as maybe explain the assert for the bootloaders and why its in there and what it does. Also a list showing all of the possible bootloaders and the order in which they were released might be beneficial. It would help people know what they have installed and whether or not they are trying to upgrade or downgrade.

I'll do up a post tomorrow for this tomorrow when I'm on my computer and maybe you can paste it in the OP or at least link it.

I know you can argue that people shouldn't be flashing anything if the don't understand the basics of what they are doing but to be honest they are going to do it either way. Might as well save them the trouble of asking and the trouble of us answering all the questions in here.

Cheers and thanks again for this thread and the flashable zips.

---------- Post added at 10:41 PM ---------- Previous post was at 10:35 PM ----------

Yes if you flash that bootloader that you mentioned you will be good to go and flash any ROM you wish.

Just to clarify for you, baseband and bootloader are not the same thing. A baseband is your modem/radio which deals with the devices cellular connection and WIFI chip for example. It doesn't matter what baseband you have installed, the ROM won't check for that during install. The bootloader on the other hand is the firmware that tells your phone how to power on when you start it up. What areas of hardware to turn on first and how to get it from an off state to a fully powered on state with your ROM running. These are what are checked for when you try to flash a ROM. So just be careful not to confuse the two things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
Thank you very much for the quick answer. One last question. Say I install that bootloader, flash my new 10.2 rom but decide I want to restore back to my 10.1.3 backup. Will the bootloader cause any issue or will I be able to restore?

Thanks! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
Thanks for that advice and reminder to re-rtfm: noted :)

Any idea where that bootloader might be available?

-- b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Flashing ROMs will never flash a bootloader for you unless its a stock ROM flashed via ODIN. Also restoring and making nandroids will never do anything with a bootloader. Once you manually update the bootloader with the file found on this page, you should never have to worry about it again. You will be free to flash whatever you want or jump between CM10.1, CM10.2 or CM11.

Seriously after you flash your bootloader update, you can leave this page behind. You are finished dealing with bootloaders and should never have to flash one again.

---------- Post added at 11:02 PM ---------- Previous post was at 10:56 PM ----------

Reminder to what?

Sorry dstruct2k hasn't posted that version yet. You are fine if you flash I747MUMBLL1 instead. That's one revision older but will work just fine. You wouldn't notice a difference between the two anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
To re-Read-The-F***ing-Manual :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
Just tried flashing that bootloader:

Installing: /sdcard/0/boot_CWM_I747UCDLK3.zip

Finding update package...

Opening update package...

Installing update...

You cannot flash from your current bootloader version. Current version: I747UCALG1

E: Error in /data/media/0/boot_CWM_I747UCDLK3.zip

(Status 7)

Installation aborted.

........? What did I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Bad news. I extracted the assert that dstruct2k has for this bootloader and its wrong. He has it set up as only able to flash this bootloader if you are on this bootloader or MG2. He should have it set up to flash this bootloader if you are on any of the versions prior to LK3.

You can't do anything about it now except wait for him to fix it. You could edit the assert yourself but I wouldn't recommend it if you don't know what you are doing. I'd say you could flash MG2 instead as it would accomplish the same thing but I check it out and there is an error in it as well. You will either have to hang tight and wait for dstruct2k to fix them or edit the assert. I can maybe do it for you tomorrow night if you still need help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
Wow thanks for the info. I definitely won't mess with the assert. I know top-level stuff about this kind of stuff but I'm not confident enough to edit code that could really mess me up. This is my only phone - it is my work phone as well so I really have to be cautious with it. I will either wait for dstruct2k to fix the .zip or if you get the time to correct it then I will be forever grateful. Truly appreciate your help in this matter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Bad news dstruct2k, your asserts for the 2 AT&T bootloaders you have posted on dropbox are wrong. It only shows the 2 new bootloaders and doesn't allow anyone coming from an older version to flash them. See below. It is what's in your LK3 assert. I checked a couple Canadian ones and they seem to be okay. Looks like just the two U variants.

Thanks.

assert(getprop("ro.product.device") == "d2att" ||

getprop("ro.build.product") == "d2att" ||

abort("This package is for \"d2att\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

assert(getprop("ro.bootloader") == "I747UCDLK3" ||

getprop("ro.bootloader") == "I747UCDMG2" ||

abort("You cannot flash from your current bootloader version. Current version: " + getprop("ro.bootloader")););
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
PM sent with the modified assert for the LK3 bootloader. Please do not redistribute it to anyone. Let me know when you have it downloaded so I can delete it from dropbox.

Also flash at your own risk. It should not cause any problems as all I did was add your current bootloader to the assert but if something goes wrong it's not my fault. I did not verify anything else in the package. I just did this to get you up and running a little sooner. If you would prefer to wait for dstruct2k to fix the ones he has posted, that's fine too. I just know he is super busy and might not get around to it for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Yes, the U versions need fixing and I'll be doing that later today. I'm really sorry to all of you that are waiting for these.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Much appreciated, [MENTION=4646474]flexfulton[/MENTION]. There's a few you missed in your quick lists of versions, but I'll be updating all of that information in the first post when I get home today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I just copied your list from the modem thread. Sorry I missed a few. I know there is a 4.3 bootloader for the Mexican M variant. Either way I'll make sure I make the changes once the official list gets updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Keland44:
thanks for the detailed over view i do have a better understanding of it now

but

that just brings up more questions :D

i'm currently running into an issue using the new 4.4 roms for some reason i keep losing reception (completely dead no data nor voice emergency call mode only) in known good reception areas

here are some screenshots of my setup any help you could provide would be awesome or a direction you can point me

actually in the last pic when i was making my screenshots and getting ready to send them to myself to post on here you'll see up in the notification bar and how my cell reception bar just goes dead but in the other two screenshots I have full bars
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That has nothing to do with bootloaders. You'd be better to ask in your ROM thread or a Q&A thread.

With that being said I don't really think this is a good answer to your question but I know some ROMs will do that for a few seconds when switching between the 3G and LTE networks. No one seems to know why and I don't think there was ever a fix. Don't quote me on any of this. I'm just going from memory about something similar I saw a while back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Does anyone know where the Ucuemjb bootloader and modem can be gotten?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
These haven't been updated to prevent downgrading.

Do not attempt to downgrade your bootloader if it is a newer version.

https://www.dropbox.com/sh/ienv2c21m1a0tme/YfjTnOGwaC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
Hey buddy, still waiting on those updated downloads on the first page!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
If you reread the post you just quoted you will see he provides you with a link for them and a warning that they haven't been fool proofed. So flash away. Be aware though that the one he posted is the newest of the new and it may not allow you to flash all ROMs

Depending on how old they are.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Modem is fine. Bootloader wouldn't flash. Error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Can't help if you don't tell me what the error says.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Error in (filename)

Status 6

Sorry about that. No worries. I know I really don't need the bootloader. I'm just a stickler for new things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Ok guys, finally got my PC running again late last night after my SSD gave out a couple days ago. I'll have the updated packages up today after work.

There might've been something wrong with the flashing script, you should get more than just a status 6 (unless your recovery is out of date) because I added error descriptions that would say more than just "Status 6". The new packages later today might help, but in the meantime, try updating your recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I have the latest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eigenket:
Any news on the new packages? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
Also wondering about the updated package. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
Why am I getting Status 7 errors?

I rooted a Samsung S3 i747 (AT&T).

Note: In the process of rooting I mistakenly flashed CWM as a bootloader instead of using PDA in Odin. I am not sure if that may be the root of the problem.

Anyway, the phone is rooted, I can reboot into recovery (v5.5.0.4) but every time I try to install CM, I get an error message.

Here is an example:

- - Installing: /sdcard/cm-10.2.0-d2att.zip

Finding update package…

Opening update package…

Installing update…

assert failed: getprop(“ro.product.device”) = = “d2att” | | get prop(“ro.build.product”) = = “d2att”

E:Error in /sdcard/cm-10.2.0-d2att.zip

(Status 7)

Installation aborted.

I see that this may be the result of not having an updated bootloader. I tried doing that a number of times, unsuccessfully.

Can anyone help me get this phone loaded with Cyanogenmod?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
https://www.google.ca/search?q=status+7+error