yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shutterbc:
That did the trick, thank you! Finally have a working 4.4.2 in fewer steps than I have read in some other threads on this forum. And yes I confirmed I was running the right firmware otherwise using adb. A reflash of the modem was all I needed (not sure why it didn't take the first time).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Glad to hear it! For some reason, for a lot of people the Ota appears to flash fine and then fail after xx%. I had never seen this before until this update, but some would end up with only a partially updated device. Especially since AT&T refuses to release the official firmware, this has probably been the worst update process I've encountered to date! I've even heard of some people having similar problems who have never rooted or anything before!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joehen873:
Hey doc I just flashed this on my i747 and nothing baseband still says mjb and bootloader says the same any ideas??

---------- Post added at 01:01 AM ---------- Previous post was at 12:46 AM ----------

Hey doc I flashed this on my i747 and nothing changed bootloader and baseband both still say mjb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sounds like the flash probably failed. Try again, but when done copy log to SD and attach it here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miten_sheth:
Downloaded ne4 twice and when I tried to flash it.. It says corrupted.. And the flash gets aborted..

Tried from the primary download and the mirror.. Anyone can upload a proper one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
i used this from [MENTION=2972841]enewman17[/MENTION]'s thread

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

(hope that this is o.k. mr. huckleberry. if not PM me and i will delete)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Hi Doc,

Failed for me. Device Info says MJB for both baseband and bootloader. recovery.log is attached. Let me know if you need anything else. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Im going to try to make a new one to test out tonight. I know I sound loke a broken record when I keep saying ill get to it asap, but I will. In regards to what I posted before about things going on here, they have gone downhill, a lot, so I still really appreciate everyones patience. Lately Im rarely at home where I can really work on it is the main thing. Ill do my best to post something to try out tonight though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Take your time, we appreciate your effort.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Well, ive tested using several update-binaries and TWRP 2.8.0.1 and the result has been the same each time. The updater-script is good, and if you manually check the sha1 each of the files does match what is in the script. But when run in recovery it fails the check, which prompts the corruption detected message.

I honestly just dont get it....pretty tired right now though so im stopping for the night. Not giving up though!

If anyone has any ideas about why we are having this problem, I would love to hear them!

Or if anyone knows a way yo verify which of the update-binaries floating around is the latest, that could help too.

We will figure this out! Sorry its been so much trouble though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Hi Doc,

I might have some ideas but I'm on my way out, won't be back until tomorrow, sorry. However, in the mean time, this might help you:

unzip -l cm-11-20140916-SNAPSHOT-M10-d2lte.zip |grep up

279484 2008-02-28 18:33 META-INF/com/google/android/update-binary

22733 2008-02-28 18:33 META-INF/com/google/android/updater-script

it appears that in the cm zip itself is the update-binary that cm is using/shipping. Those 2 things might be a good place to start. ;)

I'm ignoring the date/time stamps, nearly every file in the CM11-M10 build has those dates/times.

thanks again for your time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Well I think ive figired this out thanks to some advice from [MENTION=4788211]Aerowinder[/MENTION] and [MENTION=2972841]enewman17[/MENTION]. Im going to test in just a few min and will let you guys know how it goes! :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Annnnndddd

IT WORKED! I will post the details and get everything in the OP fixed up tonight!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry for the wait. Had things come up.

Here is the I747 NE4 base firmware

https://www.androidfilehost.com/?fid=23681161096069957

And the I747M NE6/NF2/NH2 builds are here:

https://www.androidfilehost.com/user/?w=settings-dev-files&flid=18241

I'll update the OP tonight. Constantly on the go today, but wanted to at least get these posted.

They are currently untested, but should work fine. Just remember, DO NOT FLASH OLDER FIRMWARE!

You can flash the same or newer than what you currently have only!

Will go more into detail about these when I update the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Oh, and the main problem before was the sha1 values needed to be lower case! Thanks to aerowinder and enewman17 for pointing this out to me! Can't believe I didn't even consider that!

Made a few more changes as well. Thanks to enewman17 for helping with some of this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I747 failed, sorry. Log attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I just looked through your script. I don't know the language being used so I don't know what those functions are supposed to do but I noticed you are still including dd in the script and in the zip, but don't appear to be using it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ah crap! I see exactly what I did. Once again...sorry everyone! I will fix this tonight. At least this time I know what I missed!

Thank you for the recovery.log!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Thanks for working on this. I'm going out soon but I'll try tomorrow morning. Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Yeah, I should have deleted it, but it's actually not causing any issues by being there.

Basically, I either need to use the update-binary from the latest ota, or I need to delete the backup and erase fota lines.

Will probably delete those lines from the script. Imo they probably are just extra, unnecessary write operations. It's part of how the official ota works, I guess as a sort of fail safe, but I personally think it's a little flawed to begin with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
OK. Finally fixed and uploading now!

I have tested the I747 NE4 package myself and it works just fine. The I747M versions are based off of that but are untested right now.

Will have them posted shortly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
OP Updated!!!

I know...I know! It's about time, right!?? :rolleyes:

Seriously, everyone, I very much appreciate the patience you guys have given me! Don't think its ever taken me this long to complete something like this! But, I do believe it is done! :cowboy: :victory: :victory:

OP is updated!

Please make sure you re-read the entire OP!

It has changed quite a bit.....and you just might enjoy it! ;)

The I747 NE4 firmware has been tested and found working on TWRP 2.8.0.1. The I747M firmware has not been tested, but is built from the tested NE4 package.

Once again, thanks to Aerowinder and enewman17 for taking the time to help me figure out what was wrong with the initial releases! :highfive: :highfive:

Let me know what you guys think! Hopefully this will not only make updating to the latest builds MUCH easier, but it will also allow you to re-flash the firmware in case of problems down the road!

Doc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I747 worked for me! Great job, thanks again for all of the time that you've put in. Note: shouldn't much matter but TWRP 2.7.1.0.

kc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thank you so much! Which should I get for Bell? NE6 or NH2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhumfleet:
firmware update, which to use

is this the same thing as using the one enewman posted?

http://xdaforums.com/gala...pdate-t2808654
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Just flashed NH2 with TWRP 2.8.0.1. No problems at all. I'm on Bell.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
I747 works in latest TWRP. Thanks, Doc!

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Entirely up to you. NH2 is the latest and probably has some security/stability enhancements, maybe bug fixes. All I know for sure about it is the NF2 and NH2

kernels (which are not included here) had the exploit used by towelroot patched. Beyond that I have no idea what differences they have from NE6.

Link is not complete, but no. It's in the op. There is no prerequisite bootloader/modem.

You can flash these over a mixed setup going back to 4.1.1. All previous firmware requires you be on MJB modem and bootloader. It also means you can re-flash this again in case of problems. The other ones are update only packages. You can't flash those a second time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
mrRobinson just posted a root66 version of NF2 for Rogers if anyone cares to test it out for him. It's the full official firmware, pre-rooted, for flashing in Odin. (I'm guessing de-knoxed as well, but don't know for sure on this latest.)

His thread is here: http://xdaforums.com/showthread.php?t=1739426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhumfleet:
recomendation

I have MJB is there a recommendation of which to use in order to upgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I used to follow dstruck's thread on modem and bootloader. I am new to this thread here. Can someone please explain if this 20 MB package only contains modem or it has bootloader as well?

Flashing on existing cm 4.4.4 should be just fine? Without harming any data? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
They are complete bootloaders and modem. Flashing these do not affect the rom, kernel, cache, dalvik cache, data, or recovery. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Gladly reporting: working fine on I747M :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miten_sheth:
No network after flashing the ne4 firmware.. Sigh.. What do I do now?

Edit : switched the phone off.. Removed sim and tried restarting.. Phone is not switching on.. Not even going to recovery..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
How did you flash? Do you have the I747? Were there any error messages when you flashed?

Did it seem to go through all 6 partitions?

I'm pretty stumped here. Need as much info as you can give, and as detailed as possible. Check the md5 of the file you flashed, does it match the md5 shown on the download page?

What were you running before? (Firmware, modem, rom)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miten_sheth:
I flashed the firmware in twrp 2.8.0.1..

Yes I do have an SGH i747..

There were no error messages at all.. The thing was that the phone even rebooted fine after flashing.. And since there was no network signal.. I thought of removing the sim and retrying.. Just in case.. Then after that when I tried rebooting.. It didn't start.. I tried going into recovery manually.. It didn't go.. The battery was at around 80.. I think when I flashed..

Yes it did seem to go through all 6 partition...

The md5 is matching..

I was on the likewise s5 rom.. Mjb bootloader I think..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
First, I am really sorry about this. I honestly don't understand how it happened is the thing. I took several precautions to hopefully prevent anything like this.

Plug into a computer and open device manager. If it says QHSUSB_DLOAD, it's hard bricked. Hopefully the debris thread in Q&A will fix it though. Go back several pages to find the 4.4.2 debrick.imgs, but try the 4 3 one in the op first.

I'll do my best to help, but I've got to go to a funeral and will be unavailable pretty much all day. There are several others that I'm sure will try to help in the meantime. Sorry again that that happened...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miten_sheth:
Unfortunately for me.. It does say QHSUSB_DLOAD.. :(

I'll try and get it working asap..

Thanks though.. Such things always have certain consequences! No worries! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P-tek:
Bummer man.... BRICKED hard on my S3.

Can't even get to download mode. Oh well.

:crying:

Flashed fine, no errors - MD5 Matched Etc.... Phone booted ONCE and got no data or cellular. I tried to reboot into recovery and this this is now as dead as Elvis.

---------- Post added at 05:51 PM ---------- Previous post was at 05:36 PM ----------

Mine too.... Exactly the same issue here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
I'm also curious as to how the bricks occurred, as the firmware updater script doesn't work if any of the files don't pass an integrity test.

Is there a way to re-partition the MMC by using a .pit inside the script? Reason I ask this is because if for whatever reason the key partitions are somehow corrupt, and the dd command fails silently in the script as a result, wouldn't that be grounds for a hard brick?

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticbill:
Can you provide more detail as to the specific file you flashed, and the specs of your phone... I.E. I747 or I747M - From what Bootloader and Modem combination - anything else? Meanwhile, you may want to look at - This
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P-tek:
It's an At&t I747. I used this file - https://www.androidfilehost.com/?fid=23681161096070186. and I was attempting an upgrade from UCDLK3.

Thanks for the link on the unbrick info. I'm going to try to put together a jig today and see what I can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
[MENTION=4081205]DocHoliday77[/MENTION]

You should remove the assert check for any firmware that wasn't 4.3

In order to update the bootloaders successfully they must be on 4.3 bootloaders. I'm sure it has to do with the new warranty bit.

For those trying to update from old firmware like LK3 witch is 3 updates behind. I suggest those incrementally update till 4.4

I747 LK3 4.1.1 https://www.androidfilehost.com/?fid=23269279319197287

I747 MG2 4.1.2 https://www.androidfilehost.com/?fid=23269279319197288

I747 MJB 4.3 https://www.androidfilehost.com/?fid=23269279319197285
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] highonandroid:
Whats the difference between 4.3 modem/bootloader vs this 4.4.2 modem/bootloader?

Sent from my Samsung SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P-tek:
Ok, so I made a Jig.... Tested it on a couple of older Infuses, the jig works and brings up D/L mode with those.

No such luck on my S3 after this flash. She's seized up pretty hard.

---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------

Probably where I took the wrong turn.... I tried to jump all the way up and should have done it incrementally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Hope isn't lost yet, your jig works but you need to make a debrick sdcard. Here is my 4.4.2 debrick image. https://www.androidfilehost.com/?fid=23501681358549813

I'm not sure if you a need 4.1.1 image or not... I don't have one in anycase. There are guides out there on how to get that image onto a 16 or 32 gig sdcard. I suggest using a 16 gig as the S3's partitons is 16gig.

I know spagman72 @ www.brickedmyphone.com can recover your phone, it was a tricky procedure but he figured out how to use combinations of bootloader to get them to turn back on then he can flash the new firmware. There is no easy way to do this and it requires some special hardware and skill.

If you can get it booted into recovery again flash this. https://www.androidfilehost.com/?fid=23578570567720263
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
not to but in [MENTION=2972841]enewman17[/MENTION]...but this posted by doc might help for 4.1.1 img.(i747)

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

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] P-tek:
Thanks bro... I have two older Infuse phones, one was pretty damaged in the screen, the other stuck in an infinite boot loop due to a power button issue. I've been building my "Franken-Phone" and am pretty much done with pulling the motherboard and such from one, then replacing it all in to the "best" working phone I can get.

I downloaded the Debrick image you provided (THANK YOU) and did a quick search and found some links with info. (video here; https://www.youtube.com/watch?v=8MnikrpUKZw)

I'll let you know how it turns out....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
If you can't debrick with a 16GB mSD, try a larger capacity if possible. I could not for the life of me bring my S3 back from the dead with a brand new 16GB card, so I used my 64GB storage card and it worked the first time.

Just don't give up. You may have to try multiple times with a few different combinations to get that guy to boot.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
same **** here...hard brick! why did i even try?

luckily i have three S3's...but this is the main one i use and need to get stuff from the internal mem...figures..

this is an I747M...used the Rogers/Fido file..booted fine after a good looking flash..no data no imei, etc etc..go to reboot to recovery and toast!..

I've flashed hundreds of times and on several phones...my first real brick!

I see the debricking link...will this actually work without a JIG device? In the post it mentions the debrick image on the SD card...if the phone is HARD bricked like everyone is stating here....does simply having this certain image on an sdcard then somehow allow dl mode to work again?? If still have to press Vol dwn, home and pwr...when phone doesn't respond...this method will somehow get that to work..is this correct?

Anyways..will be a learning experience..first brick..would love to fix it somehow myself...but will get a jig if i have to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
I have brought a phone back from the dead from flashing a 4.1.1 image over a 4.3 using the same method posted by [MENTION=2972841]enewman17[/MENTION]. With a little bit of work you will be up and running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
So using the debrick image from Enewman17 on the previous page is what you are talking about? he refers to "so your jig is working"...does that mean i have to have a jig device to use this sdcard debrick image? can you point me to the exact method you used....

i am using the win32image program to image my 32 gb card...does it have to be 16? have tried Mr.X's debrick image and now Enewman17's as well.... and does having the debrick image on the card actually allow the download mode button combo to actually work or do i have to have a jig device to use it?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
is it the modem(s) that cause the brick?

So..i wasn't going *backwards* in the bootloader process... had the 4.3 bootloader on here for past year so that i was able to flash all the JB and KK roms... was flashing and testing new 4.4.4 cm roms after having been on one 4.4.4 AOKP for a long time..i had some of the latest modems though.. tried several to find the best signal/data etc.. for Rogers Canadian variant.. there are:

Telus, Rogers, Bell, Fido, Koodo, Sasktel, MTS, and other M devices.

I747M

I747MVLLE8: modem_CWM_I747MVLLE8.zip - 19.42 MB - May 8th, 2012 (original shipped)

I747MLALH1: modem_CWM_I747MLALH1.zip - 19.62 MB - August 1st, 2012

I747MVLLH1: modem_CWM_I747MVLLH1.zip - 19.46 MB - August 1st, 2012

I747MUMALJ1: modem_CWM_I747MUMALJ1.zip - 19.48 MB - October 1st, 2012

I747MUMBLK3: modem_CWM_I747MUMBLK3.zip - 18.97 MB - November 3rd, 2012

I747MVLDLK4: modem_CWM_I747MVLDLK4.zip - 18.92 MB - November 4th, 2012

I747MUMBLL1: modem_CWM_I747MUMBLL1.zip - 18.97 MB - December 1st, 2012

I747MVLDMF1: modem_CWM_I747MVLDMF1.zip - 18.99 MB - June 1st, 2013

I747MVLUEMK5: modem_CWM_I747MVLUEMK5.zip - 19.17 MB - November 5th, 2013

I747MVLUEND2: modem_CWM_I747MVLUEND2.zip - 18.79 MB - April 2nd, 2014

I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014

I had been using EMK5 for a long time but had swithched to END2 and END3 in the past few months.. i was on one of those last two before the firmware flash...

so yes.. device managers has the QHUSB_DLOAD label...the phone only shows a red led when no battery is in it and connected to pc and no light when battery in.. no luck (so far) with any of the debricking images on sd card...

*** Do you HAVE to use a 16GB card for that method? i have only used 32/64 so far... and does the file system matter up front? the 32 can be fat32/ext2 etc..and the 64 was just ex2 i believe..

Is a JTAG device needed here?

or is this one of those scenarios where it is permanently bricked for good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Oh man....I'm really sorry guys! I absolutely did not see this one coming.

I don't know if enewman17's explanation a few posts back is completely correct or not. It does seem to make sense that it might have something to do with the warranty bit, but the thing is, I have an I747 now, and I flashed the NE4 file that's in the OP, updating from 4.1.1 straight to 4.4.2. Plus, other carriers, including I747M ones, have released full firmware that people have used to flash from 4.1.1/4.1.2 straight to 4.4.2 without problems. So I'm still confused as to what the actual cause is...

I'm going to take the links down in a few min to rework the scripts. I'll have them back up sometime tomorrow. I may keep them down longer to try and investigate....

Did anyone update from 4.3 using this that also bricked?

Again, I am so sorry about this! If I had any clue that it could happen I wouldn't have posted them!

I'll post a link to the debrick thread in Q&A in a few. But search the Q&A section too. tons of people started new threads every time there was a brick, so there's lots of info and links that are out there, but some can be difficult to find...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ok, here is the debrick thread so you guys don't have to go looking for it.

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

Links removed from OP.