Essentially, I have been stuck in some sort of loop. Here's my problem:
For about six months I had been using my phone with stock HTC rom, S-ON, locked as usual. After about three months, I started using Airdroid for all my media transfers etc. So after about six months I decided to start flashing custom ROMs from here. But before I started doing it, I noticed that my phone was not detecting USB and simply charging when connected to my laptop (essentially i have no idea when my usb stopped working, but it was pre-rom flashing period). However, fastboot USB worked perfectly and so I realised that it was a classical USB Brick situation. Tried the USB fix solutions for S-ON devices but they simply wouldn't work (worked randomly but reappeared).
USB and ADB work perfectly on the Andromadus rom, but they don't work on stock roms. So I am able to downgrade to a hboot 0.98 and to a previous stock rom, but I am unable to use revolutionary since ADB does not work on that rom. Essentially, I am unable to S-OFF. And with that I am unable to try the simple USB Brick solution for S-OFF devices.
USB Brick -> Can't use ADB -> Can't S-OFF -> Can't try USB Brick solution.
I hope I am not missing something (sorry for the long post).
If I understand your situation, you were able to downgrade your hboot. You were also able to unlock it, flash andromadus and verify that you could use adb.
I haven't followed the S-OFF path yet, but, now that your hboot is v0.98.*, why don't you unlock it (if not done yet), find and flash a GB custom ROM with which adb would work, and then S-OFF from this ROM ?
Correct me if I am wrong, but revolutionary needs a v0.98.* hboot but I haven't read that one needs to be on stock ROM in order to S-OFF by revolutionary.
Sent from my HTC Desire S using xda app-developers app
yaonos said:
If I understand your situation, you were able to downgrade your hboot. You were also able to unlock it, flash andromadus and verify that you could use adb.
I haven't followed the S-OFF path yet, but, now that your hboot is v0.98.*, why don't you unlock it (if not done yet), find and flash a GB custom ROM with which adb would work, and then S-OFF from this ROM ?
Correct me if I am wrong, but revolutionary needs a v0.98.* hboot but I haven't read that one needs to be on stock ROM in order to S-OFF by revolutionary.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply! I tried unlocking 0.98.* but it would'nt unlock like it does in hboot 2.x. I don't think the htc unlock thing works in hboot 0.98. Or else I would surely have installed another rooted rom.
That's a shame you can't unlock the hboot. It was worth trying anyway. The. Only other alternative I can think of is using an XTC Clip. Read http://forum.xda-developers.com/showthread.php?t=1076937 for more info.
Sent from my HTC Desire S using xda app-developers app
I dont think I can get an XTC clip.
dejavu89 said:
I dont think I can get an XTC clip.
Click to expand...
Click to collapse
Why not?
http://www.fonefunshop.co.uk/Unlocking/xtc_clip.htm
One more question that I should have asked before : are you sure that your issue is not related to your laptop ? Did you try to connect your DS to another PC ?
Edit: we know that it is not an hardware issue because your DS and laptop can communicate in fastboot, and in adb with a custom ROM. There may be a software that gets in the way when your DS is on a stock ROM. I'm not sure that stock and custom ROMs advertise themselves with the same vendor id and device id. If not, it could be the reason why it works with a custom ROM and not with a stock one.
Sent from my HTC Desire S using xda app-developers app
Related
Today, I Unlocked the Bootloader with the Unlock from HTC, but it still says S-ON.
Will I still be able to root and flash rooms with the TUTs posted in the Development Section?
Or will there be an Alternate method.
If it still says s-on perhaps you should re try the HTC unlocking process until it says s-off
Swyped from HTC Desire S using XDA Premium
Why would you use the htc method. It saves your serial number and it voids your warranty. If you use revolutions you can always go back to s on and tmo will never know the difference.
Sent from my HTC Sensation 4G using xda premium
Daveon93 said:
Today, I Unlocked the Bootloader with the Unlock from HTC, but it still says S-ON.
Will I still be able to root and flash rooms with the TUTs posted in the Development Section?
Or will there be an Alternate method.
Click to expand...
Click to collapse
From the all the gossip flying around the word is you may be able to get CWM installed but no custom roms yet, seems HTC provided an Unlock for developers and will provide S-off at later date.
Just go here http://revolutionary.io/
and follow the instructions.
Yeah if you've unlocked using HTC unlock bootloader then you can't get S-OFF and flash custom roms. You can achieve root and flash a modified version of the stock rom.
This link will help explain it better:
http://www.androidcentral.com/how-unlocked-htcs-bootloader-unlocking-method
I feel that since you have already unlocked with HTC you've officially voided your warranty. It is probably best to just to revolutionary.io and unlock using the revolutionary process that way you can get S-OFF and start flashing custom roms. It would have probably been better to use revolutionary in the first place that way you could have S-ONed your phone if you ever needed to use the warranty later but it won't make much of a difference now.
Well, thanks guys, but I can lock it back on the HTC way, I wasnt aware that it voided warranty.
It's okay.
It gives me the Option to lock the bootloader, but I'm unaware that it'd bring the warranty back.
But Should I still just use revo to get S-OFF?
Yes, you should just use the revolutionary method. Much less time consuming. Give them your serial, they give you a code, they send Caroline in, and then you're good.
I'm not sure if the Sensation is any different, but I unlocked a Evo3d the other day using the HTC method.
The h-boot will not say s-off, but it will say *** unlocked ***.
CWM can be flashed.
Custom roms can be flashed, loaded Synergy nightly on there.
The only reason the Evo3d had to go that route was because the latest OTA was accepted before I had a chance to get revo on there. Anyhow, it was actually pretty pain free and I can't imagine the Sensation being any different.
I'd imagine you just use the fastboot flash command to flash CWM but, as already said, you should've just used Revolutionary
EddyOS said:
I'd imagine you just use the fastboot flash command to flash CWM but, as already said, you should've just used Revolutionary
Click to expand...
Click to collapse
Yup, fastboot flash recovery recovery_of_your_choice.img.
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse
ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium
After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.
schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!
Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten
I've checked every possible tag in my mind about this and couldn't find one for Sensation.
Is it possible to revet back to the original state before the Revolutionary. Is it possible to completely uninstall the Revolutionary from my phone?
I'm not talking about the s-off -> s-on
I'm talking about returning the phones software to its original state.
Like it is never installed in the first place.
Thank you.
It's funny because last weekend I wanted to do exactly the same thing.
What I learnt was to go from S-OFF back to S-ON can be quite fiddly and tricky, abd if you mess it up rub the risk of bricking your phone.
In order to get the stock Rom, here is the link: http://forum.xda-developers.com/showthread.php?t=1074559
Now it's just a case of finding which one you are, and your ril and radio.
Good luck
Thank you for your answer. But this is not what I want I can do this already but when I check the bootloader I see the pink "Locked" and it tells me that Revolutionary is still there.
I can go to S-On without any trouble that is not what I am asking.
What I am asking is to be able to get rid of every little bit of coding about the Revolutionary and return my phone to its original bootloader software.
If is says locked then ur good since that's what it said when you bought the phone.
Sent from my HTC Sensation 4G using XDA App
moshe22 said:
If is says locked then ur good since that's what it said when you bought the phone.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
When I get my phone there wasn't such writing. It is the product of Revolutionary.
So it is still there. I want to be able to get rid of it.
I'm not asking this about the warranty purposes. I'm asking this because I've realized that after using Revolutionary I can't install any app from market via wireless no matter what I did. Strangely it is fine to surf and download via mobile.
I know this because this is the Second Sensation I've faced having this problem and I remember some user Leviathan(maybe wrong?) talking about wifi dieing after Revolutionary.
So what I need is to get rid of it and be able to install original bootloader(maybe bootloader is not the right term here I don't know).
webmanya said:
When I get my phone there wasn't such writing. It is the product of Revolutionary.
So it is still there. I want to be able to get rid of it.
I'm not asking this about the warranty purposes. I'm asking this because I've realized that after using Revolutionary I can't install any app from market via wireless no matter what I did. Strangely it is fine to surf and download via mobile.
I know this because this is the Second Sensation I've faced having this problem and I remember some user Leviathan(maybe wrong?) talking about wifi dieing after Revolutionary.
So what I need is to get rid of it and be able to install original bootloader(maybe bootloader is not the right term here I don't know).
Click to expand...
Click to collapse
flash stock hboot, should come with a ruu file, but you can always check if you extract rom.zip from the ruu.exe.
Sent from my HTC Wildfire
I've tried installing stock roms over it no luck untill now.
webmanya said:
I've tried installing stock roms over it no luck untill now.
Click to expand...
Click to collapse
i am saying that you probably have a modified hboot, because of the revolutionary sOFF, just like alpharev. you need to flash stock hboot to get everything back, hboot flashing is dangerous, if it goes wrong youll have a brick.
Sent from my HTC Wildfire
and stock hboots are found in ruus.
Sent from my HTC Wildfire
smokzye said:
and stock hboots are found in ruus.
Sent from my HTC Wildfire
Click to expand...
Click to collapse
Thank you for your answer. I understand what do you mean. But I'm not sure if it will help because while flashing stock rom it also updates hboot.
hello all, I have an unfortunate situation...
my charging port on the sensation has broken, and I need to send it in for warranty. I'm rooted and I need to return to stock firmware and recovery. is there ANY possible way to unroot etc without USB? perhaps wireless adb or something?
If you have a look here it tells you how to s-on your phone. Unfortunately you need to connect your phone to your laptop. Have you looked into what they actually need to do to repair the charging port? They might not need to mess around anything that would tell them your phone is s-off. Worth looking into.
sooooo no S-off without connecting the to a computer?
Sent from my SGH-T989 using XDA App
You don't need to S-On for warranty, I think, not sure. Anyways, I beleive you can just place the pd58img.zip on the root of your sdcard and boot into bootloader and it should install factory firmware unrooted.
Sent from my HTC Sensation 4G using XDA Premium App.
You can flash an RUU sing the PG58IMG method. Search it, nice and easy
Still leaves you S-OFF but it shouldn't matter
EddyOS said:
You can flash an RUU sing the PG58IMG method. Search it, nice and easy
Still leaves you S-OFF but it shouldn't matter
Click to expand...
Click to collapse
this is true i had to send mine in for the usb and it s-off and they didnt say anything about it
i've unlocked my att one x got supercid.. and then i decided to change it to htc_405... so... it was the wrong choice! and now i can't get back to supercid, i've tryied all guides on forum but no one works..
from adb shell.. command writes.. device not found.
also installed newest htc drivers but nothing changes.. the hasoon allin1 tool doesnt work and i dont know what to do..hellppp :crying:
Are you s-on or s-off?
Sent from my Evita
timmaaa said:
Are you s-on or s-off?
Sent from my Evita
Click to expand...
Click to collapse
i'm s-on
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
i know but i changed it to recieve eu update.. didn't know that he has other cpu.. so now i cant change it to supercid or the original one..
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
timmaaa said:
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
Click to expand...
Click to collapse
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
denny094 said:
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
Click to expand...
Click to collapse
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Ah I see. Well I can't be much of help then. Sorry
Sent from my HTC One X using Tapatalk 4
denny094 said:
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Click to expand...
Click to collapse
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
s79336951 said:
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
Click to expand...
Click to collapse
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
denny094 said:
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
Click to expand...
Click to collapse
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
redpoint73 said:
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
Click to expand...
Click to collapse
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
denny094 said:
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
Click to expand...
Click to collapse
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
redpoint73 said:
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
Click to expand...
Click to collapse
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
denny094 said:
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
Click to expand...
Click to collapse
That post is really confusing, your sentence structure and punctuation is all over the place. Can you clear it up a bit and ask again?
Sent from my Evita
Yeah, not sure what was being said there. Did going back to ICS fix the adb issue, or did you find another way? So you have SuperCID now? If so, do the facepalm method to get s-off.
If you are still trying to get SuperCID, I don't think hasoon's all-in-one tool will work. Believe its looking for the AT&T CID (cws__001), so any other CID, it will fail. You'll have to use the hex edit method.
Problem is solved thanks I did s-off but I would like to ask you another question.. I installed clear rom sense 5 but the device has very low signal the radio firmware is 0.24p are there new updates to increase the quality?
Inviato dal mio HTC One S usando Tapatalk 4
I'm not sure which which radio you're referring to there. Have you updated the firmware as suggested in the CR thread?
Sent from my Evita