yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
Thank you teejster. I followed the instructions using a stable version of CM10 for this phone. On running it from the sdcard, this time instead of getting the status 7 message, it just said Installation aborted.

This was on a pretty recent version of CM10. I haven't tried it on earlier versions.

So, I was cautiously excited about having found the solution, but alas, it hasn't worked for me yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Your assert failure is not due to a bootloader. The assert you are failing looks like the one that checks to make sure you are flashing your ROM on a d2att device. It appears that your device ID is coming up empty so the flash fails because it doesn't think it's safe to flash the ROM on a technically unknown device. This information is stored in CWM or TWRP. Make sure you have the TWRP or CWM built specifically for the d2att device installed. Not any of the other d2 devices like d2can or d2spr.

Be careful doing this with the goo app. It installs what it THINKS it should install based on this same information the ROM is looking for. If yours is currently corrupt you may have problems with this app. I highly recommend using ODIN or follow the instructions on the TWRP or CWM websites.

You can actually download an app called "Root Checker" from the market published by Free Android Tools that will give you information like you device type and bootloader version. Download it and see what it says for your device. If it says anything other than d2att, try redownloading and reflashing your custom recovery and see if it then comes up as d2att.

The assert in the ROM is actually supposed to spit out more information as to why it failed like this.....

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") + "\"."); );

Not sure why it didn't show that error for you. Maybe because it is unable to actually get the device it craps out before it can give the abort message. Anyway, use Root Checker to see what device model it lists. Please note you can say you have a d2att but your phone might not think it's a d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
Thanks, flexfulton. I ran Root Checker and the results include:

Bootloader I747UCDLK3

Device D2ATT

ID IMM76D

MODEL Samsung SGH-I747

I can try redownloading and flashing the custom recovery. If that doesn't work, I does re-flashing the stock ROM and starting over make sense?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
DELETED

Apologies for introducing any confusion.

Thx flexfulton.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
This information is 100% inaccurate. There is an AT&T bootloader with the last 3 letters being LK3 and it is DLK3. There is also a Canadian bootloader that is MLK3. See the difference? Furthermore, the latest update from the Canadian carriers is MK5. First off he has an AT&T version phone and the bootloader he has is absolutely acceptable on pretty much all ROM asserts when checking for bootloaders.

Also if you read the error he showed us above, he is failing the part about the device type, NOT the bootloader check which comes after the device check. If you strip down the script you will see what I am talking about.

Thanks.

---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------

Everything looks good on your end. Maybe just try re-flashing your recovery and re-downloading the ROM you are trying to flash. In some cases it can just be a bad download or an incomplete download that you didn't notice the fail on.

You shouldn't have to go back to stock. Not yet anyone. Like I said above, just try re-downloading everything first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
Thanks to the both of you. I will see about reflashing and redownloading G-d willing as soon as I can steal a few minutes away from other projects and then report back. It is refreshing to be in the virtual company of guys who know this stuff, thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
I just re-flashed the recovery (using Chainfire's links and files). It boots into recovery mode, but when I tried to install 2 different stable versions of CM10, on both I get new errors this time. Here is what I saw:

Finding update package...

Opening update package...

Verifying update package...

E: Failed to verify whole-file signature

E: signature verification failed

Installation aborted.

I should note that I did this without first wiping the cache and the dalvik cache, just in case the install would fail (so I wouldn't have go through the Android welcome screens again if it failed). Would not wiping the cache cause this error?

---------- Post added at 02:53 PM ---------- Previous post was at 02:10 PM ----------

After trying the above, I tried to flash a different recovery (file taken from the same link on XDA). It would not flash (got a FAIL) message.

Now when I reboot, I get:

Firmware upgrade encountered

an issue. Please select

recovery mode in Kies and try again.

I'm not doing anything else without experienced guidance from whoever knows the way out of this...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
Grab this recovery and flash via Odin :

http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar

in recovery do :

1.) Wipe

2.) Advanced Wipe - Choose Dalvik cache, System, Data and Cache

when complete back out to main menu

3.) Choose Install, pick your rom and your GAPPS

4.) Install

5.) Reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
I tried to, but cannot get past the Kies error message. It won't boot into Odin download mode. I also then tried to do the emergency recovery thing in Kies, which downloads the software, but then says it doesn't recognize the phone....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
Can you get into recovery at all ?

Is it possible you installed a recovery for another phone ? If so, I'm not sure what the ramifications would be..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
I cannot get past the Kies message when I boot up. When I attempt to get into recovery, it just goes back to the Kies message.

This happened after I attempted to install one of the recommended recovery files on the XDA thread (http://www.xda-developers.com/android/how-to-root-the-samsung-galaxy-s-iii-xda-developer-tv/). I was careful to use only the one for this phone.

The screen that I see reads:

ODIN MODE

PRODUCT NAME: SGH-I747

CUSTOM BINARY DOWNLOAD: Yes (7 counts)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

QUALCOMM SECUREBOOT: ENABLE

Firmware upgrade encountered

an issue. Please select

recovery mode in Kies and try again.

I did the Kies option after that. It detects the phone, downloads whatever it is supposed to download, and then in what looks like the process of installing the updated Samsung OS (to 4.1.1) it says that it cannot detect the phone.

---------- Post added at 06:49 PM ---------- Previous post was at 06:26 PM ----------

Update: Ta-da! At least I was finally able to get Kies to update the phone to 4.1.1

Now the question is - was I traumatized, or should I start the rooting process over again to install CM 10?

And if I do, I want to make sure I use the best recovery....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the.teejster:
Try ODIN V3.07 from here :

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

That's the one I had success with.. The one in the link you posted is V1.85
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ljdd:
..

I was on 4.3 ucemj2 and I wanted to flash liquids 4.4 KitKat but I couldn't flash it. I did Task's ROM and it wouldn't flash because of the bootloaders. Will this make it where the ROMs will accept the bootloaders? I really want to get off stock and get back to KitKat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moshiachnow:
Thanks to the teejster for the recommendations. The S3 is now doing well on a stock ROM.

My next project is to recover one of our two S2s. I installed Kit Kat on both of them, it had a lot of bugs. I was able to restore one of the back to stock, but the other one is still giving me problems. Are you also familiar with S2s? Should I post it in a different area of the forum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Does the bootloader quoted before come with the updated TZ and whatnot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fire_angel:
:confused: what is the importance of the bootloader???:confused::eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
As far as I know it has instructions for the kernel boot

http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dr1ftz:
I think the OP gave up on this thread. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fire_angel:
Thanks bro...the post it's very interesting....my previous device was a HTC Sensation XE and everything was more easy...but the Samsung devices it's a other world...but I loved....XD:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brayhanrd:
Excelente

i used this treat and it work greatd.. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] raylzq.cn:
May I ask where the download link is?..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arthurema:
Update flashable bootloader request

My device is running bootloader version i747UCALEM. I cannot flash any of the flashable bootloader image files using CWM recovery version 6.0.4.5.

The output that returns is similar for either of the image files

-- Installing: /sdcard/boot_CWM_I747UCALG1.zip

Finding update package ...

Opening update package ...

Installing update...

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

E:Error in /data/media/boot_CWM_I747UCALG1.zip

(Status 7)

Installation aborted.

Is there a reason that this bootloader version cannot be upgraded with this method ?

Thank for your work to repackage these individually. Can you also provide a link for how to modify one of these flashable images for Odin use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I won't assist with Odin repackaging simply because there's already Odin packages all over the internet and flashing pre-4.3 bootloaders on a post-4.3-OTA device will brick it. These packages will not allow you to move backwards in version number/release date to prevent bricks. The only reason anyone should ever update their bootloader is to actually update it; downgrading simply has no purpose, only risk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Actually, it looks like I missed the "A" in "I747UCALEM" when I wrote the list of allowed bootloaders to flash from. Updated ZIPs are on their way.

EDIT: Updated. Please redownload if you had issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Status 6

I have an AT&T i747 running CM 10.2. I just updated both the modem and bootloader from MG2 to MJB. While doing the bootloader I got a Status 6 error, saying that it didn't work. HOWEVER, it apparently did, my baseband says MJB. I did have an odd issue with sound, but it appears to have resolved itself. So I think I'm OK, I just wanted to give you a heads up.

Steps I took:

updated CWM (was only 2 minor revisions behind by hey, why not). Rebooted into recovery, things looked fine.

downloaded both the modem and the bootloader.

rebooted into recovery

installed modem

wiped cache & dalvik

rebooted

sent a few test texts, etc. Things seem to be OK EXCEPT I didn't have any sounds. I went in to settings -> sound and tried to set my ringtone and notification sounds to anything else. No sounds. Odd. Reboot.

Try again, still no sounds. Reboot into recovery

install bootloader

lists file name, etc, gives me a status 6, says didn't work. Reboot

Sound works, bootloader DID install, things seem OK.

hmmmm.....

I know how to check what bootloader I'm running in settings, is there an easy way to verify modem version?

Anyway, it's been a few hours and things seem fine.

just FYI

Thanks for the time you put in, dstruct2k.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
If it said status 6, it didn't flash. Baseband is not bootloader. ("Baseband" is actually your modem.) You need to go to a terminal and type getprop ro.bootloader to get your bootloader version. (Some system info apps also show it.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
OK, it says MG2. Any idea what caused my status 6? Should I just try again? For CWM I'm at 6.0.4.5, which appears to be the latest. (I searched and found a previous reply from you to make sure recovery was up to date.)

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arthurema:
Thank you, these updated archives work as expected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Works great on CWM and Quantom 3.15 flashed MG2 bootloader. Thanks a lot!!! :good:

FYI: didn't work when attempting to flash on Philz touch recovery.... Had to revert back to CWM and worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Any news on i747M?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Plagiocephaly:
MJB bootloader status 6

MG2 flashed fine. I'm still getting status 6 error with MJB using the latest CWM...

CM10.2 seems to run fine on MG2 bootloader+baseband, but it'd be nice to bring everything up to date to 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Same issue with twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DownTheCross:
Having the same problem, tried the latest twrp and the latest cwm. I got to mg2 without issue, but mjb is being difficult.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andy_nu:
status 6 is a improperly edited updater script
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DownTheCross:
Hmm, then It seems that both the mjb zip listed in the OP, and the "update43" file from another thread both have improperly edited updater scripts.

I'll check and see if I can find anything obvious, or maybe just repacking it will work.

Edit: I didnt see anything obvious, but I'm looking a bit more thoroughly now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
The syntax itself is fine. The line ending format is wrong. It was saved as a windows line ending file, but it should be in unix format. (CR/LF for each newline instead of just LF). If you tell CWM to show you the full log, it states line 1, character 50 is where the error happens, which is the very end of line 1.

I wanted to flash that to see if it would fix the random reboots I've been getting in CM-10.2.0, but since the flash doesn't look valid, I don't want to be the first to try it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Redownload MJB, I've fixed the line endings. I had no idea they were wrong, sorry guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Worked for me. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Thanks.. Despite my earlier qualms about being the first to try it, I flashed this this morning, and my phone still boots. :) And it does look like the bootloader is reporting the correct version. We'll see if this resolves my random reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Success! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electrojas:
So what is special about LK3.? Can you tell me the benefit cause that's what this phone had when I got it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's not special, it's just the first bootloader version that was used as a "minimum requirement" for many ROMs. When (if?) we get an official 4.4 update, it'll probably include another newer bootloader that'll probably become the new "minimum".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ktasiwa:
I'm having trouble getting any of the listed bootloaders to install on my phone. I have an i747 with the ClockworkMod recovery partition installed and am trying to flash the bootloader from there. Every time I do it gives me an error 7 and tells me I don't have a correct bootloader installed already. I unzipped the I747UCUEMJB zip and looked at updater-script, and it looks like the assert that checks to make sure the bootloader is correct is looking for the string "I747UCLH9", whereas the reported name of my current bootloader is actually I747UCALH9, with an additional "A" in it. I tried changing the line in the file, rezipping the file and flashing *that* zip, but that didn't work either. I'm at a loss about what to do here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You did exactly the right steps, although where are you getting your bootloader version from? Android does not tell you the current version. ("Baseband" is your modem, not bootloader) My script should be echoing out the current version if it fails though, so if that's where you got the version number from, then you did exactly what needed to be done. A status 7 usually means "failed assert" though, so maybe you didn't edit the line correctly? Some text editors like messing with line formatting (make sure you're using Unix/Linux line endings) or even add invisible characters in the middle of a line.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danny6514:
Hey, I'm just wondering if there are plans to update the i747m links? It has been quite a while... no rush, just wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
... I thought I did them before doing the AT&T ones. Dammit. I'll get those up later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danny6514:
Okay thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] divinestyler:
Hoping for the Canadian bootloader update as well, any luck? Thanks for your great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I've put the latest one back up, it works fine, but I need to fix all the older packages so they don't brick phones. https://www.dropbox.com/sh/a8fvzrow4gwmuqi/O9FMQ6dDZ3/I747M/boot_CWM_I747MVLUEMK5.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] divinestyler:
Awesome, thank you very much sir!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thanks for the i747m bootloader! Works find currently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sonic999:
Hey, dstruct2k! Thanks for this thread, it's very informative! But I have to point out something that is unclear, at least for a Samsung noob like me trying to help out a friend with this phone (I've an HTC One X). Sorry if this's been asked in one of the 32 pages of the thread. :angel:

So, there's different bootloaders for this phone. My friend's version is I747UCALG1, it was running the stock rom and I tried to update it with newer roms, all giving errors, and finally succeeding with a Miui (only to find that it was just in chinese and english - he needs spanish - ). The post tells you to choose the file according to your version... so I see that, and I choose the first link... in fear that the following newer versions listed below could brick my phone or whatever.

I see that basically all the latest roms tell you that before flashing them, you've to first update to UCUEMJB or the other one J2, i think it was. But nobody explains what that is in a line or two, and they just sometimes link to this or other posts.

So basically, my question is, can I flash any of the 4 available files for the current bootloader I have (UCALG1)? But if I wanted to install the latest roms, I would have to install the latest file, which is UCUEMJB, right? I think I only tried the first link but it gave me an error and didn't install, with Philz touch recovery. Probably because I was trying to flash the same bootloader that was already installed.

If these assumptions are correct, it wouldn't hurt to add what I just quoted you, right by the UCUEMJB link, advising to install that one if you want to run the latest roms. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailindawg:
Bootloader Question

I tried updating my stock rooted 4.1.1 with the 4.1.2 OTA update. Things initially seemed to go well until the third reboot. At the lock screen the phone froze and wouldn't open. After flashing the 4.1.2 OTA update, I never factory reset, probably should have. Instead I rebooted to TWRP recovery and restored my 4.1.1 rooted nandroid. I ended up with 4.1.1 with the 4.1.2 bootloader. My phone works,but the camera doesn't. Researching, it's because of the 4.1.2 bootloader.

Is it possible to just flash the DLK3 bootloader at this point time? Or am I much better off to ODIN back to stock 4.1.1 and restart from there?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HodofHod:
Did you also update the ones in your Dropbox? d-h.st is giving me issues with downloading, and Dropbox is giving me issues with flashing (status 6).

Edit: I got d-h.st to work, and I checked the updater scripts in both, and the dropbox one is still using \r\n instead of just \n.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electrojas:
Bootloader

I can tell you what I did as I was all freaked out about this stuff too and after I had a few scares, I realize its not as big of a deal as it seems. Ill try to help you here. What is the exact model of your phone is it the I747, or the I747M? second are you currently on 4.1.1, or 4.1.2? Third, are you rooted and have TWRP/CWM? and lastly if you have TWRP, is it 2.6.3.1? Thats what I have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wickedsun:
Cm11 i747m

Not sure if this is the right thread to post this in, but the latest CM11 nightlies won't take I747MVLUEMK5 (too old?) to install the latest nightlies. I just wanted to know if anyone else had had this issue and what was the workaround?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Have a look at the updater script for the ROM you want to install and make sure the installed bootloader on your phone is supported.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodflood:
baseband version shows "Unknown" after bootloader update

dstruct2k,

I have a Samsung Galaxy S3 ATT version.

Recently, CM 11 nightlies (FEB 08 2014) stopped updating and gave me an error.

I checked the phone's baseband version; it said I747UCDLK3. I had previously updated the modem to I747UCUEMJB, I think.

Anyway, to install CM 11 latest nightly FEB 08, because I was getting "...getprop("ro.bootloader")..." error I decided to update the bootloader.

First, I don't know why but the MD5 on d-h.st does not match your dropbox. ...not sure why?

Anyway, I was able to download boot_CWM_I747UCUEMJB.zip from d-h.st, verify the stated MD5, and did the install. Now, the baseband version shows "Unknown".

Do, I need to reflash the I747UCUEMJB bootloader? reflash I747UCUEMJB modem? I have done a few reboots already?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I would flash the modem. There's no point in flashing the bootloader since the 4.3 bootloader is the most recent version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wickedsun:
Yeah apparently in that nightly it was left out.. Latest now works. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StrangerAtXRoads:
Update bootloader

Updating the boot loader to latest version worked for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
[MENTION=812646]dstruct2k[/MENTION] Can you add a link to the MJ2 bootloader to the OP? Even though it's a leak it works just fine and has the advantage of being the latest that doesn't knox the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnicOrnseeD:
4.4 debrick for i747m?

Is there a debrick.img for 4.4.2 i747m?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I doubt it since all 4.4.2 ROMs are custom. I have never seen a stock TW KK ROM. What phone do you have? I think there is a debrick image for the i747.