Related
If i return to the desire rom From Froyo, and use nandroid backup, does it make a complete rom image including the radio?
where is there a tutorial on how to flash your radio, and which radio us the best for the desire rom..
No, it does not back up the radio. Flashing the radio is a dangerous business (as is going out your front door, but that's another story), and it would be not-good to be reloading the radio along with the backup everytime something got screwy.
To restore your radio, you would need to pull the radio image out of a zipped ROM - a stock one, or another one that includes that same radio image.
It seems like every person has different experience with different radios, so asking which one is the best isn't really going to help you out too much.
ok, that makes sense...
"If" i decided to go back to the desire rom, can some of you who are running it plet me know your opinions on which radio to flash back to so i can load the ROM. what are the proper steps?
thanks
Hello,
For the past few days i have been trying to find an answer to my question but so i've come up short. With regards to loading a custom rom, what is the process of ensuring that the correct radio image gets loaded as well? I have went as far as modifying my stock rom with dsixda's kitchen (great by the way, very easy to use), but I have not figured out what to do with the radio.img. I incorrectly assumed that it would be retained in the build, and now I'm a bit worried to try it until i know for sure where it needs to go.
Thanks for all your help,
Flashing a new ROM doesn't affect the radio at all. You could change your ROM 6 times per day and still have the same radio.
I'd say your best bet is to search around the forum and find one of the flashable .zips for whatever radio you want. They are out there cuz I remember doing that a while back. As long as you flash one meant for CDMA (DO NOT FLASH A GSM RADIO!!!) you should be fine.
Here's the one that a lot of us are using right now, the newest Radio that came in Sprint's 2.1 Stock release: http://forum.xda-developers.com/showthread.php?t=681703
Ok well that makes sense. I would use that radio, but I don't have a sprint device, so unless I am completely lost I should just stick with what I as my radio image. I have just gotten a bit confused with all the talk about using sprint rom's in non-sprint phones and losing the ability to make/receive calls,data, ect.
Just so I am clear, as long as I am clear, since I modified my stock rom to add root, wifi tethering, blah blah; the radio will be fine. So essentially, loading my rom would have no more effect on the carrier files than a master reset would. Am I over simplifying it?
Thanks, you are the first person is 5 different forums that explained this to me.
Ok yes, you shouldn't flash a Sprint radio if you're not on the Sprint carrier. Your provider may not recognize it and your phone might not even get signal.
And yes you're also correct that adding root, wi-fi tether, and other such apps/mods will not have any effect on your radio at all. The radio is basically just what the phone uses to receive its signal from the tower. It's like you said...if you're not having any signal/data problems, you really don't need to worry about updating your radio.
Finally, you're also correct in that you shouldn't flash a Sprint-based ROM to your phone if you're not on Sprint. The frameworks and operating files are built somewhat differently in other providers ROMs, so a Sprint-based ROM on your non-Sprint phone likely wouldn't even work.
There are other ROMs for a few other carriers out there in the Development forum. Browse around there to see if one of those will work for you.
Sounds like you understand it all just fine
Thanks, I went ahead and took the plunge and loaded my own rom and it worked flawlessly, well with the exception of my custom boot screen image and the boot sound. I guess I need to just take baby steps I guess. Does anybody know where I can get some get directions on creating custom bootup features? I read somewhere all I needed to do was open the media folder and edit the images as I see fit. It seemed easy enough, but on startup, the screens froze and I got no sound. It did load all the way but I would like to correct this if possible.
Thanks again
A somewhat basic boot animation tutorial (that doesn't seem really good in my opinion, but a good start at least): http://forum.xda-developers.com/showthread.php?t=639471
Some boot animation instructions: http://forum.xda-developers.com/showpost.php?p=6651435&postcount=2
Boot animation preview tool: http://forum.xda-developers.com/showthread.php?t=676385
There's lots more stuff out there if you search the forum for "boot animation". Looks like some ppl just modify existing boot images to their liking rather than completely building from scratch.
Thanks, I will give them a try. I am still a little afraid to try some of the tried and true custom roms out there for fear of incompatability with my radio, so I am gonna work with what I got and continue to work on my own. Thanks again for all your help
chromiumleaf is totaly right, if your not real familiar with flashing radio's stick with the one your carrier provided a wrong radio flash can brick your phone quick.
for the boot animations when cooking them into your roms, copying and pasting your new bootanimation into the /system/media folder in your working directory, and leaving the option in the kitchen unchecked will give your better results, also here's some more info that might be helpful in building them.
http://forum.xda-developers.com/showpost.php?p=7574576&postcount=12
Just make sure u delete the bootanimation.zip file in the media folder before u add ur boot animation cause the zip will always over rule ur animation.
I was able to get my gps working real good after flashing to stock gingerbread 2.3.4. I am rooted but did not feel like going through all of the steps for flashing any roms so I searched and searched and finally was able to fix it.
This is simple for those with clockworkmod but for those like me that can not use it this was successful for me. Also, I cannot take credit for any of this I am just providing a simple step by step for those who want it, since none of this fix or even the grouping of files was done by me.
follow this link and dl GPS_Fix_Dlev4.2.zip
http://forum.xda-developers.com/showthread.php?t=1146176&page=154
I believe that with clockwork you can simply flash it but I cannot use cwm so I can not say for sure.
I was unable to rename it to update.zip and install it so i manually moved the files to my phone using root explorer.
first i replaced the gps.conf with H3llstorm's
so copy and paste the gps.conf in the /system/etc folder to your /system/etc folder on your phone.
Than I copy and pasted the vendor folder found in /system to my /system folder...../system/vendor did not exist.
After that I rebooted and went from 88 seconds to lock on 3-6 sats, but unable to maintain a lock while driving, to 9 seconds to lock and maintain a lock on 7-9 sats. I tested it on a 30 min drive through local and highway roads and it was constantly locked on. I stopped it at the end restarted nav, relocked quickly and came home with it working smoothly, I also purposely veered off course to see how it would react and it quickly re-routed.
I think the big change is the gps.conf, that h3llstorm made, good looks, and am not really sure if the vendor folder does anything but it worked so i recommend trying it anyway. The 88 seconds i was referring to was also with the gps.conf file found at
http://www.darkyrom.com/community/index.php?threads/guide-gps-quickest-fix-solution.2022/
It did not seem to do anything for me. This is not really a question but I am relatively new here so I cannot post a thread in the development section. I hope this helps anyone that does not want to flash anything more than stock gb.
I like the idea... the question is do we have to have 2.3.4 stock? Or will it still work with a 2.3.3 modded rom?
kralco626 said:
I like the idea... the question is do we have to have 2.3.4 stock? Or will it still work with a 2.3.3 modded rom?
Click to expand...
Click to collapse
He took the fix from Dlev 4.2 which is a modded (reoriented) rom. If u ask if it's for stock cappy based roms only, I would say it's not. Stock roms come withOUT any gps aid and so it's hit or miss thing, while in modded roms the chefs usually have a fix backed in their roms. I'm guessing that's y he pointed out that the fix is recommended for those who are on stock, but no matter what rom your on feel free to experiment.
Sent from a captivated SensatioN
Yea he`s right i just said stock because i assumed the rom would have it preloaded, from what ppl have told me its worked with every version of gb regardless of rom or not. Also i was alluding to the fact that i with stock cant use cwm.
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?
Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
bobdole said:
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
Click to expand...
Click to collapse
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
useltonm said:
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
Click to expand...
Click to collapse
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
bobdole said:
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
Click to expand...
Click to collapse
The bottom one is definitely the correct one for jb on the bionic.
Let me check something and I'll get back to you.
Sent from my XT875 using Tapatalk 4
---------- Post added at 01:32 AM ---------- Previous post was at 01:26 AM ----------
I was going to suggest trying the house of bionic, but it looks like you already went there.
Sent from my XT875 using Tapatalk 4
Can anyone help?
I'm trying to do an experiment to flash just the latest JB bp.img and lte.img (radio files) in stock recovery.
When I do it it fails on package validation.
I found some older 902 and older radio files, those do not fail package validation, but fail to flash.
I assume they fail because of security(no going back to older version).
I need some to help package the bp, lte.img files into a zip. I tried the signapk tool. It seems to generate all the manifest files, but somehow the files do not pass package validation.
I tried taking the 902 radio files that pass package validation and run them through signapk, and sure enough they would fail package validation after signapk.
Can anyone help, please!
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi cellzealot,
I really appreciate your help. I tried flashing your file, but I get the same error as when I flash for full JB update file, which is:
assert failed: motorola.motoflash("/tmp/bp.img")
I was wondering if you could do one more thing to help..
Since it's failing assert, what if we modify the script to no do a assert check, but just run the command?
This is the update-script:
assert(show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img"));
What if we make it like this:
show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img");
I'm hoping that this might work.
BTW, how did you package the zip file and sign the files?
The original zip file had lots other system/boot files.
Thanks!
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
cellzealot said:
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
Click to expand...
Click to collapse
Thank you for your explanation.
I was able to find the radio.img file from the OTA xml.zip for fxz.
Indeed, if I open the radio.img I find the update_radio.zip that you have provided.
What I don't quite understand is why we are able to flash various custom roms that are not signed by motorola through CWM, TWRP.
Would there be a way to run a modified update_radio.zip through CWM, TWRP?
"Now to" needed
cellzealot said:
....... link removed because it won't let me post with it in here.......
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
Click to expand...
Click to collapse
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
RichT1 said:
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
Click to expand...
Click to collapse
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
http://www.droid-life.com/2011/09/2...boot-menu-for-recovery-sbf-flashing-and-more/
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
bobdole said:
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
.... link removed .....
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
Click to expand...
Click to collapse
Thank you.... worked like a charm....:victory:
I'm literally a real noob when it comes to this stuff.. But when I tried to flash the radio files from above via recovery, I got this error.
assert failed: motorola.motoflash("/tmp/lte.img")
I've lost my lte baseband way before trying this, I've actually lost it, running a Carbon nightly rom.
EDIT
I've changed the updater script and now I'm having a problem with it aborting the installation alltogether. Any help would be greatly appreciated. I just want to get my LTE radio working :|
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi CellZealot,
Do you have radio.zip file(s) from GB versions by any chance? I'm on ICS and want to try GB radio(s) hoping to get better signal strength and possibly enable 900/1800mhz band if it's disabled in ICS radio. I'm still experimenting to get my Bionic (Hw A, 08/12) to work on 900/1800mhz.
Is Droid Razr also MDM6600 Motorola device? If yes, can I try and get its radio and flash on Bionic? Please advise.
Thanks.
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
Thanks a lot CellZealot. You're a gem!!
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
I tried flashing a couple of radios from that zip file via recovery and the update was successful each time. I did NV edits, buildprop changes and the factory data reset each time. But when I checked the Baseband version info, the LTE component was missing e.g..it only shows CDMA_N_04.07.02R. I suspect somehow LTE part was not flashed via recovery even though no error was shown. Also IMEI and SV show up unknown as well. Did I miss some step or did I do something incorrectly? Please advise.
Thanks in advance.
P.S. I didn't rename the radio zip file to update.zip. Just used the files as is from the above zip. I'm trying to use them on ICS, These GB radios aren't fully compatible with the ICS version kernel or something?
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
I have been working on my bionic for months.
Casey Walt said:
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
Click to expand...
Click to collapse
This all started back in december 2013. a buddy gave me a bricked bionic.. i was able to "unbrick". and install the 98.72.22 fxz. i only get service half of the day and 3g like maybe 30min...i also have the error where the lte.img will not install. Thus please explain more as to how you were able to fix it. Do you have 4g? i haven't been able to restore it. i had to splice a usb cord and attach the pos and neg to the battery and connect a charging cord from the phone to my desktop to get a led response from the phone during the unbricking process. basically if i install a new rom daily i have steady service all day.. 3g even. but then it just craps out on me. believe me, im not giving up on this phone until i see a 4g icon on my status bar.
I have an S3 now but i can still glady help you.... what i did was put a shim in my sim card holster. then put the .905 radio in the fxz folder and flash it again... you wait like 5-10 min till you have service ( if you did it right there should be no lte in the baseband yet) then put the zip file for the 4.1.2 radio on your sd card and flash it through stock recovery. when you boot your phone up you wait 5-10 min again and you should have both 3g and lte in your baseband
Sent from my SCH-I535 using xda app-developers app