Develop Bugs

[Q] Used AAHK. In Hboot with S-ON. What now?

Ok, here's the gist. Went to root a friends phone. Used AAHK as I had on mine. It needed to downgrade (as it had done previously with mine). After downgrading it wouldn't boot. Just hung on HTC boot screen. Waited 10+ mins...nothing. Tried a few times...nothing. I can get into Hboot using power/volume but have no idea what to do from here as I can't boot into a ROM so the laptop/aahk can see it. I've tried bootloader....nothing happens. Tried Factory reset...nothing happens...just goes back to HTC boot screen. Can any kind person help out a noob in distress here. Any help will be greatly appreciated.
Thanks in advance.:good:

NipzBGD said:
Ok, here's the gist. Went to root a friends phone. Used AAHK as I had on mine. It needed to downgrade (as it had done previously with mine). After downgrading it wouldn't boot. Just hung on HTC boot screen. Waited 10+ mins...nothing. Tried a few times...nothing. I can get into Hboot using power/volume but have no idea what to do from here as I can't boot into a ROM so the laptop/aahk can see it. I've tried bootloader....nothing happens. Tried Factory reset...nothing happens...just goes back to HTC boot screen. Can any kind person help out a noob in distress here. Any help will be greatly appreciated.
Thanks in advance.:good:
Click to expand...
Click to collapse
You don't need to boot into a ROM to do stuff. You're fine as long as you can reach the bootloader. Read the Noob Starter Guide by Glevitan for more info. Find it here : http://forum.xda-developers.com/showpost.php?p=30007264&postcount=2
---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------
If you need to know what you need to read.. You already have a downgraded hboot.. you need to S-OFF it and flash a custom recovery now. You can read on how to do that from the guide I mentioned.

if4ct0r said:
You don't need to boot into a ROM to do stuff. You're fine as long as you can reach the bootloader. Read the Noob Starter Guide by Glevitan for more info. Find it here : http://forum.xda-developers.com/showpost.php?p=30007264&postcount=2
---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------
If you need to know what you need to read.. You already have a downgraded hboot.. you need to S-OFF it and flash a custom recovery now. You can read on how to do that from the guide I mentioned.
Click to expand...
Click to collapse
Thanks for the response. I have quickly read through the guide but am slightly confused to say the least. I can't find how to get S-Off from here, other than through aahk. Bootloader does nothing when selected, and recovery just takes me back to the htc boot screen. I'm stuck here. Could you please point me to the right (next) step (S-off). I have read the guide, but it doesn't say how to do it from Hboot.
For example, the guide states this :-
Unlocking the bootloader with HTCDEV tool will allow you to flash CWM recovery and install
custom roms for ACE models and not ported roms, meaning that roms ported from other devices
such as Sensation or Sensation XL will not be successfully be flashed.
..which is all well and good. Ok, I have an unlocked bootloader so I can install CWM, but HOW?

Can you post the text appearing on top of your bootloader here?
Depending on that you might need to either flash a recovery or fix your bootloader.

if4ct0r said:
Can you post the text appearing on top of your bootloader here?
Depending on that you might need to either flash a recovery or fix your bootloader.
Click to expand...
Click to collapse
Of course. Thanks again, as it's driving me crazy trying to find how to S-off and install CWM from here.
ACE PVT SHIP S-ON RL
HBOOT - 0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011, 00:55:45

Alright. You used AAHK right? Did you read the guide and follow all the steps? I'll suggest to use the "Fixing your messed bootloader" section of the guide I mentioned previously and then run the AAHK again.
Get the latest version from here : http://tau.shadowchild.nl/attn1/?p=74

if4ct0r said:
Alright. You used AAHK right? Did you read the guide and follow all the steps? I'll suggest to use the "Fixing your messed bootloader" section of the guide I mentioned previously and then run the AAHK again.
Ok this is what it says.....
Hboot fix
md5sum hboot.nb0
adb push hboot.nb0 /data/local/tmp/
adb push gfree /data/local/tmp/
adb push psneuter /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/gfree
adb shell chmod 0755 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell /data/local/tmp/gfree -f
adb shell
dd if=/data/local/tmp/hboot.nb0 of=/dev/block/mmcblk0p18
dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/hboot.test
sync
exit
adb pull /data/local/tmp/hboot.test
md5sum hboot.test
All md5sums should be 2a28dcd53ea26504be9a86572a348aa1
adb reboot
I did the first few steps, (I've removed the links as it won't let me post them here) and got the file into C ok with the files from the hack kit. When I start ADB (via the Start Here command) and I type in the commands above, it says "Device not found". I have tried to follow the link that it states to read for people new to ADB, but it takes me to a massive page of links and I have no idea where to start. Thanks for your help up to now, it really is appreciated, and I fear I'm in above my neck here, and am now a walking advert for why people like me shouldn't go down this route. When I did my phone, it really wasn't a problem and the whole AADK process went fine. I have been flashing custom roms on my phone for months without a single problem, and it's only when my friend/colleague saw me running JellyTime 17.2 that he wanted it too. Now I fear I'm stuck!
Click to expand...
Click to collapse

Calm down. It's all solvable. And we can get it back working.
For adb to work you need to connect your device and let it go into bootloop (switch it on and let it stay as it is).
Once it goes into that state, try typing "adb devices" it should show a list of devices attached, you should see your phone in there. Once your phone is recognized, the adb commands should work.
Also, do you have HTC Sync installed?

if4ct0r said:
Calm down. It's all solvable. And we can get it back working.
For adb to work you need to connect your device and let it go into bootloop (switch it on and let it stay as it is).
Once it goes into that state, try typing "adb devices" it should show a list of devices attached, you should see your phone in there. Once your phone is recognized, the adb commands should work.
Also, do you have HTC Sync installed?
Click to expand...
Click to collapse
Kicking myself for realising that HTC sync WAS installed. Have uninstalled, wiped drivers, and reinstalled drivers from here. Rebooted laptop. Still the same. Ok, my ADB console I type in adb devices and it says List of devices attached and just shows the same command prompt line underneath (i.e C:\Windows\system32> so I don't think it's seeing the device.
When you say "Let it go into bootloop", all I have have done is turned it on and it goes to the HTC screen, I hope this is right. Windows see's the phone ok. When I plug it in it sees it as "USB mass device installed". Is this the problem?

NipzBGD said:
Kicking myself for realising that HTC sync WAS installed. Have uninstalled, wiped drivers, and reinstalled drivers from here. Rebooted laptop. Still the same. Ok, my ADB console I type in adb devices and it says List of devices attached and just shows the same command prompt line underneath (i.e C:\Windows\system32> so I don't think it's seeing the device.
When you say "Let it go into bootloop", all I have have done is turned it on and it goes to the HTC screen, I hope this is right. Windows see's the phone ok. When I plug it in it sees it as "USB mass device installed". Is this the problem?
Click to expand...
Click to collapse
Did you enable USB Debugging on the stock ROM before you started AAHK? If not then thats the reason probably why ADB is not working right now.
Anyway, what I'll suggest you to do right now is to boot into the bootloader and run an RUU.
Get an appropriate RUU from here : http://www.filefactory.com/f/efa28fefafc4af9c/
Appropriate means your region, WWE is the worldwide edition and mostly safe for all devices. Download the RUU, connect your phone(in the bootloader mode) and run the .exe from the computer. Follow the on-screen instructions then. The phone should return to stock after the complete setup has run and you can try the AAHK again.
The other method is to unlock your bootloader via the HTCDEV method and flash a recovery and then flash a rooted ROM. The HTCDEV method is not good one for various reasons but it might prove easier.
Go to www.htcdev.com for using that method for bootloader unlock.

if4ct0r said:
Did you enable USB Debugging on the stock ROM before you started AAHK? If not then thats the reason probably why ADB is not working right now.
Anyway, what I'll suggest you to do right now is to boot into the bootloader and run an RUU.
Get an appropriate RUU from here : http://www.filefactory.com/f/efa28fefafc4af9c/
Appropriate means your region, WWE is the worldwide edition and mostly safe for all devices. Download the RUU, connect your phone(in the bootloader mode) and run the .exe from the computer. Follow the on-screen instructions then. The phone should return to stock after the complete setup has run and you can try the AAHK again.
The other method is to unlock your bootloader via the HTCDEV method and flash a recovery and then flash a rooted ROM. The HTCDEV method is not good one for various reasons but it might prove easier.
Go to www.htcdev.com for using that method for bootloader unlock.
Click to expand...
Click to collapse
Yes, I had enabled USB debugging. I'll try the RUU trick and let you know how I get on. And thanks for your help.

NipzBGD said:
Yes, I had enabled USB debugging. I'll try the RUU trick and let you know how I get on. And thanks for your help.
Click to expand...
Click to collapse
No worries.
There might be also a way to S-OFF from the bootloader and fastboot and I think Glevitan might help you with that. But since he's not around at the moment and you're kinda worried I'll say the RUU way is the best option as of now.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
Also.. this post here will help you with the HTCDEV method if you go for that.

if4ct0r said:
No worries.
There might be also a way to S-OFF from the bootloader and fastboot and I think Glevitan might help you with that. But since he's not around at the moment and you're kinda worried I'll say the RUU way is the best option as of now.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
Also.. this post here will help you with the HTCDEV method if you go for that.
Click to expand...
Click to collapse
I downloaded the RUU overnight as it took a few hours. I've just ran it and even though I selected the Orange UK one from that list, it started the process and then said it was the wrong RUU and to please download the correct one. I'm now downloading a WWE one to try. There's a few different ones so here's hoping!

NipzBGD said:
I downloaded the RUU overnight as it took a few hours. I've just ran it and even though I selected the Orange UK one from that list, it started the process and then said it was the wrong RUU and to please download the correct one. I'm now downloading a WWE one to try. There's a few different ones so here's hoping!
Click to expand...
Click to collapse
It worked. Success! Installed that, ran AAHK again, and it ran through no problem this time. Installed JB (randomblames Jellytime), flashed the GAPPS and all is good. He now has a working phone. If I could buy you a drink then I would! Many many many thanks for your help and patience!

NipzBGD said:
It worked. Success! Installed that, ran AAHK again, and it ran through no problem this time. Installed JB (randomblames Jellytime), flashed the GAPPS and all is good. He now has a working phone. If I could buy you a drink then I would! Many many many thanks for your help and patience!
Click to expand...
Click to collapse
I'm glad I could help. And I appreciate the gesture but really.. no need to buy me a drink.. We're all here to help each other.
Cheers.

htc unlock utility not working

hi all i have just tried the unlock tool both versions and i keep getting device not detected i have the correct drivers installed i ran the adb file and it doesnt dect its in hboot mode s-on, hboot 0.93.0001 radio 5.11.05.27
any ideas?

tamgunner14 said:
hi all i have just tried the unlock tool both versions and i keep getting device not detected i have the correct drivers installed i ran the adb file and it doesnt dect its in hboot mode s-on, hboot 0.93.0001 radio 5.11.05.27
any ideas?
Click to expand...
Click to collapse
U didnt have to open a new thread. If it says device not detected then u dont have correct drivers installed for bootloader otherwise it would of detected ur phone. Search here for adb & fastboot guide and install the correct fastboot drivers then try again.
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Also search in that thread for answers, im sure ur not the only one to have this problem..

.
jmcclue said:
U didnt have to open a new thread. If it says device not detected then u dont have correct drivers installed for bootloader otherwise it would of detected ur phone. Search here for adb & fastboot guide and install the correct fastboot drivers then try again.
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Also search in that thread for answers, im sure ur not the only one to have this problem..
Click to expand...
Click to collapse
wouldnt let me reply to the other one. i have the correct drivers i have uninstalled them and reinstalled them 4 times now from
and followed every step!

tamgunner14 said:
wouldnt let me reply to the other one. i have the correct drivers i have uninstalled them and reinstalled them 4 times now from
and followed every step!
Click to expand...
Click to collapse
i managed to get the utility to run last night and it said it was done and the phone restarted i tried putting in my working three sim and its showing limited or no service?

[Q] I have a problem.

So I have a problem. I rooted and unlocked my bootloader just fine on my T-Mobile HTC One M8. While installing insert coin to prep for s-off, I was wiping my data and accidentally deleted my operating system (oops). So I followed a tutorial and tried using firewater and I got the "whelp, no amount of retrying will make this work on your device" message. I want to use Sunshine now, but I can't because sunshine only works with stock sense, which I accidentally deleted. I have looked and looked online and the only presumable way of getting the operating system back is through an RUU which I can't do because I'm not S-Off. I can't get S-Off because I don't have sense, and I can't get sense because I'm not S-Off. Is there just a regular ROM I could use to flash sense just temporarily while I get sunshine? My whole goal of this was to make my regular M8 a google play edition, as I prefer stock android.

TrentCowden said:
So I have a problem. I rooted and unlocked my bootloader just fine on my T-Mobile HTC One M8. While installing insert coin to prep for s-off, I was wiping my data and accidentally deleted my operating system (oops). So I followed a tutorial and tried using firewater and I got the "whelp, no amount of retrying will make this work on your device" message. I want to use Sunshine now, but I can't because sunshine only works with stock sense, which I accidentally deleted. I have looked and looked online and the only presumable way of getting the operating system back is through an RUU which I can't do because I'm not S-Off. I can't get S-Off because I don't have sense, and I can't get sense because I'm not S-Off. Is there just a regular ROM I could use to flash sense just temporarily while I get sunshine? My whole goal of this was to make my regular M8 a google play edition, as I prefer stock android.
Click to expand...
Click to collapse
Who says you need to be S-OFF to run a RUU If there is an RUU available for your device then run it. Just make sure you lock the bootloader before you do.
You could also just flash a ROM(any rom) onto your device or restore a backup from the collection of stock backups thread(In general section).

BerndM14 said:
Who says you need to be S-OFF to run a RUU If there is an RUU available for your device then run it. Just make sure you lock the bootloader before you do.
Click to expand...
Click to collapse
How do I relock the bootloader and why do I have to do that? (just curious)
You could also just flash a ROM(any rom) onto your device or restore a backup from the collection of stock backups thread(In general section).
Click to expand...
Click to collapse
Also I tried downloading a stock sense rom and when I flashed it, my phone turned on and the message "unfortunately, phone has stopped" just kept coming up over and over. Do I need to find a Rom specific to T-mobile and/or my device version?
Thank you so much for your quick response and help!

TrentCowden said:
How do I relock the bootloader and why do I have to do that? (just curious)
Also I tried downloading a stock sense rom and when I flashed it, my phone turned on and the message "unfortunately, phone has stopped" just kept coming up over and over. Do I need to find a Rom specific to T-mobile and/or my device version?
Thank you so much for your quick response and help!
Click to expand...
Click to collapse
To lock bootloader, shut down device. Hold Power button + Volume down to boot into bootloader. Connect Phone to PC. Open command prompt in adb folder. Type
Code:
fastboot devices
To check if the device gets picked up, Next type:
Code:
fastboot oem lock
This will lock bootloader. Then you can run the RUU.exe as administrator on your PC and begin restoring your device back to stock.
Why do you need to lock it? I'm not entirely sure Perhaps it's just part of the verification the RUU needs in order to make changes to the device, kinda like you need to be stock to do OTA. Maybe it just has something to do with the oem method of recovering/restoring the device, I don't know mate, sorry.
Perhaps someone with a bit more expertise can answer that one for you, I only know that it needs to be locked if you're S-ON.

BerndM14 said:
To lock bootloader, shut down device. Hold Power button + Volume down to boot into bootloader. Connect Phone to PC. Open command prompt in adb folder. Type
Code:
fastboot devices
To check if the device gets picked up, Next type:
Code:
fastboot oem lock
This will lock bootloader. Then you can run the RUU.exe as administrator on your PC and begin restoring your device back to stock.
Why do you need to lock it? I'm not entirely sure Perhaps it's just part of the verification the RUU needs in order to make changes to the device, kinda like you need to be stock to do OTA. Maybe it just has something to do with the oem method of recovering/restoring the device, I don't know mate, sorry.
Perhaps someone with a bit more expertise can answer that one for you, I only know that it needs to be locked if you're S-ON.
Click to expand...
Click to collapse
Sweet! Could I just skip going back to stock sense and just go straight to the google play edition ruu?

TrentCowden said:
Sweet! Could I just skip going back to stock sense and just go straight to the google play edition ruu?
Click to expand...
Click to collapse
You'll need to be S-OFF in order to convert to the GPE as it makes changes to the partition sizes on the device. If I recall correctly it was Graffixnyc that made a thread about that and I'm almost sure he mentioned in that very thread that you need to be S-OFF.
First restore your phone to working condition, then get S-OFF then you can follow the guide to convert your device to GPE.
---------- Post added at 11:43 PM ---------- Previous post was at 11:39 PM ----------
[RUU] M8 Google Edition Conversion. 4.4.4 - RUU Zip Non-Rooted & Pre-Rooted
Yep there's the thread I was talking about. You can see he clearly states there:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge

BerndM14 said:
You'll need to be S-OFF in order to convert to the GPE as it makes changes to the partition sizes on the device. If I recall correctly it was Graffixnyc that made a thread about that and I'm almost sure he mentioned in that very thread that you need to be S-OFF.
First restore your phone to working condition, then get S-OFF then you can follow the guide to convert your device to GPE.
---------- Post added at 11:43 PM ---------- Previous post was at 11:39 PM ----------
[RUU] M8 Google Edition Conversion. 4.4.4 - RUU Zip Non-Rooted & Pre-Rooted
Yep there's the thread I was talking about. You can see he clearly states there:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?

TrentCowden said:
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?
Click to expand...
Click to collapse
Just make sure you download the correct version that corresponds to the version your device is.
If you need earlier or other version it's in here: [Recovery] [RUU 2.22.531.5] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
Once that is done you can just right click on the exe file, select run as administrator and follow the onscreen wizard to restore the device back to stock.
---------- Post added 17th September 2014 at 12:00 AM ---------- Previous post was 16th September 2014 at 11:55 PM ----------
TrentCowden said:
OK. So I re-locked my phone. I'm downloading the RUU now from the official HTC website. Once it's done, then what?
Click to expand...
Click to collapse
A quick Google search dropped this guide on restoring, might be worth a look if you're interested.
How to Restore T-Mobile HTC One M8 to Stock with RUU

BerndM14 said:
Just make sure you download the correct version that corresponds to the version your device is.
If you need earlier or other version it's in here: [Recovery] [RUU 2.22.531.5] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
Once that is done you can just right click on the exe file, select run as administrator and follow the onscreen wizard to restore the device back to stock.
---------- Post added 17th September 2014 at 12:00 AM ---------- Previous post was 16th September 2014 at 11:55 PM ----------
A quick Google search dropped this guide on restoring, might be worth a look if you're interested.
How to Restore T-Mobile HTC One M8 to Stock with RUU
Click to expand...
Click to collapse
Hey there!
So I restored my phone and it worked, so I s-offed my phone using Sunshine (because like I said before firewater didn't work for me), and I downloaded the GPE RUU but for some reason when I type adb reboot bootloader into cmd it says error:device not found. When I plug my phone in, it makes the noise that signals that a device has been plugged in, but it doesn't show it in the file explorer. Any ideas?

TrentCowden said:
Hey there!
So I restored my phone and it worked, so I s-offed my phone using Sunshine (because like I said before firewater didn't work for me), and I downloaded the GPE RUU but for some reason when I type adb reboot bootloader into cmd it says error:device not found. When I plug my phone in, it makes the noise that signals that a device has been plugged in, but it doesn't show it in the file explorer. Any ideas?
Click to expand...
Click to collapse
Nevermind, realized I didn't have USB Debugging on.

how do i turn my htc one m8 with s-off TO worldwide europe ?

can't say better :
how do i turn my htc one m8 with s-off TO worldwide europe ?
thx

Depends on which M8 model you have!
Which begs the question... which M8 model do you have?

shirreer said:
Depends on which M8 model you have!
Which begs the question... which M8 model do you have?
Click to expand...
Click to collapse
It is carrier branded device - T-Mobile Poland
CID T-MOB009
MID 0P6B10000
( ckpv5 helped me to find out )
i've used the sunshine app,and now my phone is s-off and rooted permanently ( i done the thing with the token given by htc-dev)

You could have continued here
http://forum.xda-developers.com/showthread.php?t=3286905
But if you want the wwe (latest firmware 4.16.401.13) than download that firmware, fastboot flash it twice and install any of the latest roms. Or run the 4.16.401 RUU.
Or if you want the developers edition up to MM then you can go for that firmware.
Edit :
The phone is not rooted permanently, it's unlocked (bootloader) permanently. Root itself is at OS level and is only achieved when you flash a superuser.zip via the custom recovery or install a pre rooted custom rom !

Fine.
A long and excruciating, nested multi-step process awaits:
Fortunately, your MID needs no modification, so without further ado:
1. You need to change your CID from T-MOB009 to HTC__001:
A. Connect your phone to your computer, boot into bootloader, and go to fastboot.
B. Launch adb on your computer and type (note: there are two underscores, and total 8 characters to the CID):
fastboot oem writecid HTC__001
C. reboot your phone into bootloader and check out your new CID (adb getvar all).
2. Flash the latest available WWE official RUU (stock android 5.0/Sense 6):
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
3. For best results, from my experience, flash that RUU twice, then let it boot, then do a hard-reset from settings.
4. Get coffee.
5. Set yourself up all over again.
6. Profit

shirreer said:
2. Flash the latest available WWE official RUU (stock android 5.0/Sense 6):
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
Click to expand...
Click to collapse
All OP files there are dead links

Here are 4.16.401.10 ruu files
http://forum.xda-developers.com/showthread.php?p=64434617

ckpv5 said:
All OP files there are dead links
Click to expand...
Click to collapse
You're too fast! It's like you're waiting for me to post that dead link Fine. Get this one:
http://androidruu.com/getdownload.p...6G_20.68.4196t.01_F_release_417003_signed.exe

Nah .. I just switch on my PC and I saw the post on top

:laugh: thank you guys , i'm gonna try to do this in the calm way
is still have to make Android ADB interface recognized properly by Win 10.
it gonna be fine , thansk all.

A good number of RUUs are available here:
http://androidruu.com/?developer=M8
@amif7
While I'm merely a helpful rookie, you're very lucky to have the illustrious Mr. Hofs here to help you. He's one of XDA's elite. Hats off

thanks all , hope it will help others with all that precisions.
:good:

shirreer said:
A good number of RUUs are available here:
http://androidruu.com/?developer=M8
@amif7
While I'm merely a helpful rookie, you're very lucky to have the illustrious Mr. Hofs here to help you. He's one of XDA's elite. Hats off
Click to expand...
Click to collapse
Meh. Not as much as i was on the HTC One X

amif7 said:
is still have to make Android ADB interface recognized properly by Win 10.
Click to expand...
Click to collapse
Yes, that is the only way to change CID.
Also, if you use the RUU.exe, you need fastboot interface, which goes hand in hand with adb. However, if you use the RUU zip method (put it right on the phone and boot into bootloader) than you won't need fastboot to do that.

i've done everything and i'm now at the step i try to flash my cell with RUU you've told me.
"RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed"
but problem that has been 30 minutes the status " update" of the wizard with 0/7 update was sent to my phone.
arghh..xd
edit : cid was succesfuly changed to htc__001

Disconnect the phone and try again. This just happens sometimes (its been reported, then works on the subsequent try). Put the phone in bootloader-fastboot mode, if you haven't already tried that.
If it still hangs, you might need to use a different computer. Win7 and USB 2.0 for the best chance of success. RUU is finicky with some computers.

amif7 said:
i've done everything and i'm now at the step i try to flash my cell with RUU you've told me.
"RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed"
but problem that has been 30 minutes the status " update" of the wizard with 0/7 update was sent to my phone.
arghh..xd
edit : cid was succesfuly changed to htc__001
Click to expand...
Click to collapse
Either:
A. Without canceling the ruu process, go to the root of your C: drive and search for Rom.zip file; copy it to your desktop, and rename it to 0P6BIMG.zip (first character is zero, and careful not to rename it to 0P6BIMG.zip.zip). Copy this file to the root of your phone's SD Card. Then, boot your phone into bootloader. Proceed with the on-screen instructions.
Or:
B. Cancel the ruu process, unplug your phone, download & install HTC Sync Manager from HTC's M8 support page. Reboot your PC, plug in your phone and wait until Windows installs the drivers. Start the RUU again and proceed to flashing.
Cheers
P.S. I trust you'll give us feedback about this.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Mr Hofs said:
Meh. Not as much as i was on the HTC One X
Click to expand...
Click to collapse
Those were good days, too bad nvidia messed it up. I remember you from back then.
Cheers

shirreer said:
Either:
A. Without canceling the ruu process, go to the root of your C: drive and search for Rom.zip file; copy it to your desktop, and rename it to 0P6BIMG.zip (first character is zero, and careful not to rename it to 0P6BIMG.zip.zip). Copy this file to the root of your phone's SD Card. Then, boot your phone into bootloader. Proceed with the on-screen instructions.
Or:
B. Cancel the ruu process, unplug your phone, download & install HTC Sync Manager from HTC's M8 support page. Reboot your PC, plug in your phone and wait until Windows installs the drivers. Start the RUU again and proceed to flashing.
Cheers
P.S. I trust you'll give us feedback about this.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Those were good days, too bad nvidia messed it up. I remember you from back then.
Cheers
Click to expand...
Click to collapse
Those were good days, too bad nvidia messed it up. I remember you from back then.
Click to expand...
Click to collapse
I don't understand the sentence here with nvidia ??

amif7 said:
I don't understand the sentence here with nvidia ??
Click to expand...
Click to collapse
The comment wasn't related to your issue (just a side comment). It was in response to Mr Hofs post about his presence on the One X (different phone) forum. The One X (ENDEAVORU) had its chipset supplied by NVIDIA, which created some video issues for that phone.
EDIT: Better description of the NVIDIA issue in shirreer's response below.

amif7 said:
I don't understand the sentence here with nvidia ??
Click to expand...
Click to collapse
That was meant for Mr. Hofs. The One X was HTC's 2012 flagship*(preceeding the One M7). It ran Android ICS & Sense on NVIDIA quadcore Tegra SoC. Unfortunately, HTC couldn't keep it up-to-date (and, eventually, ended its lifecycle prematurely) mainly because NVIDIA failed to provide it with system software and drivers. Next year, HTC went with Qualcomm and never looked back.
And, then...
Aren't you supposed to be focusing on the other thing?!?

Help me get back to stock on my AT&T HTC One M9.

I've played with this phone for some time, but am tired of messing around with it and just want to get back to stock with root and unlocked bootloader as fast as possible. AKA have someone walk me through it on a screenshare/call. I'm willing to pay for the help. Not sure what someone would want to tell me what to do and help me do it. Please send me a PM and I'll update this thread when I've found someone.
Current state of things:
Bootloader unlocked
S-On
CM13 from Feb2016 installed
TWRP recovery 2.8.7.0 or thereabouts installed.
I have windows7, 10, and Linux Mint boxes depending on which you prefer. I am fairly technical, but haven't messed with things since I mucked up my phone. I never thought it would be such a pain in the a$$ to get back to stock as this is the first time I modded my phone. Just don't have time to try 1000 things or read 1000 threads. :crying:
thanks

What's your current firmware version? (boot to download mode and copy the OS version number).
I'm fairly certain that AT&T has a Windows executable RUU that will restore your phone to stock. (You'll probably need to install HTC Sync Manager to get the right drivers installed)
---------- Post added at 01:48 PM ---------- Previous post was at 01:41 PM ----------
When you get your firmware version, the key is to only use a RUU that matches your version number or is a higher version. Downgrading is not possible for S-ON devices.

The current version is OS-2.11.502.18
computerslayer said:
What's your current firmware version? (boot to download mode and copy the OS version number).
I'm fairly certain that AT&T has a Windows executable RUU that will restore your phone to stock. (You'll probably need to install HTC Sync Manager to get the right drivers installed)
---------- Post added at 01:48 PM ---------- Previous post was at 01:41 PM ----------
When you get your firmware version, the key is to only use a RUU that matches your version number or is a higher version. Downgrading is not possible for S-ON devices.
Click to expand...
Click to collapse

The latest RUU worked. Where it failed everytime before. I don't know what I did this time, but I'm back to stock. Thanks man!
No more help required.
joeinatx said:
The current version is OS-2.11.502.18
Click to expand...
Click to collapse

Congratulations! Always nice have a working device.
(Please be sure to edit the title of the thread to say 'solved'.)