Develop Bugs

[Q] Reverting for repair

Hey,
I know there's already a thread on this but I wanted to ask which order I need to carry out the process and any help would be greatly appreciated. I need to return my DHD as there are problems with the speaker. I have a new radio, eng-off, s-off and a custom ROM. Which ones do I revert first in order to return to stock without messing up the phone?
Thanks !

You may be able to get away with sending the phone back even if it's not on a stock ROM. I have read other posts on here where people have sent their phones in for repair with custom ROM's and HTC have not been bothered about it, and whenever you send your phone in for any type of repair - they will always wipe the phone and re-install the phone with the latest stock ROM.
From what you have described about the problems you have got with your phone, I imagine the first thing HTC will do before doing any physical repairs on the phone is to re-flash the phone with the latest stock ROM to see if it fixes any of the problems on the phone.
My DHD has been back to HTC twice for the same camera blur problem and I had previously rooted the phone, Radio S-OFF and installed a custom ROM but then I did revert it back to stock with Radio back to S-ON right before I sent it back to HTC for the repair. The first time it went back HTC, all they did was re-flash the phone with the latest stock ROM and sent the phone back to me and hoped that it cured the problem. Within 10 minutes of getting the phone back I knew that the problem was still present and then within a couple of days it was back with HTC again for the same problem and that is when they finally physically repaired the phone.
Edit - from what I have just found out, it doesn't matter which ROM you have installed but the most important thing is to make sure that you revert the phone's Radio back to S-ON before sending it back.
Liam

Thanks, so I just have to get radio S-on back? What about eng-on ? I used the two tools to do it originally, so I'll just have to use them again ?

otibarns said:
Thanks, so I just have to get radio S-on back? What about eng-on ? I used the two tools to do it originally, so I'll just have to use them again ?
Click to expand...
Click to collapse
Yes that's right, just use the tool to revert them back to ON. When I did the process and after I used the tool to revert them back to ON, I just downloaded a stock RUU ROM that you run through Windows and then the program re-flashes your phone back to the stock ROM.
Liam

i would back to stock, just in case... i really don't think htc bothers with it, because it's way more simple to fix the phone than fight against the client.
but, since with the original RUU is very easy to back it to stock, i don't see why you shound't do...
regards!

Ok thanks. I have got radio back to S-ON but I still have eng-off. Will this matter? I can't seem to find out how to revert it back to on.

otibarns said:
Ok thanks. I have got radio back to S-ON but I still have eng-off. Will this matter? I can't seem to find out how to revert it back to on.
Click to expand...
Click to collapse
Did you read the instructions in my tool's thread? It says pretty clearly there that you should run stock RUU

I've been thinking this for a while, since I have an issue with volume rockers (they aren't as outside the chassis as a friend's) from the very first moment I bought.
Does anybody have this issue? or think it's a hardware problem HTC would repair?
Ty

jkoljo said:
Did you read the instructions in my tool's thread? It says pretty clearly there that you should run stock RUU
Click to expand...
Click to collapse
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks

otibarns said:
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks
Click to expand...
Click to collapse
When you install an official RUU you revert to original factory state. I believe bootloader,root,ENG/SOFT-OFF etc... dissapears

otibarns said:
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks
Click to expand...
Click to collapse
almost everything desappear by flashing original RUU, except Radio S-OFF, that can be changed by jkoljo's tool.
but, since you lose the root when you flash RUU, you will root your phone again with visionary, after that, use the jkoljo's tool to get s-on, unroot and uninstall visionary. done, just it.
Juduth said:
I've been thinking this for a while, since I have an issue with volume rockers (they aren't as outside the chassis as a friend's) from the very first moment I bought.
Does anybody have this issue? or think it's a hardware problem HTC would repair?
Ty
Click to expand...
Click to collapse
well, is what you are talking about? http://forum.xda-developers.com/showthread.php?t=915895

thiagodark said:
well, is what you are talking about? http://forum.xda-developers.com/showthread.php?t=915895
Click to expand...
Click to collapse
Not exactly but close. My volume rockers work, it's just they are sunken to bottom and haven't that normal touch i've seen on other DHDs
Anyway, thanks for linking post. I'll talk a bit there

[Q] Need 2.17 3 UK RUU

I desparately need the 2.17 H3G (Three UK) RUU to restore my HOX from a bootloop. If anyone could help they would be a lifesaver.

You only need the RUU if you want to go back to stock.
If you want to fix your bootloop, you need to fastboot flash the latest recovery, fastboot flash boot boot.img fastboot erase cache, and then in recovery clear caches and wipe partitions, flash the ROM.

BenPope said:
You only need the RUU if you want to go back to stock.
If you want to fix your bootloop, you need to fastboot flash the latest recovery, fastboot flash boot boot.img fastboot erase cache, and then in recovery clear caches and wipe partitions, flash the ROM.
Click to expand...
Click to collapse
I've tried what you suggested, still no joy. I just want to go back to stock.

Ogner said:
I've tried what you suggested, still no joy. I just want to go back to stock.
Click to expand...
Click to collapse
Pretty sure a google won't go a miss... I had a link but I really can't get it because I'm on my phone, it's out there but the site I got it off accidently named it wrong. They called it 1.29 and we all know that three didn't release the 1.29 update... So... It has to be 2.17 because all the other versions are there including 1.28 and 1.26.
Sent from my HTC One X

smidgeox said:
Pretty sure a google won't go a miss... I had a link but I really can't get it because I'm on my phone, it's out there but the site I got it off accidently named it wrong. They called it 1.29 and we all know that three didn't release the 1.29 update... So... It has to be 2.17 because all the other versions are there including 1.28 and 1.26.
Sent from my HTC One X
Click to expand...
Click to collapse
Cheers I downloaded that RUU from filefactory. I was able to relock the bootloader. My problem now is that the phone has less than 30% battery charge. And I can't get it to charge.
I will never buy a network branded phone ever again. And I wont mess about with roms again. Having said that I installed custom roms in the HTC Desire, homebrew on the Palm Pre, various roms via odin on the SGS2.
I still like the HOX. I guess there is no such thing as a perfect phone in either hardware or software.
If I can't sort it I will order a new HOX directly from a very famous online retailer with a very generous return policy and .....

Ogner said:
Cheers I downloaded that RUU from filefactory. I was able to relock the bootloader. My problem now is that the phone has less than 30% battery charge. And I can't get it to charge.
I will never buy a network branded phone ever again. And I wont mess about with roms again. Having said that I installed custom roms in the HTC Desire, homebrew on the Palm Pre, various roms via odin on the SGS2.
I still like the HOX. I guess there is no such thing as a perfect phone in either hardware or software.
If I can't sort it I will order a new HOX directly from a very famous online retailer with a very generous return policy and .....
Click to expand...
Click to collapse
You could flash the latest clock work mod recovery, it enables charging in recovery?
Sent from my HTC One X

smidgeox said:
You could flash the latest clock work mod recovery, it enables charging in recovery?
Sent from my HTC One X
Click to expand...
Click to collapse
The phone is dead. It won't switch on, no matter how long I hard reset it.

Ogner said:
I desparately need the 2.17 H3G (Three UK) RUU to restore my HOX from a bootloop. If anyone could help they would be a lifesaver.
Click to expand...
Click to collapse
I need the RUU file to. Did you manage to find it?

Didn't look hard enough...
http://forum.xda-developers.com/showpost.php?p=33690612&postcount=2297

EddyOS said:
Didn't look hard enough...
http://forum.xda-developers.com/showpost.php?p=33690612&postcount=2297
Click to expand...
Click to collapse
I did cause i've already got it

wigankev said:
I did cause i've already got it
Click to expand...
Click to collapse
Should've updated your last post then

EddyOS said:
Should've updated your last post then
Click to expand...
Click to collapse
I found it from a German site

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!

all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140

I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop

so you have a stock recovery now? and receive ota notifications?

Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:

sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there

alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it

nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS

sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor

sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan

Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu

I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app

xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.

Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app

Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063

I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz

Phone shutting off when I turn screen off

So everytime my screen turns off it turns off my phone itself and I have to restart it. It turns my whole phone off.
I am currently running stock rooted with s-off. It just started happening after I restored phone from a previous backup. Everything went great and worked but when I turn off screen it turns off my phone.

UnknownPopo said:
So everytime my screen turns off it turns off my phone itself and I have to restart it. It turns my whole phone off.
I am currently running stock rooted with s-off. It just started happening after I restored phone from a previous backup. Everything went great and worked but when I turn off screen it turns off my phone.
Click to expand...
Click to collapse
Did you update your firmware at any point? And how old is the backup? Because this sounds like a firmware conflict between 1.32 and later bases. If you're running 1.4 or later firmware, and the backup was on 1.32, that's your problem.

Oh **** me I love you yes, backup was before firmware update, how can I update?

iElvis said:
Did you update your firmware at any point? And how old is the backup? Because this sounds like a firmware conflict between 1.32 and later bases. If you're running 1.4 or later firmware, and the backup was on 1.32, that's your problem.
Click to expand...
Click to collapse
So how do I update my firmware? Software number right now is 1.32.661.31, custom rom I installed was 2.10.401.1,

UnknownPopo said:
So how do I update my firmware? Software number right now is 1.32.661.31, custom rom I installed was 2.10.401.1,
Click to expand...
Click to collapse
Well, that's your problem. You've got a few options:
-Go back to stock and get the OTA
-Relock and run a RUU for your phone
-S-off and update manually
The last option is my preference since you can get the latest no matter where you are, but you do have to pay $25 for Sunshine.

iElvis said:
Well, that's your problem. You've got a few options:
-Go back to stock and get the OTA
-Relock and run a RUU for your phone
-S-off and update manually
The last option is my preference since you can get the latest no matter where you are, but you do have to pay $25 for Sunshine.
Click to expand...
Click to collapse
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.

SmIzUrF said:
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.
Click to expand...
Click to collapse
Go for the sunshine method mate. Once you've finished doing the run route it may happen again in the future, by that point 25 dollars will seem like nothing for the trouble... In the state you're in you could also change the kernel you're using and that will also fix the issue.

SmIzUrF said:
I dont think you do need to relock phone for ruu. I may be wrong but I dont think I did when I used ruu for OTA.
Click to expand...
Click to collapse
You are correct. I am unlocked, and have used the RUU.exe method a few times now.

HTC M9 won't boot after update - can't flash anything, factory reset or unlock bl..?!

Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(

At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.

fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?

zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.

Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course

zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.

zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?

fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.

zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.

Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*

Failed: -2, 19 to flash via downloadzip or smth like that

Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.

zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.

Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?

zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)

i need this rru please any one have to uplode link
thanks

Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.

theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.