Related
Hi guys,
The day has arrived:
AlphaRevX now includes support for the Desire S (HBOOT 0.98).
Hop on over to http://alpharev.nl/x/beta/
We'll use this as a support thread.
This version will also download and flash custom recovery if you want to, after getting S-OFF.
Note: the very first download missed some DLLs for the windows version, that should be included now.
Note2: There have been some reports (on dinc2) that the windows version might not always work like it should. Please report errors with that as descriptive as possible. The linux version should always work like it should.
great news! is there a guide for a noob like me on how to s-off my Desire S using this software? thanks
FAILED
Hi there,
I've just tried to S-OFF my european Desire S several times, following the instructions posted for the Incredible S. Alpharevx connects to my phone, reboots to fastboot, waits, reboots to fastboot (again), waits .. then says FAILED.
I wonder if I'm doing something wrong or there's a problem with the windows version as you reported.
Thanks for the effort any way
EDIT: Downloaded the Linux version and it worked. I am now S-OFF
Hi, AlphaRevX didn't work for me on Windows either, but it succeeded on Linux (Ubuntu 11.04). Anyway, thanks a lot for your effort, AlphaRev team
@taipan_snake - Could you please guide me on How To S-OFF it on Linux ? I also have a Ubuntu installed. Thanks !
@badeaioan:
Well basically these are the steps that worked for me:
1. Download the Android SDK from here: http://developer.android.com/sdk/index.html
2. Unzip and go into the folder you just downloaded
3. Run the 'android' application within the 'Tools' folder
4. Select 'Available Packages', and select 'Android SDK Platform-tools' and 'Android Compatibility package', and install these.
5. Make sure ADB can see your device by cd-ing into the SDK folder, and then the 'platform-tools' folder, and running './adb devices'. Your device should show up (mine had a string of question marks, but it should work as long as it is there)
6. Download AlphaRevX and get your beta key
7. Run AlphaRevX as root, and follow the instructions, and you should have S-OFF
Hope this helps
Sad windows version under review
-I tried the incredible version(long time ago ),(no SDK used) and it said my phone not suported bla bla, but the fact is that it was detected (with usb debuging on and phone conected in charge only)
one question: Do i need to get temp root for this to work?
Finally !!!!! AlpharevX - a software s-off. This is awesome, for s-on guys for obvious reasons, and for s-off guys too. This is surely gonna increase dovelopment here !!!!!
Thank you for your response.
The problem starts on running AlphaRevX.
When I open gksu and try to open it, nothing happens. Am I doing something wrong ?
@badeaioan:
I just used Terminal, cd-ed into the directory, and ran 'sudo ./alpharevx', and it worked for me...
EDIT: I think I now know what you mean... it's only a command-line app, so it would only run from terminal...
Thank you again. Finally I am S-OFF !!! Thank you AlphaRev X !
Also now S-OFF! thnx to the AlpharevX guys!
also s-off great thanks! Let the rom madness begin.
That's a great news! But question, before I try to S-Off.
Can S-on be restored using RUU after Soffing my device?
I would like to keep some warranty options available after all
/Chie
It's working on my Desire S. Finally S-OFF-ed...
Thank You!
Hi
I am new to linux and i am getting a "waiting for device " message when i try to run the linux version.
I have googled to my wits end but can't work out why it is not detecting my phone.
Can anyone shed some light please??
@jh787:
Hi, have you installed ADB and made sure it can find your device?
great news for all you s-on´ies
hope to see some of you around in my development post for saga lbc mod.
happy rooting, flashing and playing
regards
Hopefully things brings more dev to the htc desire s
Works perfect from Linux (Ubuntu), and so easy too!
If it isn't working, remember you need to have USB debugging on for ADB to find the device.
Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$
I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]
I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.
Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000
HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.
I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?
@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.
got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one
im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?
Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA
just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems
Getting this while trying to re-unlock evo 3d ics. hboot 1.58.
It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )
i got same problem w my Z3 plus hbot will work on my z3 plus????????
Hi Guys,
Apologies if this has been discussed before. I have looked for answers everywhere and i could not find any.
Ok, I have a Desire S which is branded to Telstra (Australia), I was sick of all the useless app that Telstra had put in and wanted to get rid of all those.
I used revolutionary method to get it s-off and install Generic Firmware. After that i was happy not having any of Telstra's bloatware on the phone. Then came the update of 2.3.5 and as usual downloaded the firmware and used RRU to Update. Big mistake on my part, i didn't read anything and just tried to push RRU on the phone, the result was White screen with HTC logo and nothing past that. Tried everything no luck, then looking for answers, i found a solution to remove revolutionary, I could see revolutionary gone in HBOOT but the phone would not start.
to solve this i went to telstra to send it to repair, warranty was there and when telstra asked what happened, i said i was updating an app and it went to this screen, Tech guys said this is the similar 3rd problem in a day. so after 5 days the phone got repaired, New IMEI number and logic board had to be replaced.
Now all over again i have bunch of telstra bloatware on the phone. I want to get Generic 2.3.5 with sense 3.0. what is the process to follow so that i don't make the same mistake again?
All i want to do is get it s-off and install generic Firmware, the easiest way possible something like revolutionary. I tried going with ADB but found a bit risky.
Any advice in getting Generic HTC Desire S (2.3.5 with Sense 3.0) the easiest way would be helpful. Thanks in advance.
HBOOT info:
SAGA PVT SHIP s-ON RL
HBOOT-0.98.0002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 30 2011,17:29:31
Thanks
To get a generic firmware from some other area, you need to get Super CID. I don't know much about it, just that CID's like a region code, Super CID enables you to get generic ROMs from any region. Only XTC Clip can do that on a Desire S as far as i know. Flashing a custom ROM after Revolutionary S-OFF is a better option....
Listen, I really recommend you to use a Custom ROM based on the update if you are ready to S-OFF. Hyperion is much faster and has a lot more features. Hell, if you do S-OFF, why settle for Sense 3? Get Sense 3.5. I recommend endymion.
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
zryvffn said:
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
Click to expand...
Click to collapse
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
ben_pyett said:
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
Click to expand...
Click to collapse
Hey Ben, Thanks for this, I went ahead and got the ROM as you suggested. Installed the base verison, then the add-on and the update. I have been palying around with it and so far loving it.
Only problem tough, I cannot use Market. I can open market look for apps and download, but when it starts to install, the phone re-boots. any known issues with this and is there a workaround to sort this out.
Ok, so here is what i did, Flashed Base version again and market started working again with no issues. Another issue which is not so much of an issue but only at night, why does the soft keys don't lit up on Desire S?. any way to fix these. Thanks guys.
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
sadsac said:
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for that, I did a search for the issue and did the same thing as you had advised, but didn't work. Then I flashed the base version again and then the update, which worked. Don't know what had happened there.
But yeah loving the new rom and i would say was a better move to be on a custom ROM and getting rid of Carrier's junk installed.
Cheers!
Ok, so instead of creating a new post i have decided to post it here since it is already been discussed.
I was happy with rooted phone and endymion Rom and was happy until my phone started heating up and restarted on its own as if it had a mind of its own, I called HTC and they advised to send it for repair, i had to unroot the phone and sent for repair. Got the phone back with updated version and i need help rooting the phone.
when i boot the phone in fast boot this is what i get:
****LOCKED****
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Aug 22 2011, 15:22:13
Android Version 2.3.5
HTC Sense Verison 3.0
Software Number: 2.14.841.4
Baseband Version: 2.14.841.4 CL 184593 Release-Keys
Now i need to Root the phone again so i can be another happy user of endymion.
I am looking at this guide and needed help.
http://forum.xda-developers.com/showthread.php?t=1443636&page=1
The oldest RUU i can find for my provider is RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.exe
I was reading the guide and this is where i am confused.
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6 .
./misc_version -s 1.27.405.6 do i change this to 1.36.841.3 or leave it as it is?
Any help will be greatly appreciated.
Thanks.
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
chninkel said:
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
Click to expand...
Click to collapse
Thanks for that, yes i did follow the guide, and then got stuck again. The problem i am facing is after pushing all the files as of the guide, i run tacoroot the phone restarts and all i get is a red triangle with exclamation mark in it and nothing else happens.
then to get rid of it, i pull out the battery and do a complete factory reset. I have done this about 5 times now but still the same.
Also tried using super one click but that dint work either and freezes on waiting for device.
anything i have missed or is there any other solutions, any GUI programs or video to help if i am missing something.
any help is appreciated.
Thanks
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
chninkel said:
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
+1
You can pull it out as often as you want..but at least you should know the risk.
Sent by my fingers to your head
chninkel said:
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
I don't understand,"boot into original recovery". To try i booted the phone in HBOOT and pressed recovery and same thing the triangle shows. am i missing something here.
EDIT: I went till the last step and this is what i get "Patching and backing up partition 17...
Error Opening backup file.
#"
any idea
zryvffn said:
To try i booted the phone in HBOOT and pressed recovery
Click to expand...
Click to collapse
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
chninkel said:
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
Click to expand...
Click to collapse
Thanks dude, this worked and going thru revolutionary. i did some changes in the steps and will update what i did in a while after i get a rom installed.
Thank you everyone for help and support. i was able to downgrade my HBOOT and install a custom ROM. It would not have been possible if you guys had not supported.
one thing i have learnt is the more you read the more you find things useful and you actually learn how ti weigh your risk and benefits and avoid ending up with an expensive paper weight.
so this is what i did.
after using universal misc version file i was getting 140 error in RUU, boot loader version error, tried 3 time but would not let me get past that, then out of frustration i thought about giving it a last try for good or for worse, in the misc version section i changed a bit.
adb shell
cd /data/local/tmp
./misc_version -s 1.36.841.3 (Same number as my RUU)
then RUU went fine and then revolutionary.
well, if any kind of newbie person in trying to root the phone i would suggest to read and if you think you have read enough, its probably you haven't.
special thanks to @chninkel, @eyahl. Thanks Guys for all the support.
Cheers!
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/tmpadb shell chmod 777 /data/local/tmp/zergRush adb shell chmod 777 /data/local/tmp/misc_versionc. (when everything is finished, type)
adb shelld. (you will now be on the $, then type)
./zergRushe. (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.6f. 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/tmpadb shell chmod 777 /data/local/tmp/zergRush adb shell chmod 777 /data/local/tmp/misc_versionc. (when everything is finished, type)
adb shelld. (you will now be on the $, then type)
./zergRushe. (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.6f. 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
Hi everybody,
I decided to install a new ROM on my Desire S, and I thought it would have been easy, according to what I heard about HTC Devices.
At the end i was obliged to open a new thread after several nights spent finding a solution with no results: :crying:
My device has HBoot 2.00.002, Bootloader is Unlocked, and is still S-ON.
I tried following a lot of tutorials and guides, used toolkits and everything I found on this forum, but none of them seems to match my situation.
I still was not able to S-OFF or downgrade my device, and every kind of operation that has a "waiting for device" stage, remains stuck, although the "adb devices" command detects my device.
Can someone be so kind to help me understanding what to do in my specific situation?
Thanks a lot in advance :good:
I did S-OFF yesterday, I flashed old Doubleshot rom, then changed misc version, then flashed oldest RUU, enabled usb debugging and ran revolutionary
441Excelsior said:
I did S-OFF yesterday
Click to expand...
Click to collapse
I wish one day i could say that too
if you have waiting for device in revolutionary (even with usb debug on) then kill adb.exe process