[SOLVED (GUIDE)] Locking bootloader and S-OFFing - HTC Desire S

I decided I wanted to root my phone and play around with some custom roms, but as I'm a complete hacking/modding noob I decided to go the easy route and unlock my bootloader with HTC dev then flash a custom rom. Whilst this has worked perfectly for me I decided I want to go the whole hog and re-lock the bootloader then S-OFF as I am currently S-ON, as this will make it easier for me to quickly flash multiple roms etc. I understand to re-lock the bootloader you use the command
Code:
fastboot oem lock
but I read somewhere if you do this whilst using a custom rom this can brick your device? If this is true then I want to use an RUU to put my phone back into stock then re-lock it then S-OFF. This will also mean that if I ever needed to give my phone for repair my bootloader should say *locked* instead of *relocked* if I ever S-ONed again. However I have no experience or knowledge of using RUUs and I don't even know which one to use. Can someone help me?
EDIT: My HBoot remains unchanged so will I just have to run an RUU?
I looked at the DS RUU thread and there's 3 with my baseband and region (i was unbranded):
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08...
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08...
Which one do I use? And how do I run it?
SOLUTION

take a look at my thread . this wil get you back to stock u will need to change your misc_version so you will be able top use the lowest RUU avalible. here's the link mate -----> http://forum.xda-developers.com/showthread.php?t=1609499
PLEASE USE THE RUU U WANT TO GET BACKTO STOCK THEN GO INTO FASTBOOT AND TYPE fastboot oem lock that will lock up your bootloader then you will be back to stock if u get stuck mail me on here and ill help you. another guy from india had the same problem and i helped him for 2 days straight and i got his phone back on so if u mess up in any way just mail me and dont stress about it im always here to help people mate okay in any need to speak with me give me your number and i will contact u by phone and guide u what to do and get it working 100% my friend okay take care hope u get it sorted buddy

Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002

Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse

paul.robo said:
Duke_Nuke said:
Thanks but is it necessary to flash the hboots as I haven't touched mine? Mine is still 2.00.0002[/QU
EDIT. i just read over your 1st post again so now i can help you. i will pm u exactly what to do okay
Click to expand...
Click to collapse
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse

suku_patel_22 said:
paul.robo said:
XDA is a forum meant to share ideas and help openly, appreciate if we keep it that way rather than sending out instructions on PM
Click to expand...
Click to collapse
im helping a guy who is new to this sort of modding. if this is how i want to help thats my choice. its not upto u to say how i help other's. i have my guides to help the more advanced. to help noobs i help via pm. its then upto them to share how they did it. dont judge people. he is new. chucking him into other guides and helping on here will get him confused as other people would jump in and give all diff ways to do it. i have given him the very best and noob proof way to get his phone back to stock then i have provided him the files and a guide needed to get his phone downgraded ready for revolutionary. thats my way dont like it dont come onto here and messege about it
Click to expand...
Click to collapse

yeah sorry suku but paul is being really helpful, I couldn't do it without this communication, I may write a guide or a summary of what I did afterwards

may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..

Official unlocked devices with hboot 2.0..... can not S-OFF. Must downgrade hboot.

el_roi said:
may i know how this one ended up? i'm a noob and i also need some help on this. I unlocked the bootloader from htc dev and rooted using superoneclick.. i'm still s-on with hboot 2.00.0002.. i would like to go back to stock and try another method where i can have s-off..
Click to expand...
Click to collapse
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care

that would be great.. i'll send you a pm..

I do feel that a guide should be written if other people are having the same problem... I would write one but I've forgotten most of the stuff we did

your a nice person paul.robo
its nice to know that your so helpful mate. i now know the 1st person to talk incase something goes horribly wrong with my phone
P.S. sorry for being off-topic.

paul.robo said:
if you still need help let me know ill add you on gtalk and ill help you get your phone s-off properly. after we finish you or me can write up a noob proof guide to help other people let me know mate im ALWAYS willing to help and im always online dont ever hesitate to send me a private message take care
Click to expand...
Click to collapse
Thanks a lot.. took us 2 days to solve the problem.. i'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much paul...

el_roi said:
Thanks a lot.. took us 2 days to solve the problem.. I'll try to review the things we did and try to make a guide when i have time.. once again, thank you so much Paul...
Click to expand...
Click to collapse
No problem. I'm here to help all forum member's it also took me a few days to sort Duke_Nuke's problem also but we prevailed and his phones now working again this is what i am on this forum for. To help people that need help. Any time you need me send me a PM or add me on G-talk my email is [email protected] add me and give me all details of your problem so i can get to work on getting your phone back on . but i must stress. once you have got your phone back on please write up a guide on how we got your phone back on to help others

Not really a guide as such but a rough summary of what happened:
1. First, I had to get my phone back to stock. My bootloader was unlocked so I had to lock it first to run the RUU, using the command fastboot oem lock however that will show up on your bootloader as *relocked* instead of *locked*, so your warranty will still be void, but it'll be fully locked once you have run the RUU.
2. At this point I flashed stock recovery.
3. You then need to run an RUU, to make this easier you can change the misc version, the files for which is attached. This basically means you should be able to run any Desire S RUU and it will work. However the one I originally tried didn't work anyway, so I had to try a second, which worked. You may need to look around and try different ones.
4. Then I S-OFFed my ds using revolutionary.io Just follow the instructions on your screen.
5. Finally flash the hboot.img (attached) which is necessary if you want to return your phone back to stock. Then flash your rom of choice.
As I said, this is just a summary of what I did and is not a guide to be followed by the letter.

Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmp​adb shell chmod 777 /data/local/tmp/zergRush ​adb shell chmod 777 /data/local/tmp/misc_version​c. (when everything is finished, type)
adb shell​d. (you will now be on the $, then type)
./zergRush​e. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6​f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping

el_roi said:
Let me also add what we did.
So before we started I was on
*UNLOCKED*
SAGA PVT S-ON RL
HBOOT-2.00.0002
With misc version: 2.10.401.8 –check by going to fastboot and on your computer open cmd and cd to your android sdk folder then type fastboot getvar all.
1. The first thing we did was to lock the bootloader (fastboot oem lock)
2. Then we tried changing the misc version with the one duke attached (or see attachment on see previous post), but it didn’t work. So we tried another one (see attached files). To see if it works, just run the .bat file with the booted device connected to the computer. make sure USB debugging is enabled and fast boot is disabled. If the screen just flashes it means it’s not working. You can double check by looking at the results of fastboot getvar all.
If the attached files don’t work, try entering the codes manually. Still, your phone should be connected with USB debugging on and fast boot off.
a. Open cmd and cd to the tools folder of the attached file.
b. Once you’re sure that your on the tools folder, enter the following codes (one code per line. So you’ll have to press enter after every code):
adb push misc_version /data/local/tmp​adb shell chmod 777 /data/local/tmp/zergRush ​adb shell chmod 777 /data/local/tmp/misc_version​c. (when everything is finished, type)
adb shell​d. (you will now be on the $, then type)
./zergRush​e. (some things will appear, wait for it to finish. It will say on the last part “[+] Killing ADB and restarting as root... enjoy!”. Then type)
adb shell /data/local/tmp/misc_version -s 1.27.405.6​f. After it’s finished, your misc version will now be 1.27.405.6. You can double check that again.
3. Now run the correct RUU for your region/brand. My phone is unbranded and it’s European so paul gave me an unbranded European RUU. You can check out his thread for the RUUs here.
4. Once the phone has booted back, turn on USB debugging and disable fast boot then go to revolutionary.io. Follow the steps on how to s-off.
5. Then flash the eng.hboot.img that duke attached (or see attached file on previous post). To do this, first you should download the file. Then copy the file on your android sdk folder. Connect your phone to your computer and go to fastboot. Open cmd and type “fastboot flash hboot eng.hboot.img” (without the “” of course ). After it’s finished, reboot to bootloader. Now your hboot will say saga pvt eng s-off.
DONE. All credits to paul.robo.. Thanks for helping
Click to expand...
Click to collapse
hello im having problems with this guide i cant get the second line
the comands say that there is no such file or directory
.. pls help

It is a while ago when i did this. My problem was a file with a. .c after it. I googled for the correct file. This was somewhere to find in xda. I think you need the file without the. . c.
Sent from my Desire S using xda app-developers app

first line is missing, should be:
Code:
adb push zergRush /data/local/tmp

Related

[solved] s-on hboot 2.00 downgrade with explaintion

Hello all,
I've been busy searching for a way and found a lot but all keep on failing.
I have the following bootloader info:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011.15:22:13
What i want.
I want to revert back to the stock hboot of 0.98
I allready installed adb and fastboot but for some reason when I'm in fastboot on my phone the adb can't find the device (don't know if that is the way it should be :S).
i tried different guids and tricks to get there like superoneclick and android flasher but super crashes and android flasher gives me an error. (cant get the error right now, but when i get I will post it here.)
Is there someone that knows a good guid or something else that can help me.
regards.
edit / solved
I found the problem.
i needed to lock the phone before i could do another RUU update.
when i locked the bootloader with : fastboot oem lock it worked
For the people reading this
Just so people are searching for the problem and find another post saying they solved it and dont tell how or the answer is on page 500
So this is what i did:
1. i got to this post.
There it explains how to do it.
BUT there are a few changes i made.
so follow the following steps (this worked for me):
1. Installed all necessary android related drivers. (google it) also be sure to have ADB and FASTBOOT installed.
just search this form.
2. "turn of fastboot" On the phone go to "settings > power" then scroll down to find the fastboot option and turn it off.
The go to "settings > application > development" search for USB debugging and turn it on.
3. Be sure to keep the phone connected to the pc and keep it on "Charging only".
For this all to work you need the HBOOT to be unlocked.
To check this turn the phone off and than turn it on and press the volume down + power button.
You will now boot into the bootloader.
If you phone shows pink ***LOCKED*** go to HTCDev.com and unlock it.
http://htcdev.com/bootloader/
4. Downloaded files from this topic: http://forum.xda-developers.com/show....php?t=1399331 (misc_version ONLY!!!) !!!!!this is only when your phone was allready rooted. (sorry dont know more about this. my phone allready had the root options.)
Unziped the downloaded files in a folder. Best for me was just put them on the "C:/desire/" folder (just create it.)
5. if your in the bootloader the reboot the phone. Be sure the phone is in charging only mode.
6. Go to the CMD of your pc.
go to start and use run, then type cmd -> press enter.
Or press windows flag + r
navigate to the folder where the previous downloaded file is.
7 Follow the following commands (every line is a new command so use enter after each line )
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.27.405.6
The last command will change your version information.
8 Now if you dont allready have it download the RUU file that is you phone's original
9 Now reboot the phone in the bootloader like before (volume down + power)
When there after the intial load press the power button again.
This will get you in the fastbood menu.
10 Now go back to the CMD and type the following
fastbood oem lock
this will lock your phone and you can not boot to you rom.
With my phone it said *** RELOCKED *** SECURITY (something)
11 Now just run you RUU and it will (at least with me) run and your phone is back to normal.
Hope this helps you.
Took me 20 hours to find the solution.
[/qoute]
Here's a way
I was in the same boat as you just last night! There is already a post about this, but i wont get on a you, im new too
Heres a link:
http://forum.xda-developers.com/showthread.php?t=1399331
If you are on software version above 2.10.something (im not sure of exact number) or you got your update after November (I think), then you need to use this guide:
http://forum.xda-developers.com/showthread.php?t=1443636
Hope i helped, remember, no HTCdeaf (see what i did there?) = warranty still intack (as long as you return to stock and S-ON)
mountain_maniac said:
I was in the same boat as you just last night! There is already a post about this, but i wont get on a you, im new too
Heres a link:
http://forum.xda-developers.com/showthread.php?t=1399331
If you are on software version above 2.10.something (im not sure of exact number) or you got your update after November (I think), then you need to use this guide:
http://forum.xda-developers.com/showthread.php?t=1443636
Hope i helped, remember, no HTCdeaf (see what i did there?) = warranty still intack (as long as you return to stock and S-ON)
Click to expand...
Click to collapse
thnks for you comment
I allready tried the first link but those didnt work for me.
Also just tried http://forum.xda-developers.com/showthread.php?t=1482532&page=2 (fist post) and it sadly enough didnt work either.
i think the wholee problem is because of a s-on and the hboot i just cant seem to change.
I used the misc_version to and then tried to run the RUU file from the desktop.
That gives me an error 501 image update error.
when i run the ruu and get te rom.zip from the temp directory and rename it to PG88IMG.zip it does run and takes about a 1 minute but doesnt change anything.
any ideas what could be going wrong ?
possible help
I think error 501 is because you have relocked the bootloader.
command is:
fastboot oem lock
hope for the best (i would also look around for info from other people, im quite new here)
Could i also ask why you want to downgade?
If you only want to use custom ROMS and recovery, you dont need to downgrade, just go here:
http://forum.xda-developers.com/showthread.php?t=1525100
That is the HTCdev way, which voids your software warranty, i think this prevents radio and engineering HBOOT flashing though, which could possibly mean this way is potentially safer. (im not sure but i think flashing radio's is much more likely to brick if you get the wrong one)
If you need to use an RUU because of an language or area reason, then you need to downgrade. (or wait for revolutionary to be updated)
hope i helped, but as i said, there are other topics already about this, in Desire s general, where people could help you much more than i can. Also, while typing thanks is nice, using the thanks button (in the lower right hand of a post, i couldnt find it at first) is cleaner and helps me too
Good luck
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
John ssUpTrad
controvi said:
thnks for you comment
i think the wholee problem is because of a s-on and the hboot i just cant seem to change.
Click to expand...
Click to collapse
The reason for downgrading IS to S-OFF, at the moment, as far as i know, downgrading is the only way to change HBOOT and S-ON
I know, annoying right?

So what do I do now?

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.

[how to]unlock downgrade then s-off desire s

It's the steps I took to get s-off after upgrading the phone and keeping it until the warranty wore out
1.Follow amidabuddha’s guide to abd and fast boot installation(be sure to thank him its the button on the bottom left of the post)
here:
http://forum.xda-developers.com/showthread.php?t=1272595
2.Go to http://www.htcdev.com/ and follow the instructions to unlock your phone
“note use all other supported models”
3.Install this program onto your phone http://www.4ext.net/get.php?apk
and use it download the latest stable version of recovery and transfer and unzip recovery.img file to where you installed fastboot and abd on your computer.
4.On your phone go to settings/power and make sure fastboot is turned off and then turn off.
Hold the vol down button and power button until you enter the bootloader connect the usb and select fastboot using the power button as select and vol buttons as up and down
5.Now on the computer go to where you installed fastboot and abd and right click while holding shift and select open command window here.
Type the following into the command window
fastboot getvar cid(“write this down and keep it for future knowledge”)
fastboot flash recovery recovery.img
Extrecovery should now be installed
Now type:
fastboot reboot-bootloader
And select recovery from the menu
6.In recovery go to install from sd card and then choose a zip from sd card
Should be something like this cwm-superSu-v0.94.zip
http://forum.xda-developers.com/showthread.php?t=1742522 (“you can download it from here plz thank ArcMan09”)
7.reboot the phone this time letting it boot up
connect the usb select charge only
in the command console
type
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version –s 1.27.405.6
Exit
adb reboot-bootloader
What was entered above should now actually appear in fastboot
8.now use
fastboot oem lock
Whole bunch of stuff comes up but most likely your now locked again
9.Go here
http://pastebin.com/raw.php?i=YcnM8Sr9
rember that thing I told you to write down find it in the table and take note
in fact write the corresponding one down as this is tell you the ruu you must download
Now open the required ruu on the computer
You can download from here(“plz thank football”)it’s the button on the bottom left of posts
http://forum.xda-developers.com/showthread.php?t=1002506
it should be something like this:(this may not be the right one for your phone you should have checked above)
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed
10.connnect your phone to your computer in fastboot like before
open the ruu on the computer
let it run following the instructions
now if you check the hboot it should say your have something 0.98.0000 S-ON
this means you can now use http://revolutionary.io to s-off your phone
now go back up and flash your desired recovery and rom of your choosing as well as superuser
I recommend the recovery we installed before("you will have to flash this through fast boot again")
Either
Viper Saga
or
Fallout Evolution
Both are senses roms
Recommended things to install after rooting your phone
a rom backup app:Rom manager:might come with the rom
an antivirus: avast(“you can use the root install method”)
4ext recovery control-(or updater for free but control will save you a lot of time)
Superuser but that will likely come with the rom but if it doesn’t
What ever else you want your done your phone is rooted and
I'm pretty sure this is how I did it please post questions or mistakes I've made on the board and remember to thank the creator of each of the links(it takes a lot of time to write these out) I'm really just collating them into something nice and easy to read as I jumped around forums trying to find the answer.
Hope this helps
I Would Like to thank some outstanding members that have helped me create this guide (please thank them they absolutely deserve it)
amidabuddha
n0elite
Skanob
Football
ArcMan09
if I have missed anyone im very sorry i've far too many pages up here just trying to recreate what steps I took to complete this task.
In other words I have to:
1)flash to a custom rom
2)flash to official ruu
3) s-off
4)flash to custom rom again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?
Billlis said:
In other words I have to:
1)flash to a custom ROM
2)flash to official ruu
3) s-off
4)flash to custom ROM again
And why I shouldn't stay at first step? will I have a problem if I have a rooted s-on phone?
Click to expand...
Click to collapse
well no you are flashing a recovery the first time then downgrading the ruu then s-off and then flash to custom ROM.
I don't know if there are newer methods out there im currently getting a new phone so im not much help in the experimentation side. but it should be pretty solid the tricky part i found was getting a hold of the right ruu all that saving the misc version and stuff is really important as its needed to downgrade.anyway good luck let me know if it works for you i haven't got too much feed back on this topic. oh and rooting is defiantly worth it opens up the phone completely and everything seems to work all of a sudden.:cyclops: YES YOU WILL NOT BE ABLE TO ROOT AN S-ON AKA SECURITY OR LOCKED PHONE. this of course refers to kernel which is normally locked(s-on) there is a bunch of other uses such as being able to set root to open items very handy worth buying (support the devs buy apps you like!!). you can just do a search on good play is it for root only or s-off apps wich will usually have some usefull tools anyway hope that helps.
I have just unlock my desire throught HTC-dev (still S-On) installed a recovery and a custom ROM. I suppose this is not the right procedure but I have not any problem with root-access apps now. btw its the third time that I have rooted this phone
you will be able to install and run these apps normally but the will be either not working or have limited functionality
use this to check your root and install these programs if you dont have them
root checker does what it says
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ.
busy box required for root
https://play.google.com/store/apps/...251bGwsMSwxLDEwMiwic3Rlcmljc29uLmJ1c3lib3giXQ..
superuser sets permissions for apps
https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=related_apps
as I said before it's the third time that I root my device so I know the required apps. Btw Root checker says that I have root access and any other root-required program works fine till now
First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ
WoZZerZ said:
First of all, thanks for this tutorial, it got me quite far!
There's one problem:
I can't get any further than step 9, because the thread with the RUU's doesn't exist anymore (http://forum.xda-developers.com/showthread.php?t=1002506)
I can't downgrade now, I've searched the whole internet for the version I need (HTC-Dutch HTC__E11), but I can't find it.
The only thing I found is from HTCdev, but the file I get from there is a .tar, and I don't know what to do with that.
I can unzip it, but the only thing I get from the file are a bunch of folders and files I can't open.
Can you please help me?
//WoZZerZ
Click to expand...
Click to collapse
Try this site, i think they are still up http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
jugg1es said:
Try this site, i think they are still up [site]
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?
WoZZerZ said:
Thanks, but I couldn't find the version I need (HTC-Dutch HTC__E11) :crying:
Do I REALLY need to use that exact version?
Click to expand...
Click to collapse
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
jugg1es said:
Now that, i don't know. Sorry.
“Whenever you find yourself on the side of the majority, it is time to pause and reflect.”
― Mark Twain
Click to expand...
Click to collapse
Since the TS uses a 1.47 version as an example, and I only found one European version of 1.47, I'm downloading that version.
I'll try to install it tomorrow.
edit:
I tried it today, and it doesn't work... The program crashes when getting device information
edit 2:
Wait, I can't get past step 7 either.
When using the first command, I get this message:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
I tried it again with USB-debugging enabled, and this was the result:
C:\android-tools>adb shell chmod 777 /data/local/tmp/misc_version
Unable to chmod /data/local/tmp/misc_version: No such file or directory
Could somebody help me please?
EDIT 3:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)
WoZZerZ said:
I found out I had to push misc_version on the phone first, (not said in this tutorial), so I did that.
Then I could chmod it, and it worked fine.
I relocked the bootloader, and tried to install the RUU, but the RUU keeps crashing whenever it starts...
(Sorry for the double-post, I couldn't find out how to delete my other post)
Click to expand...
Click to collapse
Make a GoldCard and your phone should eat any RUU :highfive:
VnnAmed said:
Make a GoldCard and your phone should eat any RUU :highfive:
Click to expand...
Click to collapse
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Try here http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
The third-rate mind is only happy when it is thinking with the majority. The second-rate mind is only happy when it is thinking with the minority. The first-rate mind is only happy when it is thinking.
—A. A. Milne
O rly?
WoZZerZ said:
I don't think the phone is the problem here, the RUU keeps crashing while the phone is ready to accept it.
The problem is that the list of RUU's on XDA-developers is gone (see step 9 in the tutorial, the link is dead), so I might not have the right version.
I've searched everywhere, but I can't find the exact RUU I need according to the tutorial.
Click to expand...
Click to collapse
Yea, but as far as I get it that's what GoldCard is for. It fools your phone so the bastard is thinking that the software you're flashing is from nurturing bosom of mother fabrica so it swollows it whole no matter what it is and cries for dessert. I have UK vodafone Desire S and with GoldCard I have flashed official Asia Gingerbread Update
The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium
basd43 said:
The exact same way i downgraded and achieved s-off on my Desire. I believe i have the correct RUU still somewhere on my laptop. I'm not at home at the moment but i can put up a dropbox link (if i'm not mistaking and still have it) tonight if you like?
Edit; typo
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
If you could do that that would be awesome!
WoZZerZ said:
If you could do that that would be awesome!
Click to expand...
Click to collapse
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x
basd43 said:
Could you humor me and strat the Phone in fastboot, then open a command prompt and type; Fastboot getvar version main. Please post the version-main here. Just to be sure
---------- Post added at 03:01 PM ---------- Previous post was at 02:29 PM ----------
Here´s the db link, its still uploading so if its not there now wait a while. There are (or gonna be) 5 RUU´s in there, just check your version main and pick the one you need
https://www.dropbox.com/sh/engsv5p1xf9vy63/jOUwJUB55x
Click to expand...
Click to collapse
The bootloader THINKS the main version is 1.27.405.62, but that's the whole point: I had to do that in the tutorial when chmodding misc_version.
I'll try one of the RUU's thanks
EDIT:
It's installing now, I've got further than ever before! Hopefully it all works, I'll let you guys know in a few minutes
EDIT 2:
IT WORKED! Thanks!
I'm on HBOOT 0.98.0002 now, so I'll be able to achieve s-off, THANKS!
I can confirm that this tutorial also works to downgrade from HBOOT 2.02 to 0.98

[s-off] hboot 2.15 htc one s flawless

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

Seeking assistance to return to stock ROM

Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Between S-OFF, S-ON, firmware, recovery, new partition layouts, old partition layouts, OTA, Stock, kernels, custom ROMs, rumrunners, firewaters, various errors, root, adb, fastboot and other meaningless pieces of broken English, I am giving up. I have spent more time ****ing with my phone than using it in the past week.
I currently run a 'version' of Sense 5.5 made by tr1gg3r3d, on Android 4.4.2. Ultimately the only thing I wanted to achieve was to have an ordinary version of Sense but without the extraneous apps that clog it up. My phone is unlocked and 'tampered' (whatever the **** that means). What I have right now does not appear to update correctly and does not run certain apps that dislike root. The SD permissions do not work.
It is more or less useless for what I need it for.
I saw a ROM for Sense 6 here that requires 'S-OFF'... after spending 3 days jumping through hoops and following badly written instructions for 'S-OFF', and failing each time, trying around 4 different ROMs and script files that tell you nothing of what they're actually doing, I have given up trying to achieve 'S-OFF'. Do I even know what 'S-OFF' is? No.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Your 3days of reading have obviously been a complete waste of time bud as you posted in the wrong thread [emoji33]
Maybe you should have also read and understood the implications of unlocking, rooting your phone before you done so. It is well documented that certain apps eg.. banking ones etc will not work on rooted devices.. BUT there are certain modules created that can cloak root and may allow the app to work. As for removing unnecessary apps... There as also scripts/tools available to do so. It's all here on xda!
Slating a devs Rom that they have spent countless unpaid hours to bring to the xda community (that works flawlessly) is not the way to get help, nor is slating the guides/advice that other members have taken the time to post! Seems that you want the best of both worlds. There are guides on here that will help on whatever you choose to do if you can decipher all the babble/jargon and meaningless broken English.
dlyon said:
Hello,
I have an HTC One Mini (m4) and have spent approximately 3 days trying to grasp various pieces of jargon and babble of the Android community without success.
Can someone give me simple instructions on how to achieve the following:
A phone running HTC Sense 6 (or even just 5.5) that behaves normally, isn't gimped with pointless graphics and allows the extra apps to be removed.
Preferably 'unrooted' as I use apps that dislike root.
Ideally recognised as 'official' HTC so that updates can be delivered without having to spend a week wading through 90 page forum threads.
Thanks in advance.
Click to expand...
Click to collapse
Had a similar experience myself trying to return to stock, for me I was getting cheesed off with the bugs and lack of working bank apps on custom ROMS.
I fixed it by following, and reading in between the lines, on this fellows instructions here.
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
I posted a similar help thread myself a few days ago, someone has replied to say S-OFF isn't crucial to doing this so worth a go maybe. I however did get S-OFF by using the method detailed here.
http://forum.xda-developers.com/showthread.php?t=2573479
I should tell you I was on HBOOT2.19. Not sure how important that is.
So here it was I did to get S-OFF
You've obviously got ADB working on your device so lets skip that.
1.Download revone: http://revolutionary.io/revone and copy it into the same folder as your ADB.
2. Open a CMD prompt and type these commands:
Code:
adb push revone /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/revone
Now wait a minute. I found I always got kicked out of the shell after 20 seconds or so, if you do then run adb shell once again.
3. Now type the below text. It is case sensitive so make sure that -P in the second command is uppercase:
Code:
cd /data/local/tmp
./revone -P
4.You'll get an error message, it should be "-2". This is good. Restart your phone using the power button.
5.Once you're back in open up the shell again and run the following commands:
Code:
adb shell
CD /data/local/tmp
./revone -s 0 -u
BAM! You're now in S-OFF mode.
HBOOT 2.2
I used this thread to get to HBOOT 2.22
http://forum.xda-developers.com/showthread.php?t=2584810
Whilst the instructions are fairly simple I will say it is case sensitive. So when you do
Code:
fastboot oem rebootRUU
the RUU has to be in capital letters.
How to return to stock
1. First you need to get yourself TWRP recovery from here: http://teamw.in/project/twrp2/216 and copy the .img file into the same directory as ADB and fastboot.
2. To flash the recovery you need to go into fastboot (hold the power button and the and the volume down button together from a cold boot) and type from a CMD prompt
Code:
fastboot flash recovery recovery.img
where recovery.img is the name of the download.
Mine was called openrecovery-twrp-2.7.1.1-m4.img so I'd use this text:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
3. Once you've flashed the recovery go into recovery and make a backup from the backup menu.
4. Download every file from the link provided in the first post here:
http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799
5. You're going to have to use WinRAR or 7Archive to unzip the RAR files. You'll get a random folder and a stock recovery.img file.
What I did (or eventually did after lots of trail and error) was attached my phone then deleted the backup content in the TWRP folder. I did NOT delete the folders. Just the files within. Then I copied the extracted content from the download folder into the backup folder I'd just emptied on the phone.
6. Now drop back into the recovery again. First make sure what we did in step 5 worked. If you go into Restore can you see the files we generated earlier? Brilliant. Wipe the cache, factory and delvik (I think Delvik is in the advanced settings, obviously don't have it to hand now i'm back on stock!)
7. Now run a restore which should take a few minutes.
8. Reboot the phone but drop straight back into the Bootloader (power and volume down button pressed)
9. If you haven't copied boot.emmc.win into the ADB folder do so now. Whilst you're at it copy the stock recovery.img file into the same folder and rename it to stockrecovery (take the space out).
From a CMD prompt type :
Code:
fastboot flash boot boot.emmc.win/
10. Now we flash the Stock recovery using:
Code:
fastboot flash recovery stockrecovery.img
11. Now relock the OEM thingy by using
Code:
fastboot oem lock
BAM! You're back to a stock albeit a really crappy version based somewhere in the Middle East. But fear not. Boot in, setup your phone and in the Settings area you can run a software update. This will take you to Android 4.3. Once you're in run another software update to go to 4.4.2 with Sense 5.5. Once you've done that do yet another Software Update to get to 4.4.2 with Sense 6.
At this point I did a factory reset from the settings menu. Not sure if it was needed but just wanted any legacy crap completely killing off.
Also you'll see a message about it being a test device. I Google'd it and people said this is because you're S-OFF. It's not important. Nothing is going to HTC, it's merely a log file thingy.
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
danapoint said:
elmuziko.
Absolutely brilliant post. I can verify that your method to s-off the phone and update to 2.22 works perfectly. I did it 2 days ago.
I changed my cid using supercid. Do you think I should return my cid to its original value before attempting to return to stock or does it matter??
Click to expand...
Click to collapse
Hiya mate
I didn't do any of that at all, although I didn't change my CID knowingly so if it did change, I didn't change it back.
Been on stock a week now with no problems whatsoever. Working like a dream.
Cheers
thank you button is not enough
elmuziko said:
And that my friend, is how my three day headache got me from a rather buggy custom ROM back to Stock. Enjoy.
Click to expand...
Click to collapse
you know what, i just registered to this site to thank you.
i followed your post step by step and BAM, i am in back to stock rom.
thank you, it feels so good
ps: i skipped S-OFF step, so it is not a must.
Help my
Not message for phone unlock bootloader unlock token chek successfully
Failed to Get S-Off
Before my Question:
My HTC ONE MINI Details:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.28.40e.00.24
OpenDSP-v19.2.0268.0927
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2015, 15:21:25.0
Ok, Now, I bought this Mobile in Dubai, Middle East and while i was waiting eagerly for Lollipop Update and the HTC did the cheating, i decided to try some custom roms and in between the process i wiped my internal memory which means i lost my original stock rom. Somehow i got this M4_4.14.401.1_Stock_v3.0.0 flashed it and now my mobile works flawlessly, the thing is the mobile is "TAMPERED" "UNLOCKED" & "S-ON", i tried all the process to S-OFF, i tried sunshine but spending 25$ on something which is available free, i would not do that. Can you please suggest me what is wrong that i am doing here, because i found one more option which says i have to downgrade my HTC ONE MINI to S-Off, Pity is that to downgrade i need my mobile to be S-Off. I am really exhausted and would appreciate alot if you can help me get S-Off. There are my links which are broken, like the revone after a lots of struggle i downloaded it. i have posted 3 queries on XDA forum but none has been answered. I would Really Really appreciate if you can save me from my misery.

Categories

Resources