Develop Bugs

PJ46IMG

Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA

kahei036 said:
Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Go back and unlock it again then flash CWM and superuser.
Flash a stock rom or a backup if you did any?
After flashing the stock 1.26xx you will automatically have the update pop up, download and install.
This is what I did anyways. The bootloader can be unlocked and update official anyways.
And also I think you were suppose to type 'fastboot oem lock' not relock.
Hope this helps!
Cheers!

I'm trying this too....
Last night I tried to flash my stock ROM (O2 UK branded) - but downloaded the wrong RUU. So I couldn't flash a completely stock ROM.
I ended up putting Mike's stock ROM on, and tried to flash update.zip via CWM - but got errors.
I am presuming this is because it's not a completely stock ROM, flashed via RUU??
I have now got the correct RUU for my handset, so I am going to try both using PJ46IMG method - and update.zip via CWM
One thing - I am currently running Insert Coin 3.2.0 (which is 1.28 base), do I have to step down to a 1.26 ROM before flashing back the stock recovery, and re-locking bootloader, then running 1.26 RUU?
Or can I just go straight to flashing back stock recovery & re-locking bootloader, then flashing stock RUU?

kahei036 said:
Hi all,
I've just got my one x yesterday and about to flash android hd from mike. However i encounter some problem when proceeding on firmware upgrade.
My phone is still on 1.26 and i am trying to flash the pj46img.zip. bootloader has already been unlocked
1. I placed the pj46img on the root of SD, however when i boot into bootloader it is not going to search for the update, which looks abnormal (i previously owned a desire z and to my understanding it will search for the img.zip files before it let me netvigates the menu to fastboot/recovery. That's not my case on one x)
2. i checked my cid is showing "none" which i understand this is normal since i have unlocked via htcdev.com. I tried to relock my bootloader in order to get official ota flashed. However when i type "fastboot oem relock" it will show (bootloader) lock successfully following with "fail (read content is too long)"
And on hboot screen it is showing "relocked **security warning**" and i was not able to get to cwm thus can't flash in recovery as well.
It would be highly appreciated if someone can provide some checking or solution. Let me know if you need my clarification (sorry for poor english). At the moment i am sticking with leedroid
Thanks all in advance
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
How did you get on with the flashing img.zip? I seem to be stuck with it not flashing either

[Q] Reflashing to stock / RUU

Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help

Gomezie said:
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Click to expand...
Click to collapse
Please specify which RUU's you have tried

Hey thanks for your prompt reply, It is greatly appreciated.
Here are the RUU's i have tried:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.26.161.2_Radio_1.1204.90.13_release_251227_signed
Thanks

Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM

EddyOS said:
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
Click to expand...
Click to collapse
It was purchased from phones4u online.. the phone came unbranded, and is on a vodafone contract.
I am sorry about the RUU.. I wasnt aware it was something you had to acquire first..

You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!

EddyOS said:
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
Click to expand...
Click to collapse
Thanks mate.. just waiting on the download slots and Ill grab it

Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it

EddyOS said:
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
Click to expand...
Click to collapse
Spot on mate, I relocked the bootloader and the status reads "*** RELOCKED ***"
The RUU also ran perfectly, thanks for that
Would I just flash a stock recovery to restore the bootloader now? (so that it doesnt say RELOCKED)
I want to ensure that the phone is in the exact shape it needs to be before sending back.
Thanks again

It'll always say relocked - you can't do anything about that...

Ah thats a shame, should be a doorstep swap for a replacement handset anyways so thats probably no issue.
Thanks again mate, you have saved my bacon

-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA

wolfraim said:
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OP has already got it done, just asked if you could change the bootloader to say 'LOCKED' as it does out the box as opposed to 'RELOCKED'

RUU
So I have kind of a problem, I wanted to unlock my bootloader, only HTCDEV servers are a couples of days now overloaded.
So I can't get the unlock code bin.
I need to use my phone and it won't start normally because new firmare was flashed in RUU mode with JBWFTOOL.
So I want to flash a stock RUU. Only my main version is 3.14.401.41.
My phone was repaired by HTC and I got it back LOCKED and well.
Can I flash a other version RUU or do I have to wait for HTCDEV becoming normal again.
HOX E11 Europe.
H.BOOT 1.39
3.14.401.41
I am not doomed right?

Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator

Mr Hofs said:
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Click to expand...
Click to collapse
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD

jelmer-p said:
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
Click to expand...
Click to collapse
Yeah i knew that, im on the same cid

Mr Hofs said:
Yeah i knew that, im on the same cid
Click to expand...
Click to collapse
YEAH it worked thanks!

jelmer-p said:
YEAH it worked thanks!
Click to expand...
Click to collapse
Top ! Have fun :thumbup:

Help upgrading firmware

I have a tmobile htc one m8 with twrp recovery s-off and htc dev unlocked im currently running the latest viperone with 4.4.3 as the base but i havent updated my firmware to 4.4.3 so i am experiencing long boot times and such so how would i go about upgrading the firmware

It's pretty straight forward, download this and put it in your adb dir, http://www.androidfilehost.com/?fid=23578570567718638
make sure the phone has usb debuggin enabled in the developer options.
then run these commands (if you aren't fimiliar with adb then google it)
adb reboot bootloader
fastboot oem writecid 11111111
adb reboot-bootloader (verify your cid is 11111111, that way you wont have to edit a txt file in the firmware zip since they usually dont have the tmo cid in them)
fastboot oem rebootRUU
fastboot flash zip name.of.file.you.downloaded.zip (If it says FAIL at the end then run this again)
fastboot reboot
Then if you wanna check,
adb reboot bootloader
fastboot getvar all

tmobile hasnt released 4.43 yet

You don't need the TMO release. All GSM m8's are the same exact device. You can run international firmware without any issue. My setup is a UK rom with a ATT radio, with the sprint harmon kardon libs. No sense on waiting for the tmo release if you have soff, just flash the firmware update and go over to the main m8 forum and download any rom you want.

thanks; myself personally, I am going to wait for my 14 day "return" period to end, just to make sure of everything, and, by then, I assume the TMO update will be released, and I will flash it then, and then start having "fun" with this awesum phone:good: got it 3 days ago, so I'm still getting used to it after a LG Flex..

@op would you able to upgrade your firmware ?

x714x said:
You don't need the TMO release. All GSM m8's are the same exact device. You can run international firmware without any issue. My setup is a UK rom with a ATT radio, with the sprint harmon kardon libs. No sense on waiting for the tmo release if you have soff, just flash the firmware update and go over to the main m8 forum and download any rom you want.
Click to expand...
Click to collapse
I have to agree. I'm using the dev firmware. Until T-Mobile firmware becomes available.
S-off is the way to go.

how do i upgrade firmware with s-on? firewater doesn't work.
im back on stock rom with stock recovery. phone downloads update then asks if i want to update, goes into recovery, starts to update & then stops 30 seconds in and goes to a screen that shows a phone with a red triangle & exclamation mark in the middle
do i need to lock my bootloader?
EDIT: im on 4.4.2. trying to update to stock 4.4.3

pinkgabe said:
how do i upgrade firmware with s-on? firewater doesn't work.
im back on stock rom with stock recovery. phone downloads update then asks if i want to update, goes into recovery, starts to update & then stops 30 seconds in and goes to a screen that shows a phone with a red triangle & exclamation mark in the middle
do i need to lock my bootloader?
EDIT: im on 4.4.2. trying to update to stock 4.4.3
Click to expand...
Click to collapse
There is quite a discussion about this in this thread http://forum.xda-developers.com/showthread.php?t=2776785. You can start around page 8 to get to the point 4.4.3 was released.

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.

Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.

S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.

Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.

S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...

Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.

If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.

Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!

No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

[Q] HTC One bricked, need help

Hello everyone, I know there is a bunch of topics about similar issues but I still can't get out of that trap.
Here we go, I initially wanted to flash my recovery back to stock to be able to install the HTC's OTA (I was using TWRP), I guess it went terribly wrong, because when I launched the update it crashed and now I only can access my bootloader (fastboot available). Everytime I try to access the OS or the recovery it just get stuck with the HTC logo. I tried to flash the boot.img (stock), went back and forth with TWRP and stock recovery (the flashing works, but I still can't boot any of those things, stuck). I am unlocked (still have the HTC .bin in case I have to relock). I am S-ON so I am not supposed to be able to brick it completely. Moreover I can't seem to find a RUU that fits my radio (1.16.2133156). Screenshot of my "allvars" in attachment.
Thanks a lot, I don't really know what to do as I tried everything I found(except RUU, yet).
-- Edit for clarity --
My phone is not bound to any carrier and West Europe
Peace.

Relock your bootloader (fastboot oem lock) and run the 4.16.401.10 RUU and you should be sorted

EddyOS said:
Relock your bootloader and run the 4.16.401.10 RUU and you should be sorted
Click to expand...
Click to collapse
Thanks, you're the man.

Sorry for double posting, I finally downloaded the RU (the same number as previously said) and I get an error (12 signature verify fail). My device is well relocked. As I understand I must be S-OFF for the RUU to work (European phone), which is problematic as I cannot load anything. I am trying to download the RUU again, in case I got a corrupted file...

You do't need to be S-OFF, only if you want to do some other things. You just need to be relocked and it should work fine

Here is what I get, I am re-downloading the RUU from xda's source. With the crap internet I have it takes a while... Thank you for your time.
I renamed a little the file for you to see the version I used (just in case)

When using RUU zip, you need htc_fastboot.exe instead the usual fastboot.exe
Get it here : http://forum.xda-developers.com/showpost.php?p=52280888&postcount=1
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
But when using RUU exe, just relocked and run RUU

Here is what I get, I am re-downloading the RUU from xda's source. With the crap internet I have it takes a while... Thank you for your time.
Click to expand...
Click to collapse
Not the other guy, but I think you're using the file incorrectly. Did you enter the command "fastboot oem rebootRUU" first?
Anyways you can try this method instead:
1-Rename the zip to 06PBIMG.zip
2-Place it on your sd card
3-Go into the bootlaoder and select hboot
It should detect the ruu automatically.

It's working and I am a dummy.
Thanks a lot!