I'm on CM11, Snapshot M3 build, running HBOOT 1.33 and using the 1.01.04.0308 baseband/radio. I've been fighting my PC the past two days trying to get Fastboot to be recognized under Windows 8.1 without success (my relationship with 8.1 has really been a love/hate situation ever since I've upgraded), and I've been wondering - would it really be worth the hassle, to begin with, to upgrade the hboot and/or the radio?
I've heard mixed opinions about the latest radio - as it has killed the data speed for some, but has helped others. I'm using Verizon, and with CM11, I haven't had the greatest speeds or connectivity (not necessarily a ROM issue, I'm sure). I've also been experimenting with Viper4Android, which I think is actually pretty great, except I get some strange "robotic-sounding" hangs in the audio when, I'm suspecting, the WiFi radio is connecting, or the cell radio might be swapping towers or something. Though now I'm beginning to wonder if it might just be a governor issue. Sorry that I'm just speculating here, lol. But this is the main reason I'm thinking about trying different firmware.
What do you guys/gals think? Would there be a worthy difference in upgrading one or the other? I've read that upgrading the hboot has helped Win 8.1 users...but isn't fastboot needed in the first place to do that?
Any suggestions appreciated. :good:
supertoast92 said:
I'm on CM11, Snapshot M3 build, running HBOOT 1.33 and using the 1.01.04.0308 baseband/radio. I've been fighting my PC the past two days trying to get Fastboot to be recognized under Windows 8.1 without success (my relationship with 8.1 has really been a love/hate situation ever since I've upgraded
I'I've read that upgrading the hboot has helped Win 8.1 users...but isn't fastboot needed in the first place to do that?
Any suggestions appreciated. :good:
Click to expand...
Click to collapse
the real issue is 8.1 drivers. There are threads dealing with the issue, do they solve it? I don't know, I use 7.
The radio maybe it might help, try it. As far as I know the only reason for changing H-Boot would be for running an Ruu
The solutions work for some people, but the most successful one appears to cause loss of USB functionality for some. I've tried a VM running Ubuntu, but I guess that since my desktop isn't connecting natively, a VM won't help either (Ubuntu gives a device enumeration error upon attempting to connect). I could be doing something wrong using VMware though.
Sent from my HTC6435LVW using Tapatalk
supertoast92 said:
The solutions work for some people, but the most successful one appears to cause loss of USB functionality for some. I've tried a VM running Ubuntu, but I guess that since my desktop isn't connecting natively, a VM won't help either (Ubuntu gives a device enumeration error upon attempting to connect). I could be doing something wrong using VMware though.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
How about putting Linux on a cd and working from that?
RLGL said:
How about putting Linux on a cd and working from that?
Click to expand...
Click to collapse
True, I'll have to try that. I'll let you know how it goes.
A much delayed update, but I managed to get my hboot up to 1.54 and the radio to the latest as well, using my Ubuntu partition on one of my machines. Emulation under Win 8.1 didn't seem to work. Drivers still don't work under fastboot in Windows 8.1, for either USB 2.0 or 3.0. Hopefully HTC fixes this in the near future...
Related
Can anyone do ROM upgrades/downgrades successfully with Vista.RC2.5744? (regular roms or Radio roms)
Maybe pof could explain this one?
DeviLduck said:
Maybe pof could explain this one?
Click to expand...
Click to collapse
I'm sorry... I don't have Vista and have no idea how is it different from winXP.
I use linux.. and I always do sd-card flashing to flash new roms so I don't have to reboot
pof said:
I'm sorry... I don't have Vista and have no idea how is it different from winXP.
I use linux.. and I always do sd-card flashing to flash new roms so I don't have to reboot
Click to expand...
Click to collapse
I have to use my XP box for ROM manipulation on the TyTN. I am assuming this feature is not high on the beat priority list for WMDC.
Vista does NOT work at all for upgrading ROM's. It will go through the connection first, but when it gets to the bootloader, it refuses to reconnect after that, and the installer times out. Only way to do it is with XP/Server 2003. They will fix that in the final build of the WM Device Center.
I have the final the rtm version and it still not works. Try killing mobsync.exe and wmdc.exe and the firewall MSASCui.exe I then got the upgrade menu that shows the current version and the upgrade versions.
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Messed_sensation said:
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
es0tericcha0s said:
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
Click to expand...
Click to collapse
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Messed_sensation said:
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Click to expand...
Click to collapse
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Thank you for all your help and suggestion:good:. I am now running the Android Revolution HD.
This is a huge change from my iphone 4.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Messed_sensation said:
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Click to expand...
Click to collapse
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
es0tericcha0s said:
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
Click to expand...
Click to collapse
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Messed_sensation said:
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Click to expand...
Click to collapse
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
es0tericcha0s said:
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
Click to expand...
Click to collapse
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Messed_sensation said:
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Click to expand...
Click to collapse
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
es0tericcha0s said:
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
Click to expand...
Click to collapse
I think it is my battery. I picked up an Anker and the phone is now at 20% after 21hrs. Is there a way to get Emoji to work on my phone? When people SMS me, on the lock screen they show up as a question mark in a box but when i go to read the text message there is nothing there.
Using a different keyboard will let you send Emojis, but not really sure about enabling the view from other people's messages off the top of my head, sorry. I recommend SwiftKey for a great keyboard replacement with lots of built in Emojis.
So I've been using the preview build 3 for many months now, and the problem is that I don't have a windows computer to use to try to flash another build. I do have a Macbook Pro, but there doesn't seem to be a lot of support that I can find. Can anyone help me out to get my N9 running the latest build?
It's gotten laggy, and the battery doesn't seem to be as good as what it should be(even with the screen brightness turn down pretty far)
Any help would be fantastic, & great appreciated.
i might be missing something but the you can get the fastboot drivers to flash here. I'm not sure how it's different on mac.
Bond111 said:
So I've been using the preview build 3 for many months now, and the problem is that I don't have a windows computer to use to try to flash another build. I do have a Macbook Pro, but there doesn't seem to be a lot of support that I can find. Can anyone help me out to get my N9 running the latest build?
It's gotten laggy, and the battery doesn't seem to be as good as what it should be(even with the screen brightness turn down pretty far)
Any help would be fantastic, & great appreciated.
Click to expand...
Click to collapse
Do you have ADB and Fastboot installed on your Mac? If not go here: http://forum.xda-developers.com/showthread.php?t=2638673 and then download the latest factory image https://developers.google.com/android/nexus/images and either execute the flash-all.sh script (it will erase your data) or flash the images manually.
I currently have a lollipop rom version 5.1 (3.4.10-Nuk3rn3l) that has many quircks which make my DNA fairly unpleasant to use. I'd like to flash a build that is solidly reliable, even if it means downgrading.
What are my options? It is extremely daunting to wade through the endless posts of this development forum to find one that is stable.
What quirks are you having? Are you on the latest firmware and used the recommended recovery to flash? These HTC phones are very picky and can cause some undesired effects when flashing against recommendations of OP. I would assume you are running @santod040's GPE rom. His roms are pretty darn stable if installed correctly. If you did follow install procedure exactly as recommended and still have issues, try his nusense rom.
Yeah, I'd love to hear what instability issues("quirks") you might be having with my GPE port...I'm unaware of any.
Those who have issues and don't ask about them with logs or details, can't expect much.
You can always go back to a stock Kitkat Rom if the hard work of others isn't appreciated.
Sent from my HTC6525LVW using Tapatalk
santod040 said:
Yeah, I'd love to hear what instability issues("quirks") you might be having with my GPE port...I'm unaware of any.
Those who have issues and don't ask about them with logs or details, can't expect much.
You can always go back to a stock Kitkat Rom if the hard work of others isn't appreciated.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I appreciate all you do and it probably does have something to do with not having the most up to date software. I am experiencing a lot of little things that combine to be very frustrating in day to day use. In no particular order; I cannot send consecutive text messages without cycling airplane mode, the restart option when holding the power button has disappeared, every few days the phone will shut off and will be unable to be turned back on without plugging in a power cable (this has something to do with user input but I have yet to recognize the pattern that causes it), apps will frequently crash, the phone no longer automatically connects to wifi networks, and a few other things.
I don't know what info you would need, my kernel is 3.4.10-NuK3rn3l-dlx-GPE-Lollipop_v2.00 . Build number is LMY470.H6
I love that people are still developing for this phone, I just think a lot of this custom firmware business goes over my head.
Those issues sound like firmware outdated and some odd stuff that only an ruu can fix. Below is the most up to date ruu for this phone. Before you flash, be sure to back everything up to an external storage device (PC, USB otg, etc). After you ruu, flash the recommended recovery in the rom thread and then clean flash the rom (wipe data, cache, system). Do not restore the nandroid backup. It could be something software that is causing the app FCs.
http://forum.xda-developers.com/showthread.php?t=2935556
Edit: I know for a fact the Wi-Fi issue is because of outdated firmware, others might be wrong recovery, but to save the hassle, just ruu to be safe.
Do me a favor: Run "fastboot getvar all" and take a look at line three and six. I am having the exact same issues as you. My line 3 for baseband was version 1.02.01.0818, NOT the 1.02.01.0207 that the latest firmware thread stated it should be. My line 6 (version-main) was blank. After flashing the latest radio zip it now shows a 1.02.01.0207 for baseband and 4.09.605.1 for version-main. This isn't my main phone anymore so its not activated in a way that i can test it. However it may be a starting point for you. I'd be curious if you have the same radios that my phone did.