I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
You need to flash stock recovery. bootloader doesnt matter. Are you in europe?
hy3301 said:
I have a bootloader unlocked HTC one X running on 1.28. I got the 1.29 update notification today, but it kept failing when I try to install it. I am on Clockworkmod. It says cannot mount SD card. And I renamed it and deleted the assert cid thing, it failed without a reason.
And I tried to flash back to stock recovery, it still did not work. Do I really need to lock the bootloader to get this work? That's so troublesome.
Anyone can help me? Thank you very much in advance.
Click to expand...
Click to collapse
as far as i did my last OTA am on a branded phone. I restored my backup stock rom installed stock recovery and downloaded the OTA and installed fine. No need to relock bootloader or anything else. have you tried rebooting your phone and trying again? or have you flashed the proper stock recovery mate
Doesn't work for me either,puted the stock restore,i even relocked my bootloader and still nothing,it doesn't seem to work,i will try to update trough recovery mode,hope that will work.
Sent from my HTC One X using XDA
Same here, any solutions
I don't think that i will try to update to 1.29 anymore,i read on a site that 1.30 will be lauched very soon,so i will try to update to 1.30 when it will came up.I don't know what else to do,i mean,i've tryed everything and still no luck with this update.
I have exactly same issue as you,but what I think if its be realise of 1.30 for us be same problem if we don't find any solution now.
I'm in Japan. I've tried that, nothing worked.
Mine is unbranded. I've tried all of them. I've had enough of it.
It won't work. Don't waste your time.
No solutions seemed to work so far. My choice is to ignore it.
Yes, me too. No more 1.29.
Same here, was 1.28 and unlocked the bootloader and rooted. Tried CWM method but doesn't work and hope someone will have solution to this.
I have same problems i surf a lot today,and I find that my problem is that 1.29 Update CID is different from my phone CID. U can get u CID by cidgetter from store. And if u try to flash update by cwm it shows what Phone CID's supporting update witch u have. Just try to check this guys,thats what i find and my opinion it should work.
I think my solution to find update witch supports HTC__001 CID
So basicaly you are saying to download the update and then reboot the phone,enter in recovery mode (cwm) and then try to flash the 1.29 update that we've downloaded?i allready tryed that and it doesn't work,gives me an error and stops.if it's a CID problem can't we just put our HOX CID into the update?i think that i've seen somewhere on xda a metod to do that but i don't remember in which topic.
Sent from my HTC One X using XDA
if it possible to change CID in update,so yeas its solution witch we need. But I don't know how to do it.
I think we will skip the 1.29 update and wait for the next one.I'v just read on the forum that version 1.32 was released (nothing confirmed yet,just some pc screenshots),maybe that version will work.I will check periodicaly for the 1.32 update and see if it works.
I found a thread talking about deleting the lines about CID in a update-script file or something similar. I've tried that, but still ended up with error. I am going to give up.
Did any of you flashed something on 1.28?I am thinking that after i updated to 1.28 i flashed the 3 dot removal.Maybe this is the cause that the update fails?
I haven't flashed anything,just rooted flashed cwm and superU. No updates gonna work for us till we get S-OFF its just one solution. Follow guys in S-OFF Discussion they progressed a lot on it. If they crack our S-ON to S-OFF we can do with our phones whatever we want to do. And install whatever we want to install including updates. Now just wait...
Related
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.
Hey Guys,
I'm reaching the point of frustration now. To try and cut a long story short, I had the Android Revolution 6 ROM on my rooted/unlocked HTC One X, and decided to update it to Android Revolution 13. I followed all the instructions, went to boot it, and it just sat on the HTC logo for an hour at which point I knew something went wrong. I repeated the steps, including wiping data using super wipe, without success either. I then decided to just select the "Factory reset" option on the boot menu, but this has also failed to boot after 30 minutes. I can also no longer boot into recovery. I've tried reloading CWM and other recovery ROM's onto the phone, but the phone resets as soon as they load.
At this point, I just want to get some form of OS on my phone. My phone is Unlocked, S-ON and has a CID of OPTUS001. I don't know if Factory reset will work if the phone is unlocked. It's all very time consuming as you normally don't know if the boot process has locked until you've waited ~20 minutes. I can't find my original ROM from when I bought the phone either, so I assume I need to obtain another one from somewhere, but I don't have any idea about CID compatibility, etc, and I'm finding this all very confusing and frustrating. All help is much appreciated. I have a feeling I need to replace my boot.img with a stock boot.img, but once again, where do I get that?
Thanks
the phone doesn't boot because you don't have the latest firmware installed, you need HBOOT 1.31 but you can't install it cause your CID is not compatible with it, you sjould go back to ICS and wait...
Did you load new firmware 1.31? This firmware is not compatible with Your CID... Did You read carefully this thread — http://forum.xda-developers.com/showthread.php?t=1924003
Sent from HOX with ARHD 13
You forgot that you need to update the firmware to 1.31.
You can also just install ARHD 9.7.2. Ensure you have the latest CWM 5.8.4.0
faatboot flash recovery recovery.img
and then flash the boot image:
fastboot flash boot boot.img
fastboot erase cache
And then copy the ROM on using recovery mount USB and flash it.
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
without S-OFF no chance to change CID. Regarding CID compatible - http://forum.xda-developers.com/showthread.php?t=1924003
wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...
matt95 said:
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...
Click to expand...
Click to collapse
Yeah, but I'm going to put on ARHD 9.7 I think.
Optus not compatible with JB yet
Hey guys,
fairly new to this all and it seems I have messed up at some point...
I managed to root my phone and i do have TWRP on it and wanted to install a rom (blade elite 1.1). went into bootloader and flashed the boot.img with the tool, then went into recovery, cleared all the caches/factory reset/system and flashed the rom which i had previously copied onto my sd card. then i pressed reboot. It didnt start up for a few minutes so i kind of panicked and went into recovery again. I had made a backup previously, which I then restored. But it's still stuck on the screen where it sais htc one on the white screen with the beats audio thing on the bottom... Waited for around 20 mins. I can still get into recovery, so I'm hoping not all hope is lost.
What do I do now? :/ Do I have to flash the stock kernel or something first before I can restore with twrp?
Please help :/ I kinda really need my phone...
Oh yeah I forgot one thing. The tool said "error: device not found" in the first cmd window when I flashed the kerel, but when I clicked it away a second one popped up and it said it flashed correctly. It did the same thing when I flashed twrp and thats definitely on my phone, so Im guessing it has flashed the kernel correctly. Just thought I'd mention that.
fastboot getvar version-main
gave me:
2.17.401.2
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Your hboot is to low, you need to update. Since you used the ruu, go into settings - about menu and update the phone with the software update utility.
You are still on ICS and need to update to JB.
You can also update your Hboot yourself by check your cid number using this app
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Finding the Hboot to match your cid number here
http://forum.xda-developers.com/showthread.php?t=1957376
And upgrade your Hboot manually or by using a tool like this one here (you'll need to put the correct Hboot in the relevent folder of the app first!)
http://forum.xda-developers.com/showthread.php?t=1924003
Read through the full guide and comments first before proceeding!
Hope this helps.
Easiest is to update with the official ota now as he already installed the ruu
And yes you can use the old unlock code again
StreamOfLife said:
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Click to expand...
Click to collapse
You can use the original Token they sent you. No need to go through the whole HTCDev process again :good:
You guuuuuys, it worked !!
Thanks a bunch! Was totally easy with the ota update too, very smart!
Good ! Enjoy
CASE CLOSED !
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
HELP, I've bricked my phone.
I'll try to be as brief as possible.
I had android 5.0.1 (4.16.401.10). unlocked bootloader, installed TWRP, rooted.
a few months later today, my phone had an OTA update notification (4.16.401.13), tried to do it, failed and it kept sending me to TWRP.
Googled it, people said I should restore the stock recovery, I did, tried to install the OTA again. phone got stuck on splash screen.
From there I have been online for hours trying to fix this but nothing. (there has been many flashing attempts, some fail some success) so the phone is pretty much a mess now.
My question is, what's the easiest way (if there is) to just restore the phone to stock firmware? I don't care if it's going to be rooted or not, I don't care if It's going to be wiped, I just need it to work.
Currently I have (relocked) bootloader, S-On
Thanks.
Same problem here, Got this update yesterday and stuck at the splash screen.
rooted, S-on, stock recovery
tried everything from changing recovery, FUU, RUU, nothing worked
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
I suspect its related to the xposed relared problem as the old backup its not installed.
AHOHA said:
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
Click to expand...
Click to collapse
Sorry if this is a noob question, but how can I do that? is there somewhere where I can download backups and restore them on my phone? And if so, will I need anything like an S-Off or something?
Because I've tried everything else I think, I tried RUU (both from PC or from bootloader, and with both Unlocked and Relocked bootloader) and nothing seems to work.
Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help
mizaras said:
Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help
Click to expand...
Click to collapse
I finally got mine to work today!!
What worked with me is this:
I got the RUU Zip file for my CID, renamed it to 0P6BIMG.zip , and copied it to the root of my SD Card (using an adapter or using TWRP to mount it)
then I flashed the stock recovery for my phone, then RELOCK your bootloader (fastboot oem lock)
Onve you've done all that just put the SD card in your phone and boot it in bootloader mode (Vol Down + Power) and it should detect the 0P6BIMG.zip file automatically and ask you if you want to update it.
P.S: I have S-On and it worked.
I hope this helps.