Hi. I wanted to go back to stock. So according to some link I referred to:
I typed in cmd
fastboot getvar version-main to know my version. It showed 1.29.401.11
My hboot is 1.39.
I downloaded the RUU: ruu_endeavor_u_jb_45_s_htc_europe_3.14.401.27_radio_5.1204.162.29_release_298897_signed
However, when I ran the RUU, it says the update could not be done "Error: 155"
I don't know what went wrong. Urgent help needed guys. My phone is still stuck on the black screen with htc logo in the middle. And if I run out of battery, it's going to be a big problem.
Please check this fastboot command:
fastboot getvar cid
And let me know what you will get back.
Issue Resolved
Hello all,
The issue has been resolved now. I was trying to run the 3.14.401.27 RUU, but it wasn't working. When I ran the 3.14.401.31 RUU, it worked.
It was pointed out to me by Mr. Hofs that the .27 RUU is for 1.36 HBOOT and the .31 RUU is for 1.39 HBOOT.
Thank you so much, Mr. Hofs, for pointing this out to me.:good:
Related
I had ota 1.26.401.2 on my phone prior to my phone messing up and then not recovering. Ran two different RUUs, one that was a downgrade image and the other was the same image that was on my phone (1.26.401.2). Both failed with an error 140: bootloader version error. Then I downloaded and ran a newer image through RUU (1.28.401.9), and it successfully flashed to my phone.
Now I have an updated hboot which actually pisses me off because if someone finds an exploit in a prior version and there's not any way to downgrade hboot, then I'm effed. I know I shouldn't be crossing my fingers anyway for s-off, but like to think that there's a good chance. Why did RUU give me those errors?
Sent from my HTC One X using Tapatalk 2
UnlockedNand said:
I had ota 1.26.401.2 on my phone prior to my phone messing up and then not recovering. Ran two different RUUs, one that was a downgrade image and the other was the same image that was on my phone (1.26.401.2). Both failed with an error 140: bootloader version error. Then I downloaded and ran a newer image through RUU (1.28.401.9), and it successfully flashed to my phone.
Now I have an updated hboot which actually pisses me off because if someone finds an exploit in a prior version and there's not any way to downgrade hboot, then I'm effed. I know I shouldn't be crossing my fingers anyway for s-off, but like to think that there's a good chance. Why did RUU give me those errors?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
The error indicates that the bootloader on the phone is a newer version than the one in the RUU being flashed. That explains why the downgrade image failed, but you shouldn't be getting that when flashing the same version as is on the phone. Although you say you originally had "ota 1.26.401.2"; that version was the shipped software version not an OTA upgrade. The first OTA released was 1.28.401.9, so if you had installed an OTA since getting the phone it would have actually been 1.28, which would explain the 1.26 RUU failing as well. Other than that there's no reason I can think of for that to happen.
Exactly as stated, without S-OFF you can't go down an HBOOT version - you can only match or increase it
Yeah I had the factory shipped software 1.26.401.2. Never installed an ota update, so I'm confused why 1.26.401.2 ruu failed giving me error 140. Kind of sucks, whatever I'll get over it.
Sent from my HTC One X using Tapatalk 2
Give me the link for 1.28.401.9 I need it man please, my phone is broken so please
unlockednand said:
i had ota 1.26.401.2 on my phone prior to my phone messing up and then not recovering. Ran two different ruus, one that was a downgrade image and the other was the same image that was on my phone (1.26.401.2). Both failed with an error 140: Bootloader version error. Then i downloaded and ran a newer image through ruu (1.28.401.9), and it successfully flashed to my phone.
Now i have an updated hboot which actually pisses me off because if someone finds an exploit in a prior version and there's not any way to downgrade hboot, then i'm effed. I know i shouldn't be crossing my fingers anyway for s-off, but like to think that there's a good chance. Why did ruu give me those errors?
Sent from my htc one x using tapatalk 2
Click to expand...
Click to collapse
help help help help
TiborKusic said:
help help help help
Click to expand...
Click to collapse
The same problem
Back up your ROM. Then ensure the device is locked:
fastboot oem lock
Run:
fastboot getvar version-main
To check you have a '401 device and then flash either the 2.17.401 RUU or the 3.14.401 RUU (if you want Jelly Bean).
The hboot I'll be updated, but we're not getting S-Off, and really, there's no need for it.
Same problem with my HTC One X
BenPope said:
Back up your ROM. Then ensure the device is locked:
fastboot oem lock
Run:
fastboot getvar version-main
To check you have a '401 device and then flash either the 2.17.401 RUU or the 3.14.401 RUU (if you want Jelly Bean).
The hboot I'll be updated, but we're not getting S-Off, and really, there's no need for it.
Click to expand...
Click to collapse
I am having the same problem with my HTC One X when trying to run RUU. I have tried 3 different RUU's for my Optus HTC One X (CID Optus001),
RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.26.980.3_Radio_1.1204.90.13_release_251942_signed,
RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.28.980.10_Radio_1.1204.103.14_release_258004_signed,
RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.29.980.11_Radio_1.1204.105.14_release_260560_signed.
I bricked my phone and I have no ROM because it broke when I was messing around with backups, recoveries, etc... If I start the phone normally it stops at HTC Quietly Brilliant.
I can flash a recovery at any time, but I have tried multiple CWM Recoveries to try to mount USB Storage so I can install a ROM but USB storage would not successfully mount, it would just say sdcard0 shared-unmounted.
I have flashed the stock recovery.img and relocked the bootloader, then tried to install those 3 RUU's with no luck.
Bootloader reads:
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disbaled
CPU-bootmode : disabled
HW Secure boot: enabled
MODEM PATH : OFF
Nov 16 2012, 18:32:39
I ran 'fastboot getvar version-main' and it came back with
version-main: 3.14.980.27
finished. total time: 0.009s
Any help at all would be much appreciated as I need my phone working again ASAP.
Thank you.
Stop spamming stuff in other threads while you have your own ! It's so annoying
http://forum.xda-developers.com/showthread.php?t=2658434
People waste their time here while you get your answers there !
Use this info for future reference.
Sent from my HTC One X using XDA Premium 4 mobile app
I want to return my phone back to stock and I have downloaded the following RUU however when I run it, it says that i have the incorrect version.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
My Cid is HTC__001 and im on hboot 1.36 and bootloader has been relocked. Could someone please advise what to do? Thanks.
Type this in fastboot:
Code:
fastboot getvar version-main
Post result here.
It's ok now. Run RUU as Administrator and it went straight though. Thanks
Thread Closed​
Solved​
Hi
I've a problem i need to flash a RUU to send back my HOX to HTC so i run "fastboot getvar version-main" and i get 3.14.401.619 i chose
this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
but when i run it it never end so i unplug the usb cable after one hour and it's like nothing happen my HBoot is 1.31 my CID HTC_203
Can someone help on how to flash the right ruu
(ps: i didn't forgot to relock the bootloader)
What's your Cid ?
Fastboot oem readcid
Maybe its a branded ruu you need ?
And did u run the ruu with admin rights from pc
My CID is HTC_203 and yes i run it as admin
don't know what to do :s
Try to do it again, battery has enough power ?
Usb 2.0 port, not a Usb 3.0 port in use. Have seen problems using a 3.0 USB port !
Using the charger cable (original one)
Solved by flashing the last RUU
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
thanks
:thumbup: enjoy
I also have a problem, after I run the ruu it says signature error.
CID: HTC__102
version-main: 3.14.401.27
HBOOT 1.36.0000
What am I doing wrong?
Did u try the ruu that I posted about 2 post earlier ?
Solved
Mr Hofs said:
Did u try the ruu that I posted about 2 post earlier ?
Click to expand...
Click to collapse
Well, I'll be damned, that one worked. Thanks!
I still don't understand why the newer one didn't though.
In some cases a second time will work don't know why ! ... Glad it worked :thumbup:
2 successes in one evening ! You guys made my day
Cases are closed !!!
If I really really want to do a super duper factory reset. What should I do? I'm on ARHD 18.2 and hboot 1.39. 3.14.401.31 5.1204.162.29
Back to basic as far as i can...
I have issues with my wifi, I have to restart the wifi after awhile. My screen behave strange and in non responsive from time to time. The battery drains in like 8 hours, earlier it was ok for like 36 hours, that was i think when I used hboot 1.31. All this errors appeared when I went for hboot 1.39 I think.
I understand that downgrading hboot is not possible. But everything else?!?
Thanks for assisting.
Run a RUU for a super duper factory reset ruu.androidfiles.org
I guess you need to do the fastboot command
Fastboot getvar version-main
I think that the main version posted by henrik is from the custom rom that is based on 3.14.401.....
RUU failed.
Shoud I do anything pre RUU?
Fastboot something? Relock?
Yes the bootloader needs to be relocked. And you have to run the ruu with administrator rights. And keep the phone in the bootloader/fastboot usb mode
Are you sure you got the right ruu. Did you do
Fastboot getvar version-main
And did it came up with the same number you posted in the first post ?
Mr Hofs said:
Yes the bootloader needs to be relocked. And you have to run the ruu with administrator rights. And keep the phone in the bootloader/fastboot usb mode
Are you sure you got the right ruu. Did you do
Fastboot getvar version-main
And did it came up with the same number you posted in the first post ?
Click to expand...
Click to collapse
Yes same number.
When i lock it it will only boot to bootloader. To run RUU I need to get in to the phone.
Should I do anyting else in fastboot?
Regards
/Henrik
You can run the ruu in fastboot mode too.
Yeah like i said in my previous post
Thanks allot, now i'm back to scratch. The issues with the touchpanel is still there, the top part is not consistent sometime it works and sometime it doesn't. We will see if the batterylife is better.
Thanks again.
/Henrik
No problem mate, i hope it Works out fine for you in the end :thumbup:
CASE CLOSED !
Hi guys.Im new to HTC one X.I just bought an HTC one X from e-bay and it came pre rooted thought the phone looks brandnew.I tried to insert a sim and my phone keeps on showing an error saying process.com.android.phone is stopped and it does not show any signal bars.After several reboots sometimes signal bars do appear sometimes.But i am unable to make or recieve calls as my phone app keeps on force closing. My phone has stock ICS.
So if i flash a stock RUU will the problem be solved or is there anything that i can do to make my phone work?thank you.
I would recommend flashing a stock RUU.
You would need to check your CID and whether your bootloader is locked or unlocked. To do this, you can hold power+volume up down buttons to reboot phone to bootloader and see the first line.
The RUU you flash must match your CID.
Recommended for you:
RUUs: http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
About CID and other info: http://forum.xda-developers.com/showthread.php?t=2031359
Power button + volume down button (not up)
And post the outcome of this fastboot command
Fastboot getvar version-main
Tony Tan said:
I would recommend flashing a stock RUU.
You would need to check your CID and whether your bootloader is locked or unlocked. To do this, you can hold power+volume up down buttons to reboot phone to bootloader and see the first line.
The RUU you flash must match your CID.
Recommended for you:
RUUs: http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
About CID and other info: http://forum.xda-developers.com/showthread.php?t=2031359
Click to expand...
Click to collapse
Thanks for the help(i hit the thanks button too
one more question.Mine has got super CID.
So what RUU should i flash?
You mean Super CID 11111111?
Did you check with:
fastboot getvar cid
fastboot oem readcid
If my understanding is correct, you should be able to flash any RUU with any CID in that case.
Just make sure the RUU you are flashing is for your device model (HTC One X Endeavor, not HTC One XL or anything else)
I have never owned a supercid device though, so you might want to confirm with someone else.
For RUU downloads:
http://forum.xda-developers.com/showthread.php?t=2094113
http://forum.xda-developers.com/showthread.php?t=2189048
Credits to Mr Hofs for helping me find the links.
nuwanmw1988 said:
Thanks for the help(i hit the thanks button too
one more question.Mine has got super CID.
So what RUU should i flash?
Click to expand...
Click to collapse
Tony Tan said:
You mean Super CID 111111111?
Did you check with:
fastboot getvar cid
fastboot oem readcid
If my understanding is correct, you should be able to flash any RUU with any CID in that case.
Just make sure the RUU you are flashing is for your device model (HTC One X Endeavor, not HTC One XL or anything else)
I have never owned a supercid device though, so you might want to confirm with someone else.
For RUU downloads:
http://forum.xda-developers.com/showthread.php?t=2094113
http://forum.xda-developers.com/showthread.php?t=2189048
Credits to Mr Hofs for helping me find the links.
Click to expand...
Click to collapse
yup..its 11111111
Then you can flash any ruu basically !
Thanx guys..my phone is back to life now.
Sent from my HTC One X using xda premium