Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
Hi, I want to flash a development RUU, but everytime I try, I get Error [155]. This RUU is supposed to have 1.13.0000 bootloader version, but I don't know how to update from 1.06.0000 and if it may cause the error.
Any suggestion about it? Thanks in advance.
You're talking about ONE S, right?
Right, HTC One S
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
azzledazzle said:
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
Click to expand...
Click to collapse
Yes, I have the same CID that is inside the RUU.
Could you tell me how to run it from fastboot?
I'm trying almost everything I can (locked, relocked, unlocked, stock recovery...), even I'm trying now to update to the latest OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2 (now I have 1.53.401.2 from Orange Spain) as it has a firmware update (maybe hboot 1.13.0000?) what I think that can be one of the reasons why I can't flash the rom I need.
Thanks in advance!
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
azzledazzle said:
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
Click to expand...
Click to collapse
Yes, it's something I've already tried. Another problem I'm trying to solve is when installing from stock recovery, cause it says sdcart can't be mounted...
What are you trying to install from Stock Recovery ?? you cant flash an RUU and all flashable zip files MUST be signed otherwise it will fail..
I also had the cant mount sd card error in stock recovery, But when i tried CWM i didnt.. Dont know much about how stock recovery works, I just know i dont like it lol
lol, me neither!!!
I'm trying to install a stock rom, so I am supposed to do it from stock recovery, that's the matter. But I can't do it because it can't mount sdcard. I'm getting crazy, but now it is something personal, between the phone and me!!! I'll try to be patient and find the solution.
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
azzledazzle said:
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
Click to expand...
Click to collapse
Ok, it is the third option, and evidently, I'm not S-OFF. I had read a thread where they dissected this zip and I thought it was useful. Now I have found the RUU, I will try to install it. I've changed the zip and relocked it but I'm still finding Error [155]
Its useful if you are S-OFF, You just extract the ROM.zip from the RUU, Rename it to the phones model number, So in our case it would be PG40100.img ( i think) and then flash it in bootloader. However ignore this option as it wont work with a S-ON device...
If you still get the Error 155 message and you're positive you've done everything correctly, Maybe download the same / another RUU, Chances are it could have been a bad / corrupted download It happens to us all !
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
rpachecoh said:
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
Click to expand...
Click to collapse
I have done exactly (!!) the same, but you know, I have Hboot in version 2.15. And I can run none of RUUs, because I think they are not compatible with this version of Hboot (And this is that Error 155 for me). Well, so what can I do for installing the Stock RUU to my One S ?
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?
onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.
http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium
tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.
Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium
heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.
an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know
I have hboot 2.00.0002 and radio 3822.10.08.04_M ..... i want to upade it so that i can reflash ics stock rom in my htc desire s . the problem is i have rooted my phone when i have gingerbread so i have hboot and radio version of gingerbread so i cany flash ics in my phone .... please help ?
rkumbhar said:
I have hboot 2.00.0002 and radio 3822.10.08.04_M ..... i want to upade it so that i can reflash ics stock rom in my pc .... please help ?
Click to expand...
Click to collapse
If your bootloader is < locked >, you can upgrade desired components by
running RUU saga 4.0.4, that -is a simpliest of ways to upgrade device's bootloader and the radio...
If you're running stock, then upgrading to higher version of stock is just as simple as running an ics RUU.
It'd be different if you're unlocked via htcdev- if you are- then before running ruu,
you must relock your bootloader
Code: fastboot oem lock
Then run RUU.exe (on windows machine), let it completely finish
and you are done
but my htc desirse s has s-on .... and most of the forum which i read they said for upgrading hboot and radio version ...... s-off is needed
but i had a problem tht i had rooted my phone when my phone had gingerbread version ... so i have hboot & radio version whic is supported to gingerbread ... and after rooting i have deleted backup of stock rom .... so i cant officially update my phone to ics .... if there is any way to upadte please tell me .... i am using now ICS DS 8.0 . i also tried to update my phone to official ics ..... but it shows error tht you must have an official rom ....
rkumbhar said:
but i had a problem tht i had rooted my phone when my phone had gingerbread version ... so i have hboot & radio version whic is supported to gingerbread ... and after rooting i have deleted backup of stock rom .... so i cant officially update my phone to ics .... if there is any way to upadte please tell me .... i am using now ICS DS 8.0 . i also tried to update my phone to official ics ..... but it shows error tht you must have an official rom ....
Click to expand...
Click to collapse
Is your phone branded?
Have you relocked the bootloader?
if you upgrade by ruu,your hboot and radio are updated automaticaly
Edit: there is no official OTA for our device,
you'll have to download an ics ruu from htc dev site
Edit 2: you can flash RUU ics even when you've rooted your device before
It will update all device's partitions:system, bootloader, radio, stock recovery, kernel (stock) etc,
and 'll remove root and all other, previously flashed custom components.
If your device is branded to any mobile carrier, then using a goldcard is advised
to avoid errors during upgrade procedure
RUU- rom update utility- is an official, whole update pack from htc,
in a form of < exe >file- for windows, containing complete set of components that
our device requires, to function in a manner intended by manufacturer
no i have not locked my bootloader .. its is unloacked ..... and my cell dont have a STOCK ROM still it can be updated with ruu ... but when i tried it it show unable tu detect the ruu in mobile
rkumbhar said:
no i have not locked my bootloader .. its is unloacked ..... and my cell dont have a STOCK ROM still it can be updated with ruu ... but when i tried it it show unable tu detect the ruu in mobile
Click to expand...
Click to collapse
First you have to relock bootloader-in fastboot mode- command in my post above,
Then-.still in fastboot, connct to pc let it detect the phone and
start RUU.exe
In case pc does not see your device,
make sure ADB and fastboot drivers ar installed.
Newer versions of windows are known already for troubles
with connection,
Find- in that case- drivers for your windows version..
i have tried running ruu .... it gets upto sending ... and it get failed then there is recovery steps ......
rkumbhar said:
i have tried running ruu .... it gets upto sending ... and it get failed then there is recovery steps ......
Click to expand...
Click to collapse
Ok...ok...now,
If you first would answer a few questions,
1. Was it you that have unlocked your device's bootloader
2. do you know what ADB and FASTBOOT is,
3. do you know how to use ADB and FASTBOOT
4. does adb see your desire s
5. are you aware that in order to flash RUU you MUST lock bootloader again
Otherwise you'll never succeed in doing so
6. when flashing RUU- the phone must be in fastboot mode,
a) Must be connected to pc by the wire
b) there must be clear connection between the two (pc and the phone)
7. You start the RUU on the computer like any other < exe > program
8. You will not succeed in flashing RUU from recovery-
You'll not succeed in sending file through fastboot like you do with a boot image
9. Now- i think -i made it all clear as the summer sun
Edit: i do have stock 2.3.5 cwm backup, but i'm not sure if it will work on a machne other than the one which've made it
moreover it is about 600 mb, so i'm not sure where could i upload it for you
Edit 2: what do you mean by: 'recovery steps'
Edit 3: make sure your device isn't branded-because if it is, that causes errors
when you try to flash a RUU other than the carrier's your device is locked to
Try to read more from the index thread
Flashing the kind of thing a RUU is,
Is so simple and stright forward that it is (almost) impossible to fail,
One of very few things that are causing errors are
a) lack of connection in fastboot mode (wrong or to old windows drivers)
b) carrier branded stock rom- which is a bit more difficult to reflash
by world wide english version (but by all means not impossible)
c) unlocked bootloader- which in this case must be locked(or relocked) again
There is nothing else popping to my mind that would possibly prevent you
from successful accomplishment of upgrade procedure...
....well except maybe when you 'd try to flash lower software version on top of the higher one
( which is doable as well- with small modification of < misc_version >)
which- in your case is not true- or is it?
1. yes my bootloader is unlocked through htcdev
2. i dont know what is adb but i know fastboot option in phone it appears when volume down and power button is pressed together
3.i dont know the use of adb and fasboot but i use it for flashing a boot image
4.no i dont know how to lock bootloader again
5. But In Ruu setup they just said that start debugging option in phone .... after tht all options it restarts automatically
and about your edit step 2 recovery option comes in ruu after the upgrading ruu gets fail .. i show to recover phone
and call you tell me the meaning of branded ? about this line ( make sure your device isn't branded )
I Am doing this all because i want to flash pacman rom .... for it i got problem that i flash its boot image and it also get successful ... but when i restart my mobile it shows the boot image of earlier rom which i flashed before pacman ... so my mobile doesnt get started .. it stucks on boot animation
AW: [Q] Help I Want To Update My Radio Version And Hboot Verion Of My HTC Desire S ?
rkumbhar said:
1. yes my bootloader is unlocked through htcdev
2. i dont know what is adb but i know fastboot option in phone it appears when volume down and power button is pressed together
3.i dont know the use of adb and fasboot but i use it for flashing a boot image
4.no i dont know how to lock bootloader again
5. But In Ruu setup they just said that start debugging option in phone .... after tht all options it restarts automatically
and about your edit step 2 recovery option comes in ruu after the upgrading ruu gets fail .. i show to recover phone
and call you tell me the meaning of branded ? about this line ( make sure your device isn't branded )
I Am doing this all because i want to flash pacman rom .... for it i got problem that i flash its boot image and it also get successful ... but when i restart my mobile it shows the boot image of earlier rom which i flashed before pacman ... so my mobile doesnt get started .. it stucks on boot animation
Click to expand...
Click to collapse
What recovery are you using? It looks like pacman isn't being flashed properly. (I would recommend trying the latest version of 4ext)
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
teadrinker said:
What recovery are you using? It looks like pacman isn't being flashed properly. (I would recommend trying the latest version of 4ext)
Click to expand...
Click to collapse
Edit: you did flash pacman in recovery and then flash the boot.img in fastboot, I suppose?
rkumbhar said:
1. yes my bootloader is unlocked through htcdev
2. i dont know what is adb but i know fastboot option in phone it appears when volume down and power button is pressed together
3.i dont know the use of adb and fasboot but i use it for flashing a boot image
4.no i dont know how to lock bootloader again
5. But In Ruu setup they just said that start debugging option in phone .... after tht all options it restarts automatically
and about your edit step 2 recovery option comes in ruu after the upgrading ruu gets fail .. i show to recover phone
and call you tell me the meaning of branded ? about this line ( make sure your device isn't branded )
I Am doing this all because i want to flash pacman rom .... for it i got problem that i flash its boot image and it also get successful ... but when i restart my mobile it shows the boot image of earlier rom which i flashed before pacman ... so my mobile doesnt get started .. it stucks on boot animation
Click to expand...
Click to collapse
We say a device is branded when it is locked by mobile carrier to use only with his sim card
and no other ...
What ussualy follows is that system installed on a device- although official- is very often modified
in a specific way...
That is the reason why branded phone,( equipped with branded rom )
refuses other than this same carrier's RUU version,
Example:
If your phone is locked ( branded ) to T mobile, normally it'd refuse any other than
T mobile's RUU.
To force successful flash nonetheless,
one must use < gold card > (you can find how to create and use it in desire s index thread )
I have two HTC Sensation Device ---
1) Locked hboot1.27.XXXX, ICS (From Official OTA), S-ON, Non-rooted
2) Locked hboot1.18.XXXX, GB (As no Official OTA Received for ICS), S-ON, Non-rooted, Orange-United Kingdom
I have successfully unlocked and rooted both the devices with 4EXT Touch Recovery Installed in both the mobiles (Still S-ON for both devices).
Now my Device status are as below:
1) Unlocked hboot1.27.XXXX, ICS (Custom ROM), S-ON, Rooted
2) Unlocked hboot1.18.XXXX, GB (Slightly Customed ROM), S-ON, Rooted
I have tried to install different ICS based custom roms using Smart Flash of 4EXT Recovery with S-ON.
In first device, ROM installation was successful in every try
But in second device, ROM installation failed and boot-loop problem occurred (tried with 5~6 custom ROMS but failed all the time with similar problem). Then I have flashed GB ROM on second device with hboot 1.18.XXXX.
Can anyone answer my following queries, Please--
1) I think, as the custom ROMS requires hboot version 1.27.XXXX+, it failed to flash. Please confirm whether my assumption is ok or not. Please be noted that custom ROMS are flashing my first device with S-ON with ease.
2) Can I upgrade to 1.27.XXXX hboot version without S-OFF?
3) Can I flash/push by hboot.img through (fastboot flash hboot hboot.img) command with version 1.27.XXXX? If yes, can anyone provide me a proper link to download that hboot.img file?
4) Can anyone provide me download link for RUU so that I can update my hboot version by official ICS ROM (Orange, United Kingdom)
5) Can anyone suggest any better method to install custom ROMS with S-ON?
6) Can anyone suggest me how to S-OFF easily (I have tried Revolutionary.exe, but this program never opens in my PC although I have the beta Key)?
7) With S-OFF, will the problem will be solved with hboot version 1.18.XXXX? If not, please suggest...
I would be really happy if my problem is solved by any of yours' help
in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?
RE:
rzr86 said:
in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?
Click to expand...
Click to collapse
In fact revolutionary.exe is being crashed whenever I tried to open it either in Windows XP (Office Laptop) or in Windows 7 (Home PC). So, I have failed to use this tool. Can u suggest any idea?
If you can't use revolutionary for s-off, then your only hope is RUU.EXE on your PC.
Sent from my HTC Sensation