Develop Bugs

(RADIOS) **SPRINT** CDMA Basebands-Updated 09-10-2012

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

Restore GalleryGoogle to 4.1.1 so I can upgrade to 4.2.2

Hey guys,
Rooted unlocked stock 4.1.1. (JRO030)
Looking to upgrade. Downlaoded the install .zip but I'm getting a failure. Based on the recovery log I'm pretty certain it has to do with the manual upgrade I did earlier to get the 4.2 camera with photosphere working on my Nexus.
Any ideas how I can downgrade the camera first? I can't find the APK anywhere.

Parafly said:
Hey guys,
Rooted unlocked stock 4.1.1. (JRO030)
Looking to upgrade. Downlaoded the install .zip but I'm getting a failure. Based on the recovery log I'm pretty certain it has to do with the manual upgrade I did earlier to get the 4.2 camera with photosphere working on my Nexus.
Any ideas how I can downgrade the camera first? I can't find the APK anywhere.
Click to expand...
Click to collapse
Since you're unlocked and stock, download the factory image and flash the system image ONLY via fastboot.
Sent from my Galaxy Nexus using xda premium

Thanks - how do I flash the system image only? I actually haven't used fastboot in a while.

Parafly said:
Thanks - how do I flash the system image only? I actually haven't used fastboot in a while.
Click to expand...
Click to collapse
fastboot flash system system.img
done.

do I need to copy part of the 4.2.2 zip file somewhere first? Right now I just have the full (zipped) download in the download folder of my gnex.
I guess I'm wondering, where do I get system.img and where do I place it so I can load it via fastboot?

Parafly said:
do I need to copy part of the 4.2.2 zip file somewhere first? Right now I just have the full (zipped) download in the download folder of my gnex
Click to expand...
Click to collapse
if you downloaded the image from google,
untar the image
there should be a zip after you untar it, which will have the system.img in it.

Thanks ... very helpful, now i just need to know where to put the system.img? DOes it go into the same directotry where platform-tools is?

Parafly said:
Thanks ... very helpful, now i just need to know where to put the system.img? DOes it go into the same directotry where platform-tools is?
Click to expand...
Click to collapse
where ever your fastboot.exe is

Hmm the file came as a .zip not a .tar
5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip
I unzipped that and I see
folders (META-INF, patch, recovery, system) and two radio images. Did a search and couldn't find system.img in there.
Copied the full directory to where fastboot is and did the dir *.img in command prompt also didn't find any files.

Parafly said:
Hmm the file came as a .zip not a .tar
5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip
I unzipped that and I see
folders (META-INF, patch, recovery, system) and two radio images. Did a search and couldn't find system.img in there.
Copied the full directory to where fastboot is and did the dir *.img in command prompt also didn't find any files.
Click to expand...
Click to collapse
that is from a OTA zip.
you need the full factory image from here: https://developers.google.com/android/nexus/images

Ah got it - thanks. They haven't put 4.2.2 up there yet for VZW as far as I can see. Can I use the 4.1.1 to somehow flash over just the gallery? Will writing system.img do that?

Parafly said:
Ah got it - thanks. They haven't put 4.2.2 up there yet for VZW as far as I can see. Can I use the 4.1.1 to somehow flash over just the gallery? Will writing system.img do that?
Click to expand...
Click to collapse
yes.

Parafly said:
Ah got it - thanks. They haven't put 4.2.2 up there yet for VZW as far as I can see. Can I use the 4.1.1 to somehow flash over just the gallery? Will writing system.img do that?
Click to expand...
Click to collapse
That's exactly what it will do hence why you were told to do that.

^ Sorry on the confusion, I thought he was telling me to get 4.2.2 that way. I understand now. Thanks.

Parafly said:
^ Sorry on the confusion, I thought he was telling me to get 4.2.2 that way. I understand now. Thanks.
Click to expand...
Click to collapse
considering you never mentioned you were using a toro device until just recently...
if you had a maguro device, my instructions were correct.
since you have a toro device, you need factory 4.1.1 and then apply the OTA.

Zepius said:
considering you never mentioned you were using a toro device until just recently...
if you had a maguro device, my instructions were correct.
since you have a toro device, you need factory 4.1.1 and then apply the OTA.
Click to expand...
Click to collapse
You are right I neglected to mention it. Thanks, going to give this a whirl now.

I am now a happy camper on 4.2.2.
Thanks!:good:

Parafly said:
I am now a happy camper on 4.2.2.
Thanks!:good:
Click to expand...
Click to collapse
good deal. glad you got it working.

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Flash factory image VZ wireless

Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app

treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?

cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks

treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)

cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes

treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?

cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options

treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?

cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures

treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?

cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes

treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.

cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes

treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.

cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted

I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497

zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.

joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.

OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.

i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days

Bad Signal? Update your Firmware or Modem and save battery.

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

T-Mobile Oreo FLASHALL???

Does anyone have a TMO Moto Z2 Force FLASHALL for the lastest OREO build?
I was on Oreo and i was testing a ROM in Devlopement and someone BASEBAND <not found> so i have no WiFi, no signal, but on a good note the ROM booted...
So any with an TMO OREO FlashAll, please share...
Thanks in advance

I haven't been able to find anyone or any place that has the latest TMO flash all available, but here is the update for the previous 8.0 update for TMO:
here

Shiro12 said:
I haven't been able to find anyone or any place that has the latest TMO flash all available, but here is the update for the previous 8.0 update for TMO:
here
Click to expand...
Click to collapse
Thanks but i need the entire build, not just the up date. I lost my MAC and IMEI and the full firmware is my only way of fixing it, i think

AndroidDevices said:
Thanks but i need the entire build, not just the up date. I lost my MAC and IMEI and the full firmware is my only way of fixing it, i think
Click to expand...
Click to collapse
That should be what you need, I came from a test build for Nash and used the FlashAll zip (RET specifically) from that site to take me all the way back to stock., Hence why each zip is ~3GB uncompressed.

Shiro12 said:
That should be what you need, I came from a test build for Nash and used the FlashAll zip (RET specifically) from that site to take me all the way back to stock., Hence why each zip is ~3GB uncompressed.
Click to expand...
Click to collapse
There is no FLASHALL in the file and i cannot get RSD to recognize device is in fastboot mode

extract This into the firmware's folder and adapt the bat file as needed

Shiro12 said:
extract This into the firmware's folder and adapt the bat file as needed
Click to expand...
Click to collapse
Thanks, flashed and still no baseband... wtf

AndroidDevices said:
Thanks, flashed and still no baseband... wtf
Click to expand...
Click to collapse
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue

Shiro12 said:
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue
Click to expand...
Click to collapse
I'm having the same issue. I've downloaded every 2+gb zipped XT1789-04 factory reset zip I can get my hands on. It says it's flashing a modem, but I still get no baseband when I go into fastboot. no wifi or cell signal. I've tried the commands linked above after flashing. If someone has a solution I'd be eternally grateful.

Shiro12 said:
There should be a NON_HLOS.bin in that folder, if im not mistaken a fastboot command posted here should fix that, but i should mention that i have not done this myself and can not vouch for it. maybe someone else has a more (for a lack of a better word) trusted way to fix your issue
Click to expand...
Click to collapse
Thanks but NO GO .

I ran into this problem attempting to root the latest Oreo OCX27.1 and got into a bootloop. The only Oreo firmware available to download isis the previous OCX27 and I believe that downgrading to that causes the lost of baseband and imei. I am waiting to see when OCX27.1 will be available to download so I can try to return to stock to 27.1 see if it restores my baseband

The problem i am seeing is that none of the stock firmware are for ocx27.1. they are all for ocx27. i have seen an ota update that is for the ocx27.1 but i have not figured out how to extract it yet

mattlowry said:
The problem i am seeing is that none of the stock firmware are for ocx27.1. they are all for ocx27. i have seen an ota update that is for the ocx27.1 but i have not figured out how to extract it yet
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/tmo-oxc27-1-oreo-firmware-t3757469

droidgreg said:
https://forum.xda-developers.com/z2-force/help/tmo-oxc27-1-oreo-firmware-t3757469
Click to expand...
Click to collapse
thats the ota. if you know of a way to extract the contents of the rom for that file i would love to hear it

mattlowry said:
thats the ota. if you know of a way to extract the contents of the rom for that file i would love to hear it
Click to expand...
Click to collapse
Open the file win Winrar or any Zip program and you should be able to extract the contents

droidgreg said:
Open the file win Winrar or any Zip program and you should be able to extract the contents
Click to expand...
Click to collapse
not exactly what im looking for. all of the rom contents are loaded in the payload.bin file. That is the file we need extracted

mattlowry said:
not exactly what im looking for. all of the rom contents are loaded in the payload.bin file. That is the file we need extracted
Click to expand...
Click to collapse
I tried daemon tools lite and PowerISO but both failed to extract the bin file. I'll keep looking...

droidgreg said:
I tried daemon tools lite and PowerISO but both failed to extract the bin file. I'll keep looking...
Click to expand...
Click to collapse
from what i have seen there is not a way to extract it currently

I'm gonna mess with it in linux. I'm no dev but I'll see what I can pull apart, hopefully I find something useful.

https://drive.google.com/file/d/13pKSMS5zGuYsr1EEDma0L6AxHDSUmu2g/view?usp=drivesdk