[Q] T-Mobile Lollipop RUU Error 155 - One (M7) Q&A, Help & Troubleshooting

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.

Related

Help Please Unlocked M7 see Tmobile connect to network

Hello I have an GSM Unlocked HTC One M7 I can not get it to work with T-Mobile or Metro PCS. When I locked it I used it with Simple Mobile and it worked great. Now when I put in a Metro PSC or T-Mobile sim it recognizes the sim card but and when I search for net works it finds the T-Mobile but when It tryes to register It say something like "Sim card wont let you register on this network" I'm in the DC MD VA area. Please Help
Stock firmware
Sense 5.0
Android 4.1.2
M7_WLS PVT SHIP S-OFF RH
CID-SPCS_001
HBOOT-1.44.0000
RADIO-1.00.20.1108
OpenDSP-v26.120.274.0202
eMMC-boot
superman2k2 said:
Hello I have an GSM Unlocked HTC One M7 I can not get it to work with T-Mobile or Metro PCS. When I locked it I used it with Simple Mobile and it worked great. Now when I put in a Metro PSC or T-Mobile sim it recognizes the sim card but and when I search for net works it finds the T-Mobile but when It tryes to register It say something like "Sim card wont let you register on this network" I'm in the DC MD VA area. Please Help
Stock firmware
Sense 5.0
Android 4.1.2
M7_WLS PVT SHIP S-OFF RH
CID-SPCS_001
HBOOT-1.44.0000
RADIO-1.00.20.1108
OpenDSP-v26.120.274.0202
eMMC-boot
Click to expand...
Click to collapse
You should really look into updating your software, since the m7 is on 4.4.2 officially now
Anyways, flash the oldest radio from here (the initial release one, baseband 1.00.20.0315), and that might fix your issue.
StormyNight said:
You should really look into updating your software, since the m7 is on 4.4.2 officially now
Anyways, flash the oldest radio from here (the initial release one, baseband 1.00.20.0315), and that might fix your issue.
Click to expand...
Click to collapse
I tried to update OTA but since I have a custom recovery it just reset to recovery and that's it? Can you recommend me a good one for me? Thank You very much for your help
superman2k2 said:
I tried to update OTA but since I have a custom recovery it just reset to recovery and that's it? Can you recommend me a good one for me? Thank You very much for your help
Click to expand...
Click to collapse
OK, since you have a custom recovery with stock,
a) it's pretty much better to be on a custom ROM since you can update easier.
b) If you want to be on stock, it's best to back everything up and run a RUU.
If you choose option a), flash this recovery, and install a custom ROM such as ViperOne.
If you choose option b), follow the instructions on this thread.

[SOLVED] HTC One debrand with ROM Stock - No update available

Hi everyone:
My goal was to go from HTC One Orange branded (France) to an HTC stock ROM. This way no unnecessary carrier apps, and no more wait for updates. But the irony is now that i reached my goal i get a "no update available for your phone" message
My phone is considered up to date whereas i'm on
Android 4.1.2
Sense 5.0
Software: 1.29.401.12
Here is what i did:
unlock bootloader
installed cwm touch recovery
root with superSU
SOFF
modified CID to HTC__203
Tried a first RUU install with RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Got error 155
Downgrade hboot 1.55 to 1.44
RUU install successful this time.
Tried update: corrupted download error message
tried again: no update availble for your phone
Tried to kill updater app and cache but no luck
tried with RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
No luck either
Currently, bootloader says:
Relocked
M7_UL PVT SHIP S-OFF RH
CID-HTC__203
HBOOT-1.43.0000
RADIO-4A.13.3227.06
OpenDSP-v26.120.274.0202
eMMC-boot
I don't know it this makes a difference, but my device is considered as a test device, due to SOFF i guess.
If you guys may know and point me in the right direction that would be greatly appreciated.
Thanks for reading.
Regards,
Reinstalled
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Select french language > update > and now it seems to download the 1.29.401.12 update (229Mo)
But still stuck on
Android 4.1.2
Sense 5.0
No update available after that. I'm gonna keep looking into this, if you guys got any idea ...
Have you tried changing your cid to SuperCID and then install any of the RUU's you want?
Djall said:
Hi everyone:
My goal was to go from HTC One Orange branded (France) to an HTC stock ROM. This way no unnecessary carrier apps, and no more wait for updates. But the irony is now that i reached my goal i get a "no update available for your phone" message
My phone is considered up to date whereas i'm on
Android 4.1.2
Sense 5.0
Software: 1.29.401.12
Here is what i did:
unlock bootloader
installed cwm touch recovery
root with superSU
SOFF
modified CID to HTC__203
Tried a first RUU install with RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Got error 155
Downgrade hboot 1.55 to 1.44
RUU install successful this time.
Tried update: corrupted download error message
tried again: no update availble for your phone
Tried to kill updater app and cache but no luck
tried with RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
No luck either
Currently, bootloader says:
Relocked
M7_UL PVT SHIP S-OFF RH
CID-HTC__203
HBOOT-1.43.0000
RADIO-4A.13.3227.06
OpenDSP-v26.120.274.0202
eMMC-boot
I don't know it this makes a difference, but my device is considered as a test device, due to SOFF i guess.
If you guys may know and point me in the right direction that would be greatly appreciated.
Thanks for reading.
Regards,
Reinstalled
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Select french language > update > and now it seems to download the 1.29.401.12 update (229Mo)
But still stuck on
Android 4.1.2
Sense 5.0
No update available after that. I'm gonna keep looking into this, if you guys got any idea ...
Click to expand...
Click to collapse
Go HTC__001 on your CID, ive noticed that superCID isn't in the android-info text file in the 401 OTA's and RUU's, and also, why did you go back so far, why not just go straight for the KitKat 401 RUU ?
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
+1 what Seanie280672 said
btw, if receiving updates faster is your main goal in this, why did you choose the .401 version? Dev edition (.1540) receive updates much faster than the WWE .401 version. Just saying if its not to late, you could use the 3.22.1540 ruu and then updates from ota.
And the 1.20.401 ruu is a pre-release version, no updates exist for that version.
First of all, thank you guys so much for taking the time to read and help !
Alray you got a point, indeed the aim is to have update faster, I just didn’t know dev edition could be updated first, well I’m not in a hurry I’d still have them quicker than if I still were on an Orange CID. Just so you know Sense 6 is not even deployed yet on those …
So now this is what bootloader looks like
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.44.0000
RADIO-4A.13.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 11 2013,21:54:10:-1
Tried as advised : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Please see files attached.
Djall said:
First of all, thank you guys so much for taking the time to read and help !
Alray you got a point, indeed the aim is to have update faster, I just didn’t know dev edition could be updated first, well I’m not in a hurry I’d still have them quicker than if I still were on an Orange CID. Just so you know Sense 6 is not even deployed yet on those …
So now this is what bootloader looks like
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.44.0000
RADIO-4A.13.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 11 2013,21:54:10:-1
Tried as advised : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Please see files attached.
Click to expand...
Click to collapse
you will probably have to flash the corresponding firmware first to get your hboot version back up, see here, the firmware you want for that ruu is 4.19.401.9 don't forget to flash it twice.
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
Djall said:
First of all, thank you guys so much for taking the time to read and help !
Alray you got a point, indeed the aim is to have update faster, I just didn’t know dev edition could be updated first, well I’m not in a hurry I’d still have them quicker than if I still were on an Orange CID. Just so you know Sense 6 is not even deployed yet on those …
So now this is what bootloader looks like
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.44.0000
RADIO-4A.13.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 11 2013,21:54:10:-1
Tried as advised : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Please see files attached.
Click to expand...
Click to collapse
well give a try to the dev edittion ruu. It require cid BS_US001 and MID PN0712000.
try the 4.19.1540.9 ruu. If that one doesnt work, the 3.22.1540.1 ruu will work, im 100% sure. Then if you still not receiving ota from 3.22.1540.1 you can download them in the dev edition thread. We have posted them recently.
And don't worry, even if its a US version, you can also select the french language.
Bonne chance!
Merci Alray i'll give it a try to the dev version, now that i'm more comfortable with the procedures.
Thank you Seanie too!
So what i did is download the nowipe firmware version that indeed matches the RUU file as suggested by Seanie
- flash firmware
- RUU install successful
- updates finally working : currently installing sense 6
Problem solved and thank you guys again very much! You have a great day.
Regards.

[Q] Restore M7 to stock - Q on HBOOT

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

[Q] Install T-mobile RUU on Verizon HTC one M7

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

Am I 100% stock if I cant OTA update?

Hey all,
My phone is having hardware issues, its ONLY just within warranty and its going to be returned for repair. Therefore it needs to look 100% un-tampered from a software point of view.
It WAS rooted, ROM'd and S-off'd but I have followed and guide, now the TAMPERED, UNLOCKED and S-OFF messages have all gone.
Now on hboot all it says is:
*****LOCKED*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.43.00000
RADIO-4A.13.3227.06
OpenDSP-v26.120.274.0202
eMMC-boot
Feb 7 2013,21:52:09:-1;
I don't think im 100% stock yet, I cannot get an OTA updates, when attempting it says none found. I'm on android 4.1.2... I know for a fact there are updates.
I came from a custom ROM 5.XX version so therefore had to downgrade but got VERY confused on which i needed, in the end one worked and it said online that i was pretty safe as it wouldn't let me install an incorrect version anyway. i installed the RUU.exe titled: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
What alarms me is the version 1.20.401.1.1, is that okay?
Also why cant i get OTA updates? surely HTC will realise its been tampered with if it wont OTA update?
stevey88 said:
Hey all,
My phone is having hardware issues, its ONLY just within warranty and its going to be returned for repair. Therefore it needs to look 100% un-tampered from a software point of view.
It WAS rooted, ROM'd and S-off'd but I have followed and guide, now the TAMPERED, UNLOCKED and S-OFF messages have all gone.
Now on hboot all it says is:
*****LOCKED*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.43.00000
RADIO-4A.13.3227.06
OpenDSP-v26.120.274.0202
eMMC-boot
Feb 7 2013,21:52:09:-1;
I don't think im 100% stock yet, I cannot get an OTA updates, when attempting it says none found. I'm on android 4.1.2... I know for a fact there are updates.
I came from a custom ROM 5.XX version so therefore had to downgrade but got VERY confused on which i needed, in the end one worked and it said online that i was pretty safe as it wouldn't let me install an incorrect version anyway. i installed the RUU.exe titled: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
What alarms me is the version 1.20.401.1.1, is that okay?
Also why cant i get OTA updates? surely HTC will realise its been tampered with if it wont OTA update?
Click to expand...
Click to collapse
you went back too far, try installing this RUU and then see if it will update: http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
Ahh that worked! thanks!
How did you know it was this one? I still cant understand which one I needed!
stevey88 said:
Hey all,
My phone is having hardware issues, its ONLY just within warranty and its going to be returned for repair. Therefore it needs to look 100% un-tampered from a software point of view.
It WAS rooted, ROM'd and S-off'd but I have followed and guide, now the TAMPERED, UNLOCKED and S-OFF messages have all gone.
Now on hboot all it says is:
*****LOCKED*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.43.00000
RADIO-4A.13.3227.06
OpenDSP-v26.120.274.0202
eMMC-boot
Feb 7 2013,21:52:09:-1;
I don't think im 100% stock yet, I cannot get an OTA updates, when attempting it says none found. I'm on android 4.1.2... I know for a fact there are updates.
I came from a custom ROM 5.XX version so therefore had to downgrade but got VERY confused on which i needed, in the end one worked and it said online that i was pretty safe as it wouldn't let me install an incorrect version anyway. i installed the RUU.exe titled: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
What alarms me is the version 1.20.401.1.1, is that okay?
Also why cant i get OTA updates? surely HTC will realise its been tampered with if it wont OTA update?
Click to expand...
Click to collapse
1.20.401.1 is a pre-release version and you won't be able to update it. Flash the 1.28.401.7 ruu which is the first official version. If you have followed nkk71's guide to return back to stock , you should have seen this:
(...)
---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead
(...)
Click to expand...
Click to collapse
alray said:
1.20.401.1 is a pre-release version and you won't be able to update it. Flash the 1.28.401.7 ruu which is the first official version. If you have followed nkk71's guide to return back to stock , you should have seen this:
Click to expand...
Click to collapse
Ah didn't see that at all.
Thanks again

Categories

Resources