Database Develop

[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM

Here we have the RUU for the Sprint HTC One 4.06.651.4!!! This RUU is for the Sprint One ONLY to restore your phone back to stock. If you are S-ON, you MUST relock your bootloader prior to using this RUU.
HUGE Thanks to the dude who hooked me up, you're awesome!
credit to @-viperboy- for decrypting, thanks!
***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)
{
"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"
}
How to use:
-Download Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
DEVs, here is the Decrypted version!
Sprint_HTC_One_m7wls_4.06.651.4_RUU_decrypted.zip
These new RUU's now have the system.img split into 3 imgs. You must combine prior to extracting. Copy all 3 to a folder, then...
Use this cmd for Windows:
copy /b system_1.img + system_2.img + system_3.img newsystem.img
Use this cmd for Linux:
cat system_1.img system_2.img system_3.img > newsystem.img
credit to @-viperboy- for the cmds, thanks!
Here is the extracted Firmware:
Full Firmware from RUU (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407568410
Modified Firmware w/ Radio....removed hboot, boot, recovery (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407574146
some basic instructions for flashing the modified firmware....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type Fastboot oem rebootRUU
-when u see the black screen w/ HTC, type Fastboot flash zip firmware.zip
-when it's done, type Fastboot reboot
Here's a nice video from @thoughtlesskyle showing you how to flash the firmware:

Stock Rooted Romz Made From The RUU
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
MD5 5603e630ddffc29a9dd20c96867c1853
Sprint_One_Stock_Rooted_Odex_4.06.651.4.zip
MD5 022aad5e626f08ea6899d7390320324c
Unsecure boot img. init.d support, data/app support
If you get the Side by Side Configuration error while using the RUU you need to install Microsoft Visual C++​

Great work gents
Sent from my Nexus 7

If I were to do the Ruu and im s-off with hboot 1.55 will it update me to 1-56 hboot and still have s-off. I read on a thread that by flashimg the Ruu will eliminate my phone not able to update profile and prl. I jhave been having issues in updating my profile with code 1233, currently in Bad Boyz Rom 1.0 4.06
Sent from my HTCONE using xda app-developers app

Thank you for offering this option so soon, it's greatly appreciated and saves so much time!
Sent from my HTCONE using Tapatalk

there have been reports of the RUU not unzipping, I have re-upped... http://www.androidfilehost.com/?fid=23329332407573774

Will come in handy, thanks O.M.J.!
Sent from my HTCONE

This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."

Is the RUU different than the OTA?

numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
Are you asking me?

numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
systemshock869 said:
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Click to expand...
Click to collapse
Can you confirm the windows 8.1 drivers are installed?

benny3 said:
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
Can you confirm the windows 8.1 drivers are installed?
Click to expand...
Click to collapse
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.

numus said:
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
Click to expand...
Click to collapse
when u install an OTA, alot of files are "patched", RUU is just cleaner. When I diffed the 4.06 dump against the RUU, most of the files were binary equal but there were 250+ that were not.

OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.

no more simultaneous voice + LTE
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
i updated to kit kat and now I don't have simultaneous voice and LTE which I used to have...anyone else notice this? I know that simultaneous voice and 3G was never an option(unlike the EVO 4G LTE) but I always had simultaneous LTE + Voice...this sucks!!

O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
I'm trying to run the RUU but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?

jaybombz said:
This is exactly what I'm trying to do but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
Click to expand...
Click to collapse
You run this RUU from your PC not fastboot.

BD619 said:
You run this RUU from your PC not fastboot.
Click to expand...
Click to collapse
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!

Unless I am mistaken, you have to relock your bootloader to run the RUU.
jaybombz said:
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Click to expand...
Click to collapse

sevarious said:
Unless I am mistaken, you have to relock your bootloader to run the RUU.
Click to expand...
Click to collapse
OP says only if you're S-ON so I thought you didn't have to if you are S-OFF.

[Q][HELP] One ITA/EU S-OFF. Possible with the latest hboot? No HTCdev?

Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:

--anx-- said:
Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:
Click to expand...
Click to collapse
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.

nkk71 said:
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.
Click to expand...
Click to collapse
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...

--anx-- said:
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...
Click to expand...
Click to collapse
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev

nkk71 said:
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev
Click to expand...
Click to collapse
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...

--anx-- said:
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...
Click to expand...
Click to collapse
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?

nkk71 said:
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?
Click to expand...
Click to collapse
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....

--anx-- said:
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....
Click to expand...
Click to collapse
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.

nkk71 said:
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.
Click to expand...
Click to collapse
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...

--anx-- said:
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...
Click to expand...
Click to collapse
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
{
"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"
}

nkk71 said:
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
Click to expand...
Click to collapse
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?

--anx-- said:
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?
Click to expand...
Click to collapse
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)

nkk71 said:
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)
Click to expand...
Click to collapse
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...

--anx-- said:
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...
Click to expand...
Click to collapse
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller

nkk71 said:
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller
Click to expand...
Click to collapse
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...

--anx-- said:
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...
Click to expand...
Click to collapse
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???

--anx-- said:
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???
Click to expand...
Click to collapse
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.

nkk71 said:
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
Click to expand...
Click to collapse
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
nkk71 said:
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.
Click to expand...
Click to collapse
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:

--anx-- said:
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:
Click to expand...
Click to collapse
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.

nkk71 said:
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM
Click to expand...
Click to collapse
Yes, got it...and I've checked but I've noticed that 4.4.2 isn't supported for the temproot, only 4.3...sadly...
nkk71 said:
.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.
Click to expand...
Click to collapse
Yes, with S-ON pratically I can do everything, I've done that before on my old HTC ONE S some months ago, I remember it...but...HTC can recognize the unlocking because I'll have the "TAMPERED" and "RELOCKED" signatures in fastboot...so they can prove that I've used the token...while with S-OFF you can restore these signatures back to "stock" totally...like you've never used that token...
This is the only hassle...

[Q] Downgrade from 4.4.2 to 4.3 using Mac OS.

Hello Xda-Developers, im new in the Android world, since i've been an iPhone user since the original iPhone all the way to the iPhone 4 (then things got pretty boring with). I used to Jailbreak my iPhone to have a more flexible experience with it... about 8~9 months ago i bought my first Android, an HTC One (M7) and it worked like a charm and never wanted to look back to iPhone, UNTIL one day i made an OTA update to 4.4.2, i've been having troubles with the signal, it shows full bars, i have 3G signal, but it shows "No Service" and i can't make/receive calls/SMS, i've been searching for 2 weeks or so, on how to fix it and i even sent it to warranty, and had my Sim replaced... twice. The problem persists, reading further i found that many users have been having this issues (and others) since the Kit Kat Update... So i decided to go beyond the world of a normal user... i want to downgrade from 4.4.2 to 4.3 (by the way i'm a Mac user), before making this thread i've been looking other threads and forums to help me on how to do it This is my first post on XDA Developers. Trust me, i've been looking for answers everywhere, the most similar thread i found was this thread.
And at the end the guy went for a new device, so that thread didn't help me out that much.
What i was able to do (hey, at least its a start) is to Unlock the Bootloader via HTCdev.
i think i've read pretty much to know some terms already, also thanks to Lifehacker
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).

Update
hzlx said:
Hello Xda-Developers, im new in the Android world, since i've been an iPhone user since the original iPhone all the way to the iPhone 4 (then things got pretty boring with). I used to Jailbreak my iPhone to have a more flexible experience with it... about 8~9 months ago i bought my first Android, an HTC One (M7) and it worked like a charm and never wanted to look back to iPhone, UNTIL one day i made an OTA update to 4.4.2, i've been having troubles with the signal, it shows full bars, i have 3G signal, but it shows "No Service" and i can't make/receive calls/SMS, i've been searching for 2 weeks or so, on how to fix it and i even sent it to warranty, and had my Sim replaced... twice. The problem persists, reading further i found that many users have been having this issues (and others) since the Kit Kat Update... So i decided to go beyond the world of a normal user... i want to downgrade from 4.4.2 to 4.3 (by the way i'm a Mac user), before making this thread i've been looking other threads and forums to help me on how to do it This is my first post on XDA Developers. Trust me, i've been looking for answers everywhere, the most similar thread i found was this thread.
And at the end the guy went for a new device, so that thread didn't help me out that much.
What i was able to do (hey, at least its a start) is to Unlock the Bootloader via HTCdev.
i think i've read pretty much to know some terms already, also thanks to Lifehacker
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).
Click to expand...
Click to collapse
UPDATE:
I just rooted it with TWRP and SuperSU
also the bootloader has a ***TAMPERED*** flag (if this is somehow harmful, how can i remove it?)

hzlx said:
UPDATE:
I just rooted it with TWRP and SuperSU
also the bootloader has a ***TAMPERED*** flag (if this is somehow harmful, how can i remove it?)
Click to expand...
Click to collapse
Tampered is not harmful, just ugly to see. It's a flag for service to know your phone is not unlocked out of the box. You can just flash a 4.3 ROM, no need to s-off

hzlx said:
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).
Click to expand...
Click to collapse
Yes, s-off is required to downgrade. Ruu is possible with a mac if you use a ruu.zip instead of a ruu.exe. S-OFF is more difficult to achieve on hboot 1.56, so maybe you'll have to use a custom rom if you can't s-off.
If you already unlocked bootloader and rooted your phone, I assume you can use adb and fastboot from your mac. If not then read this thread: http://forum.xda-developers.com/showthread.php?t=1917237
Then s-off the phone using rumrunner or firewater.
There is also a discussion here about S-OFF and hboot 1.56: http://forum.xda-developers.com/showthread.php?t=2567727
If you can s-off you'll be able to downgrade using a ruu.zip from your mac.

donkeykong1 said:
Tampered is not harmful, just ugly to see. It's a flag for service to know your phone is not unlocked out of the box. You can just flash a 4.3 ROM, no need to s-off
Click to expand...
Click to collapse
So, i can flash any 4.3 ROM (regardless of my phones software version [4.19.401.11] and/or my CID)?
After this, will i be able to make OTA Updates?

hzlx said:
So, i can flash any 4.3 ROM (regardless of my phones software version [4.19.401.11] and/or my CID)?
After this, will i be able to make OTA Updates?
Click to expand...
Click to collapse
You can flash anything you like. If you flash stock rooted 4.3 ROM you will get OTA but you can't upgrade just like that. You need to relock your bootloader, flash stock recovery and stock kernel. On the other hand, you have great choice of custom kitkat ROMs which work great, so you can flash one of them. ARHD 53 would be my recomendation

alray said:
Yes, s-off is required to downgrade. Ruu is possible with a mac if you use a ruu.zip instead of a ruu.exe. S-OFF is more difficult to achieve on hboot 1.56, so maybe you'll have to use a custom rom if you can't s-off.
If you already unlocked bootloader and rooted your phone, I assume you can use adb and fastboot from your mac. If not then read this thread: http://forum.xda-developers.com/showthread.php?t=1917237
Then s-off the phone using rumrunner or firewater.
There is also a discussion here about S-OFF and hboot 1.56: http://forum.xda-developers.com/showthread.php?t=2567727
If you can s-off you'll be able to downgrade using a ruu.zip from your mac.
Click to expand...
Click to collapse
Thanks a lot!
So far i managed to Unlock bootloader (with a Tampered Flag), S-OFF with firewater on hboot 1.56 and root it via TWRP and SuperSU.
I cant find a RUU for my CID HTC__405 though i have this stock ROM and it says it can restore to stock radios (which hopefully will solve my problems)... stock radios will be restored now that i have S-Off... right?
and a last question... once i am back in 4.3 will i be able to download further OTA updates (say... when 4.4.3 comes out)? if not, what should i do now?

Stuck on boot scren htc one logo
I got stuck on the HTC Logo boot screen... i installed a 4.3 ROM via TWRP, im S-Off now and unlocked hboot 1.56 ... why am i stuck? i've been reading i need the correct kernels, but where do i find them and how do i install them?
PLEASE HELP :crying:

NEVERMIND
hzlx said:
I got stuck on the HTC Logo boot screen... i installed a 4.3 ROM via TWRP, im S-Off now and unlocked hboot 1.56 ... why am i stuck? i've been reading i need the correct kernels, but where do i find them and how do i install them?
PLEASE HELP :crying:
Click to expand...
Click to collapse
Nevermind i managed to solve it :fingers-crossed:

Did you check your md5's??? I've had a multitude of my friends phones get stuck on boot screen.. Tell them to check md5 and it works.. One, as others have said, I would suggest flashing a couple Roms. See what you like, if you don't like any of them, then ruu back to stock. Also what twrp are you using? Did the ROM you installed request for a certain recovery to be used? I'm a Mac user so I understand lol. But what ROM??
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF

pball52998 said:
Did you check your md5's??? I've had a multitude of my friends phones get stuck on boot screen.. Tell them to check md5 and it works.. One, as others have said, I would suggest flashing a couple Roms. See what you like, if you don't like any of them, then ruu back to stock. Also what twrp are you using? Did the ROM you installed request for a certain recovery to be used? I'm a Mac user so I understand lol. But what ROM??
Click to expand...
Click to collapse
i managed to solve it, i re installed this ROM which matches my CID (HTC__405), the ROM didnt ask me for any recovery to be used..... anyway.. so far i haven't had any luck fixing my first issue, which is that whenever i lose signal it wont reconnect, it will say "No Service" but still have 3G/4G working, i cant make/receive calls/SMSs.
Any idea on how to fix this issue?

hzlx said:
i managed to solve it, i re installed this ROM which matches my CID (HTC__405), the ROM didnt ask me for any recovery to be used..... anyway.. so far i haven't had any luck fixing my first issue, which is that whenever i lose signal it wont reconnect, it will say "No Service" but still have 3G/4G working, i cant make/receive calls/SMSs.
Any idea on how to fix this issue?
Click to expand...
Click to collapse
So, the issue is not resolved with custom ROM? I guess it's a hardware problem then

62 382926
donkeykong1 said:
So, the issue is not resolved with custom ROM? I guess it's a hardware problem then
Click to expand...
Click to collapse
Nope, before making this whole thread i sent it to warranty and they supposedly repaired it, i changed sim twice.
im going back further, trying 2.24.401.8 with android 4.2
Let's see if that works, or else i'll start trying custom ROMs... so far i've been using stocks.

hzlx said:
Nope, before making this whole thread i sent it to warranty and they supposedly repaired it, i changed sim twice.
im going back further, trying 2.24.401.8 with android 4.2
Let's see if that works, or else i'll start trying custom ROMs... so far i've been using stocks.
Click to expand...
Click to collapse
Well, good luck. I just want to say - if you have the same problem with more than one ROM, no matter if it's stock or modified there is a hardware issue.
Supposedly is what bothers me the most in your case. Maybe your service doesn't care for their customers. It wouldn't be the first

True ^^ I agree with @donkeykong1 If you've had two SIMs and all that......its a hardware issue that is malfunctioning....

pball52998 said:
True ^^ I agree with @donkeykong1 If you've had two SIMs and all that......its a hardware issue that is malfunctioning....
Click to expand...
Click to collapse
Ok... i'm just trying with this last ROM... if it doesn't work... what are the steps to go back to full stock (Locked, S-ON, remove TAMPERED, unrooted)? so i can send it back to warranty
Thanks @pball52998 & @donkeykong1

hzlx said:
Ok... i'm just trying with this last ROM... if it doesn't work... what are the steps to go back to full stock (Locked, S-ON, remove TAMPERED, unrooted)? so i can send it back to warranty
Thanks @pball52998 & @donkeykong1
Click to expand...
Click to collapse
You're s-off correct? Ive seen people not needing to go back s-on for warranty purposes. But pretty much if you want to go back to stock, its just ruu, it does it all for you. Takes you back Locked with factory recovery and full just straight stock.

pball52998 said:
You're s-off correct? Ive seen people not needing to go back s-on for warranty purposes. But pretty much if you want to go back to stock, its just ruu, it does it all for you. Takes you back Locked with factory recovery and full just straight stock.
Click to expand...
Click to collapse
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
{
"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"
}
Thanks again!

hzlx said:
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
Thanks again!
Click to expand...
Click to collapse
Okay, well a ruu can be placed on the internal memory.....but...... the way that I've always seen it done, or a lot of times is
Code:
./adb reboot bootloader
Code:
./fastboot oem rebootRUU
Code:
./fastboot flash RUU.zip
the RUU.zip could be named anything so you might have to rename the RUU or change the RUU.zip in terminal to what ever the foop you named it, although I wouldn't do the RUU with those instructions just yet.... Can someone else confirm it??

hzlx said:
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
Thanks again!
Click to expand...
Click to collapse
you might want to reset your phone using a ruu before to make sure your issue is really related to an hardware defect.
This ruu.zip will reset your phone to stock 1.28.401.7 (android 4.1.2) and hboot 1.44.
Then if you see the phone still have the issue, remove the tampered flag and set the bootloader back to ''LOCKED'' using this tool. Then s-on and send for warranty repair/replacement. This procedure must be done before you take any ota that will update your phone to hboot 1.55 or the tampered flag will come back and you'll have to s-off again and redo the entire procedure.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
pball52998 said:
Okay, well a ruu can be placed on the internal memory.....but...... the way that I've always seen it done, or a lot of times is
Code:
./adb reboot bootloader
Code:
./fastboot oem rebootRUU
Code:
./fastboot flash RUU.zip
the RUU.zip could be named anything so you might have to rename the RUU or change the RUU.zip in terminal to what ever the foop you named it, although I wouldn't do the RUU with those instructions just yet.... Can someone else confirm it??
Click to expand...
Click to collapse
Make sure the ruu.zip is in the same folder where adb and fastboot are.
Code:
./adb reboot bootloader
or manually reboot the phone in bootloader using power + vol down
Code:
./fastboot oem rebootRUU
make sure ''RUU'' are capital letters
Code:
./fastboot flash name_of_ruu.zip
First time it will output a failed message, do the same command again:
Code:
./fastboot flash name_of_ruu.zip

[Q] HTC One M7 stuck at bootmenu, relocked bootloader with custom recovery.

Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
{
"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"
}
Any suggestions? Thanks in advance.

arthurrrr said:
Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.

Danny201281 said:
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.
Click to expand...
Click to collapse
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: 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.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.

arthurrrr said:
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: 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.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.
Click to expand...
Click to collapse
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to be relocked so leave it that way.
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader

Danny201281 said:
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader
Click to expand...
Click to collapse
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out

Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app

arthurrrr said:
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out
Click to expand...
Click to collapse
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:

Danny201281 said:
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:
Click to expand...
Click to collapse
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.

arthurrrr said:
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.
Click to expand...
Click to collapse
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:

Danny201281 said:
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:
Click to expand...
Click to collapse
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.

arthurrrr said:
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.
Click to expand...
Click to collapse
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes

Danny201281 said:
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes
Click to expand...
Click to collapse
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:

arthurrrr said:
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:
Click to expand...
Click to collapse
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
sonic_boom said:
Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:

Danny201281 said:
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:
Click to expand...
Click to collapse
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?

sonic_boom said:
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?
Click to expand...
Click to collapse
Your Welcome :highfive:
No need to relock your bootloader, That's only for flashing RUU's or Firmware. Just flash the Stock rom and Recovery and your good to go. :good:

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%.