Is it possible to update the baseband only without reflashing the entire ROM. Can I update to a newer baseband without using an RUU package?
Thanks,
K
lasteveruser said:
Is it possible to update the baseband only without reflashing the entire ROM. Can I update to a newer baseband without using an RUU package?
Click to expand...
Click to collapse
Absolutely. Just flash a radio image. Most ROMs (other than RUUs and possibly stock ROMs), in fact, do not come with a radio image so your radio image will persist between ROM flashes.
See this thread: "[Radio][RIL]Flashable Radios with RIL files, Map, and AROMA Installer (Updated 8/13)" http://forum.xda-developers.com/showthread.php?t=1694012
Thanks
denversc said:
Absolutely. Just flash a radio image. Most ROMs (other than RUUs and possibly stock ROMs), in fact, do not come with a radio image so your radio image will persist between ROM flashes.
See this thread: "[Radio][RIL]Flashable Radios with RIL files, Map, and AROMA Installer (Updated 8/13)" http://forum.xda-developers.com/showthread.php?t=1694012
Click to expand...
Click to collapse
It worked perfectly. I was able to update to the 2.20 att baseband on CM 10
Thanks,
K
Related
Hey All,
This is my first post, and yes i have searched around xda to find an answer to my question, but nothing seems to suite exactly the response i am looking for, or better yet a solution.
I am currently trying to flash a custom rom however the rom comes packed with a radio in itself for my NEXUS S I9020A
My question is, I am satisfied with the radio i currently have, is there a possibility to flash a rom without the radio?
I tried unzipping the ZIP file and deleted the radio.img file that was in it. And re-zipped the file using my OSX standard zipping utility. However when i load it up and flash it through CWM, it says installation failed.
Any ideas or suggestions on how i could flash a rom by rezipping a ROM without radio?
i radio a required in order to make call and for data connection. why do you want a rom without radio?
luv2vexx said:
i radio a required in order to make call and for data connection. why do you want a rom without radio?
Click to expand...
Click to collapse
Most likely because he is trying to flash a rom that contains a radio that is not compatible with his phone. If the rom does not contain a new radio, the old one remains on the phone.
A lot of people are doing this to get ICS on their 9020a using a modified rom from the 9020t (minus the radio).
fobstar said:
Hey All,
This is my first post, and yes i have searched around xda to find an answer to my question, but nothing seems to suite exactly the response i am looking for, or better yet a solution.
I am currently trying to flash a custom rom however the rom comes packed with a radio in itself for my NEXUS S I9020A
My question is, I am satisfied with the radio i currently have, is there a possibility to flash a rom without the radio?
I tried unzipping the ZIP file and deleted the radio.img file that was in it. And re-zipped the file using my OSX standard zipping utility. However when i load it up and flash it through CWM, it says installation failed.
Any ideas or suggestions on how i could flash a rom by rezipping a ROM without radio?
Click to expand...
Click to collapse
Instead of messing with the custom rom zip file, why don't you just get the correct radio for your Nexus S I9020A phone from here: http://forum.xda-developers.com/showthread.php?t=1116884 then put both the rom zip file & radio zip on your sd-card & just flash the rom first then radio whilst in cwm recovery!?
Am I reading this right that the new radios that are part of the leaked JB update are not included in the ROMs based on the leak and that the radios should be flashed separately?
RandyGOP said:
Am I reading this right that the new radios that are part of the leaked JB update are not included in the ROMs based on the leak and that the radios should be flashed separately?
Click to expand...
Click to collapse
From what i understand you have to flash the new radio it doesn't come with the rom and if you want flash the new rpm also.
Bisyfxn said:
From what i understand you have to flash the new radio it doesn't come with the rom and if you want flash the new rpm also.
Click to expand...
Click to collapse
I can flash the new Jellywiz rls 12 just fine, but still trying to figure out what an "RPM" is. Can't find a simple explanation. The modem at least relates to the mobile data, still can't see if it's necessary to flash though.
if you flash the odin version of I5 jellybean it will include the rom, kernel, radio...however the previous root methods dont work and the bootloader is locked. im not sure if it can be unlocked yet. rpm is a power management update.
Yazzinit said:
I can flash the new Jellywiz rls 12 just fine, but still trying to figure out what an "RPM" is. Can't find a simple explanation. The modem at least relates to the mobile data, still can't see if it's necessary to flash though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1968632
Sent from my Galaxy SIII
Hi all,
I recently had a rooted phone phone and tried flashing another custom rom. It did't work and put me in a bootloop. I've flashed the right kernel and tried different roms as well as wiping my phone. Flashing the stock recovery and full wiping. I don't know what else I can do. And I also can't seem to find the right RUU for my device, Villec3 RADIO-16.05.20.24_M.
If anyone has any links or anything to help that would be great.
Need your device's CID number to find the right RUU. If you can't find the right RUU, try flashing TWRP 2.2.1 villec2 recovery, it seems the most reliable and then flash Trickdroid's v2.0.0 (C2) rom following instructions carefully. Your radio is from an older stock rom so you can't flash a newer rom like TD v4.0.0 (C2).
farang4u said:
Need your device's CID number to find the right RUU. If you can't find the right RUU, try flashing TWRP 2.2.1 villec2 recovery, it seems the most reliable and then flash Trickdroid's v2.0.0 (C2) rom following instructions carefully. Your radio is from an older stock rom so you can't flash a newer rom like TD v4.0.0 (C2).
Click to expand...
Click to collapse
My CID is OPTUS001, and I'll try TD 2.0.0
Works great thanks for that!
But I don't seem to have a notification bar
Did you flash the tweaks too? Sometimes that messes with the notification bar. Try flashing TD v3.0.0 (C2) since you now have v2.0.0. Don't do any wiping per the instructions. TD v3.0.0 has a number of fixes over v2.0.0.
farang4u said:
Did you flash the tweaks too? Sometimes that messes with the notification bar. Try flashing TD v3.0.0 (C2) since you now have v2.0.0. Don't do any wiping per the instructions. TD v3.0.0 has a number of fixes over v2.0.0.
Click to expand...
Click to collapse
I didn't flash any tweaks but I'll try 3.0.0
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command
fastboot getvar version-main
Click to expand...
Click to collapse
and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
chaoscreater said:
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
Click to expand...
Click to collapse
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Edit: It is not causing any problem as your actual firmware is same. You can flash any ICS/JB rom with this firmware. No need to flash firmware before flashing ROM.
Sent from my Sensation
MrJukeHardbane said:
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Sent from my Sensation
Click to expand...
Click to collapse
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
chaoscreater said:
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
Click to expand...
Click to collapse
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
MrJukeHardbane said:
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
Click to expand...
Click to collapse
Well, I'm the exact same with you, I could still flash JB or ICS custom roms even though mine says 1.24.401.
However, I read somewhere that it's not accurate to check under Settings for the firmware version as it could have been edited in build.prop. The safest way to check is to put your phone in fastboot mode and run the CMD command:
fastboot getvar version-main
Click to expand...
Click to collapse
I read that today and decided to check it again to make sure, and my firmware version comes up as 1.24.401. I then decided to flash the 3.33 firmware again, this time after running the same fastboot command, I get the proper firmware version shown as 3.33.xxx.x (can't remember what it was).
So ya, I think something must have went wrong....
I everyone, i have a problem with GPS. Now i am on CM12, baseband 1.15, but i tried also Liquidsmooth and CM11, with baseband 1.20. With every ROM the same problem: GPS finds me, but it freezes me in the position; and Google Nav (or Waze) finds the itinerary but then it doens't move the cursor.
How can i resolve? Reflashing the 2.16 firmware?
Thanks in advance.
No one?
Kin93 said:
No one?
Click to expand...
Click to collapse
Are you using the latest version of TWRP? One person here had issues with GPS, and solved reflashing the rom after updating the recovery. I had issues with GPS which were gone once I moved to CM11. I have 1.15 baseband and hboot 2.15.
Fiabeschi said:
Are you using the latest version of TWRP? One person here had issues with GPS, and solved reflashing the rom after updating the recovery. I had issues with GPS which were gone once I moved to CM11. I have 1.15 baseband and hboot 2.15.
Click to expand...
Click to collapse
Yes, 2.8.1.1.
Maybe i would try to downgrade hboot and see if something will change.