Develop Bugs

My DHD stuck on htc logo

hi I tried to install IceColdSandwich-1.2.0 Rom on my DHD but after i did it my device stuck on htc logo and never boot the problem is i am new in this stuff and i can't get my device back to life i 'v downloaded the ice cream sandwich using
clock work mode and my Hboot screen shows:
****UNLOCKED*****
ACE PVT S-on RL
Hboot -2.00.0029
MICROP-0438
Radio-26.14.04.28_M
eMMc-boot
Dec 22 2011,14:28:19
and i don't know what Ruu to install
please help and thx

Your phone isn't rooted. How did you manage to flash recovery onto it in first place?
Search for advanced ace hack kit on xda. Read a LOT about how to use it and once ready, let the kit do its thing. After that you'll be S OFF and able to flash any custom ROM.
Sent from my HTC Desire HD with Beats Audio using XDA App

He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot

Its not working
marsdta said:
He unlocked it using the official HTC dev tool. It allows you to flash a custom recovery.
This is an obligatory to the op. Please research before you go and do stuff to your phone. I just don't get how someone will take a risk on there phones.
The reason it didn't boot is because you have to flash the boot image seperately. One simply can't just flash a rom, in cwr and call it a day if you did it using HTC tool.
What you need to do is. Boot back.into hboot select fastboot.
Take the boot image from your rom and place in your folder where fastboot and adb are located.
Then run the command
Fastboot flash boot boot.Img
Fastboot reboot
Click to expand...
Click to collapse
yeah you are right I used htc dev to unlock my DHD but I tried to took boot.img from the Ice cream sandwich Rom and it did not workout with me please if you know any way help me
and thx for your reply

AAHK
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast

ordevski said:
This is the AAHK (Advanced Ace Hack Kit) thread.
It is ONE click Root, S-Off & SIM unlock kit.
Read carefully, go step-by-step and than you'll be ready to go.
This is how I unlocked and unleashed my beast
Click to expand...
Click to collapse
thanks but i only can access to Hboot menu and i can enter the clock work mode but the AAHK doesn't workout with me

Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41

DN41 said:
Run a fitting RUU, relock your Bootloader and use AAHK afterwards.
(if you would have taken some time to get into this stuff, you wouldn't be messed up right now "Official HTC Unlock" is not that brilliant compared to AAHK ).
You say you don't know which RUU to use.
Where did you buy your phone? Was/Is it branded?
DN41
Click to expand...
Click to collapse
no my phone isn't branded and the version of my android was 2.3.5 , HTc sense 3.0 software number 3.13.415.2
and AAHK need downgrade to workout with me so I gave it a chance but every thing went wrong
thx for your help anyway

Try one of those, i think the latest should be fine.
[ROM]Ace Test & Stock ROMS [RE-UPLOADED]
DN41

ok i will thank you but do you know error "155" and how to solve it and if Ruu works with s-on or not and thx again

When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41

DN41 said:
When do you get this 155-error?
If using a fitting RUU, it will always work afaik But I'm pretty sure.
DN41
Click to expand...
Click to collapse
I didn't really know what you meant by afaik
I tried alot of RUU but they all keeps popup with error 155 and i don't know how to fix it and i don't know how to fix this problem but i really need to work it out and thx for all of you

"As far as I know"
Did you try flashing it in fastboot mode?
Get your device into bootloader and choose fastboot. Try to run the RUU again.
DN41
Sent from my DHD @ ARHD 6.3.1

i did but its always error 155 comes up i don't know what to do but i really need my DHD back

Ok, another idea:
You have that stock RUU fitting your phone?
Open explorer here: C:\Users\"YOUR USERNAME"\Appdata\Local\Temp\
Then Run the RUU, it will extract the files to some folder in here, you will see it pop up when opening the RUU (or you run it and simply use search).
Inside there'll be a "rom.zip".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rename it to PD98IMG.zip, push it to your SD card (in root, not into a folder) and boot your phone into bootloader.
It should check the file and then you have to select "yes" to flash it. Should be fine after it.
DN41

thx I tried to do this before but it keeps tell wrong Image

So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1

Just root it using the ace hack kit..might ne worthwhile?
Sent from my Desire HD using XDA Premium App

DN41 said:
So you're a hundred percent sure, that you've got a fitting image? Cant believe that it would block a fitting image that method.
Which version did you try? Most recent one?
And BTW: would be great it you would tell before what you already tried instead of letting me explain it and then say "oh i already did that"
DN41
EDIT: I guess it doesnt take the Rom because of the high hboot version (yours is somewhere around 2, "normal" ones around 0.84). Maybe it would be the best to contact HTC's Support regarding that you used their official unlock instead of AAHK.
Sent from my DHD @ ARHD 6.3.1
Click to expand...
Click to collapse
I am sorry i didn't tell but I really need my phone back so I am trying every idea comes to my mind and I tried a lot of versions but no one works
thx again for your help

[RUU] 2.14.401.1_Radio_47.23e.35.3038M_7.57.39.01M

Finally got it. One hour fu**ing with a Chinese captcha. Om nom nom...
RUU_Marvel_S_HTC_Europe_2.14.401.1_Radio_47.23e.35.3038M_7.57.39.01M_release_246629_signed.exe
Links:
http://dl.dbank.com/en_US/c05hrf513i
http://dl.dbank.com/c05hrf513i
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

well done.
since hboot 1.09.0099 is included I have the strong feeling this is the last update for the wildfire s

Will post on a faster download site once it eventually gets here. No issues with losing S-OFF?

I'm assuming too that we'll lose bootloader unlock and have to go through the whole update/unlock process again. Am I wrong?

can u plz check if it contains arabic language ?

d33ps1x said:
Will post on a faster download site once it eventually gets here. No issues with losing S-OFF?
Click to expand...
Click to collapse
Nope, I've updated and still s-off.
Although in the bootloader it says locked, it still says ship S-off.
Radio seems to give me better signal.
I can't get this rom rooted though. Apps requiring superuser are denied.

Chinese caparcha
That's crazy.
Sent from a Time Lord, using his TARDIS.

intel007 said:
Nope, I've updated and still s-off.
Although in the bootloader it says locked, it still says ship S-off.
Radio seems to give me better signal.
I can't get this rom rooted though. Apps requiring superuser are denied.
Click to expand...
Click to collapse
you will need to unlock the bootloader again after update

eoghan2t7 said:
you will need to unlock the bootloader again after update
Click to expand...
Click to collapse
But I'm s-off, I've never had any problems with rooting previous stock roms.

I think the updated radio has more security added to it.
Sent from my Wildfire S using xda premium

To root that rom just enter the CWM recovery and install this zip file:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
honda_hany said:
can u plz check if it contains arabic language ?
Click to expand...
Click to collapse
It doesn't contain the arabic language.

Done that but apps were being denied superuser permission.
I'll try the zip that d33psx1 provided and see what happens.
Thanks.

intel007 said:
Done that but apps were being denied superuser permission.
Click to expand...
Click to collapse
Did you use the zip from my post? Some old versions of su don't work but 3.0.7 should.

N00b question - Im not gonna lose S-Off installing this am I?

rezo said:
Did you use the zip from my post? Some old versions of su don't work but 3.0.7 should.
Click to expand...
Click to collapse
Ok I will try, I did download superuser latest version from their website.
Thanks
Ko_Ka said:
N00b question - Im not gonna lose S-Off installing this am I?
Click to expand...
Click to collapse
No you won't lose your s-off mate.

Another noobish question
So I've got:
CWM 5.0.2.8 S-On
HBOOT-1.08.0099
RADIO-7.53.39.03M
How do I update? Do I just install the RUU, and then follow the HTCDev bootloader unlock and then root the phone again or do I need to take any other steps?

ERROR 140 while updating
Hello guys,
i want to update my wfs to get the latest hboot and radio.
i have an unlocked bootloader and hboot 1.08.099 and i'm running the latest cm7.2 version by alquez.
my procedure was to relock my bootloader via fastboot oem lock (to avoid the 155 error) and then i run the ruu.exe (my mobile was in fastboot usb mode all the time and yes i cleared cache etc)
at first everything seems to be fine but when the exe update the signature (or sth like that) the setup aborted with the message "RUU Fehler 140 Bootloader Version" (i'm german.. so fehler <> error)
Does anyone knows how to solve this problem?
Thanks
NQNH

I updated to last ruu and loader says now locked but i have installed super user(rezo provided) and everything is working so i will leave as it is now(even if it says bootlader locked)

NQNH said:
Hello guys,
i want to update my wfs to get the latest hboot and radio.
i have an unlocked bootloader and hboot 1.08.099 and i'm running the latest cm7.2 version by alquez.
my procedure was to relock my bootloader via fastboot oem lock (to avoid the 155 error) and then i run the ruu.exe (my mobile was in fastboot usb mode all the time and yes i cleared cache etc)
at first everything seems to be fine but when the exe update the signature (or sth like that) the setup aborted with the message "RUU Fehler 140 Bootloader Version" (i'm german.. so fehler <> error)
Does anyone knows how to solve this problem?
Thanks
NQNH
Click to expand...
Click to collapse
Hi NQNH
I had the exact same error. This is what you need:
http://forum.xda-developers.com/showthread.php?p=21408713#post21408713
It seems that the "PG7610000_Marvel_hboot_1.08.0099_20111216.exe" you probably had to install to unlock your phone made a change to a version number in your misc.img.
Mine was something like 2.17.0.0 instead of 1.08.0099.
After the RUU failed you will be able to see something like "Main version is older" on the phone's screen (if you get rid of the HTC logo)

can someone extract the radio from that ruu?

Rooting an S-Off HOX

Hey XDA :
I kneel before you a broken and confused man. Here's my issue, I bought a One X not long ago, noticed it was S-Off but still went ahead n unlocked Bootloader, dunno if I should have given fact I got S-Off ... Started flashing tons of ROMs .... But from what I understand, with S-Off I do not need to flash boot.img every time I want to flash a ROM, yet, none work unless I do ... Thus confusion reigns ...
Am seriously considering going stock with latest 2.17 RUU, thus loosing my ROOT and EVERYTHING !!! Ok all SD is backed up to my HDD ... But still I have no idea ... This is annoying ... Living in total darkness .. Am a n00b coming from iOS the main Android competitor ...
Here's proof of my S-Off :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me !!!!

Read, read some more, take a break then read some more....
Eventually you'll figure it out.
I'd help you but jumping into threads pretending you're a hero for having s off, which you didn't even earn - was just lucky, Pissed me off so I won't.
---------- Post added at 05:35 PM ---------- Previous post was at 05:31 PM ----------
PsyChoses said:
This ROM is so good it has become my daily driver! Sadly I only use my HOX to test various ROMs n learn more about Android! Nothing else, like no Sim Card nothing!
I am an iOS/MacOS fan n forever will be....
Click to expand...
Click to collapse
*rolls eyes*

1. You didn't need to unlock the bootloader if you have S-OFF, you can just flash anything you want
2. If the ROMs ZIP is written correctly you don't have to flash the boot.img as it'll be flashed with the ROM. If not you'll have to do it manually
3. You can flash any RUU you want as you are S-OFF so you don't even need to root it unless you want to

Read, read some more, take a break then read some more....
Eventually you'll figure it out.
I'd help you but jumping into threads pretending you're a hero for having s off, which you didn't even earn - was just lucky, Pissed me off so I won't.
Click to expand...
Click to collapse
Oh c'mon, really ? You took that seriously ? Yes I am an iOS fan that don't mean I can't become an Android one too !!! And am not acting like no hero ... Was just showing that S-Off devices existed ... Am really sorry it came off the wrong way ...
1. You didn't need to unlock the bootloader if you have S-OFF, you can just flash anything you want
2. If the ROMs ZIP is written correctly you don't have to flash the boot.img as it'll be flashed with the ROM. If not you'll have to do it manually
3. You can flash any RUU you want as you are S-OFF so you don't even need to root it unless you want to
Click to expand...
Click to collapse
1. So what does unlocking Bootloader on S-Off cause ? Will it cause device to act weird ?
2. Hmm... Ok ?
3. I just thought I'd flash latest RUU to get HBoot updated n stuff, then Root again to get back to flashing ROMs
Thanks

PsyChoses said:
1. So what does unlocking Bootloader on S-Off cause ? Will it cause device to act weird ?
2. Hmm... Ok ?
3. I just thought I'd flash latest RUU to get HBoot updated n stuff, then Root again to get back to flashing ROMs
Thanks
Click to expand...
Click to collapse
1. It means HTC now know you've unlocked the bootloader. Before, as you had S-OFF, there was no reason for them to know. They could now refuse your warranty
2. ???
3. Yep you can do that, I did

1. It means HTC now know you've unlocked the bootloader. Before, as you had S-OFF, there was no reason for them to know. They could now refuse your warranty
2. ???
3. Yep you can do that, I did
Click to expand...
Click to collapse
1. So to Root I did not need to unlock bootloader ? And it's ok where I live there is no such thing as Warranty ... Just a 3 month shop warranty ...
2. That means that the ROMs were not built right that is why am having o flash boot.img ?
3. After flashing latest RUU my bootloader will re-lock ? no need to unlock it again to root ?
Again thanks

PsyChoses said:
1. So to Root I did not need to unlock bootloader ? And it's ok where I live there is no such thing as Warranty ... Just a 3 month shop warranty ...
2. That means that the ROMs were not built right that is why am having o flash boot.img ?
3. After flashing latest RUU my bootloader will re-lock ? no need to unlock it again to root ?
Again thanks
Click to expand...
Click to collapse
1. Fair enough!
2. It would appear so as the T3 One X flashes differently
3. You have to relock the bootloader to flash an RUU but once flashed you just reflash CWM without unlocking the bootloader

1. Fair enough!
2. It would appear so as the T3 One X flashes differently
3. You have to relock the bootloader to flash an RUU but once flashed you just reflash CWM without unlocking the bootloader
Click to expand...
Click to collapse
1. Cool
2. Seems so
3. Relock ? How ? Where to get the stock recovery ?
You are awesome for taking the time to help thanks

To relock the bootloader:
fastboot oem lock
Then run the RUU when the phone is connected in fastboot mode and away you go! You shouldn't need the stock recovery as the RUU replaces that but I've always flashed it before using the RUU purely through habit

To relock the bootloader:
fastboot oem lock
Then run the RUU when the phone is connected in fastboot mode and away you go! You shouldn't need the stock recovery as the RUU replaces that but I've always flashed it before using the RUU purely through habit
Click to expand...
Click to collapse
Ok now one last question how do I find out what RUU to use for my device ? Like if it is ASIA, Middle East, India etc .. ?
Thanks

You can use ANY RUU you want as you're S-OFF

You can use ANY RUU you want as you're S-OFF
Click to expand...
Click to collapse
ok flashed RUU, now I try to flash CWR and all I get is stock recovery can't go to CWR no more xD
EDIT :
I HAD to unlock Bootloader else no CWR ...
No Unlocked Bootloader = No Root / CWR
Unlocked Bootloader = Root/ CWR
At least that is what happened in my case even with S-Off xD

EddyOS said:
You can use ANY RUU you want as you're S-OFF
Click to expand...
Click to collapse
Unless the CID is set, but you can also set it to all 1s as you have S-Off!

I have the solution...............................Maybe you should swap your HOX with mine. :laugh:

PsyChoses said:
ok flashed RUU, now I try to flash CWR and all I get is stock recovery can't go to CWR no more xD
EDIT :
I HAD to unlock Bootloader else no CWR ...
No Unlocked Bootloader = No Root / CWR
Unlocked Bootloader = Root/ CWR
At least that is what happened in my case even with S-Off xD
Click to expand...
Click to collapse
Now that's weird, in the past with S-OFF you just flashed CWM using fastboot without unlocking the bootloader

Unless the CID is set, but you can also set it to all 1s as you have S-Off!
Click to expand...
Click to collapse
Yeah all is good now but had to unlock bootloader in order to flash CWR even with S-Off n CID set to 111111
Now that's weird, in the past with S-OFF you just flashed CWM using fastboot without unlocking the bootloader
Click to expand...
Click to collapse
I guess not anymore .. Not on HOX anyway xD
I have the solution...............................Maybe you should swap your HOX with mine.
Click to expand...
Click to collapse
You want it ? How about $600

Can't install ROM or update

I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.

kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks

The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.

Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.

kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work

Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.

kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?

Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks

grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU

Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.

Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11

kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:

Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.

I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?

kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier

Need Help! Can't unlock bootloader after relocking it!

Here's the situation I'm in right now.
My phone is the HTC Desire Eye AT&T Model. I am not rooted, S-Off, Relocked, and on Stock Recovery and Lollipop Rom.
When in Fastboot mode the top of the screen reads:
*** Software status: Modified ***
*** RELOCKED ***
EYE_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.000
[email protected]
OpenDSP-v47.2.2-000564-M8974.1024
OS-2.09.502.3
eMMC-boot 2048MB
Aug 18 2015,20:36:07.0
Some information on how I got in this predicament:
My home internet provider is absolutely cancerous, such that tethering my 4G LTE connection is much faster.
I had an unlocked, S-Off, TWRP installed phone.
I am using T-Mobile right now, and I needed a way to tether my phone, which the phone does not allow through T-Mobile.
I did a Nandroid backup of my phone using TWRP
So, I unlocked the bootloader and installed the Taiwanese Lollipop ROM, then rooted from TWRP. I was now able to tether, and that was good enough for me.
Later, I found that Marshmallow was released. I wanted to receive the Taiwanese OTA update (AT&T could not give me the update, similarly to tethering, on T-Mobile).
I changed the CID to SuperCID. Somehow, I believe using some hex editor method, I changed the MID. However, the update could not be flashed because the Product ID was "eye_ul", which I still could not find out how to change. Even modifying build.prop didn't do anything.
I decided I must have went wrong somewhere, so I decided to start back at square one. This is where things went wrong. After I flashed the original backup I made of my phone, it was no longer rooted. I then proceeded to lock the bootloader, so I not only lost my custom recovery, but the way to flash it back as well. I went back to HTCdev and performed the unlock process, but there was this error described here.
I am aware that EYE_UL_CA is the AT&T product name, CID 11111111 is SuperCID, these two are fine.
However, the Model ID 0PFH20000 is Taiwanese. The original AT&T MID is 0PFH10000, but I don't know how to change it back
When running the command fastboot getvar all here is the information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The unlock token I received was:
<<<< Identifier Token Start >>>>
41235A6270C9338D6B0CDC8783A0B2C8
D647EB5E2F2A2FE7828A885DB6214D97
41E99F77EA8619250FD1367851924861
A46DCD4301228035FD62578DFDC6A843
F79115EC1EBDCFB8AA95BA73F62C0E2A
30F58D5AA67DDA97F91F625099943710
D708BC3BB462F7AD71A70BDC06234766
4E7DE5F4116B1BB2B6FA46C52A72645B
A6416C72CA39E41CAF8031231E3A44CF
D304616C3BD5955DA409654FAF91880B
187F7079B8CBC57EE45714B94B4823AD
265BDFC7D61B32F8357C658DAC24977D
FCD99AB305B23943E2E6678D4B8C3331
5A7A4D997CABD525F6D2BAB1DF241936
C78DF80041A4690031D448A2C462FE9C
7433BF2B54ACC53C10AA8B6F2E71EE48
<<<<< Identifier Token End >>>>>
Then unlock_code.bin file is attached as a txt. When I try to flash it with fastboot flash unlocktoken unlock_code.bin, I get the following error message. FAILED (remote: unlock token check failed).
I read that running the original RUU makes unlocking work again. However, I cannot use it because the device Model ID is still Taiwanese, and I am unsure of how to change it back to the AT&T version.
It's possible that all these problems are because I cannot remember how to change my MID back. fastboot oem writemid is not a command that works on my phone ((bootloader) [ERR] Command error !!!). I remember working with a hex editor to edit some file, but I forgot what it was.
I know it's possible to change the MID back to AT&T because it's impossible to have started out as a Taiwanese MID.
Right now, I can't use my phone to tether, so I am using my incredibly slow home internet to post this. Please Help Me!
Update: I now have root access, and I have reverted the MID back to 0PFH10000. I installed the RUU, but the bootloader still has the same error when I try to unlock it. Please let me know if you are an expert in this error and know how I can unlock my relocked bootloader. Thanks!

Have you tried Windroid software to unlock the bootloader?

netikjoshi98 said:
Have you tried Windroid software to unlock the bootloader?
Click to expand...
Click to collapse
Hey, if you're online, netikjoshi98, I wanted to tell you that Windroid did the job. Thanks!
My bootloader is now unlocked, and I'm ready to install recovery and return everything to normal!
I'll provide details of the recovery steps tomorrow, so that other people with this problem will know how to fix it.

Cheers :good:

Fixing the relocked bootloader (that refuses to unlock)
If you are found in such a tangled kite string as having a relocked bootloader, a modified MID, no custom recovery, no root, and are S-Off so s-off/unlock tools don't work, then these are the steps that I took to fix it.
The general goal here is to run the RUU so u can get the device 100% back to stock, then the HTC unlock will work, or Windroid, or whatever it is that you like to unlock your phone with.
1. obtain root
U need to root without custom recovery, so get some program that can do it from ADB. I did it using KingoRoot, which worked great and I was very happy with the result.
2. Change the MID
follow this person's guide to change the MID: http://forum.xda-developers.com/desire-eye/general/update-to-android-5-0-2-t3081580
you need root to do this that's why the first step was root
you will need the hex editor, and if you are using taiwanese RUU u need to change to taiwan's MID and if you are AT&T or International you need to change to that.
3. Run the RUU
since the MID is now matching your device and CID, you can now run the RUU without a problem, unless you have some other modifications that makes the RUU detect your device as not matching itself.
If you have RUU disappearing problem after clicking accept you are missing some Windows dependency and need to look up which one it is. This step is very easy so I won't provide the links to external sites.
4. Unlock Device
I used Windroid Toolkit as recommended by the helpful person on this post but I believe you can probably also use HTC Unlock now, since the protocol is likely the same.
5. Flash the custom recovery or whatever it is you intended to do with the unlocked bootloader in the first place

I'm glad you found a solution to your problem. And thanks a lot for posting the guide on how you got it fixed. You rock, dude.