Related
Hi, everyone.
Got a Desire 2.1 update-1 branded by Orange ES. Hboot is 0.83. Dunno if it's SLCD or OLED, does it matter anyway?
Used unrevoked to successfully root and installed a custom recovery (unrevoked standard). Right after this the phone wouldn't go past the HTC logo but I could still get recovery screen. I tried a recovery but it didn't work either. From there I tried installing RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe (which is the one I want to upgrade from to stock Froyo2.2) but I got a problem in the middle of the installation ( installer says I needed to use the proper file for my phone). Then I used the recovery screen to install a custom ROM, AuraxTSense Froyo and that worked (have it on right now) but from this ROM the RUU WWE installer doesn't work either.
Any suggestions?
You'll need a gold card to use the stock RUU file - otherwise your phone doesn't pass the CID check because it's branded...
driveboy said:
Hi, everyone.
Got a Desire 2.1 update-1 branded by Orange ES. Hboot is 0.83. Dunno if it's SLCD or OLED, does it matter anyway?
Used unrevoked to successfully root and installed a custom recovery (unrevoked standard). Right after this the phone wouldn't go past the HTC logo but I could still get recovery screen. I tried a recovery but it didn't work either. From there I tried installing RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe (which is the one I want to upgrade from to stock Froyo2.2) but I got a problem in the middle of the installation ( installer says I needed to use the proper file for my phone). Then I used the recovery screen to install a custom ROM, AuraxTSense Froyo and that worked (have it on right now) but from this ROM the RUU WWE installer doesn't work either.
Any suggestions?
Click to expand...
Click to collapse
The Error code the installer gives me is "131" if that helps. On the phone it shows "CID error, cannot continue". Any ideas what does this mean? Help? Please?
Read my last post...
EddyOS said:
...otherwise your phone doesn't pass the CID check because it's branded...
Click to expand...
Click to collapse
can i flash my =ROOTED- Desire using stock RUU WWE? i already have a gold card...
If you want, it'll remove root though
EddyOS said:
If you want, it'll remove root though
Click to expand...
Click to collapse
now i know.. after flashing to stock RUU WWE, can i still use the unrevoke technique you taught me?
i did flash my phone using stock RUU WWE Europe (as far as i can remember) and thinking to flash WWE Asia... i cant get 3G/GPRS/MMS settings in my carrier.. im thinking if flashing WWE Asia ROM could solve the problem...
Quite possibly yes, and yes you can re-root with unrEVOked once done
thanks again EddyOS ill flash right away
Ok, so now I did a goldcard and the process seems to go a bit further but it stops. It says "Error 104, wrong hboot version - please install the correct version for your mobile phone". Any answers?
to pass the CID check, try this: htcpedia.com/forum/showthread.php?t=2934
driveboy said:
Ok, so now I did a goldcard and the process seems to go a bit further but it stops. It says "Error 104, wrong hboot version - please install the correct version for your mobile phone". Any answers?
Click to expand...
Click to collapse
That now means the HBOOT version you have is newer than the one in the ROM you're trying to flash...What ROM are you trying to flash?
EDIT: If it's still the one in your OP then chances are you'll need the stock 2.10.405.2 RUU to get the generic ROM on the handset. You can get it by clicking on the version on my signature
i found it it working for me my htc is back to life
Link plz...
asifpm said:
Link plz...
Click to expand...
Click to collapse
Here you go:
rogersnm said:
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
MD5 Checksum: 347335388666a64f35b894c5baafd727
SHA1 Checksum: 2749ef0de5e518dcc4031602eb602ebc085514e6
File Size: 573.4 MB
Code:
hoxroms.serveftp.com/RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed.exe
Click to expand...
Click to collapse
This won't work on a branded 02 device right?
Sent from my HTC One X using Tapatalk 2
BigladUK said:
This won't work on a branded 02 device right?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
if your firmware version has 401 included then it will.
eg: 1.xx.401.x
Haba1205 said:
if your firmware version has 401 included then it will.
eg: 1.xx.401.x
Click to expand...
Click to collapse
Rubbish :-( mine is 1.26.206.2
Si
BigladUK said:
Rubbish :-( mine is 1.26.206.2
Si
Click to expand...
Click to collapse
hey buddy now i am on 1.28 but did not update through the ota but just by flashing custom rom..if i was to flash this baby over my custom rom and did full wipe first would that work?
apologies if this sounds stupid..still learning you see
i will but u need first relock your bootloader then instal ruu
Thank you
thank you for starting this thread. This helped me update to 1.28
Flashing RUU 1.28 over existing
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
briken.one said:
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
Click to expand...
Click to collapse
You need the flash the stock recovery, relock the bootloader and then run the RUU. That will return you to stock firmware.
briken.one said:
Hey guys, I am already running ruu 1.28 but I want to install it again over the existing system so I can start fresh. I tried flashing the img from the bootloader and via fastboot but nothing changes. I am running unlocked and rooted.
thanks for you help, i think im missing something really simple but im getting frustrated.
Click to expand...
Click to collapse
No need to flash anything, just re-lock your device and run the RUU.exe.
I am trying to put my phone back to vodafone stock ROM,
phones with hboot 0.94.000?
its vodafone UK phone, I am trying to flash 1.26 RUU as there is not 1.28 RUU for vodafone uk yet, but it keeps giving error 140 bootload version error.
and everytime i relock my bootloader i get
RELOCKED
SYSTEM WARNING
after above phone keeps going back in to boot loader and the way it comes out and goes back to old ROM is by unlocking the boot loader again.
can any one help?
thanks
rohitbaba said:
I am trying to put my phone back to vodafone stock ROM,
phones with hboot 0.94.000?
its vodafone UK phone, I am trying to flash 1.26 RUU as there is not 1.28 RUU for vodafone uk yet, but it keeps giving error 140 bootload version error.
and everytime i relock my bootloader i get
RELOCKED
SYSTEM WARNING
after above phone keeps going back in to boot loader and the way it comes out and goes back to old ROM is by unlocking the boot loader again.
can any one help?
thanks
Click to expand...
Click to collapse
hboot 0.94 comes with 1.28, this means you won't be able to run a 1.26 RUU - you can only run 1.28 RUUs or newer. If you can't get the 1.28 RUU for your CID you won't be able to run a RUU. You can still flash custom ROMs though, so if your phone is bootlooping that's your way out.
rogersnm said:
hboot 0.94 comes with 1.28, this means you won't be able to run a 1.26 RUU - you can only run 1.28 RUUs or newer. If you can't get the 1.28 RUU for your CID you won't be able to run a RUU. You can still flash custom ROMs though, so if your phone is bootlooping that's your way out.
Click to expand...
Click to collapse
I need to send my phone back to Vodafone for repair so i need to find a way to restore Vodafone ROM on the phone.
is there any other way i can get Voda rom back on the phone, also should the security warning be on the boot loader.
thanks
Dev
rohitbaba said:
I need to send my phone back to Vodafone for repair so i need to find a way to restore Vodafone ROM on the phone.
is there any other way i can get Voda rom back on the phone, also should the security warning be on the boot loader.
thanks
Dev
Click to expand...
Click to collapse
Are you on vodafone UK? The 1.28 RUU is available for that carrier.
Even after relocking the bootloader and running a RUU, it's impossible (without S-OFF) to remove any trace that you unlocked it. The repair centre will still be able to tell.
rogersnm said:
Are you on vodafone UK? The 1.28 RUU is available for that carrier.
Even after relocking the bootloader and running a RUU, it's impossible (without S-OFF) to remove any trace that you unlocked it. The repair centre will still be able to tell.
Click to expand...
Click to collapse
1.28 RUU is is only OTA not full unless there is one.
if there is can you forward me the link
thanks
rohitbaba said:
1.28 RUU is is only OTA not full unless there is one.
if there is can you forward me the link
thanks
Click to expand...
Click to collapse
It's in my sig
http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_256488_signed.exe
rogersnm said:
It's in my sig
http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_256488_signed.exe
Click to expand...
Click to collapse
thanks for the link, so from what you have told me there is no way put the phone back to how it came from vodafone.
thanks
Dev
rohitbaba said:
thanks for the link, so from what you have told me there is no way put the phone back to how it came from vodafone.
thanks
Dev
Click to expand...
Click to collapse
Essentially no. Once you unlock it, even if you relock it it won't be exactly the same. The bootloader will remember that it was previously unlocked and repair centres will be able to see it. That said, restoring the RUU is better than nothing, but from what I've heard the repair centres like to bill you for a motherboard replacement if you unlock your device.
UK law does give you a large degree of protection if you wanted to take it to court though (assuming you're returning it due to a fault that was not caused by unlocking the device)
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...
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
I have an HTC One M9 that up until yesterday had an unlocked bootloader and had S-Off.
It was running a pretty old ROM so I decided to update it. My first attempt was Viper.
After installing through TWRP recovery it would only take me to the TWRP boot screen after rebooting.
I attempted another ROM, this time Revolution and got the same results.
I’ve been messing with it for hours and somehow I have S-ON and the bootloader is locked. Actually it says RELOCKED.
It has no OS and it will no longer go to Recovery mode. I think the TWRP I tried to install is too new for it.
I’ve performed the HTC bootloader unlock procedure a few times and although it says successful, after reboot, its still relocked.
Am I screwed, or is there something more I can try?
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Dark Stranger said:
If bootloader is looked, the only solution is to try to flasher the latest ruu according to the model of your M9. It goes into downloading mode??
Click to expand...
Click to collapse
Yes, it goes into download mode. I've tried the only Telus ruu I could find (RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe)
and I get a Error 131 Customer ID Error.
I just tried a Sprint ruu (RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe) and I got Error 155 Unknown Error. They both fail right after it displays Updating Signatures.
I'm in Canada and it's a Telus phone but it's carrier unlocked.
Do I need to use a Telus RUU or should any Canadian RUU work on it?
are you sure yours already s-off?
1. re flash lastest TWRP
2. flash required lastest firmware (s-off)
Firmware 3.35.401.12 is required for proper installation! Download (S-OFF ONLY)
3. flash your fav lastest custom rom
Yes, it's definitely S-On.
Any Canadians out there? After some reading I realize I need an RUU of a specific sku. In my case 661.
I need a Telus RUU of 2.11.661.5 or higher for the M9. I'm hoping that will resolve my issue.