Hi guys
i have a serios problem, i have been sitting on my phone and flashing various new things for several hours now...
i want to flash Mikes Android HD 6.1.1 on my Sensation
according to http://forum.xda-developers.com/showpost.php?p=14192842&postcount=4
i have no Android OS running at the moment, when i start my phone n bootloader it sais:
******unlocked******
Pyramid PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.21.3504.13_2
OpenADSP-v02.6.0.2226.00.0104
eMMC-boot
as i understand i have to update the Radio to 11.68.3504.00U_11.21.3504.13_2
but whenever try it whith the downloaded "adb tool" (just click "start here" and follow the guide....)
i always get the same error Sending img OK
Wriging FAILED (Remote: not alloed)
i read some threads which suggested taht i coud be an USB driver issue, so i tried serveral different PC's -> still the same error
i found some threads which mean that the probelm is missing ENG S-OFF, but how do i get ENG s-OFF on Hboot 1.27?
i am really in trouble here since i have no working phone at the moment
BIG THX
You cant use the adb tool as the 1.27 doesnt support adb commands (from what i understand)
You should be able to flash and boot ARHD 6.1.1 anyway as you are on the 1.27 HBOOT.
If you want the new radio then i would recommend getting the firmware package from mikes thread HERE , put the PG58IMG.zip on your sdcard and boot into HBOOT. It should then reflash the firmware including the radio. Theres also noob proof firmware packages as a sticky.
Hope that helps.
Thx for the fast Answer!
i already updated the firmware package from taht link
(this one: Firmware from 3.24.401.1 RUU
--- MD5 checksum: 632F8A40991DC95F241FDF4A5FC9F006 *PG58IMG.zip ---
--- Only for 3.24.401.1 based ROMs )
but you mentionned that the Raio sould also be updated whith that?
But why is it still showing the old version number in bootloader?
THX
lol, u have got the latest radio...what else do ya want mate???
Great i just flashed ARHD 6.1.1 as a try and it works!
in fact, your radio is "11.68.3504.00U_11.21.3504.13_2" now.
so don't worry about it, just do the next step.
Related
I already followed all of this: http://forum.xda-developers.com/showthread.php?t=1192300 (except the S-ON reversal obviously)
Thought I would ask out here since my post I made in the Android Revolution thread disappeared within minutes 4-5 pages behind and no answer.
Whenever I try to follow the instructions inside the recommended Radio archive file from Mike's post, it won't let me write. ADB reboot bootloader, then ADB fastboot flash radio radio.img etc... It will say sending, then FAIL -remote not allowed. Can anyone help me figure out what's wrong?
Love 1.1.3 and just holding out anxiously for 1.1.5, it's already so much better even with my original radio file!
Currently using Bell Canada's 10.50.9007.00U_10.12.9007.21_2M Anyone experiencing better results with this ROM upgrading from this radio version to Mike's recommended one? Do I need to do one of the boot (unsecured or ENG Hboot) from this thread: http://forum.xda-developers.com/showthread.php?t=1122053 ?
Vol down + Power shows:
HBoot - 1.17.0011
Radio: 10.12.9007/21_2M
eMMC_Boot
Jun 2, 2011, 22:31:39
Got '404 not found' from your top link
If you perm rooted your phone using Revolutionary you should already have the correct S-OFF permissions to flash a radio.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1178143
But using Mike's radio, and all was good!
According to your HBOOT number you are still S-ON? 1.17.0011 is definately a S-ON HBOOT according to www.revolutionary.io and the FAILED:Remote not allowed is also a fastboot protection covered by a S-ON HBOOT.Mine changed to 1.17.1011 when i S-OFF'd it then i flashed the ENG HBOOT
It says S-OFF on that screen and I was able to flash the Revolution HD using Clockwork. I've been reading on some other threads that S-OFF Radio is separate from just S-OFF for ROMs... any truth to that?
Tacklebury, I would try the zip file way from your link but the radio version Mike recommends for his ROM isn't in there.
bartchow said:
It says S-OFF on that screen and I was able to flash the Revolution HD using Clockwork. I've been reading on some other threads that S-OFF Radio is separate from just S-OFF for ROMs... any truth to that?
Tacklebury, I would try the zip file way from your link but the radio version Mike recommends for his ROM isn't in there.
Click to expand...
Click to collapse
Use the zip file from Mike's OP but re-name it as the link says.
As far as I have found out and been told, if you're S-OFF with Revolutionary you're all good.
bartchow I also have a bell Sensation and I same radio as you. I wonder if you have flash another radio if yes you it's the work?
Thank!
revolution
Hi I just flashed the revolution hd but was I supposed to flash the radio first
I am having the exact same issue!
in recovery is says i am S-OFF
HBOOT - 1.17.1111
RADIO - 10.119007.27_M3
eMMC - boot
jun 2 2001,22:31:39
Tells adb is not a recognised command
Hi guys.. I really hope someone can help with this as i am desperate.
I unlocked my Desire S with Revolutionary, then upgraded HBOOT to ENG 2.00.0002. Until now ,after running all roms possible found on this great site, I had the pre-rooted deodexed stock 2.10.401.4
Today I downloaded the RUU_Saga_S_HTC_Europe_2.10.401.5, unpacked copied the PG88IMG.zip to my sdcard and begun update. The update was unsuccessful. Now my device says this:
*** LOCKED ***
*** Security warning ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO_3822.10.08.04_M
eMMC-boot
The phone is stuck is FASTBOOT, and selecting BOOTLOADER only loads again PG88IMG.zip, and of course after "Checking PG88IMG.zip" it errors with Main version is older! <Power> to REBOOT.
IS there anything that can be done? PLS HELP!
OPPiuM said:
Hi guys.. I really hope someone can help with this as i am desperate.
I unlocked my Desire S with Revolutionary, then upgraded HBOOT to ENG 2.00.0002. Until now ,after running all roms possible found on this great site, I had the pre-rooted deodexed stock 2.10.401.4
Today I downloaded the RUU_Saga_S_HTC_Europe_2.10.401.5, unpacked copied the PG88IMG.zip to my sdcard and begun update. The update was unsuccessful. Now my device says this:
*** LOCKED ***
*** Security warning ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO_3822.10.08.04_M
eMMC-boot
The phone is stuck is FASTBOOT, and selecting BOOTLOADER only loads again PG88IMG.zip, and of course after "Checking PG88IMG.zip" it errors with Main version is older! <Power> to REBOOT.
IS there anything that can be done? PLS HELP!
Click to expand...
Click to collapse
If you remove or rename the PG*.... file from the root of your SD card this should stop happening..
Then you should be able to enter recovery, where I'm hoping that you'll have an available Nandroid backup that you could restore to.
Problem is that choosing recovery from bootloader does nothing, just brings me back into fastboot. I think that recovery was wiped during the failed update process.
Also my device is S-on now so i cannot flash a new recovery in fastboot.
Now I'm afraid that I'm a little out of my depth here so won't offer any more advice.......but, you should be able to flash the recovery partition from fastboot...So hopefully all is not lost yet...
EDIT: Apology, only just read that you're S-ON and am not sure what to recommend.
You should look at my guides below. Both will tell and show you how to flash recoveries via fastboot.
Check my sig below.
Sent from my HTC Desire S using XDA App
Thanks, but before i wrote this question i did read all guides possible, including yours . Problem is I am stuck in fastboot, i cannot boot the phone, use adb or flash anything via fastboot as my device now is LOCKED and S-ON. Also i have no recovery not even stock one...
Smells more and more like a bricked Desire. Damn.
OPPiuM said:
Thanks, but before i wrote this question i did read all guides possible, including yours . Problem is I am stuck in fastboot, i cannot boot the phone, use adb or flash anything via fastboot as my device now is LOCKED and S-ON. Also i have no recovery not even stock one...
Smells more and more like a bricked Desire. Damn.
Click to expand...
Click to collapse
If you have read the guide, you should have known that before you can flash ANYTHING on fastboot, you have to be UNLOCKED first..
You should have tried to unlock it BEFORE flashing anything..
If these doesn't work, then you may be right on your last sentence..
Goodluck!
Before attempting the RUU update with pg88img.zip i had ENG HBOOT with S-OFF, but during that update something went wrong. It managed to update to the official HBOOT 2.00.2002 S-ON, but then i got the "Main Version is older - Update Fail! error and i think I need to send it to HTC as I see no way out of this. What i do not understand is this "Main Version is older - Update Fail!" error! why did this happen in the first place as i was updating from pre-rooted deodexed stock 2.10.401.4 to 2.10.401.5.
Simmilar problem, still wifi not working
I have got simmilar problem on desire s, got revolutionary S-OFF with 0.98 then tryied RUU with sense, something went wrong.. now i have hboot 2.00.0002 radio 3822.10.08.04_M i opened the hboot via HTC development page, then i flashed the newest ROM by Adidas108: RUU_Saga_S_HTC_Europe_2.10.401.5_signed_prerooted SENSE 3.0(http://forum.xda-developers.com/showthread.php?t=1183684)
now the system is booting properly and i can use the phone again, but the wifi is not working, which sucks because there is newest radio and according adidas108 newest ROM. I havent found solution for this as my hboot is in S-ON now and i cant flash different version of radio. I think first i need to find how to make hboot 2.00.0002 into S-OFF. Anyone any idea?
UPDATE 1: now i managed to install the ROM build 1.28.401 prerooted by Adidas108, everything seems to be working again, even wifi is ok. It is strange that the old ROM is working with newest RADIO and the newest ROM not, does anyone has any reasonable explanation to this issue?
Can you please be more specific on how you dealt with your HBOOT. Did you somehow managed to get it S-OFF. I sure need to flash a new recovery and from there i am good, i can resurrect my phone.
No my hboot 2.00.... Is s-on, i just unlock the recovery it means i can flash roms, but i cant overvrite radio or hboot on its own. I also need a solution how to make my phone s-off, and as revolutionary is only supporting hboot .98 it will not be easy. For now ill better stáy on my old ROM with sense 2.1
Sent from my HTC Desire S using XDA App
I unlocked my bootloader on htcdev. After that my old rom booted up normaly and everythig was back to normal. I then flashed in recovery RUU_Saga_S_HTC_Europe_2.10.401.5_signed_prerooted SENSE 3.0 by Adidas108 and it all works perfectly now since my radio was updated before the error with "Main version is older" in the official RUU_Saga_S_HTC_Europe_2.10.401.5. thanks guys for the help.. i read Skanob guides again and found out about htcdev.
moloto said:
No my hboot 2.00.... Is s-on, i just unlock the recovery it means i can flash roms, but i cant overvrite radio or hboot on its own. I also need a solution how to make my phone s-off, and as revolutionary is only supporting hboot .98 it will not be easy. For now ill better stáy on my old ROM with sense 2.1
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
BTW, from my experience it seems that you could update your radio to latest version if you try with the official RUU_Saga_S_HTC_Europe_2.10.401.5. It will probably error "Main version is older" and lock your bootloader, but you could unlock it on htcdev, and enter custom recovery after that and flash Adidas108's RUU. My wifi works perfectly with 20.4801.30.0822U_3822.10.08.04 radio.
Solution
So finnally my cell is working with sense 3.0. I downgraded hboot to 0.98.0000 thanx to Skanob(http://forum.xda-developers.com/showthread.php?t=1318919), then S-Off with revolutionary, flashed actual clockwork mod recovery, after the newest saga radio and as the last the newest ROM by Adidas108. Everything works fine, even with hboot 98.0002. End of Story
Hello Everybody,
I have a problem I can't figure out.
I have had my phone rooted and S-off and have had many custom roms. I wanted to go back to stock and followed the procedure, but the RUU 1.29 won't flash because I am on image 1.74 with HBOOT 1.20 I also now lost S-off so I can't flash another Radio.. There is how my fastboot screen looks
*** Unlocked ***
Pyramid PVT SHIP S-On RL
HBOOT-1.20.0000
RADIO-10.14.9035.02_2
EMMC-boot
I did the HTCDev unlocked bootloader which made it go to Unlocked mode but did not give me S-off.
Any help please
the RUU should work.
make sure u go through it carefully.
I used the 1.29 ruu today on my hboot 1.23 ICS sensation
The RUU failed the first time but gave me some menus which flashed somekind of recovery files
then i ran the RUU again and it proceeded normally
Oomike said:
the RUU should work.
make sure u go through it carefully.
I used the 1.29 ruu today on my hboot 1.23 ICS sensation
The RUU failed the first time but gave me some menus which flashed somekind of recovery files
then i ran the RUU again and it proceeded normally
Click to expand...
Click to collapse
Did you use a particular 1.29 ROM per chance?
Oomike said:
the RUU should work.
make sure u go through it carefully.
I used the 1.29 ruu today on my hboot 1.23 ICS sensation
The RUU failed the first time but gave me some menus which flashed somekind of recovery files
then i ran the RUU again and it proceeded normally
Click to expand...
Click to collapse
Thank you I will try that.
I tried the RUU recovery and it didn't trigger or do anything, I followed all instructions.. The FASTBOOT still says Update Failed and Security failed or something like that. I also tried flashing the update in bootloader by extracting the rom.zip from the RUU and no luck.
I have a custom 2.3.4 rom runing fine but my WIFI doesn't turn on, it just says Error. I really need to get this back to stock so I can warranty this phone if the WIFI doesn't come back.
Any more ideas everyone?
Thank you in advance.
Found this Thread, this is the same problem i'm having..
http://forum.xda-developers.com/showthread.php?t=1296134
Hi there
first of all i know: http://www.youtube.com/watch?v=JmvCpR45LKA
So i am completly new here and i tried to root and flash a custom rom accordng to the guide here http://forum.xda-developers.com/showthread.php?t=1192300 and here (in german: http://www.pocketpc.ch/htc-sensatio...s-off-flashen-custom-rom-fuers-sensation.html)
however i did not work properly...
My Phone: HTC Sensation with Branded Android 2.3.4 (Provider Swisscom; Switzerland)
here is what i did:
1.) I unlocked the Bootloader with the official HTCDev tool (http://htcdev.com/)
2.) i S-OFF'ed my phone accordng to:
Step 1. To S-OFF your Sensation - (You do not need to do this if you have S-off already or done this before) - WORKING NOW for TMOUS users
Visit http://revolutionary.io/
however, the CMD showed me a "Failure, Live gave you lemons"
i think it was only concening the installation of the clockwork... (???)
3.) i did the CID stuff "fastboot oem writecid 11111111" (afterwards getcid gave me "fastboot getvar cid" 11111111
4.) the i flashed the firmwareupdate from here
http://forum.xda-developers.com/showthread.php?t=1412618
(this one : "Firmware from 3.12.401.2/102 RUU" since i had id 111111111)
5.) the i tried flashing Adroid Revolution HD 6.x (after superwipe) from here
http://forum.xda-developers.com/showpost.php?p=14192842&postcount=4
but after rebooting, the phone froze in the white HTC screen for about 20 min or so
6.) superwipe again, and then i flashed Revolution HD 4.1.7 which is working now
my phone sais now: Android Version 2.3.5
HTC Sense: Version 3.5
Software number: Android Revolution HD 4.1.7 by mike1986
and if i enter recovery mode on statup it sais:
*****unlocked*****
Pyramid PVT SHIP S-OFF RL
HBOOT-1.20.0000
RADIO-11.15.3504.16_M
eMMc-boot
and if i enter recovery, this 4ext touch recovery tool (1.0.0.3 Beta 7) starts
i dont know if i have done it correctly or if i made a complete mess!
i really would like to install the Android Revolution HD 6.0.3 rom but as i said, the phone gets stuck at startup (or do i have to wait longer than 30 min on the HTC screen?!)
can annyone of you pro's see where the mistake was done? or what i have to change, to make the new rom working?
THX so Much
sincerely
N00b swissbone from switzerland
You flashed the wrong firmware for the 6.0.x rom you need to have the 1.23 hboot. Look in the ARHD thread and download the correct firmware for 6.0.3.
Link to firmware: http://tinyurl.com/creec9g
thx... actually i think i have tried both firmwares you can download at the URL you mentioned.. but i think i will try again
could it be anything else?
THX
download again the firmware, check MD5 sum and try to flash firmware again. also update your 4ext beta 8
how do i update ext4 ?
THX
there are two ways. Either you can flash 6.03 again, then you should have beta 8, or find in market "4ext uploader"
thx
there is one problem though...
if i go to cmd-> adb devies, i obly get the answer "List of Devices Attached" but no devie is listed....waht can i do?
THX
swissbone said:
thx
there is one problem though...
if i go to cmd-> adb devies, i obly get the answer "List of Devices Attached" but no devie is listed....waht can i do?
THX
Click to expand...
Click to collapse
make sure your phone has debuggin check on
i cant, since i have currently no Android OS on the device :s
can i somehow do it from ext4 ?
THX
swissbone said:
i cant, since i have currently no Android OS on the device :s
can i somehow do it from ext4 ?
THX
Click to expand...
Click to collapse
Hmm pickle indeed, whats your hboot is it still the same? or does it say something different after flashing new firmware?
if it says 1.20/1.23 you should be able to boot any gingerbread rom and older ICS Leaks,
if you want to boot 6.1.x or insertcoins 4.4.x or any variant of those roms that use the newset ICS leak your gonna need to flash latest firmware which has hboot 1.27
I would download the rom again, I had a few bad downloads before that made my phone not boot up. Oh and his roms take a while to boot just be patient
Sent from my HTC Sensation using xda premium
When he has no Android on his phone, he, isn't be able to flash, isn't he?
Somewhere I saw a posting with a describtion how from WM to Android. I thought I saw it in the ARHD 6.1.0 thread somewhere on page 4790 or so, it's a very huge thread, so start backwards to read is my suggestion
ok, i have 2.3.5 running again...
what have i to do nex? update teh HBOOT and Firmwaren? and then update the 6.1.x ?
THX
so ok i have 2.3.5 running again...
whta do i need to do next to get 6.1.x running?
update the HBOOT and i am good to go? i dont exactly know wat ENG S-OFF is, but do i need it?
THX
ok, when i start my sensation up in recovery mode it says:
Unlocked
Pyramid PVT SHIP S-OFF RL
HBOOT1.23.000
Radio-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
so what is the next thing to do?
flash HBOOT 1.27 with "debugging enabled"
do i need new firmware/radio ?
BIG THX
SO...i tried it again with USB DEBUGGING activated...
i downloadede the radio ( 11.68.3504.00U_11.21.3504.13_2 ) from here http://forum.xda-developers.com/showpost.php?p=14192842&postcount=4
but when i start this adb tool and try to install the radio it starts the phone in recovery/fastboot (as it shoud) but when i continue with "fastboot flash radio radio.img" it says:
sending "radio" .....OKAY
writing raidio....FAILED (remote: not allowed)
what is wrong?
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