Related
my lads desire is stuck on black screen with white htc and white exclamation marks in each 4 corners , could anyone please help has he has come to me , but i have very little expereince in these matters so would like a tuturial if could be fixed
thanks in advance
I'd be looking at a fault attempt to root or flash a new ROM. I assume you don't know the software version that was originally on the handset by chance?
he was running neo latest vol 8 and s-off.......think he was trying to return to stock ....latest hboot..93
just tried rnning fastboo commander and it says he is s-on and non eng hboot, if that helps
So you don't know the original HTC ROM version he was on?
it was ....2.10 before he rooted and flashed custom rom
If it was 2.10.405.2 then you can get the RUU and get back to stock. Download it from here:
http://shipped-roms.com/download.ph...00.32U_5.09.05.30_2_release_142828_signed.exe
To use this, turn the phone on holding the back button and it should boot to FASTBOOT. Connect to your PC and once the screen says FASTBOOT USB (and once Windows has installed the drivers) run the file. It will get your Desire back to stock
*** There is a chance you were on the Vodafone version, 2.10.161.2, if you got the Desire from them. If so, you currently can't get that ROM ***
EddyOS said:
If it was 2.10.405.2 then you can get the RUU and get back to stock. Download it from here:
http://shipped-roms.com/download.ph...00.32U_5.09.05.30_2_release_142828_signed.exe
To use this, turn the phone on holding the back button and it should boot to FASTBOOT. Connect to your PC and once the screen says FASTBOOT USB (and once Windows has installed the drivers) run the file. It will get your Desire back to stock
*** There is a chance you were on the Vodafone version, 2.10.161.2, if you got the Desire from them. If so, you currently can't get that ROM ***
Click to expand...
Click to collapse
cheers Eddy OS ...all back and working now
big thanks to you.
will be keeping an eye on what he doing now concerning the phone
No Probs! Just keep that RUU to hand in case it happens again
Hey everyone!
I recently unlocked the bootloader and installed the latest ClockWork Mod Recovery 5.8.3.1 on my HTC One X. I was trying to install the Android Revolution HD theme on my phone, it didn't install and when I restarted my phone - it got stuck on 'HTC quietly brilliant screen'.
I have tried a lot of the tutorials but I am having no luck and am very sad and frustrated with my phone now.
I updated my phone to software version 1.28 before doing all the above. Right now my phone is unlocked and the CWM is installed and works.
I downloaded the RUU for my phone which is:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed
Whenever, I try to run the RUU there is some kind of problem. At first it was battery below 30%, now it was get the correct version.
I tried flashing boot.img and system.img via command prompt but the system.img flash does not work for some reason.
I know that in order to run the RUU, I need lock the bootloader and I think I need a stock recovery.
But I am confused, the RUU is 1.26, but my phone software was 1.28 - so what do I do?
Anyone please help. Thank you very much.
I used the all-in-one toolkit to unlock my bootloader and installed the recovery i flashed a rom onto my htc one x when it finished flashing i unlocked the screen and i just saw htc in green over a white background for a long time i tried flashing another rom same thing happened after a while of browsing i noticed it stopped with the white htc screen and it let me do the 1st time setup now its stuck in airplane mode and i just want to get back to my stock rom :/ please help my cid is htc__102 i know its a german RUU. i have the exe for it(RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed) when i try to update to a lower version it sais the rom update utility cannot update your android phone please get teh correct rom update utility
When you have tried to flash a rom, did you flashed the boot.img?
If no, try and your custom rom works.
However, for the ruu, you need a ruu with JB; search here .
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
This thread has been created for users who are experiencing a hard brick, soft brick, boot loop, or random shutdown on their HTC 10. Feel free to ask your question(s) here.
Going forward, new threads created regarding the topics listed above will be CLOSED by the moderating staff. Please remember to follow the XDA forum rules when posting.
Cheers,
Magnum_Enforcer
FSM
Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.
TheMadKing said:
Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.
Click to expand...
Click to collapse
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.
santod040 said:
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.
Click to expand...
Click to collapse
It's pretty complicated, but long story short, I was stupid.
I can't S-Off without being able to boot the phone, so well, I'll probably just wait for a RUU.
HTC 10 boot loop
Hello guys,
my wife yesterday tried to update OTA (our htc 10 are completely stock) to OREO from Nougat 2.41.401.41. Something went wrong and it's stuck in a boot loop. I can get in bootloader and tried to install the ota, which I downloaded, manually from SD card, but after verifying it says "error: partition has unexpected content". Is there a way to get the phone back working even with data loss? Thanks really for the help, the phone has never been modified, I am getting crazy reading the forums but I am a total noob ?
i have seen i need a ruu, possibly zip since I can't boot and activate USB debug. Can someone please share a run.zip link at least equal to 2.41.401.41 (European)? Thank you very much
I have the same issue, HTC 10 in a boot loop after applying the OTA Oreo update. I'm able to get into bootloaders and such, but i need the data thats on the phone... Allready tried taking out the SIM and SD-card. Does anyone know if this can be fixed?
Same problem here!
After Reading what the rest of you lot mentioned here, i have the exact same problems! Installed the update from Nougat to Oreo, and the phone went into bootloader! I was stupid enough to delete most of it through TWRP, and even dumber to RELOCK it so that TWRP is out of the Picture. Download mode appears, but the recovery just brings me back to bootloader. Oh yes, and the OS is missing.
and fastboot / adb wont recognize the HTC Connected to the PC anymore.. Guess this is a total Brick? should i send it back since i have a warranty? Will they be able to fix this?
I too was stupid and relocked it while reverting to stock. At this point I had also flashed the stock recovery and recovered to what turned out to be a non-functional backup. (Stuck in boot-loop)
Thankfully Fastboot did however still work while in download mode, and I was able to unlock it again by flashing the same unlock_token.bin that I have kept since I unlocked it the first time, slapped in twrp again and I was good for another go.
M8 can you help out linking some procedure for a noob like me? Should I use a ruu? I am completely stock
I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
Thanks a lot for your help, I'll give you a feedback asap.
varg300 said:
I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
Click to expand...
Click to collapse
Everything worked smoothly! Thank you so much!
Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???
husnainrasheed said:
Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???
Click to expand...
Click to collapse
Flash the ruu that is posted 1 post above yours.
IMEI not showing
Mr Hofs said:
Flash the ruu that is posted 1 post above yours.
Click to expand...
Click to collapse
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??
husnainrasheed said:
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??
Click to expand...
Click to collapse
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.
Thanks Alot
yldlj said:
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.
Click to expand...
Click to collapse
:good::good:
I updated to Oreo and now I am back on track.
everything is back to normal, IMEI and baseband as well working SIM.
thanks alot man ..
:good:
I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !
budgati said:
I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !
Click to expand...
Click to collapse
Hold the power button and the volume down button to reboot to download mode. From there you can flash an RUU.zip to fix it.
What is needed to direct you to the proper RUU.zip to download and flash is for you to boot to download mode and post here what it says next to "OS"