DO NOT FLASH THESE ON GSM Nexus S! These are for SPRINT PHONES ONLY!!!!
FLASH these thru Custom Recovery
Writing the Radio always comes with risk so please be careful.
Baseband D720SPRKD8 from OTA GRJ22: MD5 checksum: 5cab3add9ea74fdb1512386a61709e8c
Baseband D720SPRKE5 from OTA GRJ90: MD5 checksum: e1bc310cf0e029d3e42d174de1461997
Baseband D720SPRKE1 (aka KH1) from OTA GWK74: MD5 checksum: f7c665022037ae08415c061153a18910
Baseband D720SPRKL2 from Unofficial Leak: MD5 checksum: 3585a1fed8fb1c052352e2633f39a606
Baseband D720SPRLC1 from OTA IMM76D: MD5 checksum: add444c0fe4ccc056ffa8b8926d1f737
Baseband D720SPRLF2 from OTA JRO03R: MD5 checksum: 0c319fad9a270e32e6c9b5f99905788e (LATEST)
Flash thru custom recovery
ALTERNATIVE METHOD: Fastboot
Rename to radio.img
Flash in fastboot using...
fastboot flash radio radio.img
*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision
*Make sure the radio.img you are flashing is in your \android\tools
**Md5 sum is for the radio.img inside the zip, not the .zip file itself.
Forgive my ignorance/noobishness, but what are the benefits in flashing a radio? Are these optimized in some way??
This is exactly what i need to fix my semi brick..is there any way this can be put into a update.zip file to beable to be flashed in stock recovery?
You da man snandlal. I'm going to try D720SPRKC9 with GRJ22. Will report back.
Just noticed something here...
Older radio is 4.94MB & newer radio is 155kb. Seems a little off to me. I won't be flashing any radios until I get some reassurance.
12MaNy said:
Just noticed something here...
Older radio is 4.94MB & newer radio is 155kb. Seems a little off to me. I won't be flashing any radios until I get some reassurance.
Click to expand...
Click to collapse
Look at the actual .img in the zip.
Not the actual zip size. Its a zip!
Uncle Jimmy says hello
snandlal said:
Look at the actual .img in the zip.
Not the actual zip size. Its a zip!
Uncle Jimmy says hello
Click to expand...
Click to collapse
Yeah....I know what it is. I saw the differences in file size and didn't go any further.
12MaNy said:
Yeah....I know what it is. I saw the differences in file size and didn't go any further.
Click to expand...
Click to collapse
Good so you understand then
Uncle Jimmy says hello
Wasn't trying to bash you man. I've just never heard of flashable radio zips so different in file size.
no your correct 12many, the radios should be about 15MBs each. are you sure you copied the radio.img file and not the patch file from the ota?
Both the .img's were dumped. Nothing came from OTA
12MaNy said:
Wasn't trying to bash you man. I've just never heard of flashable radio zips so different in file size.
Click to expand...
Click to collapse
That's fine. I have flashed them both and i know they work so I'm content with both of the zips.
When posting radios you HAVE to also post a MD5 Checksum since radios are the things that can brick a device.
Sent from my Nexus S
thx for this since I just got my Nexus today came from EVO, EPIC and now Nexus. thx again
radio image from the tar
this is teh official phone.tar from samsung, its 15.6MB's your grj22 radio.img is only 13 when fully extracted
shabbypenguin said:
radio image from the tar
this is teh official phone.tar from samsung, its 15.6MB's your grj22 radio.img is only 13 when fully extracted
Click to expand...
Click to collapse
Easy mistake. Had the two swapped
Uncle Jimmy says hello
Anyone get ahold of the GRJ06D baseband (KC9) for Sprint lemme know, i'll post it. Thanks
snandlal said:
Easy mistake. Had the two swapped
Uncle Jimmy says hello
Click to expand...
Click to collapse
its not a problem man, we are indeed human
volta said:
Forgive my ignorance/noobishness, but what are the benefits in flashing a radio? Are these optimized in some way??
Click to expand...
Click to collapse
Sorry, since no one answered me, I need to ask again:
What is the point in flashing a radio? If it's risky and could brick a device, what benefits does a non-stock radio image provide to the user?
they are both stock, just one is newer. a newer radio offers sometimes better signal, better battery life etc etc
Related
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.
Hello everyone i hope someone can help with my issue. I have done an extensive search in regards to my issue but can not find a true answer so i hope some one can help here. I was given a US based T-mobile SGH-T989. When I got it I could swipe to open phone but screen would be comepletly black. I did a wipe and restore but no luck. I used Odin to flash newest stock rom and had same result.. I then decided to flash it with stock shipped rom which was Gingerbread and phone was up and running except for one lil problem the Baseband, IMEI and such were all unknown. I have been searching to see if I could try and flash baseband but havent been able to find anything understandable or even for the T989. could anyone please advise me of what i could do to fix this problem? I do realize that maybe the Baseband chip itself could be the issue but i would like to try and flash it fresh first before i declare this phone toast. thank you all in advance. If this problem has been posted before my apologies i could not find a thread for the T989 with this issue non the less one with US T-Mobile baseband files.
Never-E-Nuff said:
. If this problem has been posted before my apologies i could not find a thread for the T989 with this issue non the less one with US T-Mobile baseband files.
Click to expand...
Click to collapse
Baseband=radio.
Try the radios from this thread:
http://forum.xda-developers.com/showthread.php?t=1895400
You will need a custom recovery(CWM, TWRP) to install them.
meekrawb said:
Baseband=radio.
Try the radios from this thread:
http://forum.xda-developers.com/showthread.php?t=1895400
You will need a custom recovery(CWM, TWRP) to install them.
Click to expand...
Click to collapse
Couldnt I use Odin to flash the baseband? the phone is not rooted it is stock. i would like to keep it that way if possible untill issue is resolved but if the only way to fix the problem is to root it let me know.
Never-E-Nuff said:
Couldnt I use Odin to flash the baseband? the phone is not rooted it is stock. i would like to keep it that way if possible untill issue is resolved but if the only way to fix the problem is to root it let me know.
Click to expand...
Click to collapse
You can take the two radio files out of the zip(amss.bin & mdm.bin) and tar them up with
tar -cvf name_for_tar_file.tar amss.bin mdm.bin
But you don't even need to root to install a custom recovery. Just Odin one of the tar files from here:
http://techerrata.com/browse/twrp2/hercules
And install the radios from the thread I linked earlier.
meekrawb said:
You can take the two radio files out of the zip(amss.bin & mdm.bin) and tar them up with
tar -cvf name_for_tar_file.tar amss.bin mdm.bin
But you don't even need to root to install a custom recovery. Just Odin one of the tar files from here:
http://techerrata.com/browse/twrp2/hercules
And install the radios from the thread I linked earlier.
Click to expand...
Click to collapse
So i did what was recomended and still same issue no IMEI or Baseband says Unknown. So is it possible that The radio I choose was not a good one or is my Baseband chip bad? when I installed the zip from recovery it said install successful but obviously it did not work. starting to think i have a paper weight at this point.
Never-E-Nuff said:
So i did what was recomended and still same issue no IMEI or Baseband says Unknown. So is it possible that The radio I choose was not a good one or is my Baseband chip bad? when I installed the zip from recovery it said install successful but obviously it did not work. starting to think i have a paper weight at this point.
Click to expand...
Click to collapse
It is possible that you have a hardware problem. I would try all the radios just to be sure though. Good luck.
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
Simple question
The August radio included in the developer image is horrible! Lots of battery life wasted.
Sent from my Pixel XL using Tapatalk
abuttino said:
Simple question
The August radio included in the developer image is horrible! Lots of battery life wasted.
Click to expand...
Click to collapse
You can flash any radio you want. I'm currently running DP3 radio and modem. The May update radio is also really good for me.
Golf c said:
You can flash any radio you want. I'm currently running DP3 radio and modem. The May update radio is also really good for me.
Click to expand...
Click to collapse
Do you just download the full file and extract the radio file and push through ADB or is there separate .zip files to flash? Thanks
john7760 said:
Do you just download the full file and extract the radio file and push through ADB or is there separate .zip files to flash? Thanks
Click to expand...
Click to collapse
Download the full file and extract the radio and modem. I do both. I don't know if that's necessary but it makes me feel better. I fastboot it.
fastboot flash radio -- slot all radio.img
Golf c said:
Download the full file and extract the radio and modem. I do both. I don't know if that's necessary but it makes me feel better. I fastboot it.
fastboot flash radio -- slot all radio.img
Click to expand...
Click to collapse
I've flashed the boot to a & b to be able to sideload, but i'm not sure on the command for "slot all" to use. Is it the same? I've been less that impressed with the last couple of radio/modem's as far as signal goes for me in my area.
john7760 said:
I've flashed the boot to a & b to be able to sideload, but i'm not sure on the command for "slot all" to use. Is it the same? I've been less that impressed with the last couple of radio/modem's as far as signal goes for me in my area.
Click to expand...
Click to collapse
Radios are really hit and miss For me too. Im on tmobile and the tmobile radios have been horrible for me. The May update radio has been the best. The slot all fastboot command is just one command instead of three commands.
Where are you guys getting the radios from? I can't find any of the new ones, because all of the threads that I have found on here have not been updated in a while.
Probably a stupid one to ask, but does flashing the vendor image update the modem?
Thanks!
bigal1542 said:
Where are you guys getting the radios from? I can't find any of the new ones, because all of the threads that I have found on here have not been updated in a while.
Probably a stupid one to ask, but does flashing the vendor image update the modem?
Thanks!
Click to expand...
Click to collapse
We are extracting them from the Google factory images
Golf c said:
We are extracting them from the Google factory images
Click to expand...
Click to collapse
Hi , can you just upload this radios and modem files ?
i search a lot in this forum and cant find any radios or modem updates ....
thanks
daniking said:
Hi , can you just upload this radios and modem files ?
i search a lot in this forum and cant find any radios or modem updates ....
thanks
Click to expand...
Click to collapse
.
They are found within googles factory images. From google site download image that contains radio you want, unzip it and you will find radio and modem images.
I'm on stock vzw, 8.0, locked bootloader..... Can I flash the radio & modem from the 8.1 preview? If so would I need to flash anything else (bootloader, etc....)?
TIA
TheCelt said:
I'm on stock vzw, 8.0, locked bootloader..... Can I flash the radio & modem from the 8.1 preview? If so would I need to flash anything else (bootloader, etc....)?
TIA
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader
Born<ICs said:
.
They are found within googles factory images. From google site download image that contains radio you want, unzip it and you will find radio and modem images.
Click to expand...
Click to collapse
Thanks. But can you just give me a link of that?
daniking said:
Thanks. But can you just give me a link of that?
Click to expand...
Click to collapse
. Factory images.
https://developers.google.com/android/images#marlin
On GSam Battery Monitor's phone signal graph, I noticed fluctuating signal graph. I work in city core and signal is always in good 65-72 dbm range.
There is certainly no reason for the phone to have signal problems. Worse is that signal problem causes battery drain.
Fix is rather simple. Update firmware or modem (NON-HLOS.bin.) Though I flashed entire firmware, updating modem alone should do it.
To update, follow [GUIDE] How to manually upgrade firmware posted by @Presterin .
However, note that I used 26S firmware as 23S firmware is the one that gave me the problem.
In the picture, those crazy fluctuation is when I was on 23S radio and right after I I flashed 26s one, it is nice and stable as you can see.
EDIT: Do not flash system.img and boot.img if you want to keep your current rom as it is. Obviously, do not format Data neither.
How about US devices on American carriers? What modem is good for them?
Sent from my LEX727 using Tapatalk
PloniAlmoni said:
How about US devices on American carriers? What modem is good for them?
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
You will need to find latest stock rom which contains firmware and flash it. As for which modem works best, I do not know. I suggest you compare them using GSam Battery Monitor.
PloniAlmoni said:
How about US devices on American carriers? What modem is good for them?
Click to expand...
Click to collapse
5.8.19s is the only modem we have for USA. I think it works pretty well. No battery drain here on my lex727.
4K2K said:
On GSam Battery Monitor's phone signal graph, I noticed fluctuating signal graph. I work in city core and signal is always in good 65-72 dbm range.
There is certainly no reason for the phone to have signal problems. Worse is that signal problem causes battery drain.
Fix is rather simple. Update firmware or modem (NON-HLOS.bin.) Though I flashed entire firmware, updating modem alone should do it.
To update, follow [GUIDE] How to manually upgrade firmware posted by @Presterin .
However, note that I used 26S firmware as 23S firmware is the one that gave me the problem.
In the picture, those crazy fluctuation is when I was on 23S radio and after I I flashed 26s one, it is nice and stable as you can see.
EDIT: Do not flash system.img and boot.img if you want to keep your current rom as it is. Obviously, do not format Data neither.
Click to expand...
Click to collapse
Can you please upload NON-HLOS.bin alone for 26S somewhere, so we dont have to download the whole rom?
Thank you
I've uploaded all of the 26s firmware files this morning, just extracted from the official ROM. Follow the link below
https://uploadfiles.io/09ywy
The zip is NOT flashable, its just an archive of all FW files.
Can we flash 26s files over PA 7.3.1? Or only over the Chinese EUI?
The whole package? or just the NON-HLOS.bin?
trizex said:
I've uploaded all of the 26s firmware files this morning, just extracted from the official ROM. Follow the link below
https://uploadfiles.io/09ywy
Click to expand...
Click to collapse
@Gorka15 yes you can @lyrebird 15 firmware files, modem (non-hlos) included
lyrebird said:
The whole package? or just the NON-HLOS.bin?
Click to expand...
Click to collapse
zip file corrupt when trying to flash; downloaded 3 diff ways
flashed manually on fastboot. thanks everything is working
Gorka15 said:
Can we flash 26s files over PA 7.3.1? Or only over the Chinese EUI?
Click to expand...
Click to collapse
I flashed whole thing on Omni rom except system.img and boot.img. Also no data format.
It did not break anything.
Does flashing this firmware enable CDMA?
4K2K said:
I flashed whole thing on Omni rom except system.img and boot.img. Also no data format.
It did not break anything.
Click to expand...
Click to collapse
lyrebird said:
Does flashing this firmware enable CDMA?
Click to expand...
Click to collapse
It does not enable or disable anything. Just an update of what you already have.
If your question is about flashing x720 modem on x722 or vice versa, I do not know but I recall reading others' posts about that on other threads.
beastonprowl said:
zip file corrupt when trying to flash; downloaded 3 diff ways
flashed manually on fastboot. thanks everything is working
Click to expand...
Click to collapse
Yeah, forgot to say, zip is not flashable, its just an archive of fw files
I have the X727. How do we tell what version of the modem we have? What is the latest version? I have issues with signal dropping in and out all the time. Very annoying.
trizex said:
I've uploaded all of the 26s firmware files this morning, just extracted from the official ROM. Follow the link below
https://uploadfiles.io/09ywy
The zip is NOT flashable, its just an archive of all FW files.
Click to expand...
Click to collapse
Do I need to flash the NON-HLOS.bin file via adb with fastboot?
yep.
fastboot flash modem NON-HLOS.bin
lazye53 said:
Do I need to flash the NON-HLOS.bin file via adb with fastboot?
Click to expand...
Click to collapse
lazye53 said:
Do I need to flash the NON-HLOS.bin file via adb with fastboot?
Click to expand...
Click to collapse
If you're rooted, you can use flashfire
slgooding said:
I have the X727. How do we tell what version of the modem we have? What is the latest version? I have issues with signal dropping in and out all the time. Very annoying.
Click to expand...
Click to collapse
I have been having the same issue myself and started a thread on it here, hopefully I will be able to update the thread with a solution soon.
trizex said:
If you're rooted, you can use flashfire
Click to expand...
Click to collapse
when i select the firmware26.zip with flashfire it give me only 10 partitions and not 15 ...it's normal?
The first two partitions on top (Primary Bootloader - Secondary Bootloader AP) are grayed out . i must enable the two partition too in the setting?
Edit: I flashed firmware26s.zip with flshfire also the first two partitions of the bootloader and everything went well ... thanks