Develop Bugs

[Q] 1.29 update failed

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...

[Q] Unable to load ROM

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.

[Q] Strange CID and Stock update help please?

Hi there.
I'm new to the forum but have lurked and used some of the great information and tools that are available here.
So firstly, thank you.
Now.
I bought my One X in China (Where I live), in around August. It seems as though the one I got isn't a regular One X and because of that I'm having some problems.
A month and a half or so ago I installed an AOKP Rom which I've had some pretty intense bugs with, such as the the phone restarting whenever I toggle WiFi on or off. Because of that, I finally attempted to return to stock today. After a while, I found some success. I restored my nandroid backup, reflashed the stock recovery and relocked the bootloader. Happy that I was back to normal, I went to download the Jelly Bean OTA update, but kept having errors when doing so. (The green bar would reach about 1/3 of the way and then a red triangle showed up.) I've tried to troubleshoot and in doing so have found out that my CID is "11111111", so I have no idea what to make of it. All i could find was that this is some kind of superCID, but if it's preventing me from installing an OTA update then how do I go around this?
Is it possible to change my CID to something more accessible? This is the international Tegra 3 model by the way.
Additionally, the HBOOT screen shows that my phone is "ENDEAVORU PVT SHIP S-OFF RL". Is this normal?
Any answers would be extremely appreciated. Thank you.

You're really lucky actually, because a lot of people want exactly your phone - SuperCID and S-OFF. You cannot flash OTAs on a SuperCID phone iirc, but you can unlock the bootloader and flash something else

Hi, there are fastboot commands to change your cid if you are s-off but I am not sure why you would want to.
With s-off you can just go and flash the 1.39 hboot from mikes thread (link from his arhd thread OP)
I have same setup as you and have been wondering what actually is stock for me if I ever needed it. I don't have a nandroid from when I got the phone and I guess that s-off and super cid means I could pick any one ? But which.
Sent from my HTC One X

Thanks for the replies. I guess i have a better understanding now of what these things all mean.
So I gather if I want to get the stock Jellybean ROM I have to flash it myself?
Eh, that's kind of a pain but I guess it's not too bad. Do I go about it in the same way that anyone else would or will there be a variation based on the situation of my phone?
Thanks

I reckon someone with an s-on would gladly swop with you if its a pain you have the most flexibility as it is.
Flash whichever update you like without worrying about the cid matching. That's the magic of super cid. Then because you are s-off you also have the option to downgrade if that ever took your fancy.
There are many guides on how to do this written far better than I could so just search the forum.
Enjoy
Sent from my HTC One X

I see.
I've had a look around and I'm still a little confused to be honest.
Because I'm S-Off and have SuperCID, does that mean I can just choose a Jellybean OTA Update, download it, install it and upgrade the HBOOT?
Everything will be the same as if I upgraded OTA?
Sorry for being so useless.

Don't hang me for this info, see it more as a pointer to more info to search on
What i have read before is that you can write yourself a CID and update the hboot with a firmware from that CID. then you can run any software out there......
Do not run a ruu, it might mess up your s-off to s-on

When I get to my pc I will write up what I did with a link.
I did as Mr Hofs said but I did not need to change my cid from super to do it.
I have never tried an ruu.
Sent from my HTC One X

Ok so first i read this and watched his youtube vid http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html
Check video here http://www.youtube.com/watch?v=AQasxRPopSM he works with an S-Off
I started on HBoot 1.12 i believe
Then I got my unlock token handy (one from htcdev) and made sure fastboot working etc
Then did a nandroid (which i subsequently deleted but hey i tried to do the right thing )
Then I got the latest firmware for HBoot 1.39 from here http://forum.xda-developers.com/showthread.php?t=1957376 I downloaded the first 1.39 for WWE (x.xx.401.x - World Wide English (WWE))
No need to change your CID. Super CID works with any of them.
Now I just followed the usual steps explained many times here to flash the firmware.
You need to put the stock recovery back on. I got mine from here http://forum.xda-developers.com/showthread.php?t=1546970&highlight=htc+one+x+*stock* EDIT: dont think you need this step actually -will let one of the pro's confirm.
Then relock bootloader and reboot in RUU and flash the firmware.
When done unlock bootloader again, flash custom recovery and flash a ROM. You can skip the extra step of flashing the boot.img as with S-Off your custom recovery can do it.
As mentioned by Mr Hofs I have no idea what an RUU would do to S-Off, Ive never tried.
Good luck.

[Q] GPE to stock to unlock

Hello guys,
I purchased a second hand HTC One M8 which has been converted to GPE, unlocked bootloader and S-OFF. The phone is currently locked to the Vodafone network, so I assume it was previously a Vodafone branded device.
Now I need to get this phone unlocked because Im with another netowork, so I purchased an unlock code online which failed (they have always worked in the past). I got a refund from the seller and was told to try a different seller. Purchased a new one but it turned out to be the same code. I told the seller my story and was told I need to make sure I am on the latest official stock ROM. Maybe the previous owner entered an incorrect code too many times and disabled this whole thing altogether? I dont know.
Im not sure how a stock ROM would make a difference, but the phone is useless to me being locked to Vodafone so I guess its worth a try. Now heres where I need your help because Im a Nexus user so Im not too familiar with all these CIDS, MIDS, etc.
I have changed my CID to superCID, do I now just flash the Vodafone RUU? Or do I need to take further steps? I dont really need to change the MID aswell do I? I will not be staying on stock, I will most likely be returing to GPE or some AOSP ROM and I'd like to keep the bootloader unlocked and S-OFF.
Also are there any other methods to get this SIM unlocked? I have read the thread about using a generated dat file, but read that no longer works.
Thanks.

Follow the 'back to sense' thread in general first, then set CID to the Vodafone one, I assume UK), then flash the RUU

Hi,
Thanks. Is this the thread you are referring to?
I thought I could flash any RUU with superCID which is why I changed to that, but no problem I'll just change it over to Vodafone to be safe, it is VODAP001 for the UK version I believe.

You can use the unbranded EU RUU if you prefer, it's up to you
And yes, that thread

No what I meant was I thought I should be able to flash the Vodafone RUU using superCID without having to change to the Vodafone one...but nevermind I changed it over anyway.
But Im having some problems with this actually. I downloaded what I thought to be the Vodafone ROM from the HTC dev site, the file name is m8ul-3.4.0-g3c7a5c1.zip, I follwed the steps laid out in the going back to sense thread but I get an error message '24 parsing android-info fail', tried a few times as mentioned in the thread but same thing happens.
I then located a Vodafone RUU exe in this thread. That failed to even run as confirmed by another member, something to do with InstallScript.
So then I tried flashing the previous zip file with the htc_fastboot that you provided in the same thread, same error as before.
Any suggestions? Or do you know if there is a working Vodafone RUU available anywhere?

The file on HTC Dev is the kernel source, which is why that hadn't worked.
As for the RUU, it looks like it could be corrupt.
You first have to flash that ZIP in the back to sense thread to get the partitions corrected and then you can flash an RUU. I'd just use the EU one as (for a start) it works and it means you don't have all the carrier rubbish

Oh ok, I didnt realise I had to flash that before flashing an RUU, I just thought flashing any RUU would sort out the partitions.
I'll go ahead and flash the zip file and the EU RUU as I am unable to find a Vodafone one. But Im really not too bothered about the carrier crap anyway because as I say the only reason for going back to stock is to try and SIM unlock the device, and if doing that will really make a difference then it would most likely do it on the stock Vodafone ROM, but I dont know I could be wrong.
I'll let you know how I get on.

You can SIM unlock it regardless of ROM. Some people say flashing the RUU will sort everything out but, in my experience, I've had to flash the first ZIP and then the RUU to get it all working properly

Thats what I thought but it didnt work. The unlock code provider then told me to make sure I am on official stock ROM which is why Im trying to get the Vodafone ROM loaded on this phone. As Ive said I dont know how much of a difference it will make if any, but it is worth a try I suppose.
Anyway Ive had some problems flashing the EU RUU, I followed the guide and flashed the firmware zip which went all fine. Then I flashed the EU RUU provided in your guide, but it kept giving me errors towards the end - 51 partition update fail. Downloaded another RUU which gave me the same error, tried an RUU exe which also failed. Tried flashing a different firmware but I cant remember if it failed at that stage or at the RUU stage. Then I thought maybe the firmware is an old version from Kit Kat. I felt as if I didnt know what I was doing and should give up!
I then came across this thread and that person was doing it through TWRP backups which I thought I should maybe try. But I dont know Ive been at this for hours and currently without a ROM or recovery! I think Im gonna flash back to GPE until I know what to do.

Relocked, OS won't boot

Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.

StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?
Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.

Hm. Out of the myriad RUU.exes I've tried the most recent AT&T one was the only one I couldn't get to start, and when I tried installing it via .zip it would just restart the phone and nothing else. That in combination with other posts I've seen on this forum saying it's borked (although I might have misread the numbers/misinterpreted the jargon) just lead me to think it was broken. I'll redownload and try again. Thanks!
Edit: Well, it worked! I don't know what I was doing wrong. Thanks a lot!