As the title goes guys.
Just a little confused regarding what I have read.
As I understand it I have to download my chosen new radio and put that file in the same folder as the ROM updater thingy.
Then run ROM.exe as normal and it should update with the new radio as normal without me doing anything. I mean update while flashing the new ROM.
Roy.
You can update the radio separately from the OS and it will not give you any problems. But if you subsequently update the ROM again, a radio may be included, so you would have to do the process over if you wanted to change the radio again.
replacing cellular radio without unlocked bootloader?
TomInMB said:
You can update the radio separately from the OS and it will not give you any problems. But if you subsequently update the ROM again, a radio may be included, so you would have to do the process over if you wanted to change the radio again.
Click to expand...
Click to collapse
sorry, could you elaborate a bit? I am desperately trying to change my radio (to make it usable on another network), but bummed out completely (locked bootloader) due to "latest" update xxx 254_13 (Android 2.3.5)...
I'd donate to the first one to help me with it...
I am rooted and have been wondering if I could not do it "somehow" during a "bootstrap update"...?
Edit: Oh, this is for HTC ... I am with Photon 4G Motorola... any help?
Ok I'm new to rooting and flashing so I have a few questions that I'm pretty sure are basic but I just don't want to brick my phone. 1.when flashing a radio Rom do you wipe before flashing? 2.when you flash a custom Rom do you flash the radio before or after the custom Rom and do you have to flash the radio every you flash a custom Rom? 3.how do you make a backup of your stock radio before flashing the new one?
4. Are there specific radio roms for different custom roms or can you use the same radio for all custom roms? Thanx a lot.
-------------------------------------
Sent via the XDA Tapatalk App
Can't back up your radio. Flash a radio, and it may give you better signal, it may give you worse signal. it may boost your battery to 100 years, it my kill it in 5 minutes.
It's all about your towers, how far away you are, what kind of signal it's getting. You might get a radio that gives you full signal at home, but none at work.
make sure you have the right radio for your phone!!!!!!!!
The radio and Rom are seperate.. can be done anytime from each other.
recommendation: dont mess with the radio yet... make sure you are having issues with the current radio before you try to update it. I still have not got the never up to touch the Radio. I flash ROMs all the time. Read on Radios.. there has been a lot of issues. Some are big issues!!!!
how do i unroot from cynanogen 4.2.17 back to 1.6 without haveing to resign in? i dont have data on my phone and and how do i do this with doing a full wipe. thanks
The only way to completely unroot is to flash NBH wich will wipe your phone and you will have to resign. Non-rooted users don't have the luxury of running the phone without signing in. May I ask, what are you trying to accomplish?
im having some texting problems with cyan, so i have to go back to rc29 and sign in with the hack and then to 1.5 and 1.6?
any easier way?
my question is where did you get 4.2.17 considering development on CM-4 stopped at 4.2.15.1? my recommendation would be to get off of a version that doesnt exist and upgrade to CM-5.
my bad wrote the wrong version, is cm-5 still haveing problems?
nahanee20 said:
im having some texting problems with cyan, so i have to go back to rc29 and sign in with the hack and then to 1.5 and 1.6?
Click to expand...
Click to collapse
Also what are the texting problems? Maybe there is a fix.. or just wiping + erasing your ext partition.
Otherwise I think (but have never tried) you can install rc29 + manually apply the two ota updates and be at a version of android where you can skip the login and login when using wifi. If you do this for non warentee reasons however I strongly recommend never rooting your phone again.
(OK I also give exceptions to developers that require to test something in a particular android build.. but they probably want to use and keep a engineering spl)
Have you considered going to stock adp1 firmwares they have the img file that if you unzip and flash userdata/cache/system/boot images via fastboot will put you on that rom without loosing your current bootloader or custom recovery? requires an engineering spl. (I support using custom Tom's after this process as well)
and how is it different from a regular image? I'm asking this since I'm still relatively new to this and learning all this custom stuff as I go on.
It is just the baseband, doesn't change the part of the software you interact with.
What is baseband?
I believe its the part of the phones firmware that provides the communication with the antenna (GSM (radio), wifi, bluetooth) and camera side of things.
So, there's still a question: what's a ROM w/ and w/o a radio? It cannot be that one is without a baseband
Deusdies said:
So, there's still a question: what's a ROM w/ and w/o a radio? It cannot be that one is without a baseband
Click to expand...
Click to collapse
Sure it can. And that is exactly what it is.
Deusdies said:
So, there's still a question: what's a ROM w/ and w/o a radio? It cannot be that one is without a baseband
Click to expand...
Click to collapse
It can. W/O rom will update the ROM and leave your radio untouched. W/radio will update the rom and the radio.
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?