I recently flashe p.a and im suspecting some issues with my signal. So the question is. Does flashing another rom alter your radio? And will coming back to stock rooted via nandroid bring back the old one?
Sent from my Nexus 4 using xda app-developers app
No.
Edit: Let me clarify. The radio resides in it's own partition, which goes untouched during a ROM install. There are, however, rampant data drop issues on many devices. However, as I understand it, if you get them, they happen on stock as well.
estallings15 said:
No.
Edit: Let me clarify. The radio resides in it's own partition, which goes untouched during a ROM install. There are, however, rampant data drop issues on many devices. However, as I understand it, if you get them, they happen on stock as well.
Click to expand...
Click to collapse
estallings15 is correct, but he is also talking about flashing a ROM by itself. If you flash a package that includes a ROM, it could potentially contain a different radio as well.
hoponpop said:
estallings15 is correct, but he is also talking about flashing a ROM by itself. If you flash a package that includes a ROM, it could potentially contain a different radio as well.
Click to expand...
Click to collapse
How many of those have you seen that contain paranoid android for the Nexus 4?
Edit: Yes, I saw the word potentially.
And how can i check what version radio is on my phone. Sorry but i havent tinkered with radios. Only roms and kernels and that is on a basic level
Sent from my Nexus 4 using xda app-developers app
nexus is region free so you shouldn't worry,
when you flash official roms from other regions with carriers then it can change it, user roms shouldnt include the baseband unless its updated by google.
radios are the baseband in /about phone.
Related
I have a question, that I've had trouble finding the answer to.
Is there a need to flash a new radio to my phone? Are there benefits to flashing a new one?
I currently use my N4 with Straight Talk (AT&T).
Thanks.
wvcadle said:
I have a question, that I've had trouble finding the answer to.
Is there a need to flash a new radio to my phone? Are there benefits to flashing a new one?
I currently use my N4 with Straight Talk (AT&T).
Thanks.
Click to expand...
Click to collapse
Depends. If you are updating your rom to 4.2.2, it's probably a good idea to flash the corresponding radio as well. If you are on 4.2.1, there are reports of incompatibility with 4.2.2 radio, so don't update. Otherwise, different radios may give you better signal/connection speeds, but it's hard to say.
Also, 4.2.2 radio disables lte, but since you're on straight talk it doesn't matter.
Do the ROMs not flash the appropriate radio for the android version? I updated to 4.2.2 before flashing MoDaCo, so do I have the correct radio?
Sent from my Nexus 4 using Tapatalk 2
wvcadle said:
Do the ROMs not flash the appropriate radio for the android version? I updated to 4.2.2 before flashing MoDaCo, so do I have the correct radio?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No, ROMs generally contain only the kernel and system images. Updated bootloader and basebands need to be flashed separately.
Edit: The above applies to custom ROMS. If you flashed stock 4.2.2, you may have the updated radio. You can check by going into settings->about phone->baseband version. For 4.2.2, the number should end in 48, 4.2.1 ends in 33.
halluci293 said:
No, ROMs generally contain only the kernel and system images. Updated bootloader and basebands need to be flashed separately.
Edit: The above applies to custom ROMS. If you flashed stock 4.2.2, you may have the updated radio. You can check by going into settings->about phone->baseband version. For 4.2.2, the number should end in 48, 4.2.1 ends in 33.
Click to expand...
Click to collapse
Great. So I do have the correct one for 4.2.2. Are there different versions for the same ROMs, or do we only need to make sure we have the correct radio for the version of android we have?
Sent from my Nexus 4 using Tapatalk 2
wvcadle said:
Great. So I do have the correct one for 4.2.2. Are there different versions for the same ROMs, or do we only need to make sure we have the correct radio for the version of android we have?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Radio and bootloader version are generally linked with your Android version. AFAIK, no one makes custom radios/bootloaders, so they're always stock.
halluci293 said:
Radio and bootloader version are generally linked with your Android version. AFAIK, no one makes custom radios/bootloaders, so they're always stock.
Click to expand...
Click to collapse
No one make custom radios/bootloaders because they're closed source. Its impossible to make a custom radio/bootloader unless you are LG/Google (and its respective manufacturers for that phone).
Let me start by saying I know I have asked a few questions lately and I really appreciate the help. I am brand new to the nexus and don't want to brick it. I don't got money to just get another if I break it so I am being very careful with what I flash.
That said, I am planning to update my radio and I have read a few threads with regards to the topic. I found most of what I needed to know. My problem is I read a lot of posts saying it "broke" sensors or WiFi when flashed with the 4.2.1 Roms. Now it also goes on to say that 4.2.2. works fine with the newest radio, but i also seen where some were using a older radio (.27 I think it was)
Question 1- Can I use the .27 radio with the newest roms or is there a reason I need to use the .48 radio? Reason being the newest radio disables lte connectivity. Maybe the .27 keeps it?
Question 2- do I need to flash the new bootloader with the radio?
Sorry to act like a noob but with my older g-1 flashing the wrong radio and SPL could brick the device. So once again I am just trying to make certain I am taking the right steps. Thanks in advance...
Sent from my Nexus 4 using xda premium
Question 1:
Some people lose audio on phone calls when running the older radios on 4.2.2, but CyanogenMod 10.1-based ROMs work fine with .33 or .27 basebands, at least in my personal experience.
Question 2:
Not sure if there is some interplay between the bootloader and whether the radios work on 4.2.2. Haven't heard of there being any issues in this regard.
Sent from my Nexus 4 using Tapatalk 2
Yeah I would figure the cm variants would be coded for all different radios . I just didn't know if anyone out there knew the exact differences in radios and bootloaders. I have read so many posts and still can't get a really clear explanation.
Sent from my Nexus 4 using xda premium
selfinflicted1 said:
Yeah I would figure the cm variants would be coded for all different radios . I just didn't know if anyone out there knew the exact differences in radios and bootloaders. I have read so many posts and still can't get a really clear explanation.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I flashed .33 radio on 4.2.2 in order to keep using LTE here in Mexico. Phone works fine, haven't had any issues with it so far.
pacoguevara said:
I flashed .33 radio on 4.2.2 in order to keep using LTE here in Mexico. Phone works fine, haven't had any issues with it so far.
Click to expand...
Click to collapse
So you're using CM 10.1 with Radio .33 without issues and maintaining LTE/4G connectivity?
If so is it the latest nightly?
I was under the impression that the 33 radio caused all kinds of problems with 4.2.2. Are you sure you aren't on 4.2.1? Its crazy because I seen a lot of posts saying that they never updated but everything worked right on 4.2.2. I really wish someone could shed light on this issue.
Sent from my Nexus 4 using xda premium
selfinflicted1 said:
I was under the impression that the 33 radio caused all kinds of problems with 4.2.2. Are you sure you aren't on 4.2.1? Its crazy because I seen a lot of posts saying that they never updated but everything worked right on 4.2.2. I really wish someone could shed light on this issue.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
+1
Sent from my Nexus 4 using Tapatalk 2
Apparently the issue with CM 10.1 and the older radio is you lose autofocus in the CM camera (for example, might be more issues). Now, being in the UK, I have no need for the old radio as we don't have proper 4G here yet so I'm all 100% up-to-date and it works fine. Once 4G comes about I'll get a 'proper' 4G phone
Is there any way to get the s4 camera app to work on a nexus 4? And how can I get it to work? I downloaded the stock s4 rom, found the camera app, tried to install it and it didn't work. I wasn't surprised though lol. So is there a way to get it to install?
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
chromium96 said:
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
Click to expand...
Click to collapse
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
NuckFuggets said:
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
Click to expand...
Click to collapse
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
I don't know about brick, but it would definitely not boot.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
NuckFuggets said:
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
Click to expand...
Click to collapse
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
exb0 said:
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
Click to expand...
Click to collapse
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
NuckFuggets said:
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
Click to expand...
Click to collapse
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
exb0 said:
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
Click to expand...
Click to collapse
Oh I see. What if the two phones have the same hardware? Then would you be able to?
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Oh ok. That sucks :/
NuckFuggets said:
Oh ok. That sucks :/
Click to expand...
Click to collapse
That's why each device on XDA has their own little section call home.
Sent from my Nexus 4 using Tapatalk 2
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Probably the way they chose to assign the partitions on the device. It would be nice if there was a standard that everyone followed, but oh well.
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
rayiskon said:
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
NuckFuggets said:
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
Click to expand...
Click to collapse
in that case it shouldn't be called a Nexus anymore
I am interested in enabling T-Mobile LTE on my N4. Does it work smoothly like any other LTE enabled phone? In my research, I've found that there are two different zip files to flash. Which one has worked best for people? It appears that enabling LTE is a simple flash of the zip file. Am I correct? Thanks.
This has been covered thousands of times. But before this thread gets deleted, let me help you out. LTE on tmobile or att works flawlessly.
http://forum.xda-developers.com/showthread.php?t=2358931
im using the 98-33 radio on tmobile and have had 0 problems. you can find it here
http://forum.xda-developers.com/showpost.php?p=48224173&postcount=882
just flash and forget it. it should work! good luck
Do I need to update the radios after every software update or can I just flash once and forget it?
Since this will get deleted anyways, I will ask the stupid question I have. Bone stock 4.4.2 soon to be rooted with TWRP. Can I flash with a stock ROM and still make a wifi hotspot? I see something about needing init.d support or something like that.
ILowry282 said:
Do I need to update the radios after every software update or can I just flash once and forget it?
Click to expand...
Click to collapse
No need to flash again.
SKYLINESSUCK said:
Since this will get deleted anyways, I will ask the stupid question I have. Bone stock 4.4.2 soon to be rooted with TWRP. Can I flash with a stock ROM and still make a wifi hotspot? I see something about needing init.d support or something like that.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 4 using xda app-developers app
I flashed the file. However the instructions state to change the network mode. I don't even see that option in the settings. I'm currently on 4.3
*#*#4636#*#* in dialer
Sent from my Nexus 7 using XDA Premium 4 mobile app
ok so i have installed JellyBeans rom and im not liking it. im on base version JSS15J.N900VVRUBMJE.
how do i get back to the most updated stock rom on note 3?
Am assuming that you are using SafeStrap. If so, boot to recovery. Go into boot options and activate the "stock" slot. Then, if you want to, you can go in and delete rom slot that you have beans installed on.
Once you activate the stock slot, you'll know it because it will tell you with red text across the top of the screen.
Then just reboot.
IF YOU INSTALLED BEANS ROM ON THE STOCK SLOT, you need to download a copy of the stock odex or deodex rom that beans put together in the dev thread. If this is the case, let us know if you need help before going any further!
♢NoteIII♢
Yes I made a new slot for beans and still have the stock one open. Thanks ill just use the stock slot. Now what about me getting the latest updated stock rom and still keep root, how would I do that?
Sent from my SM-N900V using XDA Premium 4 mobile app
spetzuu said:
Yes I made a new slot for beans and still have the stock one open. Thanks ill just use the stock slot. Now what about me getting the latest updated stock rom and still keep root, how would I do that?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So the rooted rom on your stock slot is what version?
♢NoteIII♢
LeftyGR said:
So the rooted rom on your stock slot is what version?
♢NoteIII♢
Click to expand...
Click to collapse
MI9
spetzuu said:
MI9
Click to expand...
Click to collapse
Eh...
Best way would mean you'd need to redo root. And that way would be with odin. Unless someone else has a better way?
♢NoteIII♢
ive tried finding out the benefits of the updates that have rolled on on the note 3 and i cant seem to find any... although i have seen people complaining about the battery life and what not.
do you know where i could get a complete list of what the updates bring to phone? because if its nothing major ill just stick to MI9
Honestly, it will be different for every person. Because even though we all have the same phone, Every Phone is just a little different. For example, I am on the current update and felt I needed to because I was having issues with wifi. But if you are on the original firmware, which you are, and you can find no problem with your phone that you would like to see fixed then I honestly don't see any point in updating your firmware if you do not want to. I know that the current version addresses problems people were having with wifi. Along with some other minor changes.
Now having said that... If you encounter any quirks or problems with any current custom ROMs that are listed in the development section, it may be due to the fact that they are built on the current firmware version while you are still two versions behind.
♢NoteIII♢