Android version 6.0.1 bootloader and radio files updated January 7, 2016
Hello all.
I created a few flashable ZIP files which will install the radio and bootloader images from Android 5.0.x, 5.1.x or 6.0.x depending on your choice.
To install the Android 6.0.1 radio (M8974A-2.0.50.2.28) and bootloader (HHZ12k), flash the following ZIP in recovery:
The file is N5_AndroidM_6.0.x-MMB29S_Radio+Bootloader.zip, MD5 9fef18abade89f85fe13b37320b740bd, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24352994023708028
---
To install the Android 5.1.1 radio (M8974A-2.0.50.2.26) and bootloader (HHZ12h), flash the following ZIP in recovery:
The file is N5_AndroidL_5.1.x-LMY48M_Radio+Bootloader.zip, MD5 c90de28bf48e9461a13c6617c9d792ce, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812405
---
To install the latest Android 5.0.x radio (M8974A-2.0.50.2.22) and bootloader (HHZ12d), flash this ZIP in recovery:
The file is N5_AndroidL_5.0.x-LRX22C_Radio+Bootloader.zip, MD5 4c9861bfe068d232340e961aa7726767, size 22.6MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812506
Hope this helps!
Thanks
Separate radio frm the zip
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
FunDionysus said:
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
Click to expand...
Click to collapse
I suppose I can, though it doesn't change anything to flash the same radio version on top of itself, so you could just flash the whole thing to update the bootloader. The only reason there would be to split it up would be if you wanted to keep a different radio version than the one in the zip.
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
ek69 said:
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
Click to expand...
Click to collapse
The bootloader and radio has been the same through all the revisions of Lollipop.
Wakamatsu said:
The bootloader and radio has been the same through all the revisions of Lollipop.
Click to expand...
Click to collapse
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
ek69 said:
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
Click to expand...
Click to collapse
Yes, these are from the Google factory images. Specifically, the factory images for the Nexus 5. You can see all of the released Nexus factory images here. As you can see, LRX21O is still the latest version released for the Nexus 5. It seems as though other devices have had images released with "higher" letters, for instance LRX21V is the build number for the latest Nexus Player factory image. My guess is that Google makes device-specific changes to Android and then updates only those devices that would benefit, though I have nothing to back that up.
In any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
iammuze said:
YIn any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
Click to expand...
Click to collapse
Thanks for this info. When I installed the bigxie stock Lollipop flashable ROM, the OP included a link to the updated radio. But the bootloader was not updated to the latest.
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
No problem!
FunDionysus said:
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
Click to expand...
Click to collapse
Well like i said a couple posts above there's no harm in flashing the same version radio on top of itself, so even if all you want is to update the bootloader (and as long as ths radio in the ZIP is the same version you want to keep), this will work just fine.
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
pierrep56 said:
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
Click to expand...
Click to collapse
Nope! No wiping, perfectly safe.
Thx for all your help and clarifying things
I was just wondering why some threads in the nexus 5 section were referencing LRX21V in the titles cuz like u said LRX21O is the latest out by Google for nexus 5
Simply and easy to upgrade the bootloader. Thanks!
Thanks ! :good:
If we flashed the lollipop factory image I assume we have the latest bootloader?
Thank you for this file! I was already running the latest radio but I needed the boot loader update!
Why does everyone care about latest bootloader update so much?
Just wondering
Sent From Bacon
ek69 said:
Why does everyone care about latest bootloader update so much?
Click to expand...
Click to collapse
For myself just wanting to learn the diff.
Can locate no documentation or changelog.
The Android 5.0 LRX21O - Stock/Flashable ROM I installed did not install the updated bootloader, which I believe came out for the Lollipop Preview back in October,
Just to make sure I don't have to fix anything after I do this process.
If I flashed Cataclysm ROM for Android 5.0, I need to install this correct?
Hello I tried to do to update my G900a
BASEBAND VERSION: G900AUCU3BOC4
build number: LRX21T.G900AUCU4BOF3
acording to this:
http://forum.xda-developers.com/att-galaxy-s5/general/5-1-1-phones-t3231280/page6
download the G900A-OF3toOI5-ota-2400258.cfg file, rename it update.zip, update from sd card
but unfortunately the phone is still on Android 5.0. Is someone was able to update to 5.1.1?
can someone give me a link to correct update version for my phone?
why in Settings/ About Device my BASEBAND VERSION and build number don't match?
http://1drv.ms/1PPZtYi
I'd like to get this update also. Every Time I try it fails at around 32%.
Any ideas to try? I have already cleared cache, factory reset and nothing works.
Why are you not following http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774 ?
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
Hi u , u can pm for me via zalo : +84974405300 . I can help u .
No
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
I had this exact problem with SM-G890A on 6.0.1. I flashed a stock firmware, and I had no mobile network, sim card wasn't detected, etc. The problem was that my device had the most recent update (from March). I am not an expert, but I believe this update makes it harder for devices to be susceptible to flashes (hence "extra security"). To fix this problem, after flashing a stock firmware, I put my phone in recovery mode (volume up, power, and home) and downloaded ADP, and from there, I was able to download each update after my stock firmware until I reached the update that I was on before I ever flashed. I hope that makes some sense. There is a great post on here with the updates available for download and instructions on how to use ADP. I wish I still had the link, but try searching the updated version that you should be on. Whenever I finished the last update and my phone restarted, I restarted it again in recovery mode and cleared the partition cache. Restarted it again and VIOLA, I finally had service. Feel free to email me if you have any questions. Sorry, I am not great at explaining things. I hope you can resolve this. [email protected]
Fixed and Downgraded
I had this same issue. I was able to fix it by first upgrading back to 7.0 as mentioned above, and then flashing ONLY the BL and AP files of the 6.0.1 firmware using Odin. Worked for me.
U need flash to android 6.0.1 build Pk8.
EndSliceofBread said:
After flashing default android 6.0.1 on my s6 active my broadband version is unknown and I have no imei...not sure what to do.
Click to expand...
Click to collapse
Hey I had the same problem as you and I was panicking. I downgraded to 6.0.1 from 7.0 final version but the SIM/IMEI/Broadband/anything phone related was broken. What happened was the final build of 7.0 upgrades the security of the SIM/IMEI/Broadband and so if you flash any other firmware, it won't work with the newer security and it'll remain unknown. To fix this, you have to upgrade to 7.0 final build again. Just adb sideload all the way back to 7.0 final QD1 and your SIM/IMEI should activate again. I guess ATT/Samsung is preventing us from downgrading just like Apple
Flash the Nougat Odin package.
This is Taiwan Pixel 5.
Now, The version is RD1A.200810.022.A4, but I forgot the version that I received it.
Has anyone seen it ?
Which version should I choose when I patch the boot.img ?
Interesting, if I may assume that increasing build numbers mean newer builds, then your P5 has newer firmware than mine (.021.A1)
I just got mine and it shows the same build number as yours. "...022.A4" Did you end up sideloading the .20 image available? I'm in US if that matters.
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
hawkerpaul said:
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
Click to expand...
Click to collapse
According to the Google Pixel Community Forum this is going to be fixed automatically by the Global December build.