Radio-invalid_ver_info ? - One (M8) Q&A, Help & Troubleshooting

Ok just noticed the following in fastboot screen:
M8_UL PVT SHIP S-ON
HBOOT 3.16.0.0000
RADIO-INVALID_VER_INFO ?
OpenDSP-INVALID_VER_INFO ?
OS 1.54.401.5
eMMC-boot 2048
The phone is working fine but something is not right? Did OTA 1.54.401.5 update with stock recovey couple days ago went ok so wonder if this update is the cause of this? Any idea guys?

gfreek said:
Ok just noticed the following in fastboot screen:
M8_UL PVT SHIP S-ON
HBOOT 3.16.0.0000
RADIO-INVALID_VER_INFO ?
OpenDSP-INVALID_VER_INFO ?
OS 1.54.401.5
eMMC-boot 2048
The phone is working fine but something is not right? Did OTA 1.54.401.5 update with stock recovey couple days ago went ok so wonder if this update is the cause of this? Any idea guys?
Click to expand...
Click to collapse
Ok I will answer my own question, after doing some research on this issue in various blogs and forums including xda, this is a common issue, some say when you apply the OTA 1.54.401.5 will bring this missing info on fastboot screen which is what happened in my case.
Anyhow nothing to worry about the phone is fine everything works, it's just for some reason the version info is not displayed. The only way to resolve this is to flash official HTC RUU 1.54.401.5 but that's currently not available.

Hmm mine says the same except the line for OS reads:
OS-
In other words, no "1.54.401.5". Looking in About > Software version, it says 1.54.651.8, but that doesn't show in the fastboot screen either.

rhe12 said:
Hmm mine says the same except the line for OS reads:
OS-
In other words, no "1.54.401.5". Looking in About > Software version, it says 1.54.651.8, but that doesn't show in the fastboot screen either.
Click to expand...
Click to collapse
What recovery are you using?
This may or may not be related but I had the same issue when running TWRP. I changed to Philz and the problem went away. I tried this four times with the same result.
Phone was working fine just not showing OS in fastboot

TWRP 2.7.0.5. Don't know if it's related or not...
Sent from my 831C using xda app-developers app

Same issue here.
Nothing to complain about on functionality though.
Waiting for S-Off to be able to update firmware...(I'm one of those who get the Whelp message in firewater)

Another one here. =/ Guess we all have to wait then.

Definitely related to TWRP. Don't know if latest version solves this though...
Sent from my HTC One_M8 using XDA Premium 4 mobile app

nuts77 said:
Definitely related to TWRP. Don't know if latest version solves this though...
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well maybe. I upgraded to 2.7.1.0 and now the OS reads 2.16.651.4 (I installed the latest modded firmware as well).

Totally stock here. Have same issue so no fault of twrp
Sent from my HTC_M8

i also had this issue and tried various recoverys to no avail , however i recently wanted to s-off which was not possible with firewater so i used sunshine. To do this i returned to stock first , upon returning to stock all was fine again and i no longer had radio-invalid_ver_info etc

the same for me here ... no Radio, OpenDSP or OS Version.
TWRP 2.7.0.10 flashed ...
Using ARHD 10.2 ROM
But no matter which ROM I install I always need to turn airplane mode on and off to get a carrier signal after reboot ... anyone else experience this issue?

as i posted above , you should try flashing back to stock to correct the version info issue. Since flashing back to stock i have s-off latest firmware installed and custom rom and version info now displays correctly

Invalid_ver_info
My phone (HTC One Mini 2) displays INVALID_VER_INFO for RADIO and OpenDSP, too. But I found out that, when i boot into bootloader with no SD-card inserted, it says RADIO-1.101.1102.17.0506 and OpenDSP-v28.2.2.00546.0331. As soon as I boot into bootloader with SD-card inserted, INVALID_VER_INFO comes back.
I noticed this bug only after I had replaced the recovery with TWRP 2.7. So I can't tell exactly if this bug happened by updating OTA or by installing TWRP 2.7.
Besides that my phone is running perfectly, so there's no need to worry about it.

I need help!!
I have a Sprint harman/kardon edition. In the bootloader it says the following when sdcard is inside
RELOCKED
M8_WHL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS-2.16.654.4
eMMC-boot 2048MB
July 7 2014,20:53:58.0
When I remove the sdcard it says :
RELOCKED
M8_WHL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.08.20.0612_4
OpenDSP-v45.2.2-00542-M8974_HM.0422
OS-2.16.654.4
eMMC-boot 2048MB
July 7 2014,20:53:58.0
As I have simunlocked the device for GSM use, It does connects to the carrier but does not start mobile data services. Under selling when I try to click on tab to "ON" . Immediately it says "Disconnected because service is unavailable"
I've already tried going back to stock by renaming harman specified ruu as 0P6BIMG.zip and flshing it through sdcard, it does makes the device go stock but doesnt seem to fix the above mentioned problem.
I would like to point out, it was working fine before I flashed TWRP 2.8.0.1 and a custom rom. I noticed that mobile data was not working in that custom rom, so I decided to back stock and now I am stock but mobile data doesn't work along with above mentioned status.
Please help.
Thanks

Related

[Q] Back to Stock ROM - available from any working DHD?

Hi,
I am in trouble. C.a. 6 months ago my DHD had to go to service because of headphone icon still standing at the taskbar and it was not possible to talk with anybody. After this i received new motherboard. Before that i had fully unlocked phone (root, S-OFF), but when i get it back from service, there was newest firmware installed, and of course s-on, no root. I rooted phone somehow, but s-on stayed still. And I can flash custom roms, but everytime I am doing this, I have to flash boot.img. Is it possible to turn S-ON to S-OFF? I tried many ways (AAHK, gold card + PD98IMG), downgrade to older version. Nothing was successful. The problem is, I think, that when any stock rom i am trying to flash with RUU, after rebooting to fastboot phone is locked on screen with HTC logo on black background. There is no progress bar of flashing, no screen with bootloader. What can I do to flash stock rom, can You help me?
On my bootloader screen already looks like this:
ACE PVT SHIP S-ON RL
HBOOT - 2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMc-boot
Dec 22 2011, 14:28:19
I will be very thankful for your help.
sampras83 said:
Hi,
I am in trouble. C.a. 6 months ago my DHD had to go to service because of headphone icon still standing at the taskbar and it was not possible to talk with anybody. After this i received new motherboard. Before that i had fully unlocked phone (root, S-OFF), but when i get it back from service, there was newest firmware installed, and of course s-on, no root. I rooted phone somehow, but s-on stayed still. And I can flash custom roms, but everytime I am doing this, I have to flash boot.img. Is it possible to turn S-ON to S-OFF? I tried many ways (AAHK, gold card + PD98IMG), downgrade to older version. Nothing was successful. The problem is, I think, that when any stock rom i am trying to flash with RUU, after rebooting to fastboot phone is locked on screen with HTC logo on black background. There is no progress bar of flashing, no screen with bootloader. What can I do to flash stock rom, can You help me?
On my bootloader screen already looks like this:
ACE PVT SHIP S-ON RL
HBOOT - 2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMc-boot
Dec 22 2011, 14:28:19
I will be very thankful for your help.
Click to expand...
Click to collapse
Why is the hack kit not working? Is your bootloader unlocked?
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Why is the hack kit not working? Is your bootloader unlocked?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Do you mean with HTCDev page? I tried this, but in step 14(i think) when the screen from android should appear to commit bootloader unlock operation, then happens nothing - the answer in command line window is ok - suitable to one in tutorial on HTCDev, but on the phone I can't see any changes. Well.. AAHK needs to install downgrade version and then there is the same problem like with RUU - phone cannot flash this version.

PROBLEM RADIO- INVALID_VER_INFO and OpenDSP- INVALID_VER_INFO

Hello, I have a concern which also relates to some of you.
But alas, there is no information on the.
Indeed, in the bootloader menu, there is information at the top of our HTC One M8.
And here is mine:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS-
eMMC-boot 2048MB
(you will find 3 anomalies, radio, and bone-OpenDSP)
I found no way to put the info up to date.
Malgrés all, I encounter no problem and the settings of the phone options, I have good information for radio and others.
Who encounter the same problems?
That a solution?
Or if that can tell us more about this.
Thank you comrades: D
up :crying:
Fenhyks said:
up :crying:
Click to expand...
Click to collapse
did you flash an ruu not meant for your phone? flashing the correct ruu for your phone will fix your issue.
Sent from my SM-T320 using Tapatalk
Or just flash the firmware package for your ROM and that'll sort it out
EddyOS said:
Or just flash the firmware package for your ROM and that'll sort it out
Click to expand...
Click to collapse
Thank you for your reply
the problem is that there is no ruu available for my htc one m8 international.
htc
I have flash the firmware but nothing changes.
http://forum.xda-developers.com/showthread.php?t=2735235
UP
Fenhyks said:
UP
Click to expand...
Click to collapse
I had that too for a while on my phone although I do not remember exactly when it started. I think it was after I did the last OTA. I did not think much about it at the time since it did not bother me because it was not causing any problems and everything on the phone was still working fine. It eventually got sorted out on its own, although again, I do not remember exactly when that happened but I think it was after I achieved s-off.

tried to use ruu to update, phone stuck in bootloader

So my phone is currently on a custom rom and I was trying to take it back to stock. I downloaded a ruu from htc dev because a bunch of guides I saw pointed me to do that and click a few buttons during the process it said my phone can't be updated and now i am stuck on a screen that looks like the bootloader but says this
***tampered***
***unlocked***
m8_UL PVT SHIP S-ON
HBOOT- 3.18.0.0000
Radio - 1.19.213311491.03g
OPENDSP - V382.2-00542-m8974.0311
OS-
EMMC-Boot 2048MB
Jul 16 @014, 03:33:24.0
SECURITY Fail!
RUU
I cant do anything from this screen. I tried to use another tool to get me into recovery but it says device not found. I also tried going through revovery through the ruu but nothing happens there. What else can i try to save my phone?
jayrocc said:
So my phone is currently on a custom rom and I was trying to take it back to stock. I downloaded a ruu from htc dev because a bunch of guides I saw pointed me to do that and click a few buttons during the process it said my phone can't be updated and now i am stuck on a screen that looks like the bootloader but says this
***tampered***
***unlocked***
m8_UL PVT SHIP S-ON
HBOOT- 3.18.0.0000
Radio - 1.19.213311491.03g
OPENDSP - V382.2-00542-m8974.0311
OS-
EMMC-Boot 2048MB
Jul 16 @014, 03:33:24.0
SECURITY Fail!
RUU
I cant do anything from this screen. I tried to use another tool to get me into recovery but it says device not found. I also tried going through revovery through the ruu but nothing happens there. What else can i try to save my phone?
Click to expand...
Click to collapse
nvm i fixed that problem and now I'm back to square one. maybe someone could point me in the right direction from here.
I'm currently on 4.4.3 kk and am trying to get back to stock from my custom rom. clearly the ruu I used was the incorrect method and the other method I was going to try which involves using hasoon's toolkit appears to not be the answer because when i went to check the cid the version number was not available ( unless im missing something here)
any assistance that someone is willing to offer would be appreciated.
You have to re-lock your bootloader before you run the RUU.
VolcanicSkunk said:
You have to re-lock your bootloader before you run the RUU.
Click to expand...
Click to collapse
thanks, the guide i was looking at failed to mention that.
jayrocc said:
thanks, the guide i was looking at failed to mention that.
Click to expand...
Click to collapse
How did you get back to where you were previously? Did you re-flash your custom ROM?

[Q] Unable to enter recovery after using dd install method

Good day all,
I am unable to get into my TWRP recovery, have read through the forum and tried a couple of methods but still not able to get into recovery.
Below the series of events that led to this happening.
27/5/15
-wanted to install CM12.1 but needed to update my TWRP as it prompted me to have an updated version.
[backup my rom into my ext_sd card
-went to TWRP web site ( https://twrp.me/devices/htconem8gsm.html ) via computer and used the dd install method.
-believe it to be successful thus went for a recovery reboot but learnt that I was unable to get into recovery mode after waiting 30+ mins at the 'enter recovery mode' screen.
-tried to factory reset but was unable to factory reset as was unable to enter recovery.
28/5/15
-googled more and tried a few more methods.
-Tried to use a toolkit to get my CID and version number but saw I did not have the version number which was blank and read that countless others are also facing the same problem.
CID = HTC__004
-wanted to unroot and revert to stock rom but unable to get into recovery to flash the stock rom i downloaded from http://forum.xda-developers.com/showthread.php?t=2701376&highlight=version-main
-Tried http://forum.xda-developers.com/showthread.php?t=2727831 (RUU to install twrp) --> the bootloader just seems to hang at the loading of the RUU file and can't get to phrasing it after 30mins of waiting.
-force to reboot phone via pressing power button and now my phone has a error saying 'system uids inconsistent', which i pressed feeling lucky to continue using.
Tried updating twrp via playstore app which still made me unable to enter recovery.
29/5/15
-nearly giving up hope
Use fastboot to erase cache, and flash TWRP with fastboot.
redpoint73 said:
Use fastboot to erase cache, and flash TWRP with fastboot.
Click to expand...
Click to collapse
Managed to clear cache and install 2.7.2 twrp and now able to go into recovery.
However, believe I woulkd require twrp 2.8.0 and above to flash cm12.1 and the gapps as I am getting an error when trying to flash cm12.1 nightly in my current 2.7.2 twrp that says that I am unsuccessful.
Tried to update twrp via their app this time and seems to be unable to get into recovery again.
Had cleared cache and installed twrp 2.7.2 again and now awaiting your further assistance in updating my twrp.
Thanks!
Newer TWRP doesn't seem to do well with older hboot. What is your firmware version or hboot number?
flyera343 said:
Newer TWRP doesn't seem to do well with older hboot. What is your firmware version or hboot number?
Click to expand...
Click to collapse
That's a good catch, forgot about that one.
OP should update hboot, if its older.
flyera343 said:
Newer TWRP doesn't seem to do well with older hboot. What is your firmware version or hboot number?
Click to expand...
Click to collapse
Firmware would be cm11-20150124 nightly
Hboot-3.16.0.000
also noting red point comment
Will try and update hboot and update u guys.
Thanks!
MaXeFoei said:
Firmware would be cm11-20150124 nightly
Hboot-3.16.0.000
also noting red point comment
Will try and update hboot and update u guys.
Thanks!
Click to expand...
Click to collapse
Your hboot is the original that came with the phone/4.4.2
You definitely need to update. I would recommend not just your hboot but the whole firmware package. And what you listed as firmware isn't firmware, it's your ROM.
Boot into bootloader, and post the readout from it here. I, or someone else here, will be able to direct you on how to update it with that information.
xunholyx said:
Your hboot is the original that came with the phone/4.4.2
You definitely need to update. I would recommend not just your hboot but the whole firmware package. And what you listed as firmware isn't firmware, it's your ROM.
Boot into bootloader, and post the readout from it here. I, or someone else here, will be able to direct you on how to update it with that information.
Click to expand...
Click to collapse
Good day,
Currently trying to get my phone S-off via firewater but adb dun seem to be working for me.
Will google more and get back with more updates of my situation.
Below as requested.
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 11 2014,01:27:27.24333
MaXeFoei said:
Good day,
Currently trying to get my phone S-off via firewater but adb dun seem to be working for me.
Will google more and get back with more updates of my situation.
Below as requested.
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 11 2014,01:27:27.24333
Click to expand...
Click to collapse
Firewater does not work at all, never again. Sunshine is the only reasonable solution !
MaXeFoei said:
Good day,
Currently trying to get my phone S-off via firewater but adb dun seem to be working for me.
Will google more and get back with more updates of my situation.
Below as requested.
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 11 2014,01:27:27.24333
Click to expand...
Click to collapse
Another Canadian, eh?
Bell doesn't have any RUUs, unfortunately. You will need to use Sunshine to gain S-Off and switch to superCID to flash firmware, or go back to stock and take the OTAs that Bell provides.
xunholyx said:
Another Canadian, eh?
Bell doesn't have any RUUs, unfortunately. You will need to use Sunshine to gain S-Off and switch to superCID to flash firmware, or go back to stock and take the OTAs that Bell provides.
Click to expand...
Click to collapse
Noted above. That's why I keep trying firewater and it don't seem to work.
I am from Singapore.
Will see to sunshine and update you guys again.
Thanks for the great assistance thus far.
MaXeFoei said:
Noted above. That's why I keep trying firewater and it don't seem to work.
I am from Singapore.
Will see to sunshine and update you guys again.
Thanks for the great assistance thus far.
Click to expand...
Click to collapse
I was guessing from your radio version. Y
Your OS was blank, which would have gave me the proper firmware/model you were on.
Good luck with Sunshine!
If you have any issues with it, please report back here and either use the reply button on one of my posts, or preferably put an @ in front of my username when replying so that I get a notification.

Strange Issues from CM11, going to CM12 - What is the proper process?

Hey XDA,
If anyone would be willing to help me out with what I thought would be a simple update, I'd be very thankful...
My carrier is Sprint. Currently on the latest CM11 snapshot and I have been having all kinds of weird issues.. including:
Launcher icons moving / reconfiguring
Loud Beep or Buzz at random times, eg. switching to speaker phone, opening contacts, etc
Phone was uploading at 6mb/s maxing out my wifi upstream bandwidth without any sign of what was doing the data transfer...
Needless to say I'd like to wipe everything and start fresh with CM12.
My recovery screen has the following info:
***TAMPERED***
***UNLOCKED***
M8_WHL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.08.20.0610
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
I am on TWRP V2.7.1.0
I've browsed the guides and how-to's and still am not certain what the proper procedure is to update from where I currently am (or where to find the latest trusted source for Sprint M8 firmware)
I'd like to do it manually so I actually learn and know what I'm doing in the end.
Any help? Should my first step be using Fastboot to update TWRP?
If you have S-off I would take a look through the Sprint M8 forum for the latest firmware or start with an recent RUU. Then update TWRP through fastboot and install CM 12 since it is not likely to run well on the older firmware.
Sent from my One M8 using XDA Free mobile app

Categories

Resources