Database Info

[Q] return to stock

Hi all,
I want to return my phone to stock so i am trying to flash the original RUU but this does not work.
Do i have to relock? if so how is that done? through the adb command?
is it possible for to get locked written in bootloader as in some threads it says this can only be set to relocked, is this correct?

You can relock the bootloader using adb !
Boot into fastboot, Open a command window from your adb folder (shift and right click)
Type in: fastboot oem lock
That will relock the bootloader, RUU needs a lock bootloader ! There is no way to get **LOCKED** back !! Only **RELOCKED** But this shouldnt affect your warranty.
You may also need the stock recovery in order for the RUU to work, Sometimes you do sometimes you dont..

azzledazzle said:
You can relock the bootloader using adb !
Boot into fastboot, Open a command window from your adb folder (shift and right click)
Type in: fastboot oem lock
That will relock the bootloader, RUU needs a lock bootloader ! There is no way to get **LOCKED** back !! Only **RELOCKED** But this shouldnt affect your warranty.
You may also need the stock recovery in order for the RUU to work, Sometimes you do sometimes you dont..
Click to expand...
Click to collapse
Thanks gratly appreciated, ive seen Shipped RUUS is there a thread for stock recovery?

dawnbringer said:
Thanks gratly appreciated, ive seen Shipped RUUS is there a thread for stock recovery?
Click to expand...
Click to collapse
https://dl.dropbox.com/u/69014495/stock recovery.zip
there you go, Saves you searching for it

azzledazzle said:
https://dl.dropbox.com/u/69014495/stock recovery.zip
there you go, Saves you searching for it
Click to expand...
Click to collapse
I assume i should flash this with fastboot correct? - done

If I wanna return to stock, after locking the bootloader, does it have to be the same version ROM I had initially? Or can I flash any version RUU provided it matches my phone model? Because I don't know what version I had when I bought the phone, I rooted and flashed CM9 straight away.

Hi all, I have some trouble to restore to a stock rom. I have a debranded HOS from Vodafone Spain. I did it helped by the famous Toolkit, so it was with the bootloader unlocked, with a CWM Recovery and then I applied a stock rom by CWM (1.73 about Vodafone to 1.53 but the WWE European one). But I still wasn't happy, can't upload it by OTA and I dislike to do it manually with each new version, plus backups, etc.
Then I changed the CID to HTC Europe (HTC__001); and now the system detects a new version to update it, but when it restart to apply it appears an error during the process, something like "assert failed....... (Status 7)"
I tried also by the RUU, and this way gave me the error 155.
Somebody know if this way is available?. Change the CID and then apply the respective RUU?
Something else... I remember in my old Desire to restore everything, like factory, placing a rom into a "SD" with a especific format (depends of the model), like PG88IMG.zip. Somebody know if is possible for this newer model?

Works perfectly !! thanks for the tuto ! you saved us !

Help Please I can't get any T-mobile U.S, RUUs to work ?

followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ

can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX

kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1

Thankyou my friend ill give it a go

unfortunately that didn't work either...i don't know why this wont work for me

kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.

Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville

@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )

usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?

Didn't work Hboot didn't detect PJIMG.zip :crying:

kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.

kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted

I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?

Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU

dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.

One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.

Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx

kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.

need help to back to stock

ok i need help,i install PA over stock rom on 2.2 firmare,before flashing i maked a nandroid backup,i wanted to sell the phone and wanted to back to stock rom,BUT im stuck at boot loop htc screen because while i flash Pa i flash a PA boot img so i cant boot now stock rom,what is to best advice to back to any rom,can i flash somehow flash boot image of stock rom and where can find that boot img,or something else i can do,when i get into twrp recovery i cant do factory reset its failed and i dont have gapps and PA rom on my sd card that files are no more on my sd card i dont know why,so i cant flash PA anymore,need any help asap

if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu

DvineLord said:
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
Click to expand...
Click to collapse
i will try thanks

vigorito said:
i will try thanks
Click to expand...
Click to collapse
i dont have in bootloader oem lock?

vigorito said:
i dont have in bootloader oem lock?
Click to expand...
Click to collapse
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?

vigorito said:
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
Click to expand...
Click to collapse
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app

Myrder said:
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
i did it in command promt i get bootloader lock succesfully
then bootloader tz htc svc disable ret and some numbers
and then failed (status read failed) too many links and in bootloader i see its relocked and some security warning
im running ruu now will se whats gonna happen

bro...i hit thanks!

I was actually wondering about the issue of having to flash the boot.img if restoring a TWRP backup. I assumed that it would have to be flashed via fastboot, since boot.img is obviously needed but can't be accessed by recovery on the 1.14 hboot. But haven't seen that discussed or confirmed here. Doesn't actually apply to my One X, since I'm on the old hboot. More just wondering academically.
Seems like the OP has taken the route of running the RUU. But if you ever need the boot.img for a stock ROM, many of the stock ROMs are posted in Development. So you can download the right one, and pull boot.img from it.

Yes you need to flash boot.img when restoring a backup on hboot 1.14.
Sent from my HTC One XL using xda app-developers app

Thanks for the tips guys, I also used this just now to unroot my phone and return it to bone-stock. I used the All-in-one tool to relock the bootloader and got the same error message that OP got, but after rebooting into the bootloader it said Re-Locked. Then downloaded HTC Sync and the 2.20 RUU and ran it. Took 15 minutes total and my phone looks stock, unless of course some busybody at AT&T decides to check the bootloader.
I am returning my One X and buying a One X + tomorrow morning.
EDIT: Oh and in case anyone is confused, you DO NOT need to flash boot.img in order to flash the 2.20 RUU.

i heard people say that they flashed the twrp boot backup in fastboot and it worked the same as flashing the boot from rom.zip in the ruu. i prefer the ruu method for going back to stock, just seems more official imo.

[Q] Fallout doesn't go past boot

Question in short: I have Fallout but it doens't go past the bootscreen. What can I try?
I have a european non-branded Desire S (Dutch) and wanted to try custom roms. I grabbed the most detailed tutorial I could find and started working on it. This was some months ago, but i basically ended up using MIUI because no other rom worked. Now, I am completely tired of all the fails this rom has (lagging, crashing, shutting down for no reason and the rom is just ugly imo) and therefore want to switch to another one. Now, my preference laid with the official beta for android 4.0 from the HTCdev website. I downloaded the RUU, followed the instructions, but I get an error everytime during the installation. Now as far as I have found out, this is because my phone is S-OFF. Searching how to change this, I found some commands:
Code:
fastboot oem lock
I thought, or something close. I don't think I will be helped by just this, but how do you execute this code? I believe somewhere in cmd, but where is fastboot.exe?
Given up on the idea of getting an official rom installed, I tried to install Fallout, the rom which appealed to me the most of all. Now, I remember this one from earlier, but it simply stops at the "HTC One" bootscreen. I did a full wipe as far as I know how to:
Code:
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe battery stats
format system
format data
format boot
I did all of the above. And that is the situation I am in right now. I have Fallout installed and would like to use it (if it turns out to be good), but the official 4.0 beta would be good for me too. The rest of my phone's information:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
I just realized it is already S-ON. I don't know how, but i used the program Revert to Stock too, but it gave an error. Please tell me any extra information you need to help me, I hope you can help me solve this.
Thanks in advance.

Did you flash the boot.Img after you flashed the rom?
Java is C++ without guns, knives and clubs. - James Gosling (Co-inventor of Java).

I had exactly the same problem. Try to flash Boot.img Via Fastboot.

jugg1es said:
Did you flash the boot.Img after you flashed the rom?
Java is C++ without guns, knives and clubs. - James Gosling (Co-inventor of Java).
Click to expand...
Click to collapse
Kingdomds said:
I had exactly the same problem. Try to flash Boot.img Via Fastboot.
Click to expand...
Click to collapse
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
I used a boot.img from the "Revert to Stock" application. Sending returns OKAY but writing returns FAILED (remote: image error! (BootMagic check fail)).
First of all, can I use this boot.img with Fallout? Secondly, how do I fix the fail in fastboot?

Robbertkooiman said:
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
But I have no boot.img and it now says HBOOT USB PLUG in the recovery.
The command "fastboot devices" does nothing. It's recognized, but returns nothing.
What do I do?
I now found out I had to select fastboot. Now it says "FASTBOOT USB" and "fastboot devices" recognises my phone, but I still have no boot.img. Is there a specific boot.img for Fallout or do I need one for my phone?
Click to expand...
Click to collapse
Get the boot.img by extracting it from the fallout .zip file.

teadrinker said:
Get the boot.img by extracting it from the fallout .zip file.
Click to expand...
Click to collapse
Thanks, and sorry if this is already in every tutorial to install roms. The command gave "OKAY" twice now.
My rom works! Thanks so much.

Robbertkooiman said:
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
I used a boot.img from the "Revert to Stock" application. Sending returns OKAY but writing returns FAILED (remote: image error! (BootMagic check fail)).
First of all, can I use this boot.img with Fallout? Secondly, how do I fix the fail in fastboot?
Click to expand...
Click to collapse
Stop whatever u are doing and start reading before u brick ur phone.
Here is a link for what and all u need to know.
From adb commands, unlocking/s-off, recoveries and roms.
U can flash rom with unlock or s-off, u need not need both. Unlock is less desired but in terms of flashing rom it works just fine, all u need to remember is to flash the boot.img at each point.

rain987 said:
Stop whatever u are doing and start reading before u brick ur phone.
Here is a link for what and all u need to know.
From adb commands, unlocking/s-off, recoveries and roms.
U can flash rom with unlock or s-off, u need not need both. Unlock is less desired but in terms of flashing rom it works just fine, all u need to remember is to flash the boot.img at each point.
Click to expand...
Click to collapse
Thanks for the help, but I'm already done. I'm sorry I didn't catch this in the tutorials, but I really tried.

[Q] Trying to upgrade HTC Desire S to HTC Android 4.0 (without Windows)

Thought I would try to upgrade Android from 2.3.5 to 4.0. HTC said it would work...
I've now got it stuck, though and can't move on. I do not own a Windows computer (I'm on Ubuntu).
What I did
I unlocked the phone using HTC's website tools. It uses adb, and you have to send some key to them and they generate an unlock code for you which you then do: fastboot flash unlocktoken Unlock_code.bin
I downloaded the RUU (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068) from HTC.
Try 1: OpenRUU
I extracted the rom.zip file by using Wine, then searching on rom.zip. I moved it to ~/rom.zip
I then tried running the OpenRUU scripts which failed on attempting to flash (and failed on the automatic reflash attemtp, too):
sending 'zip' (410735 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
Try2: using hboot
I then tried with the hboot script. This is not for the "desire S" and has the wrong code in for the renamed rom.zip file. I then tried manually putting rom.zip, renamed as PG88IMG.zip into the root of the SD card as clearly summarised at (1)
I booted up into fastboot and the phone opened the zip file but then said "Wrong zipped image!".
Try3: using WinXP in VirtualBox
I then tried to run the RUU exe file in an XP VirtualBox VM. To do this I enabled USB devices for the phone (i.e. added filters for it both in fastboot and android modes), installed the stuff (HTC Sync) and tried running the RUU file.
It keeps saying "error 170 usb connection error". I've tried with the phone turned on (normally) and plugged in via USB, in charge only, Disk Drive and in USB debugging modes. I've also tried with the phone in fastboot mode. I always get this error.
...disable VirtualBox's USB2.0 support
Then it's able to connect to the phone. It ran all the way through the update process except that (a) there was never a progress indicator on the phone itself, (b) at the end it gave an 155 "image error". The recovery process then didn't really relate to anything I could see on the phone. The phone is again back in a2.3.5, so at least not bricked.
Trying to re-lock bootloader...
Then I thought that maybe the bootloader should be locked again (step 11 at (2)) - I had skipped this step before because I thought "I've just UNlocked it, why would I now want to RElock it?". But this won't work either! In fastboot mode, from a terminal, I type
Code:
$ fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
then the phone reboots itself, and it still shows unlocked. My fastboot screen (in case it's useful) says:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 20111, 15:22:13
HBOOT
Can anybody help?!
Links: (1), (2) : see pastebin dot com slash 1wKTF8Am (I am not allowed to post links here)

Rename rom.zip to PG88IMG.zip (not .jpg) then put on the root of ur sdcard (not in any folder) then boot into bootloader, it should find it

jmcclue said:
Rename rom.zip to PG88IMG.zip (not .jpg)
Click to expand...
Click to collapse
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.

I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
(yes, you flash it twice - it asks you 'please flush[sic] image again immediately' because it's upgrading your hboot)
obviously, replace YOURRUUZIP.zip with the zip file you extracted (e.g. PG88IMG.zip)
From the looks of your errors, though, it looks like your zip is simply corrupt...?

shinyblue said:
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
Click to expand...
Click to collapse
What error exactly? What does it say?

Aquous said:
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
Click to expand...
Click to collapse
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Aquous said:
From the looks of your errors, though, it looks like your zip is simply corrupt...?
Click to expand...
Click to collapse
Could be but I don't think so. I've extracted it twice, once under Windows and once under Wine and the md5s are the same. I have no way of testing the integrity of the file I downloaded since htc don't apparently provide any hashes, but I would think that the .exe file probably checks its own integrity before running.
Thanks anyway! it looks like I need to re-lock it as a first step, maybe.

jmcclue said:
What error exactly? What does it say?
Click to expand...
Click to collapse
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png

shinyblue said:
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
Click to expand...
Click to collapse
and is the PG88IMG.zip on the root of ur sdcard? im guessing not coz that green writing comes up every time u enter bootloader. make sure the PG88IMG.zip is NOT inside a folder
EDIT: heres a wee guide my mate wrote, its for the htc desire but its the exact same method.
PG88IMG Method

jmcclue said:
and is the PG88IMG.zip on the root of ur sdcard?
Click to expand...
Click to collapse
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.

shinyblue said:
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
Click to expand...
Click to collapse
Oh rite. Must be corrupt download id say, coz it should work. When u downloaded the ruu, was there a md5 next to the download? If so, check it, make sure it matched, if not then try re download the ruu and try again.

Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.

shinyblue said:
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
Click to expand...
Click to collapse
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.

jmcclue said:
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
Click to expand...
Click to collapse
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands

turekk said:
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
Click to expand...
Click to collapse
Haha what a tit i am.
I know that u need to be s-off, cant believe i forgot, what a noob. I even made 16 hboots for the desire and 4ext recovery this way. Hope thats the last noobie moment for the year :sly:

shinyblue said:
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Click to expand...
Click to collapse
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?

Aquous said:
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Click to expand...
Click to collapse
Maybe, but I think VirtualBox was working fine (e.g. HTC Sync worked).
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
I have been in touch with HTC directly (they told me initially the 4.0 upgrade was available), but they now say that this won't work with my phone.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Thing is, I don't want to risk bricking the phone by trying to get S-OFF and forcing the update because handsets are expensive! I've given up on this project for now...
Thanks to all for the help and advice.

shinyblue said:
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
Click to expand...
Click to collapse
Nope, all it does is this:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Click to expand...
Click to collapse
My phone wasn't WWE either and that was no problem for me.

Aquous said:
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
My phone wasn't WWE either and that was no problem for me.
Click to expand...
Click to collapse
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html

shinyblue said:
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
Click to expand...
Click to collapse
Yeah it was a DS. The article you link to even mentions that flashing a WWE RUU should always be possible: 'Everyone can de-brand his device easily by flashing a stock system image' (although, that sentence continues, that will make you unable to receive carrier OTAs, but that doesn't matter for our device)

Can I confirm that
Aquous said:
Code:
fastboot flash zip YOURRUUZIP.zip
Click to expand...
Click to collapse
means the whole RUU.zip as downloaded from HTC, or the rom.zip as extracted from running the .exe file within the downloaded RUU?
And also, http://www.htc1guru.com/2013/09/new-ruu-zips-posted/ says "You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first."
AFAICS the RUU I have downloaded has a different CID so won't work. Also my bootloader is unlocked (and the oem lock command fails, as mentioned above). (And I'm S-ON.)