Develop Bugs

T999 UVDMD5 Firmware / Bootloader

UPDATED 2013/11/21: Added more warnings.
This is for US SGH-T999 devices ONLY. If there is ANY letter after your model such as 'L' or 'V' DO NOT FLASH THIS OR YOU WILL DEFINITELY BRICK YOUR PHONE! For SGH-T999V VLDLD1 firmware, please see this thread: http://forum.xda-developers.com/showthread.php?p=41701398
DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.
Currently I don't have a SGH-T999L firmware update script, sorry. If someone would like to work with me on guinea pigging it and has heimdall installed, PM me and we'll get it done in no time.
This is the latest firmware update for US T-Mobile (SGH-T999) that flashes the UVDMD5 radio and bootloader with a convenient update.zip. Flashing it on anything other than the US SGH-T999 is strongly not advisable. It will likely brick your phone. It CANNOT be used on the Canadian T999V variant.
This script flashes all of the firmware that comes with the UVDMD5 OTA -- this upgrades the firmware as if you had just flashed the whole package through Odin, but without actually touching system, recovery, kernel, etc. There are two versions of the script -- one just does the bootloader+firmware, the other does bootloader+firmware+modem.
What are these firmware files?
rpm.mbn - Resources and Power Manager
sbl2.mbn - Part of Secondary Bootloader
sbl3.mbn - Part of Secondary Bootloader
aboot.mbn - AP Bootloader
tz.mbn - Trust Zone
NON-HLOS.bin - Modem / Radio
Why do I want this?
If your phone has old enough firmware, newer CM10.1 builds will no longer install on it. It is unknown if updating to UVDMD5 from UVDLJC, for example, has any noticeable positive effects. No known negative effects have been reported and the Odin method ends up upgrading all this stuff anyway.
Note that you can flash the above files via heimdall but this updater below is handy as you don't need heimdall, download mode, etc. All you really have to do is flash it in recovery.
Flashable UVDMD5 Bootloader / Firmware / Modem update.zip: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_firmware_v4.zip (md5: d040ea4193234cbe9a36f95ffa780086)
Above flashable update without modem: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_noradio_v4.zip (md5: 4c4aa065ee7c86dccea92ec7856a7af4)
OLDER UVDLJC Firmware update.zip script (w/modem) -- only if you specifically need it for some reason.: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999UVDLJC_firmware.zip (md5: 537b69ec54ce6a3580a9c56ca379e72c)
Instructions:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
NOTE: If you plan to flash anything else, please at least reboot recovery or it won't pick up the bootloader change.
Changes:
v1: Initial release. Modified someone's UVDLJC firmware update.zip script to update to UVDMD5.
v2: Removed certs from a previous update.zip that could've been causing signature verification errors with some recoveries.
v3: Updated Edify script courtesy of @Aerowinder
v4: Corrected a derp in package_extract_dir() (my fault) that prevented v3 from working at all. I've since tested v4 personally and verified it.
Many thanks to whomever put together the original update.zip and to Khaytsus and invisiblek for pointing me in the right direction. Also many thanks to all who've tested it and provided feedback. There is no greater enjoyment than in helping people.
I've also hacked together a firmware backup script that works for both T999 and T999V: http://forum.xda-developers.com/showthread.php?p=41548550
DISCLAIMER: I do not take any credit for this stuff, I just put it together. I am not liable for your device if you break it, etc etc. READ THE WARNINGS BEFORE PROCEEDING.

Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2

I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2

re: bootloader
OhhCoreey said:
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?

Misterjunky said:
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Click to expand...
Click to collapse
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2

itzsmokey said:
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5

OhhCoreey said:
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.

Misterjunky said:
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Click to expand...
Click to collapse
FWIW, I'm getting much better radio performance after switching to UVDMD5 modem. YMMV but I'm definitely getting better up/down and stronger signal indoor where I had terrible signal. But you you can just flash the modem separately from this .zip -- there's a thread in the d2tmo dev forum with the modems and their recovery flashable update.zip files.
The OP of said thread also undertook a project to allow people to post on some shared Google Map what modem they're using and their results, so you might want to look into what works best for your area too if you care about getting better signal or speed.
Cyanogen pushed the assert for newer bootloaders in the 5/14 nightly I believe as there were lots of people complaining about random crashes and supposedly much fewer reports on newer firmwares. I actually wasn't having this problem very much with LeanKernel, though it did seem to be happening like crazy at some point.
I actually didn't know about all the bootloader versions for our phones until today, it was interesting diving into all this stuff. I discovered at the beginning I was running with the same firmware the device had shipped with and if Cyanogen hadn't pushed for the newer bootloaders, I might have let things be. But since he pushed for it, I decided might as well have the latest stuff.
Cheers

mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
Seen this after I flashed it.....it works perfect, I did a clean install just to have things fresh.
Sent from my SGH-T999 using Tapatalk 2

I don't know if I have a newer bootloader or not but flashed cm 10.1 and it runned perfect how do I know if I have it.

mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
NM
Sent from my SGH-T999 using xda app-developers app

I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.

Aerowinder said:
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Click to expand...
Click to collapse
It is just DD which is what basically Odin would do anyway. The filenames are irrelevant. It's what data goes to which mmcblk0 partition. The file names are what they are as they are taken from the T999 UVDMD5 Odin .zip and for clarity. Why would I rename aboot.mbn to some random file name?
Just run heimdall print-pit some day and you can see how your eMMC is partitioned and what goes where. I could've flashed all these files with heimdall using the correct named partition identifiers rather than numeric identifiers, but I found it more convenient to make a flashable update.zip.
Update however you want, but as someone who doesn't use Windows and doesn't like screwing around with heimdall / Download Mode much, just dd'ing the files to the correct partitions was the most elegant solution I could find.

Nice work!
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.

mondokat said:
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
Click to expand...
Click to collapse
Thanks though I can't take credit for writing the script. I just extracted the UVDLJC firmware updater script written by another dev, substituted the UVDMD5 files in, updated the script with the new SHA1 sums, and re-zipped it, thus making a flashable UVDMD5 updater script.
It does not flash the system -- it just flashes aboot, rpm, tz, modem, and some sbl files. I run CM10.1 and was able to just flash this without killing any of my system stuff. Recovery, system, kernel, etc. are all preserved. You can make a backup (as anyone should anyway), but you shouldn't need to do any restore or even a cache wipe after flashing either UVDLJC or UVDMD5 updater since it's just bootloader, modem, and some other pieces unrelated to system/kernel.
In retrospect, it would've been trivial to extend the script to create backups of the current partitions on the phone. In fact, I'm pondering a "firmware flasher" script that gives one a menu of different firmwares and ability to backup/restore for fun. Then again, I've never touched these firmware bits until Cyanogen necessitated a newer bootloader in CM10.1.
Anyway, I modified this script for myself at first and I had spent the whole day trying to research the topic without too much info. I saw S3s from other carriers had update ZIPs and was frustrated at the lack of one for d2tmo. After testing it on myself successfully and realizing how safe it is, I decided to just release it so people can benefit from it by upgrading their firmware or ripping it apart and learning how it works and/or making it better.
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.

Thanks for putting this together it has made a huge difference for me with the new radio I have gained 7 mb down and 3 mb up from this I'm running jovy stockoaroma rom right now :thumbup: great idea I was going to odin so I could update that now I don't have to...
Sent from my SGH-T999 using Tapatalk 2

How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium

mnasledov said:
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Click to expand...
Click to collapse
Here's what I found:
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
SBL = Secondary Boot Loader
According to the article, the sbl is something like an efi bios, basically it turns on a bunch of hardware bits and then hands off to the next stage of booting. So I guess now we know. :silly: I'd think if you are updating the boot loader, you'd want to include the secondary bootloader as well. Probably your zip file is correct in that if you update any of those pieces, you should PROBABLY update all of them to the same revision, just in case.
Which means EXTRA thanks to you, for doing the work. Now when people say "why can't I flash the latest CM10?" we can just point to this thread and say "flash that first".
:highfive:

Thanks op so much for this. Running the latest cm nightlies again
Sent from my SGH-T999 using xda premium

djtheraven said:
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just open up a shell either in your ROM or CWM Recovery (adb shell) and run:
Code:
$ getprop ro.bootloader
It should print out something like "T999UVDMD5"
I had T999UVALG1 before I upgraded the firmware.
EDIT: If you're going to do it in CWM Recovery, you might have to do it as root. Make sure to adb kill-server as root to kill any adb servers that may be running and a subsequent adb shell should grant you access.

cannot flash new AOKP (error 7)!!!!

hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ

Maybe check to see if you have the latest recovery installed
Sent from my SGH-I747 using xda premium

ginnz said:
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Click to expand...
Click to collapse
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.

ginnz said:
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
Click to expand...
Click to collapse
Okay, first thing first. You are reading WAY TOO MUCH into this, You need to slow down and do some reading on what is what for your phone.
There is no confusion about d2can and d2att in here. Here it is as simple as I can explain.
You live in Canada (as do I) our phones are SGH-I747M when you install a custom recovery (Clockworkmod or TWRP) The phone is registered as a Canadian model. The developers on this forum build ROMS for d2att only. They just happen to work on our phones as they are identical. To be able to flash these ROMS on our Canadian phones you have to flash the d2att recovery (Clockworkmod or TWRP)
So my suggestion was to make sure you have flashed the d2att recovery to your phone. You can get the Odin files from the websites or a quick search here would get you the flashable .zip files you would flash in recovery like a ROM (no wiping needed though)
Anything on THIS FORUM ONLY will not brick your device. Anything labelled under anything outside this forum ie. i9300 (International S3) or the other carriers will cause harm to your phone and you'll be a sad panda.
I747M4LDLK4 is your bootloader.
What Is A Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Click to expand...
Click to collapse
If you were to flash a US bootloader on your phone you'll be a sad panda.
The newer ROMS are requiring an updated bootloader to work properly. The newest Canadian bootloader MF1 still won't work for most of these ROMS so don't update it that far.
I don't know what else to suggest.
There are 2 main reasons for status 7 (3 if you're on a Canadian carrier which you are)

@KorGuy123
Nice job on the explanations. Many Users (none of which are obviously in this section of course ) would see that he was running a version of Task's ROM from December and jumped all over him. Keep up the good work.
OP ~ KorGuy123's last post points out to what a Status 7 recovery error is. Most of the times Status 7's are mainly due to Recovery issues. Bootloader issues will usually throw a [getprop ro.bootloader] error instead of a Status 7 just for future reference.

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.

ginnz said:
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
Click to expand...
Click to collapse
Glad it worked out for you. Enjoy!
Sent from my SGH-I747 using xda app-developers app

[Q] Unable to flash custom roms!

Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!

Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app

Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?

I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app

You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???

baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?

Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...

LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.

lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?

LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.

lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."

LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.

lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device

Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David

[How-To][GUIDE] Update and Root T999 JB 4.3 update - UVUENC2 Firmware

T999 JB 4.3 update - UVUENC2 Firmware
Samsung And T-Mobile have released the next update UVUENC2 for SGH-T999.
EDIT - @mrRobinson has a Root66 version of UVUENC2. That version is KNOX Free. So my recommendation is to visit his thread and using that firmware instead.
WARNING - The following steps are only for those who had accepted the previous 4.3 Update UVUEMJC or flashed it from Root66 thread.
Essentially with the newer updates to the Odin, version 3.09 makes the process pretty easy to those who are familiar. This does work even if you have custom Rom and Custom Recovery. Both of which will be destructively replaced by the new firmware. So take a Nandroid!!! Those with Stock firmware UVUEMJC, please take a Titanium Backup of all the essential stuff to external SD. You have been warned.
1. Obtain the Stock update UVUENC2 from SamMobile Link.
2. Download the CF-AutoRoot zip file for D2TMO by @Chainfire.
3. Obtain Odin 3.09 from here. Do not run Odin.
4. Take a backup of important stuff and put the phone in Download Mode.
5. Connect the phone to the PC and let the drivers install if not installed already.
6. Execute Odin as System Admin and then choose the Stock Firmware as AP (AKA PDA in prior versions).
7. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
8. Complete the Odin flash process.
9 Once that's successful, make sure the phone is still in Download mode.
10. Again Click AP (AKA PDA) and choose the CF-AutoRoot zip previously downloaded.
11. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
12. Complete the Odin Flash process.
13. When it is successful, Disconncect the phone and pull the Battery. Boot the phone to Stock Recovery and wipe Cache as well as Dalvik if there's an option for Dalvik. (My Phone does not have stock so don't remember)
14. Let the phone boot normally and enjoy Rooted Stock update. Profit !
You can use Root Checker App from Play store to confirm Root. If for some reason it failed, update the binaries of the Super user app. Upon launching that app, it may prompt for the same.
CREDIT - Nasirtech Tutorial from over here.

This is perfect, bro! Thanks for the guide!

Is there a flashable file for just the modem?
Sent from my SGH-T999 using XDA Premium 4 mobile app

Yes There is. @Synthetic.Nightmare Posted in this post.

Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem

pp085ster said:
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
Click to expand...
Click to collapse
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: [REMOVED FOR NOW]
EDIT: This one works: modified UVUENC boot.img

Totally agree
Is very frustrating dont have ROOT on T999UVUENC2.
My T999 was updated from 4.1.2 to 4.3 T999UVUENC2 directly and was a big mistake I alredy loose my root and cant instal CM11 by any way since I cant disable KNOX.
Heeeelp

Solved

Synthetic.Nightmare said:
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: UVUENC2 boot.img
Click to expand...
Click to collapse
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha

pp085ster said:
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
Click to expand...
Click to collapse
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk

Synthetic.Nightmare said:
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It installs the modules but then gets stuck at extracting boot.img. The exact error is:
assert failed: write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7")
Does that help? :good:

Yes. That's exactly what I needed.
Went ahead and decided to just go ahead and install TW for some time just to get it working right.
This one should work. Tested and tried on the latest DanDroid.
I've repacked the ramdisk so that androidboot.selinux=permissive (you can check this via terminal by entering
cat /proc/cmdline
after "su"...without quotes), though the settings still seem to show selinux as enforcing.
[LINK REMOVED FOR ANYONE DIRECTED HERE]
EDIT:
Latest T999 boot.img with selinux permissive and init.d support by @enewman17
http://www.mediafire.com/download/v57ka148accbky8/T999_UVUENC2_boot-img_init.d.zip

That works great thanks! let me repost it for the other users that had problems with it too ok? thanks again!
Sent from my SGH-T999 using xda app-developers app

problem with UVUENC2 update
I am on T Mobile, and received the UVUENC2 update on my SGH-T999 Samsung Galaxy SIII. But I believe that resulted in my S3's wifi radio becoming unstable-- on multiple hotspot sites (including my very reliable SSID at home), it is regularly reporting that is disconnected due to "the internet connection on this wifi site is unstable/slow" when in fact, I know that is not the case, at all. What I have to do now to correct this temporarily, is to restart my S3. But it will eventually repeat this annoying (and erroneous) "unstable/slow" wifi error reporting & disconnection. Just thought I would pass this along, since I noticed this problem with mine, specifically and only after I got this update-- the wifi connection on my S3 was working fine historically, til then.

Would this work on the videotron gs3? the baseband is different

Yoddel_Hickory said:
Would this work on the videotron gs3? the baseband is different
Click to expand...
Click to collapse
No it will not. Even the bootloader is different.

Damn well thank you, i'll try something else

I updated to 4.3 UVUENC2 from the OTA upgrade I got from tmobile, but I can't flash a root66 version of this because it's not released yet.
My question is, I thought you couldn't just use CF-Auto-Root with a knox-enabled firmware? I thought the root wouldn't stick? Or am I misinformed?
I'm debating whether I should wait for root66 of UVUENC2 or just do your method...

Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app

masondoctorjt said:
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
I suggest reading the thread title and the first post. A single search can do wonders.

[Q] SGH-I747 Update Issues to 4.4.2

I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?

Follow one of enewman17's how to update threads in General.

4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks

bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2

DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).

Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse

jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.

Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.

I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse

jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?

I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse

jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.

Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse

jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.

Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.

Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.

Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse

Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk