Related
Hi,
I was trying to root my phone with the guide that is on this forum, but then when i restarted my phone, it was stuck on the white "HTC" boot screen. Then i tried to do a "Factory Reset" in hboot and rebooted, and still stuck on the boot screen. I tried to put a PD98IMG.zip as it was prompted in hboot as "no image or wrong file", so i loaded PD98IMG.zip onto my SD card, and still not working. any suggestions ?
my phone is S-ON.
I guess your phone is branded ? If that's the case, you need to follow the tutorial for a goldcard.
Also, if your rom is 1.7x or 1.8x, you can't root it. You have to follow the downgrade tutorial 1st
Mine took 30 mins to boot once. You could try the ruu look in dev section, you just flash it from Windows, then start again. Was your she branded?
Sent from my Desire HD using XDA App
Howling Wolf said:
I guess your phone is branded ? If that's the case, you need to follow the tutorial for a goldcard.
Also, if your rom is 1.7x or 1.8x, you can't root it. You have to follow the downgrade tutorial 1st
Click to expand...
Click to collapse
<-- This
I was in the same situation, downgraded ROM and clockwork mod and did a restore and it works fine now
@Howling Wolf - I cannot get the CID for the SD card, because
in the 'adb shell' command, my command prompt says "error: device not found". But i want to know, can i still get the CID through another HTC desire phone ? and can i still update a stock rom with S-ON ? and how do i know if my phone is branded ?
I got my phone from Taiwan, a friend brought it over for me, and when i last checked it was on software version 1.37.921.1 .
@turbo_d - ill try that thnx
did you try installing the htc sync software then do adb devices
ye i did, i installed HTC sync to get the HTC drivers, but from what i noticed is that your phone needs to be "running" instead of being stuck on the white HTC boot screen or even the hboot doesnt pick up the device aswell >.<
Totoro_tw said:
ye i did, i installed HTC sync to get the HTC drivers, but from what i noticed is that your phone needs to be "running" instead of being stuck on the white HTC boot screen or even the hboot doesnt pick up the device aswell >.<
Click to expand...
Click to collapse
Try going into bootloader, and then run adb from pc..
@SAPPH1RE - i tried that but thanks for the help !
ok i acquired my CID through linux, but now its telling me
main version is older !
update fail.
any suggiestions ? my current software version of the phone is 1.37, which stock RUU should i be using ?
If you are on 1.37 you should be fine to continue with getting s-off and such. You don't need to upgrade or downgrade your ROM until you achieve s-off. And then you should upgrade to a custom ROM such as LeeDroid.
Sent from my Desire HD using XDA App
did you get it working ?
I fixed mine a few weeks back by doing a full wipe and then loading a fresh ROM
Thing is, i cant get my phone to start up, so i need to flash a stock rom, so that i can get my phone started and then do S-OFF. But it keeps telling me "Main Version is older!"
ive tried 2 roms already, 1.32 and 1.72 RUU. What could be the problem ?
thnx problem solved, the gold card wasnt done properly, so i re did everything.
thnx for the help guys !
paulcoop007 said:
I fixed mine a few weeks back by doing a full wipe and then loading a fresh ROM
Click to expand...
Click to collapse
@paulcoop007 i have same problem with you, same version with your phone and S-ON. and my phone at black screen with htc. how can i fix it. can you explain how did you fix your phone?
Hello!
I have a question.
Currently I have the phone Rooted and a custom Rom is installed. Now you have my phone for repair. I would like the phone back in the original condition (ie without root privileges and ClockworkMod menu) to bring.
I had then the original image, which I did for the root time, have re-played.
But unfortunately I get the menu ClockworkMod not go away.
The menu is still available.
Next try:
After I had been playing the original image, and I had started the cell phone was offered by T-Mobile is an update.
But unfortunately this update is not installed.
It aborts with an error message.
Now I have read that I should just flash the original RUU, Complete new. So I went to shipped rom on the side and I have the appropriate RUU for my phone charged. (RUU with the Tmobile UK).
But this I do not get installed.
The flash process is interrupted after a few minutes with the error 140 (wrong bootloader version).
Now my question:
How do I bekome out there, I have on my phone without the original T-Mobile software ClockworkMod, or do I uninstall ClockworkMod?)
Did any of you an idea?
Thank you!
Greeting Hollux
P.S.: Sorry for my bad English.....
Everything you need to know about putting your wildfire to original condition is in this post:
http://forum.xda-developers.com/showthread.php?t=1160251
Enjoy
dragdusan said:
Everything you need to know about putting your wildfire to original condition is in this post:
http://forum.xda-developers.com/showthread.php?t=1160251
Enjoy
Click to expand...
Click to collapse
Hello!
Thank you for the link, but my Handy is not S-off!
I'm at HBoot 0.80 and I have the Problem, that I can not flash the original RUU for my Wildfire....
I become an Error 140 Code (Bootloader error)...
Greets Hollux
what is your language?
is your phone branded?
you have breaked your recovery?
Maybe you have installed the bootloader driver from Unrevocked
Is yes,download and install htc syn from its official site and after the installation,unistall ONLY htc sync,not the drivers
my phone is unbranded and i used this
http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_160191_signed.exe
it will update your HBOOT to 1.01.00001 so you need s-off to flash recovery and custom rom
kylon said:
what is your language?
is your phone branded?
you have breaked your recovery?
Maybe you have installed the bootloader driver from Unrevocked
Is yes,download and install htc syn from its official site and after the installation,unistall ONLY htc sync,not the drivers
my phone is unbranded and i used this
http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_160191_signed.exe
it will update your HBOOT to 1.01.00001 so you need s-off to flash recovery and custom rom
Click to expand...
Click to collapse
Hello!
I have my phone with Rooted Unrevoked3.
Then a Custom Rom installed. (DK ROM).
Original is the phone branded by T-Mobile Germany. It was originally Froyo still on the phone.
HTC Sync I have installed and then uninstalled so I only have the drivers on my computer.
For flash process:
I've taken on shipped-rom RUU following:
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed
If I'm in HBOOT USB plug mode, the mobile is an Android Phone - Android detected bootloader interface.
However, so after the start of the RUU, the phone is not detected!
If I'm in the fast boot mode, the USB phone as a USB device is Android - My HTC detected.
Even after you start the RUU detected the phone and I can start the flash process.
However, it comes out after a minute the error 140 (bootloader error).
If I install the image, which I then made by the original ROMs, will start after the one offered on Air update.
This, however, can not even install.
The flash process will start, but after a short time I see a picture in the phone with an Android males and a triangle. Then I am back in ClockworkMod menu ....
As I've written, I only want to install my phone with the original RUU from T-Mobile Germany and the menu should disappear ClockworkMod ...
Did any of you an idea?
What happens if I flash a non T-Mobile RUU ....?
I can try to flash another RUU and then later, my T-Mobile?
Please Answer, thank you
Greeting Hollux
You will have to downgrade MISC Partition, to allow "Downgrading" your ROM. (DK Custom ROM is based on 2.22.405.1, and you are trying to flash 1.10.114).
The Guide for AlphaRev X to Downgrade HBoot from 1.01.0002 to 1.01.0001 follows this same procedure, but, its for the WWE 2.22.405.1 ROM only.
But, you can follow this procedure, since you are on HBoot 0.80x
http://forum.xda-developers.com/showthread.php?t=905003
Obviously, the command version numbers will change in your case, and, you will need the TMO Rom.zip from that RUU.
NB - Disclaimer - It should work, but, it's a sensitive process, and I am not responsible for bricks.
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.
Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.
MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.
Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!
First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?
Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!
Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.
THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.
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