Database Develop

My HTC One is screwed?

Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.

Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.

MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this

MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry

[Q] Help me unbrick my htc one please?

im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:

ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.

ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!

OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.

ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.

Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app

stuck on slash screen, No recovery, Bootloop

Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001

profixit said:
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
Click to expand...
Click to collapse
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide

Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.

profixit said:
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
Click to expand...
Click to collapse
downgrading hboot is pretty easy
just follow the steps under ''If you’re on hboot which is above 1.44'' from nkk71's guide
then change cid
then run ruu.exe
but do not use a win 8.1 computer (compatibility issue with hboot 1.44)

Thanks for that last bit, what about Win8.
I've spotted the steps that apply to me, just playing them out in my head.
Out of curiosity after a downgrade the HBoot, will it be locked and s-on?

profixit said:
Thanks for that last bit, what about Win8.
Click to expand...
Click to collapse
windows 8.0 should be fine, but definitively not 8.1

alray said:
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Click to expand...
Click to collapse
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?

profixit said:
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
Click to expand...
Click to collapse
sry my bad
use this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/
1.28.401

No worries, Thanks.

Can you try fastboot erase cache from fastboot menu and re enter recovery?

Tried that, thanks
Sent from my HTC One using Tapatalk

OK, a little lucky positive progress.
I managed to flash clockworkMod recovery, don't ask me how, maybe erasing the cache lots of times did it, i'm sure it was a recovery I had already tried. I checked my download list and confirmed I did download it., so i would of tried to flash it two days ago. Funny.
Still stuck on splash screen, but can boot into recovery. (clockworkmod)
Please, what is the best way to proceed, I'm thinking nandroid backup, but like I said, I couldn't care less about orange. I would love to put Mike1986 stock rom 4.3 or 4.4
I'm unable or don't know how to get folders or files on the phone's internal SD card, because it doesn't boot up a rom any more. Y-cable?
I'm concerned with all the "can't" at the bottom of recovery screen.

[Q] Help Unrooting HTC One M8

Hi so I rooted my One M8 and installed a custom recovery while on software version 1.54.654.10 and tried to do S-Off but was having problems with that so have been attempting to unroot and get a stock recovery for that software version but I''m having problems with my computer not detecting fastboot or ADB or something so I can't do it from there I just need someone's advice on what to do and how to unroot and go back to stock
So what I'd really like is a stock RUU since I'm having trouble finding that file and not a ZIP since I don't have a micro SD card so if someone has that to the latest one or some way they know to fix my issue that'd be great
UPDATE: So I've flashed the RUU zip through the bootloader multiple times and have unrooted the phone through the SuperSU app after said RUU didn't do it and I still can't seem to download and install the latest official update. Any ideas on a fix?

Hit the second link in my sig. Scroll down to the section about RUU's. The RUU for 1.54.651.10 can be found at the bottom of the first post. You'll need to relock your bootloader before running the RUU. I recommend installing HTC Sync on your PC before you run the RUU.
Edit: Scratch what I said above. This particular RUU has to be run off the external SD card, which you already stated you don't have. You can try it from your computer but according to @O.M.J it won't work (or it didn't for somebody else that tried it from their computer).
Why not try the method outlined in the thread below?
http://forum.xda-developers.com/showthread.php?t=2736048

Magnum_Enforcer said:
Hit the second link in my sig. Scroll down to the section about RUU's. The RUU for 1.54.651.10 can be found at the bottom of the first post. You'll need to relock your bootloader before running the RUU. I recommend installing HTC Sync on your PC before you run the RUU.
Edit: Scratch what I said above. This particular RUU has to be run off the external SD card, which you already stated you don't have. You can try it from your computer but according to @O.M.J it won't work (or it didn't for somebody else that tried it from their computer).
Why not try the method outlined in the thread below?
http://forum.xda-developers.com/showthread.php?t=2736048
Click to expand...
Click to collapse
I might be able to borrow an SD card from a friend, so I'd just put the RUU zip on an SD card, boot into the bootloader and it'll install the stock recovery and revert back to that state?

LemonNinja said:
I might be able to borrow an SD card from a friend, so I'd just put the RUU zip on an SD card, boot into the bootloader and it'll install the stock recovery and revert back to that state?
Click to expand...
Click to collapse
yes, extract the 0P6BIMG.zip from the RUU zip to external sd card, then boot into bootloader....if it doesn't work, you'll have to lock bootloader first w/ this cmd:
fastboot oem lock
if your fastboot is not working, make sure you have the drivers installed or htc sync
all the required resources are on the htcdev.com site:
http://www.htcdev.com/bootloader/unlock-instructions

O.M.J said:
yes, extract the 0P6BIMG.zip from the RUU zip to external sd card, then boot into bootloader....if it doesn't work, you'll have to lock bootloader first w/ this cmd:
fastboot oem lock
if your fastboot is not working, make sure you have the drivers installed or htc sync
all the required resources are on the htcdev.com site:
http://www.htcdev.com/bootloader/unlock-instructions
Click to expand...
Click to collapse
Should I unroot from the SuperUser app or just go directly into the bootloader?
Edit: Also i seems to say ***Security Warning*** under Relocked on the bootloader screen I'm guessing that's natural when it's been tampered but relocked?
Edit Edit: So I had it on the external SD and fastboot OEM locked it and for some reason it didn't get rid of SuperSU or install the stock recovery, when I tried to install the newest update it just went directly to the bootloader

The security warning is normal. Just run the RUU from the bootloader-it will unroot your phone. No need to mess with SuperSU.

Magnum_Enforcer said:
The security warning is normal. Just run the RUU from the bootloader-it will unroot your phone. No need to mess with SuperSU.
Click to expand...
Click to collapse
I did it, ran it and it didn't delete SuperSU or anything and I'm guessing TWRP is still there because I ran the RUU zip and tried to update to 4.4.3 and it just went directly into the bootloader
Edit: Alright I found a stock recovery for the .8 and going to hope that works y putting it through bootloader in the same zip file name the stock RUU was on

Sounds like the RUU didn't run like it should have.

Magnum_Enforcer said:
Sounds like the RUU didn't run like it should have.
Click to expand...
Click to collapse
Yeah I just flashed that stock recovery through the bootloader and it isn't booting into TWRP so it may have worked, I'm going to try that. Do you have the stock recovery from the .10 firmware that matches mine? If so could you upload it here or send it to me just in case the .8 doesn't work?
Edit: Alright looks like the stock recovery has flashed since it doesn't say ***Security Warning*** anymore and just Tampered, Relocked
Edit Edit: Alright I went to go do the official update from the phone itself and it went back to having the ***Security Warning*** for some reason

You can't get rid of the security warning unless you're S-off.

@Magnum_Enforcer for some reason it was going away when I'd flash one of the files through fastboot I had no idea why
Sent from my 831C using XDA-FORUM, powered by appyet.com

Softbrick (kinda) problem

Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance

soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.

I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.

Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.

soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at

dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember