Hello I have a question about a recent update I did to my Spint HTC harmin kardon ONE M8. I'm currently running the google play edition on my M8 but my phone recently told me that there was a software update available. I tried updating the phone from the regular OTA update it didnt work. I figured I needed to update my radio which I did afterward. Now after the radio update isnt allowing me to get cell phone service. Is there a way that I can roll back the radio firmware, Is it something I can just put onto the root of my SD card and flash and if so where can I get the specific Radio? Below Is what my bootloader lists prior to the update and my current radio after the recent update is Radio - 1.14.2133191.LA02_2G.
*** UNLOCKED ***
M8_WHL PVT SHIP S-OFF
CID-SPCS_004
HBOOT-3.16.0.0000
RADIO-1.08.20.0610
OpenDSP-v45.2.-00542-M8974_HM.0422
OS-1.54.654.15
eMMC-boot 2048MB
Jun 4 2014, 12:00:35.0
Related
I have a SPRINT HTC ONE (M7spr) and using it in India. It is currently carrier unlocked and i dont know how... I got it through someone in my circle. also i ma not very accquainted with all this rooting and stuff. recently i downloaded the OTA update (4.3) and when tried to install, the phone restarts into the bootloader with the following msg
tampered
relocked
security warning
M7_WLS PVT SHIP S-ON RH
eMMc-Boot
Jul 5 2013, 17:19:22:-1
when i restart it again iam able to use it as normal without the update installed. superSU was installed already. i not want to update but not able to understand what to do since iam unknown to all this
plz help.
Hi
Back in december I converted my HTC One M7 to the GPE. I remember I had to unlock both with HTC and with another program, and also that I had to modify the CID etc. My device now looks like this:
CID-GOOGL001
HBOOT 1.54
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
Dec 9 2013 00:38:19
Now I saw HTC just released a new update for the HTC One including Sense 6. I'm wondering how I should approach the update. Should I try to revert everything back and install the original operating system (from when I made the switch to GPE) and then let HTC do an OTA to get to the new version? Will I need to modify CID etc? Will I lose S-OFF in the process? Or can I - now that I'm S-OFF - just format the phone and install the latest software from HTC? Will I need to update anything that has been modified in the time I as away from HTC (Radio firmware, HBOOT)?
Thanks!
Hi I need to restore my HTC One M7 European to stock, since I want to return it for repair of the purple tint issue. My question is what HBOOT is now the "official" from HTC Europe, so I can choose the right one.
When I got the phone in summer 2013 I initially just followed the OTA upates. In December I converted to Google GPE to get KitKat faster (and also later got Lolipop). This involved getting S-OFF etc.
Phone info before I converted (December 2013) - had HBOOT 1.55.
M7_UL PVT SHIP SON RH
HBOOT 1.55
RADIO 4A.21.3263.04
OpenDSP-32.120.274.0909
OS-3.62.401.1
eMMC boot 2048MB
Oct 17 2013
Used RumRunner to get S-OFF, change cid etc. and convert to GPE. Then followed OTA updates for a while, including upgrade to Lolipop. Status today:
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.274.0429
OS-5.11.1700.3
eMMC-boot 2048MB
Dec 2 2014 22:11:20.0
So I'm actually on a lower HBOOT now than before I did any hacking.
Questinon is - if I had followed the official upgrade cycle would I still be at HBOOT-1.55?
Here's my idea for reverting this phone to stock:
1) Rewrite CID to original
2) Install suitable KitKat RUU
3) Upgrade to HBOOT 1.55 (since this was the original - I'm wondering if I get 1.55 automatically through step #2 though).
4) fastboot oem writesecureflag 3 (in order to return to S-ON)
5) Install OTA updates
Will the phone now be in the same state as if I had not done any hacking? I've also seen people somewhere suggest you need HBOOT-1.44 to get S-ON back. Is that true? If so, can I downgrade to 1.44, put S-ON and then upgrade to 1.55? Also what about the other elements in the list (OpenDSP etc.) will they return to stock via the RUU? The trouble is I have no way to tell what the values would have been if I had not hacked the phone and had just followed official OTA's.
Any help will be much appreciated. I'm a bit confused over HBOOT issues.
kenzorio said:
Hi I need to restore my HTC One M7 European to stock, since I want to return it for repair of the purple tint issue. My question is what HBOOT is now the "official" from HTC Europe, so I can choose the right one.
When I got the phone in summer 2013 I initially just followed the OTA upates. In December I converted to Google GPE to get KitKat faster (and also later got Lolipop). This involved getting S-OFF etc.
Phone info before I converted (December 2013) - had HBOOT 1.55.
M7_UL PVT SHIP SON RH
HBOOT 1.55
RADIO 4A.21.3263.04
OpenDSP-32.120.274.0909
OS-3.62.401.1
eMMC boot 2048MB
Oct 17 2013
Used RumRunner to get S-OFF, change cid etc. and convert to GPE. Then followed OTA updates for a while, including upgrade to Lolipop. Status today:
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.274.0429
OS-5.11.1700.3
eMMC-boot 2048MB
Dec 2 2014 22:11:20.0
So I'm actually on a lower HBOOT now than before I did any hacking.
Questinon is - if I had followed the official upgrade cycle would I still be at HBOOT-1.55?
Here's my idea for reverting this phone to stock:
1) Rewrite CID to original
2) Install suitable KitKat RUU
3) Upgrade to HBOOT 1.55 (since this was the original - I'm wondering if I get 1.55 automatically through step #2 though).
4) fastboot oem writesecureflag 3 (in order to return to S-ON)
5) Install OTA updates
Will the phone now be in the same state as if I had not done any hacking? I've also seen people somewhere suggest you need HBOOT-1.44 to get S-ON back. Is that true? If so, can I downgrade to 1.44, put S-ON and then upgrade to 1.55? Also what about the other elements in the list (OpenDSP etc.) will they return to stock via the RUU? The trouble is I have no way to tell what the values would have been if I had not hacked the phone and had just followed official OTA's.
Any help will be much appreciated. I'm a bit confused over HBOOT issues.
Click to expand...
Click to collapse
DO NOT GO S-ON EVER !!!
DO NOT RELOCK YOUR BOOTLOADER (you will never get it unlocked again)
Hboot 1.54 is what all GPe phone's have
Simply change your CID and MID back to what they were and flash a RUU and your back to Sense Firmware with the hboot in that RUU
theirs a full guide for returning to stock here >> http://forum.xda-developers.com/showthread.php?t=2541082
clsA said:
DO NOT GO S-ON EVER !!!
DO NOT RELOCK YOUR BOOTLOADER (you will never get it unlocked again)
Hboot 1.54 is what all GPe phone's have
Simply change your CID and MID back to what they were and flash a RUU and your back to Sense Firmware with the hboot in that RUU
theirs a full guide for returning to stock here >> http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Hi thanks. I had great troubles using the KitKat RUU. I suspected it was due to incompatibility with HBOOT. Downgraded HBOOT to 1.44, still didn't work. Then instead I used an RUU for Jelly Bean (in fact the original image) and this worked like a charm. Then I've applied a tons of OTA updates and now I'm on HBOOT 1.54. But now I'm stuck because it can't find the 4.19.401.11 update on HTC's server! I guess they have simply removed it and most people aren't bothered because they are way past.
BTW, why would it be a problem to go S-ON? Can't I go S-OFF again using the same method I originally used (using Rumrunner etc.)? Why would this S-ON be more permanent than a factory S-ON? I need to be S-ON to send the phone into service.
kenzorio said:
Hi thanks. I had great troubles using the KitKat RUU. I suspected it was due to incompatibility with HBOOT. Downgraded HBOOT to 1.44, still didn't work. Then instead I used an RUU for Jelly Bean (in fact the original image) and this worked like a charm. Then I've applied a tons of OTA updates and now I'm on HBOOT 1.54. But now I'm stuck because it can't find the 4.19.401.11 update on HTC's server! I guess they have simply removed it and most people aren't bothered because they are way past.
BTW, why would it be a problem to go S-ON? Can't I go S-OFF again using the same method I originally used (using Rumrunner etc.)? Why would this S-ON be more permanent than a factory S-ON? I need to be S-ON to send the phone into service.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ota_m7_...19-401-11_release_372404wj19h95c0x6oa19n-zip/
if not helped Run this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/ then try to update
I have the Verizon version of the HTC Once M7 and would like to get it fully compatible with T-mobile. Here's what the last few hours of research and reading through these forums has led me to believe. Can anyone verify if my understanding is correct? Or am I missing something?
All HTC One M7 phones have the same hardware, so there's no hardware limitation causing network incompatibility, rather carrier incompatibility is due to firmware/sofware.
To be able install the T-mobile RUU (htc.com/us/support/htc-one-t-mobile/news) on a Verizon version of the HTC One M7, I need to s-off the phone using sunshine (theroot.ninja/index.html)
To install the T-mobile RUU, I should follow the instructions on htc's website (htc.com/us/support/htc-one-t-mobile/news)
To be thorough, here's the details of the phone I have:
HTC One M7:
M7_WLV PVT SHIP S-ON FR
HBOOT-1.57.000
RADIO-1.13.41.0702
OpenDSP-v32.120.274.0909
OS-5.28.605.2
eMMC-boot 2048MB
And the name of the RUU that I'd like to install:
RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.10_Radio_4T.28.3218.04_10.33E.1718.01L_release_405711_signed_2
Thanks! Just want to make sure I have everything thought out before I begin.
hacklan07 said:
I have the Verizon version of the HTC Once M7 and would like to get it fully compatible with T-mobile. Here's what the last few hours of research and reading through these forums has led me to believe. Can anyone verify if my understanding is correct? Or am I missing something?
All HTC One M7 phones have the same hardware, so there's no hardware limitation causing network incompatibility, rather carrier incompatibility is due to firmware/sofware.
To be able install the T-mobile RUU (htc.com/us/support/htc-one-t-mobile/news) on a Verizon version of the HTC One M7, I need to s-off the phone using sunshine (theroot.ninja/index.html)
To install the T-mobile RUU, I should follow the instructions on htc's website (htc.com/us/support/htc-one-t-mobile/news)
To be thorough, here's the details of the phone I have:
HTC One M7:
M7_WLV PVT SHIP S-ON FR
HBOOT-1.57.000
RADIO-1.13.41.0702
OpenDSP-v32.120.274.0909
OS-5.28.605.2
eMMC-boot 2048MB
And the name of the RUU that I'd like to install:
RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.10_Radio_4T.28.3218.04_10.33E.1718.01L_release_405711_signed_2
Thanks! Just want to make sure I have everything thought out before I begin.
Click to expand...
Click to collapse
CDMA (Verizon - Sprint ) version of the One have a different partition layout. flashing that file may or may not totally brick the phone
Hi hacklan07, how did this process go for you?
ehance said:
Hi hacklan07, how did this process go for you?
Click to expand...
Click to collapse
It cant be done. Use only verizon ruu on verizon phones
Hello,
I have an unlocked HTC Phone. The phone is from AT&T but I'm now using it with T-Mobile. Many of features do not work correctly now such as MMS, Hotspot, Software updates etc. (In place of Software update, I have AT&T software update which always reports that there are no updates for my phone)
Someone suggested that I can use RUU provided by HTC to replace the current software with T-Mobile one. I used the RUU that HTC recently posted for t-mobile but it fails with Error 155 pretty quickly. I tried booting the phone in fast boot mode and I get the same error from the install wizard.
Here's what it tells me when I got to boot menu,
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OPENDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MN
Jan 28 2014,09:32:41.0
I'm new to upgrading ROM so have no idea what any of these mean. Any ideas on how I can fix the error and upgrade to t-mobile RUU? Thanks in advance.
cornerwings said:
Hello,
I have an unlocked HTC Phone. The phone is from AT&T but I'm now using it with T-Mobile. Many of features do not work correctly now such as MMS, Hotspot, Software updates etc. (In place of Software update, I have AT&T software update which always reports that there are no updates for my phone)
Someone suggested that I can use RUU provided by HTC to replace the current software with T-Mobile one. I used the RUU that HTC recently posted for t-mobile but it fails with Error 155 pretty quickly. I tried booting the phone in fast boot mode and I get the same error from the install wizard.
Here's what it tells me when I got to boot menu,
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OPENDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MN
Jan 28 2014,09:32:41.0
I'm new to upgrading ROM so have no idea what any of these mean. Any ideas on how I can fix the error and upgrade to t-mobile RUU? Thanks in advance.
Click to expand...
Click to collapse
155 error is wrong RUU, to convert your phone to t-mobile you will need s-off, you can only update an AT&T phone when you are on the AT&T network, so although your sim is T-Mo working in a AT&T phone, you will never be able to update.
You can try rumrunner to s-off your phone. http://rumrunner.us/
If that doesnt work, the only way is sunshine @ $25 http://theroot.ninja/
Seanie280672 said:
155 error is wrong RUU, to convert your phone to t-mobile you will need s-off, you can only update an AT&T phone when you are on the AT&T network, so although your sim is T-Mo working in a AT&T phone, you will never be able to update.
You can try rumrunner to s-off your phone.
If that doesnt work, the only way is sunshine @ $25
Click to expand...
Click to collapse
Thanks I will give that a shot. Once I s-off my phone can I simply use the t-mobile RUU or do I need to flash it some other way?
cornerwings said:
Thanks I will give that a shot. Once I s-off my phone can I simply use the t-mobile RUU or do I need to flash it some other way?
Click to expand...
Click to collapse
you will need to change your CID and MID to match the T-Mobile RUU, quite easy to do, we can guide you to do that once you get s-off.
You may then have to flash the firmware first before the RUU, then just run the RUU and you will be full stock T-Mobile then.
p.s once s-off, never go s-on, it will cause you more headaches than you can imagine.