yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
yes...this was coming from 4.3 bootloader... from what i'm reading...i think it is the MODEM that is causing the brick.. and a PERMANENT one from the looks of it..can't tell for sure though..and waiting to hear back....

as stated..i have been on 4.3 bootloader for a long time..so this was NOT a downgrade... was on 4.4.4 rom but had some of the latest modems (in this case..for Rogers Canadian variant...the latest two recently of END2/3...the two AFTER MK5 modem)

flashed and just like everyone else.. went through fine..reboot (ONCE) into rom and it then showed IMEI,etc of unknown.. reboot again to go to recovery and ...BRICK... nothing.. QHUSB_DLOAD in device manaager..red led on phone when connected to pc with no battery.. tried several debrick images via sd card but to no avail...

so would just like to know if this is a permanent brick or a fixable one?

***EDIT***

actually...after reading the link you just added again.. It appears i'm (we?) are in the FIRST SCENARIO he posted...which is likely PERMANENT...

theramsey3 states:

thus far this method will not work for any of your 4.4.2 ota bricks if you flashed the 4.4.2 modem on the mjb bootloader, the only way to fix those bricks is with a new emmc, motherboard or a new phone. Jtag won't save you this time the phone is now a glorious paperweight.

****

so that would be this...correct? this 4.4.2 firmware update DOES ALSO install the 4.4.2 MODEM in the flash package...as you show.. the mjb bootloader is the 4.3 one i believe...

but technically i or we were not just installing the 4.4.2 modem to the older 4.3 bootloader.. it was updating the bootloader to 4.4.2 along with new modem...so ...i'm confused...if anyone can clarify and tell if i'm in this scenario or not would be great!

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ok, so you were on official 4.3 firmware already and it still happened. I updated from 4.1.1 using the NE4 package posted in the OP. So I can't really see how it would have anything to do with not having a Warranty Bit or knox related bootloader.

You do not have to use a 16GB card, It has to be at least 16GB (32GB if you have a 32gb S3). But I have seen plenty of times where certain sdcards simply just don't work. No rhyme or reason to it either. I've seen lots of 16GB class 10 cards fail and then a 32gb class 4 work, and vice versa too!

I have also seen many times (and experienced it too) where the first several attempts did not work. But after trying again and again, it finally did. And yes, when it finally did work, it was on an sdcard that had previously failed several times. Again, no rhyme or reason to it, but it does happen, so don't give up if it doesn't work on the first few tries. Be vigilant.

But if you simply cannot get the sdcard method to work, the only other option is a jtag service. Someone recently posted about one they had a good experience with that only cost $25. I have not been able to find it again though. Pretty sure it was close to 3 weeks ago in the Q&A section.

I will keep you guys posted of any information I find and will do my best to answer you as quickly as I can if you have any questions. In the meantime, if you think of anything that may have been unique about your device, please let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
God I hope and pray its not permanent! The only permanent brick I have ever seen on the S3 happened when flashing only a 4.4.2 modem on 4.3 bootloaders.

As for your setup, you had a mixed build, all 4.3 but with newer modem. Has this been the case for anyone else?

There may be hope by the way. As I said, the permanent bricks happened only when flashing a 4.4.2 modem on 4.3 firmware. (It did not brick when flashing the 4.4.2 modem on 4.1.2 and 4.1.1 firmware). And I can see no way that the firmware you flashed could have left you with a 4.4.2 modem on 4.3 firmware. (The modem flashes last, after everything else.) So, I think it would be too early to say its a permanent brick. But it does sound like it might have something to do with the modem....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halojinx:
For me my S3 was on 4.1, I flashed 4.3 due to prerequisites for a few Roms I wanted to use. But after flashing 4.3 I just flashed 4.4 over and expecting to run fine. Phone did bricked, screen did not turn on, red led when charged, and computer beeped when connected but was not found by Odin until I loaded debrick image and booted into download. From there I flashed your NE4 base and stock dump by enewman17 and was able to return phone back to working conditions. Maybe I got lucky but that was what worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
cool..another success story.. some seem to be able to do the debrick method fine..i havent had luck yet..but the op for the debrick says this is a scenario that should be recoverable.. with either debrick or jtag (hope i dont need to do that)...as long as we didn't flash only a 4.4.3 modem on the 4.3 bootloader...this is flashing the whole package...so *should* be ok.. are you AT&T or 747M? all the successful debricks i've seen are *non* 747m's... i have been trying the 747m debrick file but to no avail..

the only variable i can think of atm is that i have been using a 32 and 64gb sdcard....which should work..but everyone else says they used a 16gb..even though 16+ should in theory do fine..

anyone know if that debrick-SGH-I747M-UEMK5.img file is the only one file i can try to debrick with for the 747m?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
You have to use a debrick image that is meant for the firmware that's loaded onto the device. But in this case it's not too certain what has or what hasn't been installed.

I would say try 4.4 first. And if you absolutely can't get it to boot, then try the image for your original firmware.

Someone correct me if I'm wrong.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
any other links for 747m debrick images

Hey Doc..or anyone that may be able to help..

are there any other links for debrick images that you know of?

Mr.X is the only one I can find that is for 747m but is 4.3... i'm thinking because of this flash that updated to 4.4.2...i need a 747M version of the 4.4.2 debrick and can only find 747 versions...

i'm likely going to a friend in the electronics business who has a JTAG soon (if no other option) but want to try everything i can first...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry I haven't been on much these last couple of days. It's just been a very rough time for my family and have been finding myself out where there is little to no signal a lot more than usual...

This is great news that it appears these bricks are indeed recoverable with our debrick method though! I am planning to be home later tonight and will try to find some of the available images you all can try. Will put them all together to make em easier to find.

If anyone does need it though, here is the post I referred to before that mentioned a good $25 jtag service.

http://xdaforums.com/showthread.php?p=55382796

Huge thanks to [MENTION=5511100]mrrocketdog[/MENTION] for taking the time to hunt it down for us!

I will be on as often as I can to help get things fixed up. Just know that I am not ignoring or avoiding the problem at hand. Believe me, I do not feel good about the bricks that happened and I will do everything I can to help you guys out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Oh and I'd suggest trying the 4.3 images first if possible. Probably doesn't matter which you try first, but in case trying the 4.4.2 one does something that would otherwise prevent the 4.3 image from working, I would start with the earlier one until we know more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
I flash this firmware with no problem only my problem is I cant flash 4.4.2 rom because recovery give me status 7 data permission error problem or something like that I only flash cm11 or other aosp rom but not stock 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That's a rom Issue with its updater script. Doesn't have anything to do with how you flashed the firmware, just that you did. Cm never updates their scripts to allow flashing when newer firmware is released. You'll have to edit that yourself or use a newer version that does have an up to date script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
'SENT FROM MY SGHI747' ? what the.....

just kiddin doc. lmao.

thanks for working so hard for us. you take care of family and doc first.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
Nevermind, resolved my issue. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
update on my new brick..

well been few days now..i ended up having to go the JTAG route..i know someone who has one that I was able to use then subsequently get him and another expert to jump in and give it a try..

firstly..i DID flash the correct 747m Rogers file..that was confirmed..i (we) have no way of knowing if there is something with that file that is an issue..but no matter..

none of the debrick options worked...but i think because i didn't find the correct image.

as for the JTAG'ing... I was able to get a bootloader reset in no time..so that part was easy! phone would boot to recovery/dl mode and os no prob.. but when in OS, obviously the main issue of unknown baseband, imei, wifi, etc etc was still there.. so we all expected to just flash the proper STOCK FULL FIRMWARE and be done with it.. at this point..i took the phone home to do myself cuz i wanted to take some stuff off the internal memory and I could Odin it back myself..

Got the full official 4.4.2 firmware from Samsung..and flashed..went through beautifully with no probs..but at the "auto reset" part of the phone... brick!....again!? lol did i do something wrong i thought...friend thought so too...

took phone back..buddy hooked it back to JTAG and redid bootloader..no prob again..and then he tries...same thing.. brick again!i leave it with him..he then gets a veteran JTAG'r to help out...

ultimately, they have tried re-imaging several different full images...and individual low level images, etc etc...to no avail.. it's a scenario they haven't exactly seen like this before..

So, the last ditch effort now is to do a FULL REPAIR/REPARTITION bit by bit on the whole damn thing...and hope for the best... that process take a while! dunno if you remember the old days with hard drives and the "low level format" they had..would have to leave it for 12-48 hrs to complete..something like that.. but also putting the whole drive tables back in (new) place..and then reflash again..who knows..

if not...luckily i can get another board (for $50/$60) and do that.. but a learning experience thus far.. will update again to inform how the last step went
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Wow! That's insane! I don't know what they did in 4.4.2 to cause that type of stuff, but they should at the very least provide some sort of warning! I do like kk plenty, but the hidden risks involved are rediculous if you ask me!

Thanks for the update! Keep us posted!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
pchemerys... That is definitely crazy... I am definitely curious to know how that turns out, please let us know what happens...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
perm brick...so new board it is...

well. all JTAG'n options and tricks have been exhausted by two long time JTAG'ers that say that haven't seen a brick quite like this one.. Did go ahead with the "repair n repartition" last resort and then tried several full stock 128/256/512mb firmware images and nothing would work. Bootloader fix..no problem but brick on all flashes even after resetting the whole emmc and board.. The worst part is not knowing exactly why this happened. Correct 4.4.2 firmware file and it was going "forward" not backward in any way...so we were all clueless as to why.

But did get a new board..as stated..i have (had) a few S3's..one that i gave to nephew got wrecked a bit..cracked screen and bent..but board was ok.. so i thought..installed no prob but camera had issues (i think just needed a resodder. Buddy took it off my hands though and i got a good replacement board for $20.

So it's in now and working.. FULL STOCK 4.3 bootloader/system was initially loaded.. I have since put in new recovery/rom/kernel, etc.. likely to do the firmware to 4.4.2 ..but that will be the FULL STOCK OFFICIAL Samsung 4.4.2, lol.. and then i can reroot and change everything again..

So that's that! Been doing this for few years now and flashed hundreds of times on dozens of phones...and got my first full official HARD BRICK! Ah well..lesson learned.. Got good at JTAG'ing! Learned a lot..actually fixed a few others phones at the same time..and even had one successful debrick via sdcard..but was due to different cause..

Would love to know how and why this happened for the future but doubt i ever will

One obvious recommendation..from the JTAG'ers was (only for when doing FIRMWARE) is to always do the FULL OFFICIAL upgrade and then do whatever is needed afterwards to get back to other roms, kernels, etc.. This was a "parsed" firmware done via a flash file..and well..not the most recommended way to do so..

Still think has something to do with the previous bootloader/modem that was pre-existing when this 4.4.2 went on.. (and still think there was *maybe just maybe* a chance to save it after the first brick and the initial bootloader fix but will never know). Like I said..learning experience!

take care and if any thoughts on what might have happened or more questions..fire away..as well would like to know what happened with a few other of the bricks that happened in here..i know some were fixed (good) but some others have not been or not heard back from.. especially the 747m's.. but nonetheless it does appear that there were far too many bricks causes in the first place..period.. even for the US phones that were eventually fixed... not saying it's anyone's fault ..just an observation that something was inherently wrong with this firmware upgrade method..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
No worries..sh*t happens

I do hope some of the others were able to fix or unbrick their devices without going the board route.

I probably (on this phone anways) will likely just leave all the 4.3 firmware on their and not even bother doing the full 4.4.2 anyways.. maybe when 5 comes out...who knows.. the 4.4.4 kk roms are working ok (if you find the correct one)...many are still having some known hardware issues to work out..but i'm good for now..

As said before..this was a learning experience and it appears that yes..4.4.2 is problematic.. actually everything went a little wonky once Knox came in and after the 4.3 MJB firmware/perm e-fuse took hold..

is there really any (good) reason to change and update to 4.4.2 firmware (from 4.3) to update the modem/bootloader, etc.. ? if using custom roms/kernels, etc..

actually on most carriers (if you are stock) i'd still recommend NOT updating past 4.3 until 4.4.3 or later is released as 4.4.1 and 4.4.2 are HORRIBLE with major lag and battery issues..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I've been considering acting along this same line of thought. That is, contemplating upgrading to the MJ2/MJB firmware/modem combo and then going with the custom roms which will work with this configuration. Maybe something like TMS3KK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RiTZiE_CDN:
Hey Everyone, just hoping for a simple answer here and haven't been able to find it through searches.

Is it ok to flash the stock firmware to NE6 if I already have NH2. I'm trying to get root on NH2 and everything that I have tried fails (knox?). I have tried flashing root with cwm recovery, towelroot, etc. I have read that towelroot only works up to NE6.

Thanks for any help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AddictedToB3er:
I do believe that will result in a brick and would not suggest trying to downgrade bootloader ever
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That would brick your device. Try this to get root....

Reflash your current NH2 firmware via Odin.

Flash TWRP via Odin

Reboot recovery

Factory reset

Flash this in TWRP:

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

Reboot Normal

After fully booting, wait a couple of minutes and open the SuperSU app and let it disable Knox.

Done!

If that doesn't work, boot TWRP and flash this:

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

Factory reset

Reboot

Open SuperSU and let it disable Knox.

Once rooted, DO NOT UPDATE SuperSU!

Hope this helps! The only other alternative is flashing a rom btw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedy2887:
Doc, if this is just samsung being samsung wouldn't it be fine if we did it in stages?

4.anything-to-4.3.zip -> 4.3-to-first4.4ota.zip -> first4.4ota-to-4.4.whatever.zip

With reboot in between, so that fuses and bits can be toggled as needed?

For the record I'm on SlimKat 4.4 with probably a 4.3 bootloader and modem_CWM_I747MVLUEND2.zip

This mostly works but there are times with 3G or GPS is annoying.

Also how is I747MUMUEND3 newer then I747MVLUEND2? Like I understand END2 vs. END3 and the release dates.

But it's also UMU vs. VLU, And the glorious I747MVLUEMK5 I've run forever is VLU.

God I wish we had changelogs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I don't know if a staged flash would be safe or not. Too many unknowns. I updated straight from 4.1.1 with no problems, others bricked. Some updated fine from MJB, while others bricked.

It just doesn't seem worth the risk to continue pursuing this. But i decided to leave the thread open in case anyone has a specific need for it. They can post a request for the files.

I'm not familiar with an ND build. But the V represents a Canadian build if I'm not mistaken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
I've been seeing a lot of people who are brick in phones with the 4.4.2 (official Samsung firmware) update...some recoverable..some not..coming from 4.1.1 up to 4.3..it's crazy. Seems to be more from 4.3 but either way..that firmware upgrade when not done via OTA on stock unrooted seemed to be very problematic.

Sent from my *ROOTED* Note 4 SM-N910W8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedy2887:
I'm on a VLUEMK5 bootloader with VLUEND2 modem. How should I update everything to kitkat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrROBschiz:
Ive been on i747UCALH9 since I first got and rooted my phone

Been trying to update my modem and Bootloader to MJB but every attempt resulted in failed assert checks

no idea why atm.... should I even try leapfrogging into this one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epiquiem:
I'd love to be gifted the AT&T download link, if the OP is still around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrctony:
AT&T firmware...

Can you send me the Firmware for the AT%T Variant please..? I will PM you my email thank you in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Just saw new 4.4.2 firmware for Canadian S3 variants (NK2) on Sammobile site.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navpal93:
how do i download this firmware for my i747 s3 i cant seem to find the download link
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
From the first line of the first post:

Fortunately, there are some threads by enewman17 that have the NE2, NJ1, and NJ2 bootloader and modem files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umbro4:
give me link plz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
For i747 use this or this
[Nexus 7 (2013) LTE Android Development] sykopompos:
Flashing tips by [MENTION=275009]ramjet73[/MENTION], this should be read by everyone

http://xdaforums.com/showpost.php?p=55228784&postcount=12583

Deb does not have a working mobile radio yet, radio turns on but without access to the settings, we can't configure it. A work around is being worked on

INSTALLATION INSTRUCTIONS

FIRST TIME FLASHING

Put the file onto your Internal Storage

Reboot into Recovery (CWM/TWRP]

"wipe data/factory reset"

"mounts and storage" -> "format system"

"install zip" -> "install zip from sdcard" -> choose the mako-bla-bla-zip and confirm flashing procedure

"reboot into system"

first boot may take up to 10 minutes - be patient

UPDATING

Put the latest L-bla-bla.zip onto your Internal Storage

Reboot into Recovery (CWM/TWRP)

"wipe data/factory reset"

"install zip" -> "install zip from sdcard" -> choose the [filename.zip] and confirm flashing procedure

"reboot into system"

Updater-script wipes the cache files so no need to wipe cache

Sources

Mako

GPL KERNEL SOURCE - github.com/Android-L-Porting-Team/android_kernel_mako

Flo, Deb and Hammerhead use the modifed stock preview with the kexec-hardboot patch directly provided by [MENTION=452513]tassadar[/MENTION] to provide multirom support. Flo and Deb use the same kernel.

Hammerhead - http://xdaforums.com/showpost.php?p=48508468&postcount=2

Flo - http://xdaforums.com/showpost.php?p=45886584&postcount=2

We are using the rebase repos right now since they are cleaned out

Github https://github.com/Android-L-Porting-Team

slim builds have excess google apps cut out for those on a bandwidth budget or like to pick and choose their google apps from the play store

OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.

Please do not complain about OT, it encourages a fun and relaxed environment

Like the work I did, consider donating. I'm currently not working so it helps feed me

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92

Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
[Nexus 7 (2013) LTE Android Development] sykopompos:
nexus devices threads

Mako

http://xdaforums.com/nexus-4/development/lpv-79-mako-port-beta-t2807446

deb

http://xdaforums.com/nexus-7-2013/development-lte/l-android-lpv-dev-deb-t2856915#post55016443+

flo

http://xdaforums.com/nexus-7-2013/development/l-android-lpv-dev-flo-enhanced-t2856920#post55016534

hammerhead

http://xdaforums.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934

Changlelog.

Changlelog.

Stable-9001

Now over 9000!!!!!!

Updated selinux security policy

tracked down some missing permissions

did some other work but can't remember

B7.0.1

Flo & Deb

removed some excess apps that were replaced and I missed in b7

B7

updated fonts, res files, animations from the latest sdk

updater-script wipes cache files

updated some more google apps.

now using smart-art

force dns to google's public dns

B6

B5.9

Rebased completely from scratch on 81c

improved reliability and stability.

Ported to Deb, Flo and Hammerhead

Beta 5

fully permissive sepolicy based on aosp, cleaned out a lot of crud

removed reliance on n5 frameworks, merged in some current aosp

improved smoothness and increased reliability, daily driver status

Beta 4

New Kernel

more smashy smashy bugs
[Nexus 7 (2013) LTE Android Development] sykopompos:
reserved for [MENTION=1316336]defconoi[/MENTION] kernel info
[Nexus 7 (2013) LTE Android Development] mucinch:
Installed it now, works great. Thank you for bringing this to deb.