yashsingh1/xdaforums huggingface dataset:
[HTC One X] mustakeel1981:
hboot 1.31

hi,

it didn't work with me hboot: 1.31

rom arhd 13

i try several times but always i stuck after i run ARUWizard.exe.

can anybody make video guide and upload it on youtube .. that will help alot.
[HTC One X] civilization:
aim not able to locate rom.zip after i run the RUU. How can i show the hidden files?
[HTC One X] ClydeB1:
Click Windows Start icon, in the search bar at the bottom type %temp% - then select the temp folder and in that folder search for rom.zip. You need to run the ruu, without doing any of the steps and keep it open until you locate the rom.zip file. You can then copy it to another location and then close the ruu.
[HTC One X] gabrielvl:
Please help with this

zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)

What i must do exactly?

This is what i do

-i put all 3 files in a folder and i zip the folder witch contains the files.

after that i rename the zip in rom(just rom ,not rom.zip :)) )

What i do wrong?
[HTC One X] ClydeB1:
You must zip the 3 files and not the folder with the 3 files in it.
[HTC One X] gabrielvl:
Just zip? no modification of name?

This is what i understand i zipp files and ai remane all 3 zipp file in rom.zip..

Is that correct?

Sorry for my english..
[HTC One X] ClydeB1:
Yes, you will need to also rename the zip file but not the 3 files in the zip, they still need to keep their names, but your problem was probably that you were zipping the folder with the 3 files and not the 3 files directly, ie no folder. When you are done you should have a zip file named rom.zip and that should contain 3 files named android-info.txt, boot_signed.img and system.img
[HTC One X] gabrielvl:
This is what i did now and still appear error 156

What i do is this:

zip files

rename zip in rom (just rom ,not rom.zip)

put rom.zip in customRUU

open ARUWizard ,and fallow steps from there

But ghet error 156

EDIT

I try all from steps again from tutorial (start from step 1 to last)

Still same result

Thx for help.
[HTC One X] ClydeB1:
Sorry bro, you'll need to wait for the OP to help. I'm not sure what the error could be.
[HTC One X] hokoonho:
You should not zip the folder!

Only zip the 3 files into a single zip
[HTC One X] gabrielvl:
Exactly this is what i did

i select all 3 files into a zip ,and i rename that zip to rom but is not working.
[HTC One X] noodlez04:
So I got the rom.zip file and everything, did EVERYTHING like you wrote, but I keep getting error 158, which means

Rom file error (Rom size larger than maximum allowed.
should not happened if you place the right zip that only contain
Android-info.txt, system.img and Boot_signed.img)

the thing is - all I put in the zip file are the 3 files you said in the tutorial.

Any ideas?

btw, my current version is 2.18.751, trying to go back to 1.29.751.
[HTC One X] hokoonho:
It should be the problem of the Android-info.txt . Try to extract the file from the customRUU.zip again. When editing the Android-info.txt, make sure that you only replace the numbers, don't add/delete any space or press any Enter key. (If you delete a space, then add it back, it may not work as well. )

When finish editing, save the file (do not save as, which may change the char encoding).

OR download any text editor that's for programming.

OR if you edit the file with Linux.
[HTC One X] leventccc:
I was using arhd 13 with 1.31 ruu. Now I am using 1.29 rom again thanks to this thread. Only problem is it says there is no update but I have updated to 2.17 base in the past. I don't understand why I can't update now. Can anyone help me?

Note: My cid is HTC_102 (unbranded)
[HTC One X] hokoonho:
What is the hboot version of your phone? and what is the full version number of the? 1.29.xxx?

Have you flash the recovery-signed.img and relock? If not, just do that.

If you still get trouble, run the customRUU again, this time, your phone should be in relock state and you may need to also include the "recovery-signed.img" in the rom.zip and place it in the customRUU folder.

Good luck
[HTC One X] leventccc:
My phone was using 1.31 hboot on 3.14.401.619 rom. (CID: HTC_102)

Here is the list of what I have done.

1) Download Custom Ruu and Extract it To CustomRUU folder

2) Download RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio_2.1204.127.19_release_271851_signed.exe

3) RUN Official RUU and Get rom.zip from it

4) Extract rom.zip to htcruu folder

5) Reboot phone to fastboot mode and get necessary variables

6) Edit android-info.txt to match phones using notepad++

7) Select boot_signed, system, android-info and zip them. Rename zip to rom.zip

8) Move rom.zip to CustomRUU folder

9) Reboot to fastboot and run the aru wizard and finish flashing

10) fastboot flash recovery recovery_signed.img (recovery is from 1.29.401.12 ruu)

11) fastboot oem lock

12) reboot and check for ota to 2.17
[HTC One X] gabrielvl:
I did exactly what you say u did,but when i get to step where i run aru wizard after it start i get error 156
[HTC One X] leventccc:
ERROR [110]: FILE OPEN ERROR

This error message indicates that the RUU lacks some specific files or they are damaged, so the RUU cannot continue with the update. You have to get the complete RUU package and try again.

ERROR [120]: MAIN BATTERY POWER

This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).

ERROR [130]: MODEL ID ERROR

ERROR [131]: CUSTOMER ID ERROR

One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.

ERROR [155~159]: IMAGE ERROR

One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.

ERROR [170]: USB CONNECTION ERROR

This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone.

Are you sure you zipped the files correctly? If you did it right when you open the zip file it should show you 3 files. Not a folder
[HTC One X] gabrielvl:
This ruu i use for that RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed

So what i do wrong?

my main version 2.17.166.3
[HTC One X] leventccc:
I have returned to 2.17.401.2 and locked my bootloader succesfully. My hboot is 1.31 and I have one question, when the official jelly bean will arrive, may I be able to update to jelly bean without unlocking bootloader? It is very important because I will sell my phone soon and I want to make it updatable to the latest version.
[HTC One X] alearcy:
Thx for the reply! I took the recovery file directly from ROM.ZIP in the original RUU temp folder.Then I put the command

fastboot flash recovery recovery_signed.img

and after that this other command to relock

fastboot oem lock

. But when the phone is in recovery mode it appears a red triangle and when I start OTA they do not arrive (both with full battery charge and unplugged USB).

Help me please...I just need this info to solve the problem :(:good:
[HTC One X] noodlez04:
Has anybody actually gone back to stock and received the update? (TW devices for example)
[HTC One X] hokoonho:
I have try it on 3 different One X one in HK and two in TW. They all received OTA without problem.
[HTC One X] hokoonho:
You can try to unlock the phone again, flash a custom recovery, then wipe anything by using the custom recovery, e.g. wipe system, cache, battery stat... then run the customRRU again and follow the steps. make sure there is no error message in every step you do...

any small mistakes may lead to problem.
[HTC One X] alearcy:
thx, but CustomRUU and RUU.xx.xx.exe it's the same thing???
[HTC One X] hokoonho:
In theory, yes.

But the customRUU is extracted from an early version of RUU, if you extract the same thing from the latest, I don't know if you can still "fool" it, or it may cause other problem.
[HTC One X] alearcy:
I did but the recovery continues to give me error. The system works fine, but the OTA does not work. I've not used the customRUU but the RUU that matches with my CID. :crying:
[HTC One X] Feepitee:
Thank you! Restored phone to stock from 2.17.728.3 to 1.29.728.12 :D.

Edit: I seem to be on the same boat as the person above - can't receive OTAs, when in recovery mode a red triangle next to a phone appears. If you test the original RUU, it says I'm on 2.17.728.3, not 1.29.728.12. Maybe the phone thinks its on a newer version when it isn't, and thus it thinks it doesn't need an OTA?
[HTC One X] hokoonho:
Try unlock and reinstall the custom recovery, then wipe everything, erase any thing in the SD as well, then go over the steps again, it is most likely due to some part of the newer system are left somewhere in your phone.
[HTC One X] hokoonho:
Have you wipe your SD as well?
[HTC One X] billd2439:
Working link to RUU

Has any one got a working link to the RUU.(the link on page 1 is broken):crying:
[HTC One X] DeeZZ_NuuZZ:
i need it too :(
[HTC One X] Rhadamanthis:
http://kuai.xunlei.com/d/EEBCUIKHYXTG
[HTC One X] Kespa76:
I'm on hboot 1.31, i installed 1.29 rom with the customRUU method. All works fine but when i do the 2.17 update, i have freeze and boot loop on the sim screen (after the installation of 2.17)

When i do fastboot getvar all, it display me main version : 3.14... I don't understand. I have wiped my sdcard and factory reset..

I need help
[HTC One X] khro1:
i can't unzip original rom.zip

winrar, winzip, universal extractor - gives error with archive

help please....

upd: with old (2.17) rom.zip all ok.

jb (3.14) problem.
[HTC One X] Feepitee:
Yeah, I erased everything, including SD card etc, still not OTA :(. Thanks though.
[HTC One X] leventccc:
I will sell my phone tomorrow. I returned to 2.17.401.2. My hboot is 1.31 and I relocked my bootloader. My device is unbranded and cid is HTC_102. I hope the phone is updatable without unlocking because I don't want any trouble with the buyer. Do I have to do anything more without selling to make sure its updatable. system boot and recovery partitions are %100 untampered 2.17.401.2.
[HTC One X] eXceed:
Thanks for the guide, was smashing my head against the wall trying to get this to work beforehand!
[HTC One X] meletios:
Thanks OP....was able to 1.29.* on 2.17.*...was then able to upgrade to 2.17.* again then....

Very good ...
[HTC One X] nihal.shaikh:
wow! its work....

Great Workkkkkkkkk...... Its too simple only a difficulty comes to me to extract(step 4) from Rom.zip of RUU, and its work with winrar (as not works with winzip).
[HTC One X] hokoonho:
I am not sure it works 100% perfect with higher HBoot, what should work is upto 2.17. someone with cid HTC__001 may try with jb.
[HTC One X] lukems:
Been trying out a few ROMs and decided to go back to stock again.

Followed this guide again and worked perfectly, stock rom, stock recovery, relocked bootloader, and received my latest OTA.
[HTC One X] majkyke:
It works well Hboot 1.31:D

Thanks :cowboy:
[HTC One X] [★]:
Please can you reupload the Custom RUU the link is down again :)
[HTC One X] billd2439:
download

Hi Folks,

Not my file but I am aware the link keeps going down. I have put a copy in this dropbox folder,please feel free to use it.

http://db.tt/z8ajRTuH

Please feel free to hit the Thanks button !!
[HTC One X] hokoonho:
Thank You for your file, I am just too busy in this month...

I have a open day for my school... which is a BIG event. Just keep working every single minute. telling my students to do this and that.... drama, music performance...

I will post your link to the OP and all others please give a thanks to billd2439 :good:
[HTC One X] [★]:
Firstly cheers for the mirror man!

Second, I received an error in the middle of the process [152] I think. So I pressed recovery and now I have error recovery [0]

:(

And now my phone is bricked with the htc grey writing, wonderful.
[HTC One X] ClydeB1:
Can you boot to bootloader? Press power button for about 10 seconds to switch off and then try to boot to bootloader. Then see if device is still recognised by pc.
[HTC One X] [★]:
I can power off but then instead of going into bootloader, the phone just comes back to the same black screen. But yes the phone is still recognized by my pc and can take fastboot commands
[HTC One X] ClydeB1:
Well then the good news is it can't be bricked. Enter command fastboot reboot-bootloader which should hopefully boot you into bootloader mode.
[HTC One X] [★]:
I've tried that but had no luck, it just boots back into the same screen :(

---------- Post added at 08:19 PM ---------- Previous post was at 08:01 PM ----------

If I relocked the bootloader through fasboot then reflashed the 1.28 Firmware, do you think I would be able to get back into bootloader?
[HTC One X] ClydeB1:
Have you tried rerunning all steps? IIRC Error 152 is normally a sign that you haven't locked your bootlaoder.
[HTC One X] [★]:
I haven't, the guide did not say anything about locking the bootloader?
[HTC One X] [★]:
Are you supposed to relock the bootloader at some point?
[HTC One X] ClydeB1:
Sorry, I haven't tried this method, but I see that according to the instructions you need to keep it unlocked. Step 11 seems to possibly be where you may have gone wrong as it mentions the ruu errors there.
[HTC One X] [★]:
The thing is it was already unlocked :( I have no idea how to get out of this screen
[HTC One X] ClydeB1:
Which is fine as the instructions say to leave it unlocked. Try doing a full reboot by holding volume up + volume down + power button all together for a few seconds until the device reboots.

If the fastboot commands are still recognised in that screen, then you can try rerunning them.
[HTC One X] [★]:
I've tried running them three times with no success, still getting Error [512]. The error always occurs on the 'flushing' part of the process. Implying that maybe the memory is damaged? (which were my suspicions before about this phone)

---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------

If I use the commands:

erase <partition> [ <filename> ]

To erase all the partitions - essential manually flushing the device (if my idea of what flushing means is correct haha)

followed by

flashall

with the boot, recovery and system in the fastboot folder

Might I rebuild the phone back to basics?
[HTC One X] ClydeB1:
I'm not sure of that tbh
[HTC One X] [★]:
Anyone else know what to do?
[HTC One X] kakanjac:
Probably, I'm stupid.

Can someone post a video how to do all these steps, because I don't know how to unzip the files, I can only extract rom zip, and than take the files(copy), and how to zip these 3 files... Sorry
[HTC One X] hokoonho:
May I know what is your CID? And the text in the android-info.txt.

Also the file name of the rom you ate using.

And if you can, please goto fastboot and get the current version of your One X.

I will try to figure out the problem.
[HTC One X] VerRer1:
"17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img""

Got to this stage, how do I flash the recovery_signed.img?

When I try I'm getting this - error: cannot load 'recover_signed.img': Unknown error

Is there a specific folder the .img file needs to go into, or do I need to modify the command? Thanks

---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------

Don't worry, realised I failed the IQ test. I copied the command word for word from the guide - including the missing "y" from recovery on the file name. Derp. :)

---------- Post added at 10:39 AM ---------- Previous post was at 10:31 AM ----------

Also if anyone else runs into a failed relock attempt when trying the command:

c:> fastboot oem lock

It isn't an issue. have a read of this:

http://xdaforums.com/showthread.php?t=1655832

:good:
[HTC One X] Karolix21:
Hi.I'd like to ask,i followed every step with major care....my phone had cwm recovery installed and 2.17 orange rom before starting....i downloaded orange UK 1.29.061.11 rom and after running ARUwizard i am at sending for about 30 mins now...I am trying to revert it back to stock to get OTA's up to hboot 314 so i can go custom roms again....

Boot loader is unlocked and rom.zip theoretically compliled correctly ...
[HTC One X] ClydeB1:
If you want to flash a custom JB rom, you only need to update the hboot. Use this firmware.zip file and then:

1. Relock bootloader - fastboot oem lock

2. Boot to ruu mode - fastboot oem rebootRUU

3. Flash firmware - fastboot flash zip firmware.zip (if you get an error, rerun this command)

4. Unlock bootloader - fastboot flash unlocktoken Unlock_code.bin

5. Flash custom recovery - fastboot flash recovery nameofrecoveryfile.img

Then flash boot.img from your rom of choice and then flash rom.zip via Recovery. Please take a backup of all important files on device as well as on sd card as phone memory will be wiped and for some users their sd cards were wiped as well.
[HTC One X] pericleszone:
Downgrade to install offical UK Orange JB OTA

Thanks, this Custom RUU method worked for me. :)

I was unable to return my UK Orange to stock due to having installed a later custom rom (not JB) as my version-main: 2.17.61.3 was too high.

I downloaded 'RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed' however the update would not run on the custom rom I had installed (as expected).http://www.filefactory.com/file/6kxoz8s1fpdx/n/RUU_ENDEAVOR_U_ICS_40_Orange_UK_1.29.061.11_Radio_1.1204.105.14_release_260736_signed.exe However using this file I extracted the required .img files using the extract from RUU method to retrive the files fomr the temp directory. (and 7ZIP unpacked the rom.zip)

I then copied the files and followed instructions in this thread on page one of this guide (and after a long holding of breath) my ROM reverted to the Orange default and also the OTA worked. After three OTA updates I am now running JB :)

Also the guide here http://xdaforums.com/showthread.php?t=1859714 was very useful and http://xdaforums.com/showthread.php?t=1832891(Thanks ClydeB1)

I would also add that the One_X_All-In-One_Kit_v2.0 on http://xdaforums.com/showthread.php?t=1604439 was also very useful. (Thanks hasoon2000)
[HTC One X] SrebX:
Will it work for any CID and any hboot version?

I have some weird CID and low hboot version :| [v1.12], And I really want a stock Jelly bean... is that possible?
[HTC One X] Siriondel:
This method allowed me to go back to stock just fine, but it didn't allow me to do the OTA. I double checked everything and nothing, it was always saying that no update was available, even when I went back to 4.0.3 so there should be at least 4.0.4. My CID is T-MOB102, back from 2.17.112.3 to 1.26.112.3. Still a great guide though, now I've got a way back just in case. Many many thanks to the OP, to billd2439 and to ClydeB1 for directing me to this thread and for providing the right firmware package so I could upgrade to JB through firmware.zip :) You guys are awesome.
[HTC One X] mcmaxi:
Htc one x update 4.1.1 now

Now possible update HTC ONE X TIM_401 to 4.1.1 JB by OTA.

---------- Post added at 01:33 AM ---------- Previous post was at 01:19 AM ----------

RIPORTARE UN HTC ONE X BRAND TIM (TIM-401) COME QUANDO LO AVETE ACQUISTATO.

http://depositfiles.com/files/ygjw5i97i

- Scaricate il file che include fastboot e tutto il necessario dal link qui sopra.

- Create una cartella in C (nominatela come volete)

- Scompattate TIM_401 in quella cartella

- Copiate la cartella clockworkmod nella SD del telefono (se vi chiede dI sovrascrivere fatelo tranquillamente)

- Andate sul cellulare in modalità fastboot usb

- Entrate nella cartella da voi creata precedentemente da DOS.

Digitate:

1. fastboot erase cache

2. fastboot flash boot boot_signed.img

3. fastboot flash recovery recover_signed.img

A questo punto entrare in recovery sul telefono e andate su RESTORE per

ripristinare il telefono come in origine.

Scegliere il backup precedentemente copiato nella SD (2012-09-21.13.54.56)

Al termine tornare subito in fastboot usb e digitate:

fastboot oem lock

Il telefono si riavvierà e non appena imposterete una connessione wifi vi

chiederà di fare l'aggiornamento.

(Oggi 10 gennaio 2013 alle ore 1.06 ho fatto aggiornamento 4.1.1 e tutto funziona alla perfezione).

By Mcmaxi

---------- Post added at 01:42 AM ---------- Previous post was at 01:33 AM ----------

Probabilmente a qualcuno di voi è capitato di aver fatto per precauzione un backup tramite recovery feamod (il cosiddetto nandroid backup ) ma al momento del ripristino si è presentato un inconveniente: capitava infatti che venisse visualizzato un errore di “md5 mismatch”

Ora fortunatamente non dovrete più cestinare il backup come danneggiato ma basterà seguire questa guida (per utenti esperti) per poter Fixare il problema:

Prima di tutto create una cartella (se non fosse già creata) clockworkmod /backup/2011-12-16.12.56.43 NELLA SDCARD INTERNA (NON MICROSD) (ovviamente data e ora del backup possono variare)

Aprite Terminal Emulator (se non lo avete scaricatelo dal market -> Terminal Emulator

digitate

codice:

su

#cd / sdcard/ clockworkmod /backup/2011-12-16.12.56.43

#rm nandroid .md5 (se vi da errore "failed for nandroid. read-only file system" andate avanti)

#md5sum *img > nandroid.md5

Riavviate in recovery mode

Ripristinate il backup dalla memoria interna.

(TROVATO IN RETE, TESTATO E FUNZIONANTE)

Mcmaxi
[HTC One X] SrebX:
Anyone?
[HTC One X] clarkg:
Thanks a lot! Worked for me restoring 1.29.781.14 back to 1.26.781.2

You saved me paying Telecom NZ $85 to reflash my phone and being without it for however long it would have taken them. You rock!
[HTC One X] hokoonho:
In theory, Yes. because you have to extract the rom.zip from the RUU for your CID.

The CustomRUU is only a windows program which help you to flash the rom.zip to your One X, it came from original HTC RUU.

However, someone report that they were unable to see any OTA after restore using this method. In this case, you can still back to any custom rom.

make sure you have skills to flash things via fastboot, and make sure you have read all the steps and understand every steps before you do anything.
[HTC One X] mcmaxi:
Well!! I'm happy for you!! :)
[HTC One X] sadpwner:
People say the ruus are encrypted now. I can't extract the rom.zip
[HTC One X] mcmaxi:
Encrypted?

No, it's free and not encrypted file zip.
[HTC One X] H377:
The ROM.ZIP from the RUU are not a valid ZIP file. So it really seems to be encrypted.... :(
[HTC One X] stalvatero:
Hi all.

My HOX has 3.18 version with HBOOT 1.39. I have installe ViperX but i want to revert to all to stock. But tryng to launch the last WWE RUU, it ends with errors. Following this guide can help me to revert to stock 3.14?

Thx
[HTC One X] Viridis:
Anyone able to re-upload the custom RUU please?
[HTC One X] zumyman46:
The same problem.

Did u managed to revert to stock? i cant. extract the rom.zip, seems to be a problem.
[HTC One X] ZiDanRO:
It is an interestesting method to downgrade and I need to know if anybody tryed to downgrade the touch panel driver this way.

In RUU's for 401 zone you can find TP.img even in the older versions like 3.14, not only 3.18

If anybody had tried this, it will be nice to know if it is possible.
[HTC One X] stalvatero:
R: [Guide] Return stock without latest RUU

Unfortunately not. But i haven't tried this method yet.

Inviato dal mio HTC One X con Tapatalk 2