[Q] [s3] RUU problem - HTC One S

Hi everyone,
I am trying to revert my phone to stock rom.
I dont know which RUU to flash and I have tried the Asian version. It didnt work and pop out error says I had the wrong version of RUU.
I am now stuck in the HBOOT. It seems the only solution is to find the correct version of RUU.
I have the following information on my phone:
HBOOT-2.09.0001
RADIO-16.05.20.16_M2
Hoping someone could give me some advice such that I could at least use my phone.
Billion thanks...

AYTIM said:
Hi everyone,
I am trying to revert my phone to stock rom.
I dont know which RUU to flash and I have tried the Asian version. It didnt work and pop out error says I had the wrong version of RUU.
I am now stuck in the HBOOT. It seems the only solution is to find the correct version of RUU.
I have the following information on my phone:
HBOOT-2.09.0001
RADIO-16.05.20.16_M2
Hoping someone could give me some advice such that I could at least use my phone.
Billion thanks...
Click to expand...
Click to collapse
use command: fastboot getvar cid --> u will get the CID of your phone which will tell u which RUU u actually need.

You need ruu_villec2 2.15
Sent from my HTC One S using TrickDroid 4.0.0

Related

Returning to Stock few questions.

So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.
Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.
What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
I am super CID.
gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too

stock rom fail

Hi,
I'm trying to go to the stock rom because I have to return my phone because I have battery problems and dust behind my screen.
But when I try to flash a stock rom it doesn't work. It says that I using the wrong image update.
Current image is 1.11.401.110 and I want to go to the lastest stock rom 3.32.401.105
What do I have to do?
Thanks
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
gol_n_dal said:
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
Click to expand...
Click to collapse
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
OK I don't understand where 1.11.401.110.... figures in the situation. If I understand correctly that is a custom ROM based off a different platform with Sense 4.0. Probably wrong though..
Are you fully S-OFF (clutching at straws here). Assuming you are you should be able to install an RUU easily. I recently went from 3.32.161.... to 3.32.401.. then back to 1.27.161... with no issues at all.
I'm sure someone more able than me can help you here.
GL
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
ok you are SOFF seeing that you have revolutionary HBOOT ..
so when returning stock ...its better to flash the correct stock...which can be found using CID
but as you have supercid now ...you need to know your original cid or the carrier/country the phone is linked to ..for finding the proper stock RUU
this guide helps you in fiding the proper stock RUU and it has flashing instructions too
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Install "cid getter" from the market.
AFAIK the entry for "ro.cid" should tell you your original CID.
e.g. It says VODAP001 for me while "fastboot getvar cid" gives "11111111".
tommeke19 said:
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Click to expand...
Click to collapse
from which country you bought the phone from and to which carrier it is linked to ?
Thanks everyone for helping me, but after using google I've found a site and found the solution.

Htc Desire C Downgrade Hboot

hello everybody...
i recently install slim-sense on my desire c , and then i wanted to return to stock rom but i can't do that because hboot of the ruu that i am flashing with is older than the one on my device so how can i resolve this problem...
some information :
bootloader unlocked with htcdev
s-On
current hboot : 1.28
ruu that i am using to return to stock is : RUU_GOLF_U_ICS_40A_HTC_Europe_1.35.401.1_Radio_10.08.98.09H_1.05.98.08M2_release_260338_signed
Solved
sayed.hosam said:
hello everybody...
i recently install slim-sense on my desire c , and then i wanted to return to stock rom but i can't do that because hboot of the ruu that i am flashing with is older than the one on my device so how can i resolve this problem...
some information :
bootloader unlocked with htcdev
s-On
current hboot : 1.28
ruu that i am using to return to stock is : RUU_GOLF_U_ICS_40A_HTC_Europe_1.35.401.1_Radio_10.08.98.09H_1.05.98.08M2_release_260338_signed
Click to expand...
Click to collapse
I think i figured it out i must flash it with the asian ruu
RUU GOLF U ICS 40A hTC Asia WWE 1.45.707.1 Radio 10.08.98.09H 1.05.98.11M3 release 262030 signed:silly:
Test
Sent from my SAMSUNG-SGH-I747
vmxice said:
Test
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
I am trying but it always keep saying error "wrong CID"!! Even with golden card !!
I am trying to change CID using fastboot but keep saying INFO[ERR] Command error !!!
Anyone have an idea ?
uff.... I finally managed to fix this out by flashing the right ruu
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
Hi sayed.hosam,
I'm trying to install the asian RUU to get the system in chinese.
But I allways get an error 131 (customer ID error).
I bought the device in Germany, that's why I suppose I have to use a goldcard, althougt it should not be locked by a provider.
After a couple of attempts, it also doesn't work with a goldcard.
Did you need a goldcard to flash the asian RUU?
If yes, did you use mmc0, mmc1 or mmc2 to get the CID?
Installing the european RUU is working for me, but doesn't containt chinese language.
cixpa said:
Hi sayed.hosam,
I'm trying to install the asian RUU to get the system in chinese.
But I allways get an error 131 (customer ID error).
I bought the device in Germany, that's why I suppose I have to use a goldcard, althougt it should not be locked by a provider.
After a couple of attempts, it also doesn't work with a goldcard.
Did you need a goldcard to flash the asian RUU?
If yes, did you use mmc0, mmc1 or mmc2 to get the CID?
Installing the european RUU is working for me, but doesn't containt chinese language.
Click to expand...
Click to collapse
No I didn't need a golden card.. I just found the right ruu and no errors happened !!
I must say that my device was unlocked from the "htcdev" site , and i relocked it before installing the ruu
Thanks for your reply!
Maybe it worked for you because you came from slim-sense, which is not locked.
Did you ever used a gold card on your desire c in the past?
Sent from my HTC Desire using xda app-developers app
sayed.hosam where did you get the RUU from? I have looked on HTCdev site and for the DESIRE C it only lists CRC files
sayed.hosam said:
uff.... I finally managed to fix this out by flashing the right ruu
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
Click to expand...
Click to collapse
hi sayed.hosam....
can you tell me the exact [TUT] for downgrade the htc desire c...
im flash the custom rom nameless rom. But i dont like the rom i back up before flashing,
when i get back to stock rom from back up...
i get an error its say MD5 mismatch.!
my only hope is to downgrade to stock RUU rom..
my baseband version is: 10.08.98.09H_1.05.98.11M3
my build number is 1.45.401.4.CL65553 release-keys
can you tell me where i get this right RUU rom..?
thanks and more power....

Fido/Rogers Stock RUU

Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out
jimlee2 said:
Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out
Click to expand...
Click to collapse
Iam also having the same problem did you found any solution for that dude
jimlee2 said:
Hello
I am officially getting crazy over the fact that my phone is broken
I tried everything and nothing works
now I want to flash a stock RUU
I tried both :
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed
but they gave me error 155
here is the info I have :
VLE PVT SHIP S-On RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OPENDSP-V31.1.0.45.0815
eMMC-boot
Cid : ROGER001
I really appreciate any help
this has been a problem for 7 days now and I cant figure it out
Click to expand...
Click to collapse
From the looks of it, seems like Those are ICS RUUs so that won't work. (Downgrade isn't possible without S-OFF which seriously I won't recommend)
Either:
- Find a JellyBean RUU.
OR
- Find a JellyBean OTA. (Though for OTA you will have to be on Stock ROM and Stock Recovery)
khan.orak said:
From the looks of it, seems like Those are ICS RUUs so that won't work. (Downgrade isn't possible without S-OFF which seriously I won't recommend)
Either:
- Find a JellyBean RUU.
OR
- Find a JellyBean OTA. (Though for OTA you will have to be on Stock ROM and Stock Recovery)
Click to expand...
Click to collapse
I tried to manually install the second RUU but it said HBOOT fails so when I researched it appeared that mine is HBOOT-2.15.0000 and the RUU is older version,
what do you mean find a JellyBean RUU ? another Rogers RUU ?
jimlee2 said:
I tried to manually install the second RUU but it said HBOOT fails so when I researched it appeared that mine is HBOOT-2.15.0000 and the RUU is older version,
what do you mean find a JellyBean RUU ? another Rogers RUU ?
Click to expand...
Click to collapse
I meant to say that these RUUs hold ICS stuff in it. Which is why it won't work since your phone is on JellyBean.
You need to find and Run a JellyBean RUU for Rogers.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
I meant to say that these RUUs hold ICS stuff in it. Which is why it won't work since your phone is on JellyBean.
You need to find and Run a JellyBean RUU for Rogers.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
oh, I did not know they are ICS ,
the problem is I can not find any other Rogers RUU, can you please help me find the correct one ?
I am new to this and in the past few days I tried almost anything, but still not working
jimlee2 said:
oh, I did not know they are ICS ,
the problem is I can not find any other Rogers RUU, can you please help me find the correct one ?
I am new to this and in the past few days I tried almost anything, but still not working
Click to expand...
Click to collapse
Okay, I couldn't find a JB RUU for Rogers. But I found an OTA.
You can find all the RUUs/OTAs Here.
OTA specific to your phone is in above link or Here Directly.
When you download it, be sure to match the MD5 checksums of the downloaded file to that of the file on server. MD5 hashes are given on the website. Long bizarre number.
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
For further material on how to flash an OTA (Since it won't work normally by flashing it over anything via custom recovery), follow This Guide.
Though it is for VilleC2 or the S3 variant, the rule is the same for S4.
I know it's a bit unusual process, but it's the only way to avoid doing the S-OFF which poses numerous problems afterwards.
khan.orak said:
Okay, I couldn't find a JB RUU for Rogers. But I found an OTA.
You can find all the RUUs/OTAs Here.
OTA specific to your phone is in above link or Here Directly.
When you download it, be sure to match the MD5 checksums of the downloaded file to that of the file on server. MD5 hashes are given on the website. Long bizarre number.
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
For further material on how to flash an OTA (Since it won't work normally by flashing it over anything via custom recovery), follow This Guide.
Though it is for VilleC2 or the S3 variant, the rule is the same for S4.
I know it's a bit unusual process, but it's the only way to avoid doing the S-OFF which poses numerous problems afterwards.
Click to expand...
Click to collapse
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again
jimlee2 said:
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again
Click to expand...
Click to collapse
Doesn't cause problems but won't let you update if anything other than stock. That's how it is different.
You can avoid using Stock Recovery, by editing updater script. That is explained in the afore mentioned thread.
And to get stock ROM you an use a nandroid backup of stock ROM and then flash this OTA.
Sent from my HTC One S using Tapatalk 4 Beta
Stuck at the same situation
jimlee2 said:
thank you so much for the help
you said :
For the OTA to work, you need to have:
- Stock ROM
- Stock Recovery
since I dont have the stock ROM , is it possible to fix this?
I heard OTA is different from RUU, will that cause more problems ?
thank you again
Click to expand...
Click to collapse
Hey
Did you ever manage to get your phone back to the stock ROM? I am stuck exactly at the same place as you. All numbers about my phone are the same too.
I cannot find any suitable RUU or nandroid online. Could you please point me to one?
Best,
Vic
veemon said:
Hey
Did you ever manage to get your phone back to the stock ROM? I am stuck exactly at the same place as you. All numbers about my phone are the same too.
I cannot find any suitable RUU or nandroid online. Could you please point me to one?
Best,
Vic
Click to expand...
Click to collapse
Here's your OTA.zip. Flash it using the method in my signature.
Sent from my Nexus 7 using Tapatalk HD

[Q] No more Bootloader

Hello XDA community!
I recently had a problem with my HTC one XL, the AT&T version. I know I'm not in the right section but, as both phone are very similar, I would like to know if anybody as already encouter a problem as mine.
I recently try to convert my HOXL into an international version by following this tuto. http://forum.xda-developers.com/showthread.php?t=2356401
Everything was fine until the point 4.b. To make quick, (more informations on my thread http://forum.xda-developers.com/showthread.php?t=2430573 )
As said in the tuto, my HTC One get stuck at about 3/4 completed, So I reboot it, and type the folling commands: "fastboot oem writemid PN0710000" but instead of getting a successful message, I get an error
<bootloader> [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time 0.009s
I've been stuck on the black HTC screen with 4 triangles and "!" in each corner until I found a command on the web "fastboot oem boot". After this command, the phone has booted directly on the viper boot screen but without the white HTC screen "Quietly Brilliant". Now, my phone is working perfectly, as before under the Viper rom. But when I reboot the phone there is no more the HTC screen, and moreover, I no more have the bootloader ! If I reboot the phone and select the "reboot to bootloader" option, my phone go back to the black HTC screen with 4 triangles and "!" in each corner.
I would like to go back in stock rom, but I'm afraid to flash my phone without bootloader. I think it's to risky. So do you think I can fix my bootloader before flashing ? Anyone already had kind of problem like this one ?
My phone is Tampered unlocked, S-OFF, I was in super CID, but I get back to the original ROGER001.
Thanks for reading...
That's not a tutorial for this phone. The title indicates that it's how to turn an at&t HTC One into an intentional HTC One. You've tried to flash firmware that isn't intended for your device. If you can still boot it up it might be recoverable.
I'd suggest you try running a Rogers RUU (one that's actually for your phone) to see if it helps. I don't know if it will though.
In future don't go looking all over the place, stay in the One XL forum and only EVER flash software/firmware from it. You'll find it here.
Sent from my Evita
I ended up in a state similar to yours once.
Fastboot was still working so I flashed a modified hboot from this thread and then I was able to boot into bootloader. from there I think I ran an RUU.
exad said:
I ended up in a state similar to yours once.
Fastboot was still working so I flashed a modified hboot from this thread and then I was able to boot into bootloader. from there I think I ran an RUU.
Click to expand...
Click to collapse
Seems to be a good idea, but unfortunatly my hboot is 1.11 and there is no hboot 1.11 file ...
That's because you've put a non One XL bootloader on your phone by following that tutorial. You're not looking for an RUU that matches your current setup, you're looking for an appropriate RUU for your phone.
I suggest you do a lot of reading and learning before you attempt anything else though, you're in way over your head which is pretty dangerous as you've found out.
Sent from my Evita
timmaaa said:
That's because you've put a non One XL bootloader on your phone by following that tutorial. You're not looking for an RUU that matches your current setup, you're looking for an appropriate RUU for your phone.
I suggest you do a lot of reading and learning before you attempt anything else though, you're in way over your head which is pretty dangerous as you've found out.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, I admit that it's a bit complicated... I use to flash rom on phone but I found it's very special on HTC's phone !
BUT, maybe (and certainly you're gonna proove me I'm wrong!^^) I think bootloader 1.11 is also good for HTC one XL. I've been looking at the link in you signature, and in that link there is stock RUU for HTC one XL : Stock ruu and related > HTC OTA and RUU collection > brings us here http://forum.xda-developers.com/showthread.php?p=37227608
And here, in ROGER cannada there is this one with my hboot :
1.94.631.3
File Timestamp: 29/06/12
Publically Seen: 30/07/12
Android: 4.0.3
Kernel: 3.0.8-01169-g209f9dc
hboot: 1.11.0000
radio: 0.18as.32.09.28L_10.103.32.24
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
RUU: RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32 .09.28L_10.103.32.24L_release_268972_signed.exe
Source: evita-ics-crc-3.0.8-209f9dc.zip
Am I completly wrong ?!
No you're not wrong, I was wrong, that is an RUU for our phone. As long as you're still s-off you should be ok to run that. You might want to take Exad's advice and fix up your hboot first though.
Sent from my Evita
The tutorial linked in the OP seems so convoluted. If the OP already has S-off, why bother with this stuff? You were already in a state (S-off) where you could flash whatever you want, whenever you want. Not have to wait around for OTAs and be limited by stock firmware.
timmaaa said:
No you're not wrong, I was wrong, that is an RUU for our phone. As long as you're still s-off you should be ok to run that. You might want to take Exad's advice and fix up your hboot first though.
Sent from my Evita
Click to expand...
Click to collapse
Ok, that's what I've planned to do but,as I said it before, in Exad's topic, there is no my hboot, do you know where can I find mine ?
redpoint73> what do you call "OP" ?!
The OP is the original post, as in your first post. It's also short for original poster, as in you
There are multiple links to downloads in the thread Exad linked to.
Sent from my Evita
timmaaa said:
The OP is the original post, as in your first post. It's also short for original poster, as in you
There are multiple links to downloads in the thread Exad linked to.
Sent from my Evita
Click to expand...
Click to collapse
Okay,I've read the whole topic, but there is no 1.11 to dowload. But there is people which were in 1.11 just like me and flash 1.09.
So gonna try with 1.09
You can get hboot 1.11.0000 inside any OTA that shipped it, eg Rogers 1.94.
I am not following why you want hboot 1.11, you can upgrade hboot to 1.14.
Typically downgrading hboot is harder than upgrading it
Why not just flash the AT&T 3.18 RUU?
twistedddx said:
You can get hboot 1.11.0000 inside any OTA that shipped it, eg Rogers 1.94.
I am not following why you want hboot 1.11, you can upgrade hboot to 1.14.
Typically downgrading hboot is harder than upgrading it
Why not just flash the AT&T 3.18 RUU?
Click to expand...
Click to collapse
EXCELLENT !
I had my bootloader back !!! (and the white HTC screen !)
Thank you to all of you... Really !
Gonna ask you few more questions ...
I 'm now TAMPERED, unlocked, S-OFF super CID, hboot 1.09. It means that I can install a european RUU right now ? Nothing else to do than plug the phone and run the RUU ?
As long as you run an RUU meant for your phone you should be fine.
Sent from my Evita
timmaaa said:
As long as you run an RUU meant for your phone you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Hey !
Still having a problem ...
I'm trying to put a french RUU (the only one I've found...) RUU_EVITA_UL_ICS_40_S_Vodafone_FR_2.34.163.2_Radio_0.20os.32.09.10_2_10.113.32.28L_release_275673_signed
But I got an error when I tried to flash my phone:
An error (-5001 : 0x0070002) has occured while running the setup .....
I've read that it's because I'm trying to downgrade or something like that... I've been typing fastboot getvar version-main
Version-main: 3.17.707.1
So, what can I do ?
[edit] I'm not looking especially for a french version if there is some kind of HTC "pure" international version...
Are you sure you're s-off? Click on the link in my signature, it's a resource thread and there you'll find RUU threads.
Sent from my Evita
timmaaa said:
Are you sure you're s-off? Click on the link in my signature, it's a resource thread and there you'll find RUU threads.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I'm sure. I've been into differents threads, I always find this vodafone RUU (which I just see isn't a "naked" RUU)
There is no HTC evita "international" RUU ?
Check here, the HTC Hong Kong RUUs are WWE.
Sent from my Evita
timmaaa said:
Check here, the HTC Hong Kong RUUs are WWE.
Sent from my Evita
Click to expand...
Click to collapse
Hello !
I'm stuck with an other problem right now. (hope it's gonna be the last !). I've put the EVITA vodaphone FR RUU and everything is working perfectly. But, when I try to do an OTA with the phone, it doesn't work: thephone download the OTA but when finished, I got a message saying it's not gonna be installed because of differrent version...
I've been looking for a solution in the forum, but most of the time it just say to relocke the bootloader, and flash an original recovery. That's what I've done from the .zip of a vodafone FR that I've found. I even try to put the vodafoneFR CID instead of the superCID, but I still got the same error...
Am I missing something ?
You can't install an OTA on a modified phone. If you want to use Android 4.2.2 / Sense 5 why don't you just flash one of the many ROMs available in our development section? They're all based on the official update.
Sent from my Evita

Categories

Resources