Database Develop

Need RUU for UK htc one M7 CID: VODAP001 M7_UL_JB_50_S

Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.

HTC One CID: VODAP102 OS(2.24.161.1) Death to Stock
granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
i Also have HTC One 4.2.2 Jerry Beam CID: VODAP102 *Death*
OS: 2.24.161.1
Anyone help me to upload Stock firmware to recovery
My Device Detail is Below
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.161.1
eMMC-boot 2048MB
Jun 23 2013, 03:49:03.0

granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
Hi, I have a nandroid backup of this buried on my phone however as an extreme noob I do not know how to extract

granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
Did you get a resolution for this?
I too am on hboot 1.54 with S-ON and CID=VODAP001 and i'd like to be able to go back to Stock so I can get OTA updates.

OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck

L0rdNels0n said:
OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck
Click to expand...
Click to collapse
Well iam stuck with the same, trying find ruu or stock version for my htc. I tried to flash stock dump it fails as the cid doesnt match.
Can some one advice, details of my device
Cid:vodap001
S-on
Device : PN0710000
Boot loader 1.54.0000
2.24.161.1
Thanks

L0rdNels0n said:
OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck
Click to expand...
Click to collapse
Hi L0rdNels0n, thanks for the help but i'm not quite sure where you are directing us to in Mike1986's thread? If i have understood correctly because we are S-ON with hboot 1.54 and CID=VODAP001 we are unable to flash firmware or return to stock unless someone has an RUU or nandroid for CID=VODAP001. SuperCID doesnt work because we are S-ON and we cant S-OFF because we are on hboot 1.54 (Revone doesnt work). Is that not correct?
I know we can flash ROMs and use a different 'recovery' but we cant update firmware or return the handset to stock Vodaphone.
Have I not understood something?

Mine was originally VODAP001 and I am also looking for a way to go back to Vodafone stock because I am planning to return the phone (i have that awful red/blue noise when taking pictures in low light conditions).
This is my current setup (running mike's 4.3 ROM).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suppose I also need to downgrade my firmware to x.xx.161.x
Any ideas?

Yup Im in the same boat, need to return my phone to htc for repair but need to return it to stock.

any of you teo sort it out im in the same boat. would like any advice appreciate it

Grathite said:
any of you teo sort it out im in the same boat. would like any advice appreciate it
Click to expand...
Click to collapse
you may wanna check my guide , and adjust to your needs: http://forum.xda-developers.com/showthread.php?t=2541082
post there if you have any issues

Any updates on this?
I am guessing that there are still people who want to recover their device to Vodafone for warranty repairs, is there any more info on a file that can be used (& how) for the UK Vodafone ROM?
Cheers
Martin

still no RUU? i can only find a nandroid for Vodafone Germany -.-

Cactus_Punch said:
still no RUU? i can only find a nandroid for Vodafone Germany -.-
Click to expand...
Click to collapse
if you're talking about this one: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work for UK also:
Code:
ro.aa.modelid=[B]PN0710000[/B]
ro.aa.cidlist=[B]VODAP001[/B],VODAP102,VODAPE17,VODAP405,VODAP304,VODAPD18,VODAP120,VODAP110

nkk71 said:
if you're talking about this one: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work for UK also:
Code:
ro.aa.modelid=[B]PN0710000[/B]
ro.aa.cidlist=[B]VODAP001[/B],VODAP102,VODAPE17,VODAP405,VODAP304,VODAPD18,VODAP120,VODAP110
Click to expand...
Click to collapse
I'm using this that you wrote in another thread
if that is the right one for you, and you stay S-Off, then:
"1- extract the "firmware.zip" package and put it in your adb folder; you'll need it later
2- download and install this (using CWM or TWRP): http://www.htc1guru.com/dld/guru_res...-24-161-1-zip/
select WIPE, unselect ROOT, unselect "stock recovery"
3- use either the Guru Bootloader Reset method (mentioned in the guide), or if you are comfortable with adb:
http://forum.xda-developers.com/show....php?t=2477792 (if you need to remove TAMPERED)
http://forum.xda-developers.com/show....php?t=2475914 (IF you need to set LOCKED)
(the above adb commands work in custom recovery)
4- flash firmware.zip, you extracted earlier:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
you should now be back at stock."
I'm installing the zip and selected wipe but its stuck at 0% D:
Edit: reloaded it and unchecked restore stock radio its installing now

Cactus_Punch said:
I'm using this that you wrote in another thread
if that is the right one for you, and you stay S-Off, then:
"1- extract the "firmware.zip" package and put it in your adb folder; you'll need it later
2- download and install this (using CWM or TWRP): http://www.htc1guru.com/dld/guru_res...-24-161-1-zip/
select WIPE, unselect ROOT, unselect "stock recovery"
3- use either the Guru Bootloader Reset method (mentioned in the guide), or if you are comfortable with adb:
http://forum.xda-developers.com/show....php?t=2477792 (if you need to remove TAMPERED)
http://forum.xda-developers.com/show....php?t=2475914 (IF you need to set LOCKED)
(the above adb commands work in custom recovery)
4- flash firmware.zip, you extracted earlier:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
you should now be back at stock."
I'm installing the zip and selected wipe but its stuck at 0% D:
Edit: reloaded it and unchecked restore stock radio its installing now
Click to expand...
Click to collapse
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.

nkk71 said:
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.
Click to expand...
Click to collapse
Awesome mega thanks!
---------- Post added at 05:22 PM ---------- Previous post was at 04:40 PM ----------
nkk71 said:
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.
Click to expand...
Click to collapse
I finished doing all those steps I still get "This is a test device" messages any idea?

Cactus_Punch said:
Awesome mega thanks!
---------- Post added at 05:22 PM ---------- Previous post was at 04:40 PM ----------
I finished doing all those steps I still get "This is a test device" messages any idea?
Click to expand...
Click to collapse
Because of s-off, disregard msg.
Sent from my HTC One using Tapatalk

OTA update nightmare, am I rooted or not??
Hello,
I've had a real nightmare with this so wondering if you guys could help.
I rooted my phone no probs. I then installed elementalX, no probs. (S-on and still is now) OTA update needs installing, so I thought I'll just put the stock recovery on and install the update, then revert to TWRP all cocky like.
FAIL. So I blame the custom kernel and try uninstalling it, or installing over it with the stock Kernel from htcdev.
Then realise I might have screwed something up using the kernel developer kernel??!! Kernel version currently states:
3.4.10-g40b189c
[email protected] #1
SMP PREEMPT
Flash stock recovery on phone (don't ask me which but I switching between that and TWRP no probs). I panick and disable SuperSu, but it carries on. I delete it using ESfile explorer (giving root permissions to deleting it), its still there. I re-lock the bootloader. I flash the version of the firmware.zip on this thread which is compatible with my VODAP001 (even if it wasn't I'm still s-on, so it won't do anything at worst) it flashes fine, fastboot reboot. Then I try installing the OTA and after a quarter of the install progress I get red triangle and "!". ADB.exe see's my phone as unauthorised, but the phone behaves as if it's rooted still?!
ALL I WANT TO DO IS INSTALL THIS BLOODY OTA UPDATE!! So I can forget about it again. I am currently on 6.12.161.8 the new one is .9. Or is it really that important? Should I freeze "SYSTEM Updates MUC" or similar using Titanium?
Any help would be much appreciated, thanks in advance :good:

mofoofighter said:
Hello,
I've had a real nightmare with this so wondering if you guys could help.
I rooted my phone no probs. I then installed elementalX, no probs. (S-on and still is now) OTA update needs installing, so I thought I'll just put the stock recovery on and install the update, then revert to TWRP all cocky like.
FAIL. So I blame the custom kernel and try uninstalling it, or installing over it with the stock Kernel from htcdev.
Then realise I might have screwed something up using the kernel developer kernel??!! Kernel version currently states:
3.4.10-g40b189c
[email protected] #1
SMP PREEMPT
Flash stock recovery on phone (don't ask me which but I switching between that and TWRP no probs). I panick and disable SuperSu, but it carries on. I delete it using ESfile explorer (giving root permissions to deleting it), its still there. I re-lock the bootloader. I flash the version of the firmware.zip on this thread which is compatible with my VODAP001 (even if it wasn't I'm still s-on, so it won't do anything at worst) it flashes fine, fastboot reboot. Then I try installing the OTA and after a quarter of the install progress I get red triangle and "!". ADB.exe see's my phone as unauthorised, but the phone behaves as if it's rooted still?!
ALL I WANT TO DO IS INSTALL THIS BLOODY OTA UPDATE!! So I can forget about it again. I am currently on 6.12.161.8 the new one is .9. Or is it really that important? Should I freeze "SYSTEM Updates MUC" or similar using Titanium?
Any help would be much appreciated, thanks in advance :good:
Click to expand...
Click to collapse
your missing system files from unlocking the bootloader, OTA will never work unless you RUU back to stock or find a Guru reset that includes the priv-app system folder that got deleted during unlock.
when the OTA fails you can hold volume up and tap power to see what file is missing / changed

Help me please! :(

My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me

JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
tried to boot into recovery with this command:
fastboot boot "C:\pathtorecovery\recoveryname.img"
Click to expand...
Click to collapse
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...

Thank you but have to wait until I get home in approx 4-5 hrs, will try it! Thanks

LibertyMarine said:
tried to boot into recovery with this command:
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...
Click to expand...
Click to collapse
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF

stovie_steve said:
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF
Click to expand...
Click to collapse
JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:

klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Edit: I found a way with HTC ONE Toolkit 2.0, hope I´ll get everything You said working

JeySee said:
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Click to expand...
Click to collapse
I already put it up mate it's "adb push Rom.zip /sdcard

klashnikoff said:
I already put it up mate it's "adb push Rom.zip /sdcard
Click to expand...
Click to collapse
Got Rom installed

JeySee said:
Got Rom installed
Click to expand...
Click to collapse
Ooo good good let me know how it goes

klashnikoff said:
Ooo good good let me know how it goes
Click to expand...
Click to collapse
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!

JeySee said:
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!
Click to expand...
Click to collapse
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware

klashnikoff said:
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware
Click to expand...
Click to collapse
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?

JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.

Everything done, thanks for your help!
Good night ;;?
Sent from my HTC One using xda app-developers app

klashnikoff said:
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.
Click to expand...
Click to collapse
Your welcome good night
Sent from my HTC One using xda app-developers app

klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair

LibertyMarine said:
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair
Click to expand...
Click to collapse
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris

klashnikoff said:
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris
Click to expand...
Click to collapse
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54

nkk71 said:
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54
Click to expand...
Click to collapse
Thought so. Thanks for clarifying

klashnikoff said:
Thought so. Thanks for clarifying
Click to expand...
Click to collapse
no problem, it might have actually been broken by accident, someone disassembled the code and saw a bad memcpy; sort of lost track of the post though

[Q] I need help with restoring my One to stock for warranty purposes.

Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this 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 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.

seklerek said:
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded this 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 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
Click to expand...
Click to collapse
if your phone was on a x.xx.401.x version originally, then use the 1.28.401.7 ruu, then remove *tampered* and *relocked* banner using guru bootloader reset tool by booting a custom recovery using "fastboot boot recovery.img". You can then turn back s-on and send your phone. Everything is described in nkk71's guide linked in my signature.
Don't forget to set back your original CID and MID if you have changed them to convert your phone to GPE before running the ruu

Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.

seklerek said:
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
Click to expand...
Click to collapse
not for warranty purpose cause you must be on hboot 1.44 or 1.54 to remove the "tampered" and "relocked" flags form bootloader.
4.x.401.x ruu is hboot 1.55
1.x.401.x ruu is hboot 1.44

@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?

seklerek said:
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
Click to expand...
Click to collapse
Ruu update everything, firmware and software.
Yes you'll be able to take ota update after but don't update before you have removed tampered and relocked from the bootloader. Follow instructions in the guide.

@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?

seklerek said:
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
Click to expand...
Click to collapse
If you are able to achieve s-off again yes.
They will probably update your phone so it might be more difficult to achieve when it comes back.

@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?

seklerek said:
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
Click to expand...
Click to collapse
do not update the phone now, just turn back s-on and send it for repair. Its easier to get back s-off on lower version so better not to take any ota, however they will maybe update your phone at the service center (hopefully not).

Htc One M7_UL Bricked , help please

hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
see this pictures please , this is all info you need to know
please help me ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello alishadlou,
here you could find stock roms from Google Play Edition and Firmware.
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Hope that help you out.
Greeting
Crytix

alishadlou said:
hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
Click to expand...
Click to collapse
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?

alray said:
Your bootloader version (1.44) doesn't match your firmware version btw
Click to expand...
Click to collapse
not to mention he has the HTC (white) hboot, not the GPE (black) one
that device was definitely S-OFF before

alray said:
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?
Click to expand...
Click to collapse
very very thanks for your nice help ( i love the people who help each other like this .... )
my phone + my friends phone sometimes + love to change roms , try new things , and all of them , and maybe this will be my job for future .
and i treid that you said
but this error
check it please

I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
Click to expand...
Click to collapse
Greeting
Crytix

Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
Greeting
Crytix
Click to expand...
Click to collapse
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more

Crytix said:
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
Here you could find the stock ruu, firmware, bootloader and recovery.
alishadlou said:
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more
Click to expand...
Click to collapse
I don´t allow to link outside xda, because I´m low poster. Please use the external link in that topic linked above.
Greetings
Crytix

Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so.
Click to expand...
Click to collapse
The actual Hboot installed on OP's phone is a Hboot from a Sense based firmware (not a GPE hboot) like nkk71 noted. GPE hboot are black colored. The current firmware version installed (5.11.1700.3) include the 1.54 GPE (black) hboot (he is on 1.44). So its a Sense hboot on a GPE phone + not the right version number for the firmware installed, so its confirm what nkk71 said, that phone was previously s-off, someone flashed the wrong hboot and turned it back s-on.
That being said, you can only, on a "normal" GPE phone, unlock the bootloader using the "fastboot oem unlock" command as opposed to Sense firmware which must be unlocked using htcdev's unlock code. There is also a well known bug with newer GPE firmware (hboot 1.54+) making the bootloader not unlockable.
So in theory, since the phone is running a Sense Hboot, he should be able to unlock using htcdev's unlock code which doesn't seem to work. "fastboot oem unlock" method for GPE variant doesn't work neither.
In his situation, he probably can't unlock his phone because of the wrong hboot installed vs his current firmware version or since the phone was s-off at some point, he might have a custom hboot...
The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities.
Click to expand...
Click to collapse
And this is not applicable to the M7, all shipped M7 bootloader were unlockable and currently, the only M7 version that can't be unlocked is Verizon due to carrier demand.
So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Click to expand...
Click to collapse
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again.[...deleted...] I would try to flash the ruu and achieve s-off with sunshine.

alray said:
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again. I would try to s-off before trying a RUU and then if its not working, flashing the ruu and try to s-off again.
Click to expand...
Click to collapse
With hboot 1.44 it's possible to unlock and S-Off with revone.
@op could you get an adb connection to your phone? Recovery for example.
If not, I can't help you more. Sorry.

Crytix said:
With hboot 1.44 it's possible to unlock and S-Off with revone.
Click to expand...
Click to collapse
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
could you get an adb connection to your phone? Recovery for example.
Click to expand...
Click to collapse
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...

alray said:
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...
Click to expand...
Click to collapse
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone

alishadlou said:
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone
Click to expand...
Click to collapse
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu

alray said:
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu
Click to expand...
Click to collapse
<3 Tnxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <3
My Phone is up nowww
thankkk youu very much
tnx everybody

my phone worked nice , but yesterday , its turn off and no power
when i connect it to pc , its show this driver installing : qhsusb dload
what should i do now ?

help please ...

no help ... ? ....

Use charger to charge it till 100%.

[Q] HELP needed, HTC One Soft Bricked and RUU's wont work

hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work

reealumni said:
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
Click to expand...
Click to collapse
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.

alray said:
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
Click to expand...
Click to collapse
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF

reealumni said:
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
Click to expand...
Click to collapse
At first you need a running system cause sunshine is an app based service. After that you can download the latest sunshine app and install it, then the app will test your device if it is possible to make it s-off. If it can, in the second step you have to buy a license for your device within sunshine (about 20€/25$). After sucessfully payment your device will reboot and sunshine will set it to s-off.(The license is bind to your device and you can use it on this device as often as you want, for other devices you need to buy another license)
http://theroot.ninja/

phone is now working but...
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?

reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
If after flashing the RUU your problem isn't fixed, it's probably an hardware problem.

reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd

KARIM9377 said:
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
Click to expand...
Click to collapse
will try reflash the RUU. i do not have any backups of the partitions :crying: