PROBLEM RADIO- INVALID_VER_INFO and OpenDSP- INVALID_VER_INFO - One (M8) Q&A, Help & Troubleshooting

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.

Related

Problem trying to unlock bootloader

My Wildfire S is:
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
I've followed the instructions at http://www.htcdev.com/bootloader/ruu-downloads which, for my network (O2UK), instructs me to "update" my ROM to 2.13.206.1. So I've updated OTA and find I have 2.26.401.3.
The problem is that the RUU from the above website won't recognise this 2.26.401.3 ROM as 2.13.206.1 and insists I "update" to 2.13.206.1 which I do not know how to do.
Is there any other way I can unlock the bootloader? Or can I get the 2.13.206.1 ROM from somewhere else and install that?
Just proceed to step 1..............If your version is higher than specified,you can unlock your phone's bootloader
You cannot install other ROM into your phone without bootloader unlocked.root permissions and CWM recovery.
If i helped you,click the "Thanks" button.Sorry for my English and have a nice night !
P1ngP1ng said:
My Wildfire S is:
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
I think you're already have HBOOT unlockable (xxxx99)
Go to steps unlock bootloader without download ruu from htcdev.
Sent from MARVEL
You really don't need to update the boot loader and search for RUU when the HBoot ver is 1.08.xxx or later.
Just go thru this guide, will help you
http://androidforums.com/wildfire-s-all-things-root/480954-guide-how-root-wildfire-s-s-finally.html
Hope this may be useful.
Senthamil said:
You really don't need to update the boot loader and search for RUU when the HBoot ver is 1.08.xxx or later.
Just go thru this guide, will help you
*Androidforums-link*
Hope this may be useful.
Click to expand...
Click to collapse
Hi
I have the exact same Phone values and I got threw the prozess(the one behind the link above) and i got my wfs to ***UNLOCKED*** and i'm able to install new ROM's
buuuuuuuut
every Rom i installed is not capable to make or receive phone calls. Every time i try to do a call, the wfs says:
android.phone.prozess is shutting down
Did i forget anything or did anything wrong?
Got any help?
@clusternate, if your phone is MarvelC (cdma) then you have to flash ROM that suits your model.
Senthamil said:
@clusternate, if your phone is MarvelC (cdma) then you have to flash ROM that suits your model.
Click to expand...
Click to collapse
I've got the europe (germany) version. so i think i need the GSM version.
I'm quiet new to rooting this devices. Are there different versions of every ROM?
I tried about 6-7 ROM's and not one of them worked. (MIUI, CM7, CM9, everyone from the wfs section of this forum)
A co-worker told me something about updating the modem of my wfs.
Is this true and is there a way to do it?
PS. Which ROM should work on my device?
PPS. There is another prozess that is failing.
Prozess.android.acore is also crashing.

[Q] htc one v RUU canada gsm koodo/telus

**Update** I solved my own problem >_>
I just restored the boot from the cwm nandroid image and the cellular network was restored. If anyone was in a similar situation with this phone there you go.
I'm a noob obviously. I watched the noob video... I've searched here and on google for hours upon hours on how to fix the problem i'm currently in.
I tried to root the One V in order to eventually overclock it with whichever ROM would help me do so. Got tired of the sluggishness of it.
I unlocked the bootloader, made a nandroid backup with cwm, then rooted it with supersu. My only problem is now the cellular network is unavailable. WiFi works fine though.
I've tried to flash the recovery I made but it doesn't help. It seems that the only solution is to flash the stock rom/ run the RUU for the One V.
Anyone know how I can either get back the cellular connection, or where I can find/download the RUU, since I just found out through this whole process that the website for the stock ruus was recently taken down by HTC! :crying: I'd really like to not lose $100 and have to waste more money on another phone.
Thanks...
curious if your specs are the same as mine as I haven't found an RUU for my device either. Can you let me know if you're running the same as me please?
my HBOOT says:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.000
RADIO-3831.19.00.120
eMMC-boot
Jul 2 2012, 20:51:45
Device Info:
CID: TELUS001
BASEBAND VERSION: 20.76.30.0835U_3831.19.00.120
Thanks =)
crazy_dr0id said:
curious if your specs are the same as mine as I haven't found an RUU for my device either. Can you let me know if you're running the same as me please?
my HBOOT says:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.000
RADIO-3831.19.00.120
eMMC-boot
Jul 2 2012, 20:51:45
Device Info:
CID: TELUS001
BASEBAND VERSION: 20.76.30.0835U_3831.19.00.120
Thanks =)
Click to expand...
Click to collapse
How do you expect to find the answer to your own question when you never checked your own post ??
http://forum.xda-developers.com/showpost.php?p=38129204&postcount=10
Hello everyone,
I too have the same phone and no network service. I have tried the RUU_PRIMO_U_ICS_40A_TELUS_WWE_2.22.661.2_Radio_20.76.30.0835U_3831.19.00.120_release_275931_signed but no win. Would it be asking to much for someone to upload a copy of their boot? I am not sure what makes the radio so difficult with this Koodo version, but I have been fiddling with this for 3 days on and off. Needless to say, I'm losing my mind and developing a twitch lol.
Any help would be greatly appreciated.
Thanks!

[Q] Update HBoot w/ SuperCID - HELP

Hello everyone!!
I can't remember how long ago I custom flashed my device, but I've had to recently go back to it, and need to clearly update somethings on it (apart from poor performance, I want it to feel new again).
So ... Some help please.
I've tried to put a new HBOOT onto it.
Here are the stats from the bootloader:
***TAMPERED***
*** RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.11.0000
Radio-0.18as.32.09.28L
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7, 2012, 13:10:34
I think what the problem IS is that I flashed it with a rom that now calls the device "EVITA" ... and I don't know how the heck to change it.
If someone could point me in the correct direction, that would be GREATLY appreciated!!!
(Not sure what the custom rom is, but I'm going to guess codenameandroid)
Thank you!
And yes, I'm sure I'm on the HTC One X (Rogers Version)
anime4tw said:
Hello everyone!!
I can't remember how long ago I custom flashed my device, but I've had to recently go back to it, and need to clearly update somethings on it (apart from poor performance, I want it to feel new again).
So ... Some help please.
I've tried to put a new HBOOT onto it.
Here are the stats from the bootloader:
***TAMPERED***
*** RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.11.0000
Radio-0.18as.32.09.28L
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7, 2012, 13:10:34
I think what the problem IS is that I flashed it with a rom that now calls the device "EVITA" ... and I don't know how the heck to change it.
If someone could point me in the correct direction, that would be GREATLY appreciated!!!
(Not sure what the custom rom is, but I'm going to guess codenameandroid)
Thank you!
And yes, I'm sure I'm on the HTC One X (Rogers Version)
Click to expand...
Click to collapse
Rogers version is the Evita. So thats alright. Here can you find the right forums. http://forum.xda-developers.com/forumdisplay.php?f=1538
Sent from my HTC One X using xda app-developers app

Radio-invalid_ver_info ?

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

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?

Categories

Resources