Related
hi all. I’ve been trying to unlock desire HD for a while and eventually managed to get it sorted.
The info was on this site, but scattered around a bit, so if this is useful (i.e. all in one place) let me know..
Like all these things:
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, AND YOU SHOULD ONLY DO THIS IF YOU KNOW WHAT YOU ARE DOING...!
IT WORKED FOR ME FIRST TIME. I DID THIS AS AN EDUCATIONAL EXERCISE ON A BRANDED ORANGE UK HTC DESIRE HD PHONE.
This was done with no sim card installed at any point, just a formatted SD card.
First do a factory reset of the phone with an SD card inside, no sim.
Start the phone, and go through the basic setup, by skipping most things, just so you can get to the home screen.
Step 1. Put your device in USB debug mode.
Press 'settings', then 'applications', press 'development', then tick 'usb debugging'
Step 2. Get visionary and install to the phone to do temproot, then permroot.
The apk file you need is com.modaco.visionaryplus.r.14.apk
I will try to upload, if the site lets me. Otherwise a quick search will find it.
Once it is installed to your phone (i used the htc desktop sync tool to install the app) by connecting my phone, select htc sync as the type of connection (as opposed to charge only) then from HTC sync suite (on your PC) select application installer, then select the visionary .apk file.
Once installed, disconnect the phone and power cycle the phone. (With all the power cycles mentioned in this post there is no 'holding of other keys' required)
Once back up, go into settings on the phone and you will see the visionary logo in your list of applications.
Start the application, and you will see the temp root option. Select this, and then come out of the application and power cycle your phone.
Once you do this, and the phone is back up again, go back into the visionary app, and then select permroot option.
Then again power cycle your phone. BTW, i did not select the tick box to make the folders r/w, some instructions said to do this.
Once you have restarted the phone for the second time, it should be perm rooted. To confirm its rooted, you can take the time to install a terminal program, and run an 'SU' command, but i did not bother. I just figured that the permroot worked.....which it did...
OK we are finished with visionary, thanks visionary guys..!
Step 3:
You need to get hold of the 'HD easy radio tool', again, i will try to upload the file.
Basically you need to unzip the zip file to a folder on your PC. Connect your HTC Desire HD, and then select 'charge only' in the phone selection. (i happened leave the HTC sync suite running on the PC, even though it was idle)
Go to the folder you unzipped on your pc and run the desire hd easy radio tool_V2_2.exe. you then get several options to choose. I went the whole way and selected the first option 'super CID,s-off, unlock'
Then proceeded to do it. It took about 30s to 1m. You should get a message that it was successful.
Thanks easy radio tool guys!!
Step 4.
You need a ROM, or RUU file. I chose this one. Its quite a large file and i will try to upload. I got it from this (xda) site, but cant find it now. From what i understand this one is completely 'blank' ie it does not appear to have lots of modifications, and it appears (from what i see on my phone) to be a clean factory rom. I tried to upload, but too big for site. You may need to google it.
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
Connect your phone (again in charge only mode) and then start the 'RUU_Ace....' application on your PC.
It will start an HTC installer application that will try to connect to your phone. It will then show the current ROM you have installed, and confirm that you want to update to the one shown.
Remember to have a good charge in your battery, and don't disconnect during this point, you will brick your phone if you do. Make sure your PC does not go to sleep, and have it on external power if its laptop.
The flashing process takes about 2-5 minutes.
Once complete the pc htc application will tell you all was good.
The phone needs to be rebooted, if it has not done so already, and when it starts up, the phone will be brand new. No orange logos, no orange s/w, and fully unlocked to use any SIM card.
Good luck!
The only thing is using the 1.72 ruu you will lock yourself out of hboot and you missed off eng s-off as you would need this if you decide to flash a different Rom or update the radio
You also will not have root access once flashed as its been explain in the forums including the thread warning do not flash 1.72
The method is good but add the eng s-off and advise to flash 1.32.405.6 not the 1.72
E=Mc2
Thanks, this worked for me first time.
what does the eng s-off mean and will I have any problems with OTA updates?
sorry new to this
Thanks
smeg90 said:
what does the eng s-off mean and will I have any problems with OTA updates?
sorry new to this
Thanks
Click to expand...
Click to collapse
Eng s-off will give you access to flashing radio updates and other hboot uses and give you complete unlock and access to the phone as for the updates not sure if you will get them now
E=Mc2
leith51 said:
Eng s-off will give you access to flashing radio updates and other hboot uses and give you complete unlock and access to the phone as for the updates not sure if you will get them now
E=Mc2
Click to expand...
Click to collapse
Thanks.
is it possible to reflash with 1.32.405.6 using this guide or am I stuck because I can't root?
I'm sorry, but lol. You've made a guide which is utterly useless due to the fact you are telling people to flash an official 1.72 ruu. Bad mistake.
Sent from my Desire HD using Tapatalk
smeg90 said:
Thanks.
is it possible to reflash with 1.32.405.6 using this guide or am I stuck because I can't root?
Click to expand...
Click to collapse
Can you get into bootloader which is turn fastboot off in applications then power off then power up while holding volume down and power button keep pressing till phone powers up if it does might have a chance of going back to 1.32.405.6 let me know if it does I will help you get back if I can
Also my guide how to flash radio.img gives the same information here on how to debrand your phone with links to the threads with the tools to use
E=Mc2
liam08 said:
I'm sorry, but lol. You've made a guide which is utterly useless due to the fact you are telling people to flash an official 1.72 ruu. Bad mistake.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
What makes it worse mate is all he done is downloaded the tools then made a guide then uploaded the tools what could work well if it was the right ruu and included how to do eng s-off which is required
My guide on how to flash radio.img has also got all the info all ready and links to the right threads to do everything you need before flashing anything
So this thread is pointless really the op should have read better
E=Mc2
Hi got into bootloader ok.
Sent from my Desire HD using XDA App
Please remove the easy radio tool from the attachments and give link to my thread to download it. I like to keep count of downloads and keep it from spreading
smeg90 said:
Hi got into bootloader ok.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
good good
right here goes nothing once again like every one else if you attempt this its at your own risk you can leave the phone as it is if you choose to do so
here is a link to another thread how to downgrade to 1.32 you can follow this guide as there is a high chance it will work but it is difficult to get your head round
but the other option you could try is the way i did it when i wanted to clean my phone of everything i had done including installing custom rom with build 1.72 it did work but it does not work on every phone im told download the signed.exe ruu of 1.32.405.6 from >>>>>here<<<<< 7th one down from top of list
you will need htc sync installed then plug phone in set to charge only
extract the zip folder to the desktop
then run the ruu.exe as you would any other application double click it
follow on screen instructions yes it does take a while and it will wipe your phone of anything you had on it so do a back up of what ever you want to keep
dont forget you can back you contacts up to sd card using people>menu>export to sd card
like i said it is your choice if you use this information i take no responsibility if anything goes wrong but the second option is the way i did it and my phone is running
good luck if you do do it either way let me know how it goes
jkoljo said:
Please remove the easy radio tool from the attachments and give link to my thread to download it. I like to keep count of downloads and keep it from spreading
Click to expand...
Click to collapse
i dont blame you for saying that mate but to be honest the whole thread should be taken down as it gives false impression and tells ppl to flash 1.72 so in turn losing root
leith51 said:
good good
right here goes nothing once again like every one else if you attempt this its at your own risk you can leave the phone as it is if you choose to do so
here is a link to another thread how to downgrade to 1.32 you can follow this guide as there is a high chance it will work but it is difficult to get your head round
but the other option you could try is the way i did it when i wanted to clean my phone of everything i had done including installing custom rom with build 1.72 it did work but it does not work on every phone im told download the signed.exe ruu of 1.32.405.6 from >>>>>here<<<<< 7th one down from top of list
you will need htc sync installed then plug phone in set to charge only
extract the zip folder to the desktop
then run the ruu.exe as you would any other application double click it
follow on screen instructions yes it does take a while and it will wipe your phone of anything you had on it so do a back up of what ever you want to keep
dont forget you can back you contacts up to sd card using people>menu>export to sd card
like i said it is your choice if you use this information i take no responsibility if anything goes wrong but the second option is the way i did it and my phone is running
good luck if you do do it either way let me know how it goes
Click to expand...
Click to collapse
Will give it a try and report back
Thank you for your time..
So is it possible to debrand an/or sim-unlock the Desire HD without to root your phone because I would like to update my phone with regular ota updates from HTC ?? And because my phone is sim-locked I can't download the new software version OTA 2.2.1 ??
milosmeda said:
So is it possible to debrand an/or sim-unlock the Desire HD without to root your phone because I would like to update my phone with regular ota updates from HTC ?? And because my phone is sim-locked I can't download the new software version OTA 2.2.1 ??
Click to expand...
Click to collapse
Trying to do both at same time I do believe if its locked to network you need to create a goldcard first
E=Mc2
Can you point me to the link on how to create goldcard aor the whole proces of unlocking the desire hd,...
milosmeda said:
Can you point me to the link on how to create goldcard aor the whole proces of unlocking the desire hd,...
Click to expand...
Click to collapse
Sorry I'm at work so no where near computer I can only suggest googling how to create a goldcard it should bring up unlocker.com normally really good for info on there
E=Mc2
connection problem
Hi I have a vodafone branded DHD its not sim locked, and Its already rooted and I'm trying to flash a different rom.I've downloaded the RUU and when i run the .exe it says Verifying pda phone etc then error 170 it can't find the phone.I have it in charge mode and it shows up under device manager as. ADB interface> My HTC .I've tried every connection option but it won't find my phone.all the drivers are installed and i can use htc sync to install aps. anyone got any ideas thanks.michael
mackemsrule said:
Hi I have a vodafone branded DHD its not sim locked, and Its already rooted and I'm trying to flash a different rom.I've downloaded the RUU and when i run the .exe it says Verifying pda phone etc then error 170 it can't find the phone.I have it in charge mode and it shows up under device manager as. ADB interface> My HTC .I've tried every connection option but it won't find my phone.all the drivers are installed and i can use htc sync to install aps. anyone got any ideas thanks.michael
Click to expand...
Click to collapse
An RUU is a pre-packaged install from a vendor? Do you mean a proper custom rom?
If not, then you will unroot your phone
firstly, Im not asking for a detailed explanation of what to do here.. I can read up on various sections, but I do need steps to follow. This phone is the most complicated thing to flash, give me ODIN and a galaxy S any day.
Im trying to upgrade to the latet open Europe.HTC-SAGA 401_9 not a custom rom, my DS is the same Radio Version so thats ok.
After following the various guides, What I have so far is:
1) the Stock HTC 401_9 Rom from File Factory.
2) Ive downloaded Goldcard Helper, fitted my 2GB SD and gotten the reverse ID
3) Ive d/l'd the GoldCard Image for my DS reverse ID
4) Ive d/l'd the HexD editor for making the goldcard.
5) I know about having FastBoot OFF, USB debugging ON and the phone USB set to Disk Mode for making the Goldcard and the USB to "Charge only" when flashing.
So, now what. Can I just flash the HTC Stock 401, or do I root it first. My Hboot is 2.000.002 and its S-ON.
The phone has Virgin UK Software, but its not Locked.. Ive had both O2 and Orange sim cards in and they work fine.
I just need to know the 1, 2, 3 .. steps for flashing this stock rom
Thanks in advance
Always helps to write your full bootloader screen.
ben_pyett said:
Always helps to write your full bootloader screen.
Click to expand...
Click to collapse
Im all for protecting your product against time wasting "bricked" returns, but Whoever at HTC thought of this system wants slapped... hard, Bootloader says:
### Locked ###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822. 10. 08. 04_M
eMMC-boot
Aug 22 2011, 15:22:11
HBOOT
Then it lists on screen:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Hope that helps and hope you can give some steps. Seriously, Ive looked on here for days but there seems to be so many questions about different aspects and parts of the flashing, its confusing.
Thanks in advance
First of all, forget all about radios you know from Samsung.
At htc you can use every radio on every rom, there are only 3 possibilities you need to change radio:
It is shipped with a ruu you want to use
You face issues with radio related hardware
You want to be up to date
Ok, now to your question.
At HTC the bootloader version is important (only at stock roms).
If your bootloader has the same or a smaller version than the one from the ruu and your device had no branding, just reboot to bootloader plug it to your pc, enable fastboot usb and start the ruu.
If a branding is present and you want to stay with it, do the same with the fitting ruu.
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Tectas said:
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Click to expand...
Click to collapse
Ok I used this guide for the goldcard:
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
So, because Im not changing anything about the kernel, just debranding to an offical ROM, once I set up my Goldcard, I activate debugging, copy the RUU 401_9 to SD Root of my Goldcard, click "Image CRC" from bootloader menu and it should install it.
Is that correct?.
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
NightOrchid said:
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
Click to expand...
Click to collapse
Image crc just checks your rom, got nothing to do with updating.
The ruu itself is a exe, means a windows program , do the steps i described before with fastboot, the only difference is that you need to create the goldcard before, otherwise the bootloader won't allow (if your lucky) you to flash the ruu with the different branding.
If it fails that way run the ruu without attached device as far as you can go without closing, don't close it and search for the rom.zip at your temp folder, copy it to another folder and close the ruu, rename it, copy it to the root of your sd and reboot to bootloader and let it flash it directly, just to say it, you also need a goldcard before you do it this way.
One additional thing, be sure you got a ruu for the desire s, i just say it, because your goldcard guide is for the desire, what is no real problem there, but a wrong ruu will always fail and if it won't lead to a brick at worst case.
Sorry Tectas.. Just wont work.. I created my goldcard, extracted the RUU, changed the rom name from "disk1" to PG88IMG as you said, copied to root of goldcard, selected Fastboot then bootloader, but it just doesnt detect any image or file.
I am struggling a little with your english because you are telling me too many different ideas, Im confused... instead of telling me.. just 1, then do 2, then do.. 3, but Thank you for trying, i appreciate your help..
I will try again later..
Small thing the file you copy to the sd card must be called (case sensitive) PG88IMG.zip
Swyped form ym Dersie S unsig XAD Permuim
First method:
1. Create goldcard
2. plug in your device
3. Reboot to bootloader and enable fastboot
4. Start the ruu at your desktop and follow the instructions
5. Enjoy
If it fails make sure the drivers are installed, by downloading and installing htc sync, but uninstall it straight after you installed it, the drivers will still be present but the program itself can cause problems with ruus and/or adb.
If it still fails, try the second method.
Second method:
1. Create goldcard
2. Start the ruu without attached device
3. Go on till the only remaining possibility is to close the program, but don't close it
4. hit the windows button + r, a window should pop up
5. Type %TEMP% into the textbox of this window and hit enter, the explorer should open up and show your temporary folder
6. Search for the rom.zip (make sure hidden files are down if you can't find it)
7. Copy it to another folder i.e. the desktop
8. Close the ruu
9. Rename the rom.zip to PG88IMG.zip (case sensitive)
10. Copy it to the root of your sd
11. Reboot to bootloader
12. Choose bootloader
13. Confirm the update with vol +
14. Let it update
15. Reboot by hitting power
16. remove the PG88IMG.zip, otherwise it will update your device every time you access the bootloader
17. Enjoy
Thank you very much tectas for taking the time to sort and explain this. The 2nd methord worked just fine. However, at the end of the update flash, bootloader said:
"image on device is newer, update aborted"..
It does say that my virgin software is 2.13.351... the image is 2.10.401, so, in computer world, the numbers 2.13 is newer than 2.10. This may not be the case of the ROM itself, becasue the date is 22 Aug 11, but theyve engineered it that way probably so you cant flash it Open Europe.
The great thing is, youve taught me about the desire s and how the flash updater works, plus I have a 2GB goldcard out of it for future custom roms.. so all is not lost.. thanks for the lesson, its much appreciated.. Im gonna have a go at routing next.
It would be great to sticky this or copy it as a very Basic guide to flashing an HTC Rom.
Many Thanks again Tectas
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
I have now found that my phone is actually Locked to Virgin Mobile (has a Virgin media splash screen on boot up). Sorry for the confusion about that:
I followed the advice of Tectas and followed this:
http://forum.xda-developers.com/showthread.php?t=1399331
everything went great until I got to the end of the procedure and I only go the
"$" which after typing line 5: adb shell /data/local/tmp/misc_version -s
said "access denied" then mentioned "blue flames".
On page 6 or 7 of that thread, someone mentions this "blue flames" as being a new security mod that HTC have implemented to stop modding at all.
Is this true?.
Also, Virgin mobile and other places have quoted me £15 to unlock my DS. £15 seems alot of money, but would an unlock help (would it be worth it) for me being able to flash both Stock and custom ROMS.
I do enjoy the challenges of modding, so to me this is frustrating.
cheers
The $ indicates you have no root access, i must confess i never heard about the blue flame before, but also have to say, i never got deep into the downgrade stuff, because i used xtc clip to unlock my device, which made my device s-off and debranded.
If those Sellers use the same method, your good to go and spend the money, it saves you from a few traps you can run into with other methods (i paid €20 about a year ago), but you need to be aware that this is a hardware unlock which is irreversible, what can bring problems at warranty purpose (but must not).
Your second choice would be to use htcdev at first step and get root and so on afterwards, the downside here is also warranty, because your device is stated as unlocked at the htc database and if you leave it this way and won't use it to gain full s-off you also need to flash the kernel for each new ROM yourself with fastboot, because the recovery got no write permissions there.
If the seller would also use htcdev, safe the money, you can do it yourself, at xtc i can recommend it, but it's your choice.
Thanks for the advice Tectas. The guy in the street said it would take about 1 hour.. not sure if that helps to know. I suppose with Virgin, theyll be removing their own locks, so the virgin way might be better.
Also, the phone was bought from a 2nd hand shop, it was an unwanted upgrade someone just traded in without using it, the box it came in and the outer shell of the phone has no branding whatsoever.. thats why i was confused about it being locked.
Anyway, Ill have a think about who to go with and ill ask which methord they use before I hand it over.
Thanks again.
Tectas said:
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
Click to expand...
Click to collapse
Its Done.. phew.. hehe. After I got back to Virgin 1.31, just used the goldcard with rom.zip and it worked fine. 1 thing though, doing it this way flashes the rom in 7 stages, so what ever you do, when it reboots after the 1st install, do not think its repeating itself.. leave it. i Nearly did that, anyway, I sorted things using this thread:
http://forum.xda-developers.com/showthread.php?t=1443636
As long as you follow it to the letter, it all goes fine, the whole thread is really good support as well, so if anyones interested, read through the whole 13 pages (so far).
Also had access to the phones Recovery menu, so wiped Cach partition and did a factory reset, also probably not necessary, but backed up my SD card and formated it under the new OS.. I find this is always good on a new rom, for the file table and prevents app errors.
Happy i now know how to flash a rom, didnt quite root it yet, just flashed a stock RUU first.. which is what you should do if, like me, your new to this.
Anyway, Open Eu 2.10.401.9 is sweet and slick smooth.
Have a good one all, Thanks Tectas.
Hey Guys!!!
I've been looking around for a straightforward tutorial on how to flash back to stock.
If anyone could point me to the right thread that would be helpful, I'd would just like to set everything back to normal since I need to send the phone back.
I just want to know what the process is, like 1. Relock Bootloader 2. Flash Stock T-Mobile ROM 3. Flash Stock Recovery, something to that effect, so if any of you can point me to the right direction that would be greatly appreciated.
Thanks in advance guys:fingers-crossed:
!!!!!!--UPDATE---!!!!!!!!
So it worked everyone like a charm, so much thanks to baseballfanz, jdizzle316, and Senzune
So here's the breakdown on what I did, and again !!! This is for TMOUS and I tested with the 1.84.531.2 software !!!!
1. Re-locked the bootloader
- You can use the All in one tool from http://forum.xda-developers.com/showthread.php?t=1604677
- Or boot into fastboot and enter fastboot oem lock
2. Reboot the phone, check everything is ok
- no need to go back to bootloader or recovery
3. Boot back into bootloader
4. Go into fastboot
5. Run TMOUS RUU, go through the process and then just let it run, don't touch anything
- I found it from this forum http://forum.xda-developers.com/showthread.php?t=1744177&page=3
- If anyone needs another dropbox link let me know
6. Once it's all set you'll be back in the bootloader and all you have to do is just reboot the phone
And again thanks everyone for the help :fingers-crossed::fingers-crossed:
Are you on stock but rooted ROM or a custom ROM?
baseballfanz said:
Are you on stock but rooted ROM or a custom ROM?
Click to expand...
Click to collapse
I'm on Trickdroid like you are it seems, so I think that's considered custom no?
Just lock the bootloader and run the T mobile RUU
Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app
jdizzle316 said:
Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:
dbo87 said:
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:
Click to expand...
Click to collapse
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.
Senzune said:
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.
Click to expand...
Click to collapse
Yeah, I think you're right my build number is 1.84.531.2 so I assuming that I have to use the 1.84RUU, we'll see what the others have to say, but I'll be sure to keep you all posted once I run through the process.
1.84 is the latest and has latest radio
1.53 was previous version
So there are many tutorials out there for obtaining S-OFF for the HTC ONE S for all kinds of HBOOTS. But what about those of us with the newest model and HBOOT 2.15 and so on? Well it's been solved after months of trying.
1) First thing you're going to need is an appropriate RUU for your device. Mine is "RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2"
There is a thread for obtaining the proper RUU and how to distinguish which one you need. If you're here, you probably already have the appropriate RUU.
2) Second, youre going to need THE CORRECT VERSION of Moonshine. If your device is like mine, it will look like this: HTC One S T-MOB Windows 3.14.531.11 moonshine_ville_3.14.531.11.zip. If you have a different ROM version, get that one. Same goes for the carrier. Use your RUU name for a cheat sheet if you have to. Note the similarities??
3) Probably one of the most important steps is making sure that you have FASTBOOT AND ADB both installed and running AND detecting your device!!! I can not stress enough how important these are! Without them, you're gonna have a bad time. MAKE SURE USB DEBUGGING IS ON AT ALL TIMES! Snoop05 made a fantastic tool called 15 SECONDS ADB INSTALLER 1.1. Here's the link for that http://forum.xda-developers.com/showthread.php?t=2588979
Follow his instructions in the OP for a how to if you run into a problem, which you shouldn't if you can read.
Use the terminal command " adb devices " and you should get something like this
C:\Users\C***********\Desktop>adb devices
List of devices attached
HT26TW407378 device
This means your phone is being recognized as an adb device, which is fantastic! If not, try disabling and re-enabling USB DEBUGGING.
Boot into BOOTLOADER and go back to your command prompt and enter " fastboot devices ". You should get a reply that looks something like this:
C:\Users\C***********\Desktop>fastboot devices
HT26TW407378 fastboot
CONGRATULATIONS, you're almost there!
4) Once you have ADB and FASTBOOT both running properly, it is ALMOST time to run your RUU. First we have to relock our BOOTLOADER! It is very simple. Go into your Bootloader and make sure you have FASTBOOT USB on your screen. Once you see that, open a command terminal on your PC where fastboot is located, or anywhere if you used the 15 file I have above, as it makes sets fastboot machine wide! (exciting, huh?) In the command window type in " fastboot oem lock ". Now your bootloader is relocked and you are ready to run the RUU.
Run the RUU and allow it to finish. Reboot your device. HERE IS WHERE STUFF CHANGES!! Other people would have you ROOT. All you need to do is this:
-RE-ENABLE USB debugging and set your screen to NEVER TURN OFF. Trust me, you want this for now.
-Unlock your BOOTLOADER again
-DO NOT root
-DO NOT install SU or busybox
-DO NOT flash a custom recovery
-ONLY RUN MOONSHINE, follow the prompts, answer Yes twice and let it do its magic. My phone took 4 tries to get it done, but it worked!
If you followed my instruction to the T you should be moonshine S-OFF. Your device will be turned off when it finishes. Reboot your phone into Bootloader and profit, because you are S-OFF!
>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?
Misconception, sorry pal
808phone said:
>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?
Click to expand...
Click to collapse
Allow me to clarify.
When Moonshine is running it sends your phone into bootloader and restarts the phone.
After it checked to see that ADB and fastboot were working properly, it started doing that.
It went into fastboot to adb to fastboot to adb and had a running line of "moonshining<1,2,3,4>.........." after each time.
It did this four times before moonshine actually gained S-OFF.
It went something like this:
Waiting for device..........................................................................
Device found
Moonshining<1>.........................................................
Moonshining<2>..................................................
Moonshining<3>...........................................
Moonshining<4>......................................
Waiting for ADB Device
Waiting for device
Powering off device. Unplug and reboot device (or something of that nature)
Hope you enjoyed the moonshine.
Keep in mind this is off of my memory of what the terminal said. I did NOT have to restart moonshine 4 times. I ran it once, and was done.
It took about 10-15 minutes all together.
What do I need to know about RUU to use Moonshine
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650
fonnae said:
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650
Click to expand...
Click to collapse
An RUU (recovery update utility, I believe) can be used to upgrade your device OR (in our case) return your phone to stock. There is a sticky in the development area that has a page with an RUU repository. That page should tell our exactly how to match the correct RUU with your phone. I'm sorry I don't have the link handy, I'm not on my laptop right meow.
Sent from my One S using Tapatalk
Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?
fonnae said:
Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?
Click to expand...
Click to collapse
You should be able to! Right after I moonshined, I went right into flashing a recovery and then flashed my ROM. It was so exciting not having to boot into bootloader and the use fastboot to flash the kernel. It was instantaneous!
Flash a recovery (I've noted having trouble with old recoveries meow)
Restore your nandroid and report back here?
I'm sure there will be another user with your question. I'll add it to the OP if all goes well. And it should go perfectly. The recovery should fix root, it'll ask you before you reboot the device.
Sent from my One S using Tapatalk
Hi, I was having issues so i ran a RUU by suggestion and reset my device. afterwards I unlocked, flashed twrp 2.6.3 (2.7+ doesn't work, just boot loop) and then i upgraded to hboot 2.14 so i could install the roms i wanted. since upgrading to 2.14 i was getting new errors so i tried to wipe the device and restart and now I did that all the files are missing.
I cannot mount anything or boot, so i can't install via recovery or sideload at all, because it can't mount to anything. I can't restore or do anything else because it can't mount the cache, data etc.
I tried running the RUU again but now i am getting error 117 and it can't detect the phone, and since it has no OS installed it doesn't go far enough to register with the RUU application, or so i believe.. the phone does work fine, can access fastboot and recovery, i just can't mount or install anything else.
I am currently
Unlocked
S-OFF
HBOOT 2.14 (TextRemoval)
TWRP 2.6.3.0 (Anything higher doesn't work, will just show htc logo(20s), then go to black screen(15s or so) and bootloop
CID:111111111111
Some suggestions would be great. I've run out of ideas and spent the whole day trying different things to fix it.
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
On twrp 2.7,aren't we supposed to delete the .twrp .twrp in twrp folder by using a file explorer? I remember reading that in pandasas twrp o.p
Sent from my Desire HD using Tapatalk
I didn't need to do that, but yes, if you experience problems that's the first thing to do. Reading the OP is essential, and reading the last few pages of a thread is strongly recommended.
Sent from my Evita
timmaaa said:
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
Click to expand...
Click to collapse
Firstly, thanks for your help timmaaa.
The RUU i used was:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed.exe
I simply went to the RUU list and picked the most recent one of my carrier.
I installed it and it worked and booted, however the touch screen did not work. This confused me more because the reason I did a RUU was because the 3 softkeys were no longer working prior, and I was trying to fix it.
I was then having issues flashing roms because of the hboot, so I upgraded the hboot to 2.14 to solve this, using the method and 2.14 Textremoval file in the thread here: http://forum.xda-developers.com/showthread.php?t=2156686
After installing the hboot fine, I then went back to install candykat (to be honest all i want is a working phone, any rom works for me) and then was met with the error that it could not mount E:cache. Now i was also having issues where the bottom buttons in the Recovery menu would not respond (not the softkeys under the screen) and so i tried fixing permissions to this. Either way I got it working again - but was just other strange thing.
I just formatted the phone after mounting it in twrp 2.6.3.0 so now its ready to continue. Not sure what RUU or rom or what to go with next.
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
timmaaa said:
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
Click to expand...
Click to collapse
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
xlmama said:
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
Click to expand...
Click to collapse
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
timmaaa said:
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
Click to expand...
Click to collapse
I was able to get the RUU working and the 3.18 at&t is now installed and working. However I'm now back to my old issue of the 3 capacitive buttons at the bottom not working.
Is there anything software related to fix this or is it likely a hardware failure? When i tap any of the 3 keys, at best it will activate a touch at the lowest portion of the screen on that particular y axis. Example: I press the home key; instead of going back to the homescreen it does nothing, and at most sends a touch command just above at the bottom of the actual touch screen area.
Also, if you think it is a hardware issue, would it be the digitizer? I see they are $30 or so on ebay and figured i could fix up the phone. Everything else works fine except the damn cap. keys
http://www.ebay.com.au/itm/Genuine-...gitizer-front-panel-replacement-/261100897324
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
timmaaa said:
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
Click to expand...
Click to collapse
At most the cap. buttons will light up / flash when the phone does a particular action, but no actual response or input of the cap. buttons registers. I'm going to order the digitizer from the link above and hope for the best. It doesn't clearly say it, but I'm assuming it does come with the digi + screen in one.
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
timmaaa said:
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
Click to expand...
Click to collapse
Hmm, thats a bummer.
On another note. I just picked up the phone and unlocked it and it started vibrating like crazy, opened up the message (sms) app and started inputing random keys on the onscreen keyboard. Definitly something malfunctional with the screen. Bottom cap keys not working and random bouts of the screen randomly inputing.
The vibe crazy thing sounds like what happened to me on an inspire. Flashed wrong firmware
Sent from my HTC One X using Tapatalk