yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduaponce:
Hello everybody,

I have bricked my device once (SGH-I747 AT&T) by flashing wrong bootloader to my phone (It's a very noobish mistake, I know) and I had to pay someone to unbrick it by using a J-Tag but this person told me he was "unable to install SGH-i747 bootloaders" and now I'm unable to use LTE because I have a Non-LTE bootloader and modem. I've tried flashing T999L modems but no SIM card/IMEI recognized so I had to go back to T999 modem. The questions are:

Can I Odin flash SGH-I747 bootloader I747UCUEMJ2 without bricking my phone?

My phone is unlocked to use with any operator, will it remain unlocked after this?

My IMEI will be ok after this?

My phone information is:

Baseband: T999UVUEMJC

Bootloader: T999UVUEMJC

Android Version: Lineage 7.0.1

RIL Version: 3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loosemoose613:
Does anyone have copies of these bootloader zips that they could upload on a different hosting site like androidfilehost.com? Apparently d-h.st has been self-destructing lately, and besides the fact that the site is full of ads and malware, the downloads seem to always time out.

I PM'd the OP, but based on his past posts it doesn't look like he's following these threads any longer.

These files are exactly what I need since I've got a mismatched bootloader and modem. (specifically I need boot_CWM_I747UCDMG2.zip and boot_CWM_I747UCUEMJB.zip)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chuckles5150:
Have a look here from enewman17.

https://xdaforums.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loosemoose613:
Thanks, but I've read through that thread a few times and as far as I can tell, all of those zips are a combination of both bootloader+modem together. I need just the bootloaders alone, in order to get my versions in sync. My bootloader is LK3 and modem is MJB, therefore I believe I should flash the MG2 bootloader and then the MJB bootloader, before I can start flashing enewman17's combo files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chuckles5150:
What firmware do you want to end up or be on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loosemoose613:
Ideally NJ2 to be on the latest, but I've read there might be a chance NE4 may work. I'd like to install some Nougat ROMs (RR, Lineage, OctOS), but even if I wanted to go to LP I need to update the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chuckles5150:
If a complete ODIN Firmware flash is acceptable, Data wiped, I have complete MJB and NE4 Firmware plus stock recovery flashable NJ1 and NJ2 Updates. I can post my Google Drive Links if interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loosemoose613:
Thanks for the offer. I'll let you know if it comes to that. For now I'll keep checking d-h.st to see if their downloads start working again, or take a risk and just flash the MJB bootloader/modem combo and hope it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nader2020:
the link that you provided for downloading doesn't work anyone has any other links?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThePublisher:
Yes please! Trying to get my S3 back to stock for this Samsung Trade in thing and it isn't happy with me going from ResRemix to NJ2 flashing via TWRP. I'm having trouble finding any links to odin flashable files that aren't dead links.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chuckles5150:
Sure thing...

https://xdaforums.com/showpost.php?p=67903970&postcount=3

NJ1 and NJ2 updates...

https://drive.google.com/drive/u/0/mobile/folders/0B0lfMZeSyJnYRExraEVoVVBNSkU
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AjvarXX:
I know it's old topic for very old phone but I think first post must contain info about MJ2 bootloader which provides both advantages of MJB one (support new ROMs) and KNOX-free bootloaders (unlocked).

enewman17 provided this combo: d2att_I747_MJ2-bootloader_MJB-modem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
All bootloaders for the sgh-i747 and sgh-i747m are unlocked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It is. I doubt we'll get another new one unless by some magic we get another update... Pretty sure adding multi-window was the last big update for the S3. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Recovery-flashable I747U

DMG2

bootloader added to OP! Or, download here: boot_CWM_I747UCDMG2.zip - 1.13 MB

If you have issues booting after installing, update your modem to match (link in my sig) or you can always reinstall the previous one, DLK3.

I'll work on getting the original stock bootloaders added soon, just for the sake of completeness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Just wanted to say thanks to OP, this worked perfectly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Yep, sure did
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Thanks, figured that out. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I realized that after I posted :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sneedish:
Total noob question here. I've installed the milestone release of the PACman rom. TWRP recovery installed as well. I'm sure I'll need to update the bootloader and modem for future updates. Will I just be able to flash this new bootloader and the corresponding modem in TWRP or do I need to restore to stock? I haven't been able to find an answer in the forums. Be gentle....:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The whole reason for creating these 2 threads is so people don't have to revert to stock and install official updates. Just flash the ZIP containing the version you want and clear cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sneedish:
Followed the OP and everything worked! Thanks again for your help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Worked perfectly for me. Thanks!

For the record, I have an AT&T device running latest TWRP. About a month ago upgraded I to DLK3, and now DMG2. Both updates applied without incident.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Good to hear, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
Same here!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iCyanideS3:
help

I'm currently on a TW rom that has the baseband i747UCLG1 can I update to the newest baseband by just simply flashing the newest file or do I need to update to DLK3 then to DMG2 ? thanks !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Just install the newest modem from the modem thread. Baseband = modem. This thread is for bootloaders. (You can install the newest bootloader too if you want. Neither of them require that you install anything older first, just flash the newest.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
this boot loader breaks camera in stock Android 4.1.2 .. you get camera failed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's much more likely that you flashed a custom kernel that broke the camera, as most parts of the camera drivers are in the kernel, with some in /system. Flashing a bootloader doesn't touch either of those partitions. Also, these bootloaders come from stock ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
nope I have a masters in comp sci and I know what I flash.. flashed this...

and camera failed... flash back to thus and camera OK

most likely 4.1.1 camera not compatible with something in 4.1.2 boot loader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You, sir, are posting in the wrong thread. You flashed modems, not bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
nope took wrong sceen shot fixed now flashed boot loader then flashed back and camera works again..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Well, the whole reason there was new bootloaders was to support the 4.1.2 OTAs... They may rely on some feature in the new ROM version that's only in the new bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
if u really need proof I will show you camera failed message and current boot loader version with rootchecker

..

sorry tried but cannot take screen shot with camera failed message...doesn't work.. best I can do is camera fails with .

and OK with
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Thanks for this! Worked flawlessly on my Canadian s3 :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Please, just update your ROM. You're essentially attempting the same thing as replacing the Windows 7 bootloader with the XP one and expecting Windows 7 to boot... It ain't gonna happen. You do not need to update your bootloader if you're on an old ROM and never plan on updating it.

I also don't think you realize that I can't do anything about your issue. I don't make the bootloaders, I just repackage them once they're released by Samsung. If you'd like to ask Samsung to fix a new bootloader's compatibility with older versions of Android, be my guest, but I doubt you'll get very far.

Perhaps you'd be better off returning to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
don't need to update .only thing really new was multi window and don't care about that on my phone.. also spent great deal of time customizing the status bar..

didn't expect you to fix issue.. just wanted to make others aware that if their camera is not working this may be the cause.. know its not your issue. just strange that boot loader affects camera.. would think that once phone is booted it has no further affect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
If you're not interested in updating your ROM for security fixes and feature updates, why on Earth would you want to update your bootloader? I still fail to understand why you flashed it in the first place. Again, I strongly suggest that you update your ROM. There's a (multitude of) reason(s) that the carriers pushed these OTAs out, and staying on an old ROM is just asking for trouble.

Malware authors tend to read a lot of changelogs to see what holes have been plugged, and then go after devices that haven't yet been updated. I notice you've added Google Wallet to your ROM, so I would think that you'd be more interested in device security considering your credit/bank card is tied to your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
My camera works fine. And I updated the bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Many (all?) are having issues running a 4.1.1 ROM after the 4.1.2 update unless they are using a custom kernel.

I also experienced the camera issue. I have no explanation ATM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Ohhh, with the 4.1.1/older. I misunderstood again. Sorry. Again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamescable:
OK, so I updated my boot loader and am on PA 4.3.. I want to go back to 4.2.2 but every time I try to install a ROM it says failed to get.prop lk3!!!! Can I flash the lk3 boot loader over the new one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Of course you can. Although I'd suggest you just tell the ROM dev about this and have them add the new bootloader version to the assert function in their flashing script. (They should know what this means if you don't.) This would also cause issues with people moving from the stock OTA ROM to that custom one, because they'll all have the latest bootloader already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamescable:
Are you sure? It won't brick my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm 100% sure it works fine. Some ROMs won't boot up if the bootloader is too old (they depend on functions that were added in later BLs) but that is the absolute worst that can happen. And then you can just go back to recovery and flash another one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnnyutah22:
I'm on S3Rx rom, what is the benefit of updating my bootloader? I'd like to flash the latest modem released July 2, and I don't know if that's related to updating, but beyond that I don't know the benefits of updating. Are there any performance increases or other things to be gained?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The bootloader is simply the code responsible for booting up whatever version of Android is on your device. The DLK3/DLK4 updates were to support Android 4.2, and I've also been able to boot 4.3 just fine using those. Updating your bootloader won't ever affect performance, battery life, or anything else. The code is only run during boot-up. It's much like GRUB or the Windows bootloader.

If you're having issues with ROMs that won't boot, updating your bootloader might be the solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcm.hdl:
Little noob

Hi friends a little noobster here, maybe is a stupid cuestion.. Be gentle, hahahahaha... I have a huge cuestion!!! I updated my i747 (at&t) to 4.1.2 and I have this bootloader: I747UCDMG2 (I think is the newest one) But I can't install cm 10.1.2, when I try at the end of the process appears me an error with the bootloader..

Please help me!!! What can I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Downgrade your bootloader to the 4.1.1 version to install aosp ROMS, until cm and the other aosp folks change their updater script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcm.hdl:
Sorry for say this...But I don't know how to do that...hahaha...Could you give me a little tuto step by step? This is my first android...

Thanks :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Look at the first post of this thread. It will walk you through it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] john.s.kim79:
I can't seem to get to the .zip file, even after downloading the different file managers from the ads. Is there anywhere else I can get the boot_CWM_I747UCDMG2.zip?

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Over 700 downloads worked fine for other people. I don't know what "file managers" and "ads" you're referring to, there's a simple grey "DOWNLOAD" button on d-h.st, and then you just need to copy that downloaded file to your device.

Also, please refrain from quoting the entire OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
I have a unlocked gs3 that I bought from rogers and an currently with Telus.

It's an i747m but I guess I changed it to an i747 (it had been working fine like this for quite a while).

I've tried flashing cm 4.3 but I get an error I also don't seem to get as good coverage as other people on tellus (they are running apple and blackberry).

Should I just flash the i747m bootloader?

Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jumpinjupiter:
I got my ota the other day and am now running 747ucdmg2 rootloader and aosp Roms will not install. I downloaded the previous booloader from here and then tried to install the ROM again and I receive the same error about improper boot loader. Am I doing something wrong or mis understanding something
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You need to reboot after installing a new bootloader; The old one is still in memory until after a reboot. I should add that to the OP.

You didn't "change it to an i747", that's just what your build.prop says the device is. Mine currently says Galaxy Nexus in there. What you need to pay attention to is your baseband version, which says "I747M..." and you cannot flash I747U-specific things. (Modem/bootloader)

What error are you getting when flashing 4.3?

Also, you can't compare coverage between unrelated devices, even 2 similar Android devices can get completely different reception in the same area. It all depends on the physical antenna design and the modem firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
You should never flash a bootloader intended for another device, even if they are as similar as the I747 and I747M. Doing so will exponentially increase your chance of making a paperweight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FlyinHi:
My bootloader is I747UCDMG2. I am still getting an error when flashing cm 10.1, do you have any idea why? I am running 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
I believe they do not accept the new bootloader yet. You will probably need to downgrade to DLK3. Don't forget you must reboot (just back to recovery is fine) after flashing a bootloader for the changes to take effect, and recovery to see the change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] st3n0:
okay...

so i did this and now my phone won't start anymore.

i think i just DESTROYED the bootloader

what do i do now?

where do i get the original bootloader from?

i have a HTC one S (ville)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
This is for the Samsung Galaxy S III, not the HTC One S. Fortunately, I have personally messed with an HTC One S. Send me a PM and I can try to help you. My initial suggestion is start here: [TOOL] HTC One S All-In-One Toolkit v4.0 [7-10-2013] [PERM ROOT][Noob-Proof]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
What made you try to flash this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
In the HTC One S world, there are S3s and S4s. He may have been mistaken by the GS3 vs One S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Alright, fair enough...

I could code in a model-detection to each package, to prevent bad flashes in the future... Although then the packages would fail to flash even on the correct device if it was running an unrecognized bootloader version (from OTAs that I haven't seen yet, etc) so it's probably best to leave them as they are...

Thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] st3n0:
i don't think you have to change anything as the only cause this fault happend was my stupidity^^

seriously...i wasn't paying attention so i don't think you have to
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
I take it you just flash it with ODIN right? Any adverse side effects from downgrading?

Since the new bootmanager doesnt even install a new modem I assume flashing the ODIN one would just reflash the one already on the phone from the 4.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
I personally choose to do separate flashes so I can up/downgrade my bootloader and modem as needed. I have not noticed any side effects from downgrading (I did to try out PA), nor from re-upgrading (went back to Slim).

I would assume that the modems in the ODIN files are the latest modems, yes, from 4.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The Odin packages (not my work, btw) also include the "matching" modem versions. You do not need to have "matching" versions, You can mix-and-match to try to get the best possible results. There may be incompatibilities with certain combinations, but all you'd need to do in that case is flash a different modem/bootloader. I haven't had time to test every possible combination, so if someone finds one that just won't boot, please let me know here or in the modem thread.

"Matching" versions will always work together, as that's how they were packaged by the carriers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
Oh ok I gotcha, so neither method is really more efficient than the other. Ill probably just use the CWM/TWRP flash-able ones from now on since its a hassle to use ODIN on Mac. :D

While I am here... Say I am wanting to update to the newest bootloader AND modem. Which would I flash first, or does it really matter? *talking about DMG2*

Also do you recommend clearing the cache and dalvik cache after flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Order of flashing doesn't matter, especially if it's all done in one session in recovery. And yeah, just like with pretty much everything else that gets flashed, a dalvik cache is suggested. A full cache wipe is never a bad thing either, no matter when you're doing it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayemprady:
I already have the Bootloader mentioned in your first post but still unable to flash CM10.

I get the error 'Installation Aborted'

http://xdaforums.com/showthread.php?t=2421266
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
As you can see, from your error that you posted, CM 10.2 only accepts up to DLK3 for I747. If you have updated your phone to MG2 for the bootloader (which I'm assuming you did since you're having issues, as well as your baseband has been updated), then CM 10.2 will fail. You would need to downgrade to DLK3 for the I747.

To do so, simply download the recovery-flashable DLK3 zip in the OP. Don't forget: FOR RECOVERY TO RECOGNIZE A NEWLY FLASHED BOOTLOADER, A REBOOT IS NECESSARY BEFORE PROCEEDING WITH FLASHING ROMS REQUIRING CERTAIN BOOTLOADERS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
Is I747MVLDLK4 the latest bootloader? because I had I747MVLDLK4 boot loader when I got the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
For the I747M, yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] k29er:
? not mf1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
Correct me if I'm wrong y'all, but MF1 is the latest software for the I747M, whereas DLK4 is the latest bootloader. When an update is pushed from a carrier for your phone, it does not always entail a new bootloader and/or modem. So, when they pushed DLK4, they pushed an Android OS update as well as a bootloader update. However, when they pushed MF1, Android was updated, but not the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Correct on all counts. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
That strange because I flashed the Stock TW 4.1.2 Telus from http://xdaforums.com/showthread.php?t=2363882 and when I check my bootlooder with Root Checker is indicated I747MVLDMF1, it was DLK4 before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm looking into this and I'll let you know in a bit. Having some unrelated device issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vanisleryan:
Same here bootloader is mf1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Alright, boot_CWM_I747MVLDMF1.zip - 1.13 MB has been added to the OP. Sorry for the delay on this one guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Is there any extra benefit to flashing the new bootloader if one is to flash a rom like pac? I'm sitting fine it seems without. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
No, as a matter of fact, I'm fairly certain that the new PAC (at least the stable, perhaps not the nightly) will only accept the DLK3 when flashing, meaning they are unsure of how it would react to MG2. Will it make a difference, however? Probably not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm thinking that there's other hardware init code in the bootloader, like for the camera, because I remember there being issues with DLK3 on AOSP ROMs when it first came out. I don't know if the newer one will cause similar issues, but it's up to each ROM dev to accept specific bootloader versions in their install scripts. I strongly advise against bypassing those restrictions, because if you run into problems you'll get no support from either myself or the ROM dev.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonathanh221999:
As far as I know, the latest update also included the latest bootloader available at that time. I've the same as you with my Rogers SGH-I747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
This has already been discussed and the bootloader version in question is already available in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deathsting_50cal:
So this should help me with my boot logo freeze (soft brick) with any 4.3 roms that i try?