yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gd1147:
Having the same issue

You suggested re-flashing the modem, forgive my ignorance, where can I get that ZIP? I am having the same baseband unknonwn after flashing the latest bootloader. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Try here: http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eri000:
I747UCALG1 is a bootloader from ics .... so cm won't install

is this right ??????? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Look at the updater script in the ROM to see which bootloaders are supported.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aenbone:
Freew

This is for the I747M canadian S3.

OP I suggest putting up this link in the first post since canadian S3 users would flash this in order to flash most of the custom roms available.

AlsoI have flashed it and I'm using it with no problem whatsoever.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Weird. I have the mjb bootloader, and can only use the mjb modem. Phone won't see the sim card if I use any other modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vamanos:
Unlocking Bootloader

If I am already rooted and have the mjb bootloader, is there a need to unlock the bootloader/flash one of these updates before downloading any of the CM ROM's? I'm trying to be cautious, and I've seen posts about unlocking bootloaders but they always seem to be tied to verizon models.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyDa:
Hi dstruct2k,

Did you also update the script in your DropBox? I just grabbed the bootloader file from there, and am getting Status 6 (installation aborted).

EDIT: Never mind, I fixed the endings myself. Thanks for making these available!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dy/dx:
Now I am in big trouble!! I upgraded my boot on my I747 using the latest zip (boot_CWM_I747UCUEMJB.zip).

Now, I have no service any more!!

Besides from that I really wonder how flashing a new boot can affect the radio/modem?!

Since it was stated so often that reverting if not possible without bricking I don't want to reflash anything.

Please help me out! Thanks so much!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dy/dx:
Finally got it working :) :) Solved by flashing the latest modem. But: The following question is still up:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Well, you just installed Knox. You can no longer use any other modem, and you've voided the warranty. Boot into download mode and it will say Warranty 1. I curse the day I installed that bootloader. I will never buy a Samsung product again. They can burn in hell.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayShades:
Hi there!

So I bricked my SGH-I747M RLTE Rogers S3 with CM11 d2lte latest nightly due to an entirely different issue & I was just wondering if by any chance you had a bootloader dump for CM11 d2lte??

I've already tried the CM10.2 Android 4.3 which you've provided & from other sources but sadly they don't work probably since CM11 is Android4.4.

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
There's no such thing as a "CM11" or "CM10.x" bootloader. The bootloader is provided by Samsung and will be one of the "I747M..." files posted at the start of this thread. Since Samsung hasn't released 4.4 for the S3, there's no bootloader that's specific to 4.4.

PS - The best way to debrick (and most likely way to succeed) is to return to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayShades:
Thank you for the reply dstuct2k, well I guess I forgot to mention that it's a hard brick & not a soft brick, so no I can not return to any other ROM what so ever :( Basically I can't turn the phone on nor go to recovery or to the download mode, the only thing that happens is when I connect the phone to a computer it connects as a Qualcomm high speed USB download mode device (QHSUSB_DLOAD) in the device manager.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
That should mean you can Odin to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
Last time I bricked I tried that Odin doesn't recognize the phone when it is hard bricked. You cannot access download/Odin mode nor can you access recovery. The only two responses you get from the phone like this is with the battery out and the USB connected you get the red charging led illuminated and with the battery in and USB connected to computer you get the Qual come high speed USB message on the computer. If he flashed an AT&T bootloader on an I747M he needs a jtag if not he can try the debrick image that Mr. X posted which is quoted above which is where I got my stuff from. I pulled the debrick for AT&T that he has above from my phone the day before I tried flashing different things on my phone and bricked 3 times in a week.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayShades:
Yeah exactly, well, I bricked it messing around with a swap partition actually, I had created a new swap partition on a new external sd card & when I tried to reboot the phone into recovery it just went blank & hard bricked I suppose.

& no I can not use the debrick image that Mr.X has provided sadly because I was running CM11 which is based on Android 4.4 & Mr.X has the debrick image for 4.3 :(

But I'm trying to get a debrick image for 4.4 & I also have ordered a jig, so if neither of those work I'll be giving this to a repair shop for jtag'ing which only costs around $50.

I'll post the 4.4 debrick image here if I get it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
You need a debrick image from whatever bootloader you were using the rom shouldn't matter as the debrick card only gets the bootloader image written to it and gets partitioned to replicate the phones internal storage, so in a sense we are simply getting the phone to boot up to recovery with the sd card method and then we can repair the internal storage after you get back into recovery. Do you recall which bootloader you were using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayShades:
No sadly I have no idea which bootloader I was using but as I believe don't the bootloaders get updated with the OS? So doesn't the fact that I was running 4.4 make a difference? :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
It shouldn't be any different running 4.4 vs 4.1.x the rom is just that a rom. The debrick fixes the boot section so the phone can boot. The boot section assigns tasks for different processes when it gets messes up you can use the debrick method to gain access to recovery and download mode so you can fix the portions you messed up.

There are 4 main components that make our phones run: the bootloader, the kernel, the rom and the modem. There more to it that just those but they are the main things you need to have a functional phone. They're all separate and necessary. When there is a problem in the bootloader partition it will not get the phone up and running because the other components cannot perform the functions of the bootloader. For the most part the bootloader determines (depending on user input) whether to boot to recovery, download mode or the rom(OS).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I hard-bricked my first S3 on launch day trying to do the same thing, but I was stealing part of /data/ to make a swap partition. It was habit from my previous device to set up swap, but the S3 definitely does not need it.

Unfortunately, I never found a way to fix it, and ended up taking it back to the store for a new device. (Salespeople will accept anything that comes back "broken" on launch day.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zibranm:
debricked and booted from SD card, now need to restore boot loader

Hi,

I have been able to debrick my galaxy s3 i747m running Android 4.3 by following your instructions in step 1 and step 2. Now the phone is booting with the SD card inside. It can also go to download mode. But without the SD card the phone remains dead. So, I need to restore the Bootloader in the internal SD of the phone. I tried to use Odin to flash your flashable Bootloader. It's in .zip file, but Odin 3.09 accepts .tar file only. So I unzipped the content and produced a tar file, which I used in Odin. But odin failed reporting a write error!

What can I do from here, please advise. Can flashing stock firmware or stock ROM restore Bootloader? Is Bootloader a part of ROM or Firmware? I am new in the Android world. Thanks a lot for useful instructions from you and others in this forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reymundo911:
Cannot flash new Bootloader with CWM

I am trying to flash a new bootloader, so far I have tried the most recent one and CWM_I747MUMLK3 and cwm is telling me that I cannot flash these new bootloaders from the current bootloader I have installed, ie the original bootloader version I747MVLLE8.

Will I be forced to use Odin to do the update of the bootloader? Or is there a way or a specific bootloader version that I can flash with CWM?

Thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Line 6 of boot_CWM_I747MVLUEMK5's updater-script is:

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

This means that you should have no issues flashing boot_CWM_I747MVLUEMK5 on an I747MVLLE8 bootloader. Did you try redownloading the ZIP file and making sure CWM/TWRP are up to date?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reymundo911:
Thanks for the fast reply. I am currently running ClockworkMod Recovery Non touch version, v6.0.4.7 .

I have tried flashing the zip from my external sd card as well as the internal sd.

Here is the error message in CWMR :

Installing /sdcard/0/tmp/boot_CWM_I747MVLUEMK5.zip

Finding update package...

Opening Update package...

Installing Update...

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

Errror in ........

Installation Aborted.

So from typing out this error I have noticed that although the Baseband version in my settings is I747MVLLE8, the current bootloader version I am running is apparently I747MVLALE8 according to CWMR... And it does not seem like it is failing the assert tests, its almost as if it does not even get there in the installation process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
No, that is the assert test failing. I wrote that error message, not CWM. I've never seen that bootloader version before ("I747MVLALE8"), but it's an older one ("L"=2012, "E"=May, 8... May 8, 2012) that you should have no trouble updating from. I've added it to the list of bootloaders you're allowed to upgrade from, just redownload boot_CWM_I747MVLUEMK5.zip and try it again.

The same warning as in the first post applies here; You can not downgrade your bootloader.

PS: I'm tired of people getting this wrong, even though I've posted it 100 times before.

"BASEBAND" IS YOUR MODEM VERSION. ANDROID DOES NOT SHOW YOUR BOOTLOADER VERSION ANYWHERE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reymundo911:
Thanks for adding it to the list. Works great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CreamyTwinky:
dstruc2k,

I have I747M phone and downloaded MF1 bootloader from your dropbox a few days ago. Which BTW.... I have noticed it is no longer available in your dropbox nor mentioned anywhere on the on 1st post.

My question thou.....Can MF1 be downgraded ????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
MF1 was from before they started KNOX'ing everything, so yes, you should be able to downgrade from MF1 to anything older. I still can't think of a valid reason to downgrade though. (That's why the older bootloaders still aren't up. Nobody should need them.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ratcet:
Hoping someone can help. I flashed my bootloader on my Bell S3 following the instructions. Everything seemed to go smoothly, and it booted back into CM again with no problems. However, it will not detect my SIM card now. I have CM 10.2.1 installed, when I try to upgrade to the latest milestone it gives me an error. I've tried restoring/wiping/etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Update your modem to match your new bootloader version. (Link in my signature.) Some modems and bootloaders just don't work together.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reymundo911:
Cannot connect to camera

I flashed the new bootloader and the new modem firmware that goes along with it. But now for some reason I cannot connect to the phone's camera. It used to work with the current ROM I am using. Is there a required camera firmware update with this bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Very old CM-based ROMs had an unfinished camera driver that only worked with specific bootloaders. If you're on the newest bootloader, you can't revert, but you can install a newer ROM.

PS - This was fixed around the same time as a few major Android security flaws, so it's likely your old ROM still has those flaws and should be updated anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reymundo911:
Upgraded from AOKP 4.2.1 to Quantum 4.4.2, camera works fine now. Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
which one is the updated bootloader for i747MVLDLK4 (Rogers)

And can you flash this on 4.2.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C4M3R0N808:
Thanks!

Thanks for this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dethredic:
I'm having trouble updating my bootloader.

I have the I747M (I'm with Bell).

My current bootloader: I747MVLALH1

I'm trying to install: I747MVLUEMK5

I downloaded the I747MVLUEMK5 zip from the OP, booted into recovery and tried to install form the zip but I get this error:

You cannot flash from your current bootloader. Current version: I747MVLALH1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Freewaymad:
Upgrade From ICS4.0 bootloader to JB4.3 bootloader in an OTA

Hi,

How do I customize the update script to update u-boot? Because android only upgrades the boot.img, system.img, and recovery partitions, the automatically generated update package does not support upgrading bootloader. So...would I unzip the update.zip, and then modify the updater_script by implementing the following operations:

# Write u-boot to 1K position.

# u-boot binary should be a no padding uboot!

# For eMMC(iNand) device, needs to unlock boot partition.

ui_print("writting u-boot...");

package_extract_file("files/u-boot-no-padding.bin", "/tmp/u-boot-no-padding.bin");

sysfs_file_write("class/mmc_host/mmc0/mmc0:0001/boot_config", "1");

simple_dd("/tmp/u-boot-no-padding.bin", "/dev/block/mmcblk0", 1024);

sysfs_file_write("class/mmc_host/mmc0/mmc0:0001/boot_config", "8");

show_progress(0.1, 5);

then put the "u-boot-no-padding.bin" in the update package and zip it? Should this script be at the beginning of the updater_script or the end?

:confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused:

Please help.

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] santij07:
Will you have Debrick dump for I747M Telus Mexico am I from PR but for not wait i flash it with This I747MUMUEMK3_I747MTCEEMK3_I747MUMUEMK3_HOME.tar an then i apply an update zip and no boot or download mode just unplug battery conect usb cable and led is red, with battery and usb cable Windows 7 detect Qualcomm HS-USB QDLoader 9008. Any Help will be appreciate.:):(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You're in a much worse state; You need to use QPST to interact with a device appearing to Windows as "Qualcomm..." anything. I'd guess that your storage device is in a corrupted state, such as missing the partition table or something equally critical, and so the device is unable to load any firmware to boot from. You might be able to fix it with QPST, or with a proper bootable SD-card...

When I bricked my first S3, it was in the same state. I just took it back to where I bought it and they replaced it. I'm sure that was due to lack of product knowledge though, I got mine from a big-box retailer. I hope you find a way to reprogram it or replace it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] david240894:
Please help me.

I have a sgh-i747 att with 4.1.1 ucdlk3.

I download the bootloader update for this version but when i flash with philzs touch advanced cwm say:

This update is only for d2att and this is my model.

Enviado desde mi SAMSUNG-SGH-I747 mediante Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
The latest Philz is for d2lte, which is all the US carriers combined. I'd say download an older Philz listed under d2att, flash the bootloader, then reinstall the latest Philz for d2lte.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Modem

I747UCUEMJB - Oct 11, 2013 - boot_CWM_I747UCUEMJB.zip - 1.14 MB

This flashable zip appears to just be the Baseband and does not contain a Bootloader? I used Root checker after flashing still LK3. However, baseband is now MJB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I think you flashed the wrong ZIP. A modem is ~15-20MB zipped, while a bootloader is ~1MB. It's impossible for me to have packaged them backwards. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
I must have done something incorrectly. Maybe I will use Odin this time. I see the instructions for it in the OP but didn't see the .tars.

UPDATE: I know you already knew this....I made a mistake. I forgot I downloaded the modem months ago and didn't look at the file close enough when I flashed. I just found the bootloader zip and flashed it. I am now on MJB. Sorry for clogging up the thread with stupid mistakes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Freewaymad:
U-boot.bin (Bootloader) How To Open

Hi,

Is there some way to open the u-boot.bin? Is there some software for this? I need to open my old u-boot.bin (or as it is called on the old rom; uImage_update) It is still the bootloader. Is there a way to get the information off the tablet? Please help.

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Please go to the correct device forum for support. This forum is for Galaxy S3 LTE (phone, not tablet) devices, and there's no "u-boot.bin" file in our bootloaders. Nor is there a reason to try to "open" bootloader files, as they are pure executable code loaded at boot to make the the device load the OS from storage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Freewaymad:
Hey sorry my bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
I747MVLALH1 to I747MVLUEMK5 not allowed...any idea why?

Hi there,

I'm having exactly this issue. Can anyone say why an upgrade from I747MVLALH1 to I747MVLUEMK5 is forbidden/inadvisable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
I'm going out on a limb here and

guessing

it's fine. The reason the script fails is due to assertions it makes to ensure you are: 1. on the proper device, and 2. upgrading from an older bootloader. I see in the script for the I747MVLUEMK5 bootloader, one of the bootloaders it checks for is "I747MLALH1" which is, if you look closely, a single letter off:

I747M

V

LALH1 (yours)

I747MLALH1 (script check)

When I Google "I747MLALH1", only 7 results display, 2 of which are the modem thread. Google even suggests: "Did you mean: I747MVLALH1"

However, I'm not an expert on bootloader nomenclature, so before you go bypassing asserts in the script, we might want to make sure... can anyone confirm that the bootloader name includes the "V" character (I747MVLALH1), or does someone have a bootloader without "V" (I747MLALH1)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bhotel:
Hi,

Thanks for the help!

To answer the question, the output in recovery on my device definitely contains the "V":
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nostodnayr:
Original post. (Or original poster, most commonly.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Sure, installing a custom recovery would've already tripped the counter, but flashing ZIP files from within a recovery will not increase the counter any further.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Technically, you may be right. It won't trip until you reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Guys just one question can I flash this modem file https://www.box.com/s/1seybahcb50fnute5utb vía update.zip renaming the file or vía Odin, this is the original módem for Claro Puerto Rico.

The phone is running with Rootbox nightly 6/18. And the baseband is 1747MUMLL1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That is a recovery-flashable modem, but you should probably check the modem thread in my signature for downloads. The one you've linked to is from Bell (Canada), which may be the same as the one you're looking for, but there's many more choices in the modem thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chuyochosiete:
Silly question I think

I know that this is a silly question but... I have an SGH-I747M (Carrier: Telcel / México), do I need unlocked bootloader to install the update?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
There's no such thing as an "unlocked bootloader" for the I747. The bootloader was never locked on this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jf2011:
Just to make sure I get it right, the "Recovery-flashable update" will not update then modem, just the boot loader? (not sure the note about the modem update applies only to the first link, Jiangyi's one).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
My recovery-flashable update only changes your bootloader. If you're looking to change your modem, I have a separate thread for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It looks like AT&T users that skipped over this in the past will now need to flash the bootloader update to be able to install AT&T's 4.1.2 and related files. Luckily, this shouldn't affect "normal" users that have never flashed their phones.

EDIT: Did 4.1.2 come with a new bootloader for AT&T users as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akitten007:
I think so, seems what other people have said on threads. My question is, if I update to the 4.1.2 bootloaders, could I still flash the same roms, or do they need to be modified/updated?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
With the last bootloader update, the new version could still boot old ROMs just fine. I would imagine this would be the same. I don't have a way to verify that though.

I'll add the new bootloader to the first post when I get a chance. Still at work lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akitten007:
Thanks for responding quickly. I'll probably flash the update through TWRP. So when you install these recovery zips, do you specifically have to flash it as an update.zip? And I assume the zips include the bootloader as well? Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Just flash the recovery-based ZIPs the same way you flash GApps or a ROM. The recovery-based ZIPs do not include modems. (I should probably clarify that in the OP.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Any chance of posting the bootloader from the latest ATT 4.1.2 update? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I wish I could mark posts as "favorite" like on Twitter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Lol.. I know I didn't read the other posts on a 4 page thread.. My bad :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thelakeshow:
Is DLK4 still the latest bootloader for Canadian (Telus) devices?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You're right, and the assert has been fixed. Anyone with issues flashing should re-download I747MVLUEMK5.