Hey guys
Flashed CyanogenMod about 5 months ago, phone now has hardware issues, need to install stock rom, my bootloader shows this...
Bootloader info
M7_UL PVT S-OFF RH
CID-O2___001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC0boot
Apr 10 2013, 00:11:36:-1
Baseband version - 4A-14.3250.13_10.33.1150.01L
Running - cyaogenMod verion - 10.1-20130529-NIGHTLY-m7
Can someone show me the correct RUU to use for my phone the O2 one i have found has different radio stats, as do the European ones, is it safe for me to use those RUU's??
There isn't an o2 RUU, you'll have to rely on a Nandroid backup (if there is one)
Is there any other RUU that i could flash to my device to bring it back to stock?
Is there any criteria or things i should look for when looking at RUU's?
Sas_22 said:
Is there any other RUU that i could flash to my device to bring it back to stock?
Is there any criteria or things i should look for when looking at RUU's?
Click to expand...
Click to collapse
You can change the CID to HTC__001 and then flash the generic 1.28.401.7 RUU to go back to stock
Related
Hi,
Another noob question from me.
I recently bought a HTC One. I uploaded a custom ROM (was silly and didn't backup properly). I'd like to have the ability to restore the phone to a complete factory reset. I want the same, exact HTC ROM that the phone originally shipped with, and also no ***TAMPERED***, ***UNLOCKED***. I'll worry about the tampered and unlocked later (locking should be easy - but i want ***LOCKED*** not ***RELOCKED***).
My phone's info:
M7_U PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 15 2013,22:11:42:-1
I keep on running into deadends thinking I've found the factory stock ROM, but when I try to install it, I get errors like 'could not install'...
At some point I relocked the phone and the install went further, but eventually failed with a 'wrong model' error or something. Based on the model info above of my phone can someone point me in the right direction to find the correct ROM?
Thanks so much. I hope soon to be just as much of a contributor as I am an asker...
First of all you cannot get it to state locked it will always say relocked until a s-off is achieved where you will be able to downgrade hboot and second of all download the app below and post the results.
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
daleski75 said:
First of all you cannot get it to state locked it will always say relocked until a s-off is achieved where you will be able to downgrade hboot and second of all download the app below and post the results.
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Click to expand...
Click to collapse
Thanks...downloaded. A long list of variables with no cut'n'paste...but here is maybe the relevant info:
ro.boot.carrier HTC-Asia-SEA-WWE
ro.boot.cid HTC__044
ro.boot.mid PN0711000
ro.cm.device m7
ro.product.module HTC One
ro.product.name htc_m7
Any other details I can provide?
I think this original RUU should suffice.
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
Hello
I have some questions regarding debranding and running a stock eu htc one rom.
this is the info from my phone
m7-ul pvt ship s-on th
hboot 1.44.0000
radio 4d-14.3250.26
opendsp-v26.120.274.0202
emmc-boot
Is there a way to to flash an original rom from HTC without provider branding to this phone and will it use OTA updates after that.
I see a lot of information on this forum that I first need to unlock it and make it s-off and change the id , but is there somebody who can tell me how to do this and what to use.
From what i understand I will need to put back S-off and lock it to get OTA working again ....?
thanks for an answer
eastern1 said:
Hello
I have some questions regarding debranding and running a stock eu htc one rom.
this is the info from my phone
m7-ul pvt ship s-on th
hboot 1.44.0000
radio 4d-14.3250.26
opendsp-v26.120.274.0202
emmc-boot
Is there a way to to flash an original rom from HTC without provider branding to this phone and will it use OTA updates after that.
I see a lot of information on this forum that I first need to unlock it and make it s-off and change the id , but is there somebody who can tell me how to do this and what to use.
From what i understand I will need to put back S-off and lock it to get OTA working again ....?
thanks for an answer
Click to expand...
Click to collapse
Yes, you have to have be S-Off and i would change the CID to SuperCID 11111111. Look here http://forum.xda-developers.com/showthread.php?t=2314582 and here http://forum.xda-developers.com/showthread.php?t=2317536. Bootloader lock command for when you did that: ./revone -l to receive OTA`s,
change andfose
I did what you said and it worked perfect , the only thing was i needed to change the supercid back to the cid from the rom I flashed
dutch ruu rom - cid HTC__101 after this the update to 1.29 was found and it installed , after this I relocked the htc one again.
Hi all,
I installed an update today for 4.4.3, clearly i shouldn't have as its rendered the phone almost useless. Screen isn't displaying things properly, i can't really describe it, but have the pixels are missing intermittently. Also there is no poweroff dialogue and hardly any apps load.
Why isn't it possible to use the OTA updates, and what's my resolution now?
I'm having the same problem. Was your phone originally a Stock HTC branded phone and you converted it to a GPe HTC One?
That's what I did which is probably the reason I received an OTA update that not intended to my hardware.
So at the moment I'm going down the route of reverting to a stock image. I've changed my CID to HTC__001, Relocked the bootloader and turned S-ON.
However, I'm not having any luck flashing the RUU (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)
Carrier: H3G (Three)
Country: Ireland
*** Relocked ***
M7_UL PVT Ship S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.62.1700.1
eMMC-boot 2048MB
Dec 9 2013,00:28:19.0
Can anyone recommend the correct RUU I should use?
Many thanks,
Pat
Patcheen said:
I'm having the same problem. Was your phone originally a Stock HTC branded phone and you converted it to a GPe HTC One?
That's what I did which is probably the reason I received an OTA update that not intended to my hardware.
So at the moment I'm going down the route of reverting to a stock image. I've changed my CID to HTC__001, Relocked the bootloader and turned S-ON.
However, I'm not having any luck flashing the RUU (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)
Carrier: H3G (Three)
Country: Ireland
*** Relocked ***
M7_UL PVT Ship S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.62.1700.1
eMMC-boot 2048MB
Dec 9 2013,00:28:19.0
Can anyone recommend the correct RUU I should use?
Many thanks,
Pat
Click to expand...
Click to collapse
I've had the phone since release and it originally had HTC Sense on it. I'm currently trying to copy over a ROM to /sdcard/ via adb push and hoping i can just flash it again
sg86 said:
I've had the phone since release and it originally had HTC Sense on it. I'm currently trying to copy over a ROM to /sdcard/ via adb push and hoping i can just flash it again
Click to expand...
Click to collapse
OK, best of luck
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.
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