HI, my Cid its HTC__044 wwe sea asia.. ive downloades the endeavor ruu both oh them, and also the wwe asia, and in all the cases cames an error in the updated, diferent vendor or wathever...
Ive relocked the boot and the original recovery but nothing happs..
soo how could i go back to my stock ROM
HTC ONE X 32
CID HTC__044
THanks
Which specific ones did you try, what specifically was the error and what did you expect to happen?
I think you need the 2.17.707.x RUU, and before running it you need to lock the bootloader with:
fastboot oem lock
BenPope said:
Which specific ones did you try, what specifically was the error and what did you expect to happen?
I think you need the 2.17.707.x RUU, and before running it you need to lock the bootloader with:
fastboot oem lock
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.2_Radio_1.1204.90.13_release_251281_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed
ive tried those 4, with bootloader locked and on original recovery
if you try "fastboot getvar version-main" instead of "fastboot getvar cid" you will be given the number of the ruu you need.
For example, if it is the SEA_WWE version the number will be"1.29.728.12", but by the sounds of it, it isn't.
Let us know what result you get for it.
You need this file... "RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed"
Mine is the same _044 and it works.
Not neccesarily... I have CID _044 but need this RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
It's important to run the "fastboot getvar version-main" command.
peedub said:
Not neccesarily... I have CID _044 but need this RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
It's important to run the "fastboot getvar version-main" command.
Click to expand...
Click to collapse
Also, at least I think, is important - go in fastboot menu with your phone, then connect via usb and then start ruu.
I had same as yours CID - 044 and "Asia_WWE_2.17.707.3"worked perfectly.
Hope this helps.
Regards.
lets see if it works and soon i will post some news
u can run any ruu with 707 cod in that.
707 for htc__044 cid.its for asia sea wwe version.
becareful your phone has uper than 30% battry charge,beacus when you relock your hboot,its erase all recovery and you cant charge your device.so just you can run ruu,if you havent 30% charge it give an eror for battry charge and not install ruu.
Sent from my HTC One X using Tapatalk 2
shadow fiend said:
u can run any ruu with 707 cod in that.
Click to expand...
Click to collapse
I don't wish to be rude, but if you don't know what you're talking about, it's best not to add to the confusion.
In order to flash an RUU, you need to flash the hboot in the RUU, and the hboot cannot be downgraded. The hboot version is almost always increased for a new RUU. So, you can only flash the same or newer RUU.
I gave the solution in the post immediately following the original question.
mmm its not working, can get the stock ruu back on..
same error.. and in soma exe packages i cant even run it getting some error opening it.
tried in different pcs.. same deal
jachig said:
mmm its not working, can get the stock ruu back on..
same error.. and in soma exe packages i cant even run it getting some error opening it.
tried in different pcs.. same deal
Click to expand...
Click to collapse
If it's not working, then you'll have to fix it.
Due to some error, I say do it differently.
You know, in my first response to you I asked you to be more specific, you don't learn fast, we're not mind readers.
What is "it" that's not working? Flashing a specific RUU? Which one? Where you get it?
What error are you getting?
ERROR 155
Different Vendor
ERROR [280]
ERROR [294]
those errors, on
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.26.707.2_Radio_1.1204.90.13_release_251281_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed
WTF man?
Flash the 2.17.707 RUU like you've been told and tell is what happens.
Haha yes, this is getting a little frustrating.
You still haven't told us what result you get when you run this command: "fastboot getvar version-main"
fastbook getvar version-main gave me a: 2.17.707.3
so what do i have to do now?
well the error this time says... its in spanish but i will try to translated right
error 155: update error
the utility update of the rom could not update ur android phone
please obtain the correct rom and try it again.
jachig said:
well the error this time says... its in spanish but i will try to translated right
error 155: update error
the utility update of the rom could not update ur android phone
please obtain the correct rom and try it again.
Click to expand...
Click to collapse
fastboot oem lock
And run the RUU again.
This will delete all you data, so take a backup if you want.
Flash the 2.17.707.3 RUU and you'll be good to go
thats the one ive just used ¬¬
Related
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Gomezie said:
Hi Folks,
Having some serious issues with my HTC One X
Upon recieving the device I left it on stock for a couple days and then flashed to ARHD 5.2 by unlocking the bootloader via HTCDev and flashed the rom, allwas awesome.. I have now since seen that yellow tea marks are appearing on one side of the screen, so I would like to return the handset to a stock state so that I may return under warranty.
Here is what I did:
Relocked the boot loader
Flashed stock recovery
This resulted in a security error and the phone refused to boot into anything but the boot loader...
almost identical to this thread:
http://forum.xda-developers.com/showthread.php?t=1649737
I have now solved this boot issue by reflashing the latest custom recovery, and the phone now boots into a nandroid backup that I have restored of the stock ROM.
I have tried to use several RUU's and they all halt after the reboot into bootloader phase (where it erases user data, writes the rom and then does something with signatures)...and the handset itself just stays on a black screen with a HTC logo and there are no progress bars or indication of things happening.. until the RUU errors with 155 (unknown error)
After looking at several threads I have become stuck and would really appreciate some advice
Here are the current details of my phone:
Sim free UK handset
HBOOT-0.94.0000
Radio-1.1204.104.14
CID - I have tried to gather this via fastboot, but it comes up as NONE
(also tried getprop ro.cid via the adb shell but this just errors)
Not sure if it makes any difference but I have also tried the HTC One X AIO Kit.. but any commands it sends error with indications that It cannot locate a device
Please please help
Click to expand...
Click to collapse
Please specify which RUU's you have tried
Hey thanks for your prompt reply, It is greatly appreciated.
Here are the RUU's i have tried:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed
RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.26.161.2_Radio_1.1204.90.13_release_251227_signed
Thanks
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
EddyOS said:
Where did you get the unit from originally? Was it branded?
This is why you should get the RUU BEFORE flahsing a new ROM
Click to expand...
Click to collapse
It was purchased from phones4u online.. the phone came unbranded, and is on a vodafone contract.
I am sorry about the RUU.. I wasnt aware it was something you had to acquire first..
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
EddyOS said:
You don't HAVE to get it first, it just means you don't have to panic about which one to use!!!
If it's unbranded then 1.29.401.7 or 1.29.401.11 will do the job (I'd go for .11)
Relock the bootloader and run the RUU when in fastboot and you should be good to go!
Click to expand...
Click to collapse
Thanks mate.. just waiting on the download slots and Ill grab it
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
EddyOS said:
Get it here, MUCH quicker
http://www.geeks0.com/downloads/mob...04.105.14_release_260491_signed_c9d22.exe.zip
RUU is in the ZIP file. No idea why it's been changed to lower case but it's the one I used and I maxed out my 8Mbps connection getting it
Click to expand...
Click to collapse
Spot on mate, I relocked the bootloader and the status reads "*** RELOCKED ***"
The RUU also ran perfectly, thanks for that
Would I just flash a stock recovery to restore the bootloader now? (so that it doesnt say RELOCKED)
I want to ensure that the phone is in the exact shape it needs to be before sending back.
Thanks again
It'll always say relocked - you can't do anything about that...
Ah thats a shame, should be a doorstep swap for a replacement handset anyways so thats probably no issue.
Thanks again mate, you have saved my bacon
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
wolfraim said:
-Run your RUU and wait for a complete load.
-go to windows>run and write: %temp%. Find a folder that contains a file called: rom.zip. Get the boot_signed.img and recovery_signed.img.
-flash boot_signed.img and recovery_signed.img.
-fastboot erase cache
-fastboot oem lock
-Do a factory reset with the new recovery.
-Now run your RUU and everything gonna be ok
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OP has already got it done, just asked if you could change the bootloader to say 'LOCKED' as it does out the box as opposed to 'RELOCKED'
RUU
So I have kind of a problem, I wanted to unlock my bootloader, only HTCDEV servers are a couples of days now overloaded.
So I can't get the unlock code bin.
I need to use my phone and it won't start normally because new firmare was flashed in RUU mode with JBWFTOOL.
So I want to flash a stock RUU. Only my main version is 3.14.401.41.
My phone was repaired by HTC and I got it back LOCKED and well.
Can I flash a other version RUU or do I have to wait for HTCDEV becoming normal again.
HOX E11 Europe.
H.BOOT 1.39
3.14.401.41
I am not doomed right?
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Mr Hofs said:
Are you sure.....you don't have 3.14.401.31 as a software number ?
Try this one
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
Put the phone in the bootloader/fastboot usb mode and right click the ruu.exe and select
Run as adminstrator
Click to expand...
Click to collapse
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
jelmer-p said:
Yeah I'm sure, it suprises my also I will try now!
EDIT: Oh no Im not wearing my eyecontacts XD It is 31! XD
Click to expand...
Click to collapse
Yeah i knew that, im on the same cid
Mr Hofs said:
Yeah i knew that, im on the same cid
Click to expand...
Click to collapse
YEAH it worked thanks!
jelmer-p said:
YEAH it worked thanks!
Click to expand...
Click to collapse
Top ! Have fun :thumbup:
So, my problem is, I currently have ARHD 9.7.2 installed. In bootloader it says I have HBOOT 0.94.0000 and radio version 1.1204.104.14.
I think the correct RUU is this: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_ 1.1204.104.14_release_259281_signed but I cant find it anywhere (well I found it, but download freezed because of bad mirror site). Can I use another RUU or what should I do? And if someone could post the correct steps for this reverting-to-stock procedure. First relock, then run RUU or what? Couldn't find a proper guide...
http://forum.xda-developers.com/showthread.php?t=1859714
a full guide a dont forget to hit the thanks button
Squbbe said:
So, my problem is, I currently have ARHD 9.7.2 installed. In bootloader it says I have HBOOT 0.94.0000 and radio version 1.1204.104.14.
I think the correct RUU is this: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_ 1.1204.104.14_release_259281_signed but I cant find it anywhere (well I found it, but download freezed because of bad mirror site). Can I use another RUU or what should I do? And if someone could post the correct steps for this reverting-to-stock procedure. First relock, then run RUU or what? Couldn't find a proper guide...
Click to expand...
Click to collapse
If you are sure the RUU that you need is 1.29.401.7, you can find it here at http://htcruu.com/?dir=Endeavor
But I recommend go for the latest version 2.17.401.2 because when you installed 1.29.401.7, the system will prompt you to OTA update to the latest.
So, just relock the bootloader in fastboot mode - fastboot oem lock
then again in fastboot mode, run the RUU
Thanks to both of you :laugh::good: I was a bit worried when relocking the bootloader I got a message from CMD: ... INFOLock successfully... FAILED (status read failed (Too many links)) but the RUU installed fine (fastboot said security warning under the relocked-message). I'm going to RMA my phone because of the backlight flickering and the bottom of the screen is getting loose from the body. One final question, do I now have the phone 100% ready for the RMA (I mean, is the software now fully stock)?
Yep... it is now 100% stock except the relocked status instead of originally locked. So it depends on your luck at HTC centre.
On my past experience with other htc phone, no problem for RMA.
Hi Guys,
It's the first time I post. Nice to meet you guys.
I bought a HTC oneX in Hong Kong 3 months before with relative cheap price around 435 US dollar. When I got OTA Android 4,1 I cannot install it because it said that my Android is modified. I didn't modify it by myself.
Anyone knows what happens and how to make is possible to upgrade again?
Thank you very much!
Cheers,:laugh:
George
Your rom is indeed modified (at the very least in build.prop, maybe more), so flash a RUU to return to completely stock rom. This will wipe everything, but it allows you to update. There are links to RUUs in the General section.
你的软件的确被改性了。最容易的方法来解决这个问题就是把Android完全擦除，以HTC的RUU方法来恢复到HTC未经修改的Android。这会把你所有的软件、资料等等消除掉，但会让你更新你的Android。你能在General的部分找到下载RUU的论坛主题。
还有：如果你要回复我的答案，请用英语来回复，因为论坛规则说我们必须用用别的语言得有英语的翻译。
That's not an official HK version (which would be '708).
This RUU will wipe your phone but hopefully fix the problem:
http://htcruu.com/securekey.php?fil...Radio_1.1204.105.14_release_261350_signed.exe
Thanks all!
I found that my HTC One X was was already rooted and unlocked when I bought it. It's strange
I got Error 120 at the beginning and I clear the cache in Hboot then it's fixed. Afterwards I got error 155 when running RUU.
Then I try the method in this following link:
http://forum.xda-developers.com/showthread.php?t=1609190
I tried to flash the rom directly but when I execute the code ''fastboot flash system system.img'' it failed.
Do you have any suggestions?
My god, I spent like 5 hours to read but still cannot fix it. Your commands save me lot of time!
Thank you very much!
Run:
fastboot getvar version-main
To check that was the right RUU.
To run the RUU you need to have a locked bootloader:
fastboot oem lock
BenPope said:
Run:
fastboot getvar version-main
To check that was the right RUU.
To run the RUU you need to have a locked bootloader:
fastboot oem lock
Click to expand...
Click to collapse
Hi Ben,
It's written 2.17.707.3. This is the latest version??
You could try this one
http://www.htcruu.com/securekey.php...Radio_5.1204.162.29_release_296434_signed.exe
Brings you straight to JB stock
Hi Mr. Hofs,
Thanks for your advice. I still encountered Error 155. I have relocked my OneX already.
If you saw the capture I posted my software version is modified, may be because of this reason I cannot flash my rom and run RUU.
Do you have other ideas?
Hmmm can you also give the command
Fastboot oem readcid
Mr Hofs said:
Hmmm can you also give the command
Fastboot oem readcid
Click to expand...
Click to collapse
HI Mr Hof,
CID: HTC__044
I don't understand what does it mean?
Thanks!
It means the RUU you tried (3.14.707.) Should work. I wonder if you need to update the firmware before flashing it.
Did you run the RUU with admin priviledges?
Sent from my EndeavorU using xda app-developers app
Hi Mr Hofs
It's working now! The problem is that I didn't run RUU in bootloader. I have to install stock rom 4.0.3 first and upgrade.
Many thanks to your advice! Finally I can fix this problem! Spend me much time
Cheers,
George
Good !
CASE CLOSED !
Hello, im new to flashing roms on htc and need to know will I brick my htc one x phone if I flash it with ruu a few times? Thanks
andrew21 said:
Hello, im new to flashing roms on htc and need to know will I brick my htc one x phone if I flash it with ruu a few times? Thanks
Click to expand...
Click to collapse
no but if you are doing it wrong then yes i right then not
Can you elaborate what you mean by doing it wrong, also just need to know which ruu region has Portuguese and Russian and French language in it? Thank you
If you know your cid, check the help forum, and use the correct ruu then you'll have no issues. The best thing to do is look through the forum for similar posts to understand, tbh
Sorry to bother u but how do I know CID of my phone and I don't think I'll brick my phone with wrong CID, the process will just abort and not brick the phone
i think you are best off to read first before trying anything else
http://forum.xda-developers.com/wiki/HTC_One_X
there you go
Still don't understand, wiki ruu link invalid....just need to know how to know CID and how do I know ruu is compatible with it? I plan to flash stock rom through pc
Use this app to find your cid https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter e.g. mine is O2_001, Download the appropriate ruu for your cid and run it.
You can also find your cid opening cmd on your PC and typing in fastboot usb mode: "fastboot oem readcid" and your firmware version: "fastboot getvar version-main".
Your ruu version has to match exactly.
You're on ICS or JB now? It's very difficult to find ruu for JB roms.
If you have doubts about flashing via ruu you can always flash with nandroid backup
Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.
alicine said:
Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.
Click to expand...
Click to collapse
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5
andybones said:
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5
Click to expand...
Click to collapse
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:
alicine said:
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:
Click to expand...
Click to collapse
Were sensors working before?
What did you change cid/mid to?
I would do supercid and change mid to match the RUU which is us locked, 2PS620000 iirc
Hopefully that will fix things up.
I also suggest flashing RUU using sdcard method, but fastboot works fine just make sure to use htc_fastboot not fastboot, for ruu
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Do a quick search though to confirm that's the mid u want that matches that Ruu.
Sorry I should have mentioned earlier.
When I take the phone first, was having sensor issues. I was thinking it's because of leedroid rom and sensors were driving crazy. Screen was closing itself, ice screen was appearing and back and other button blinking itself home button was not working etc. I barely acces to main screen
*#*#3424#*#* I couldn't diagnose hw so somehow I installed an app to see how sensors were behaving.
I couldn't read values so I thought that it's because of rom.
That's why as you said I change cid to supercid mid to 2PS620000.
After that I used sd card method from download mode and I installed the rom.
After the process I recieved the errors that I mentioned above
As final conclusion when mobile phone has leedroid rom, hw somehow damaged and was working strange because sensors.hub was there.
With clean installation sensor.hub didn't installed and hw is not working. And not behave strange.
It's my theory. I'm searching schematics for sensors to define where is exactly failure is.