Develop Bugs

get phone back to s-on

I have been having random reboot problems for weeks and no matter what I try I cant get it to stop. So I have tried to get back to unrooted stock so i can return. I have unrooted 2.2 on my device now, but i have s-off. From what I have heard I need s-on in order to return it.
Can anyone help me on this ?
I had hoped that going back to stock ROM's would stop the rebooting, but it has not. I still get the random reboots. sometimes it reboots a few times and then goes dead on me. I have to remove the battery and sd card to just get it to turn back on again... ugh
Hank

Guess you never read Unrevoked when they said that S-OFF is permanent for the time being and that they didn't know if they would be able to turn it back on. Your best bet is to say you lost it file a lost/stolen report with the police pay the insurance deductible get the new phone and sell the old one with bad ESN for sprint.

I just reflashed 2.1 via the first step of the how to root 2.2 method by regaw. 2.1 was always much more stable for me. it was when i went to 2.2 that i started having all the issues. and I thought that you could go s-on with 2.1 using the latest unrevoked. but i could have read that wrong.

I just looked at there site and it looks like I was wrong they have a S-on tool now
http://unrevoked.com/rootwiki/doku.php/public/forever

yeah, i read that. i dont see where it says how to turn it back to s-on though. only really talks about s-off. it does say there is a tool to turn back on. i assume that is in the custom recovery somewhere ?

mrsexkey said:
yeah, i read that. i dont see where it says how to turn it back to s-on though. only really talks about s-off. it does say there is a tool to turn back on. i assume that is in the custom recovery somewhere ?
Click to expand...
Click to collapse
It's the same as flashing unrevoked
Forever. Just flash the zip file in recovery.
Sent from my PC36100 using XDA App

So if there's an S-ON now, what's to stop HTC from incorporating that in their next OTA?

Nothing.
Sent from my PC36100 using XDA App

dallashigh said:
So if there's an S-ON now, what's to stop HTC from incorporating that in their next OTA?
Click to expand...
Click to collapse
probably the fact they don't really care. why would that be a priority for them?

nicholaaaas said:
probably the fact they don't really care. why would that be a priority for them?
Click to expand...
Click to collapse
So is it just a coincidence that every OTA up to this point has broken root?

dallashigh said:
So if there's an S-ON now, what's to stop HTC from incorporating that in their next OTA?
Click to expand...
Click to collapse
HTC totally knew how to S-ON this whole time. They built the damn thing.
The UnrEVOked team mentions this in the link posted above. If they DID S-ON everyone it would break every phone that's legitimately S-OFF for testing purposes.

dallashigh said:
So is it just a coincidence that every OTA up to this point has broken root?
Click to expand...
Click to collapse
ViViDboarder said:
HTC totally knew how to S-ON this whole time. They built the damn thing.
The UnrEVOked team mentions this in the link posted above. If they DID S-ON everyone it would break every phone that's legitimately S-OFF for testing purposes.
Click to expand...
Click to collapse
what he said... further. root methods represent legitimate security holes in the software. s-off doesn't

ViViDboarder said:
HTC totally knew how to S-ON this whole time. They built the damn thing.
The UnrEVOked team mentions this in the link posted above. If they DID S-ON everyone it would break every phone that's legitimately S-OFF for testing purposes.
Click to expand...
Click to collapse
It may enable the security but it won't break them by any means, they could easily leave a backdoor on their devices that would allow it to be disabled again

I don't understand why everyone's worried HTC will S-on everyone, who unlocks there phone and flashes official OTA's

P_Dub_S said:
I don't understand why everyone's worried HTC will S-on everyone, who unlocks there phone and flashes official OTA's
Click to expand...
Click to collapse
Kind of a noob to the Evo (gave up my nexus today) I looked around but didn't see anything so sorry to ask but, what is this s-on s-off stuff about anyway?

polo79 said:
Kind of a noob to the Evo (gave up my nexus today) I looked around but didn't see anything so sorry to ask but, what is this s-on s-off stuff about anyway?
Click to expand...
Click to collapse
Here's the thread about S-Off http://forum.xda-developers.com/showthread.php?t=752163

question for orange uk users ..

since my rebooting issue has gotten progressively worse, i'm obviously now going to have to get the phone back in for repair.
i assume i'll need to re-root it and re-flash the stock rom to be on the safe side, in case of any accusations i've invalidated the warranty. i know it sounds like a daft question, but what exactly is the stock rom ?
is it the official HTC Sense rom ? i guess i'm so used to using OpenDesire and, more recently, Oxygen, i've kind of lost sight of what the official rom used to look like.
cheers

This is where you have a problem. You need to put the Orange ROM back on it and that is the only ROM never to have been leaked...you'll either have to put a stock WWE ROM on it or hope Orange are nice enough to not invalidate your warranty and fix it regardless...
You could try this but there's no guarantee it'd work...
http://forum.xda-developers.com/showthread.php?t=796975

The method eddyOS posted woirks fine for me I tested it after I debranded my desire then rooted it.

EddyOS said:
This is where you have a problem. You need to put the Orange ROM back on it and that is the only ROM never to have been leaked...you'll either have to put a stock WWE ROM on it or hope Orange are nice enough to not invalidate your warranty and fix it regardless...
You could try this but there's no guarantee it'd work...
http://forum.xda-developers.com/showthread.php?t=796975
Click to expand...
Click to collapse
Orange replaced my desire with that rom on it. It but it leaves superuser apk in system apps and probably busybox and whatever else unrevoked adds to /system too. But it will be unrooted with stock radio, recovery and hboot. The only difference is superuser.apk afaik.

mercianary said:
Orange replaced my desire with that rom on it. It but it leaves superuser apk in system apps and probably busybox and whatever else unrevoked adds to /system too. But it will be unrooted with stock radio, recovery and hboot. The only difference is superuser.apk afaik.
Click to expand...
Click to collapse
Hi,
does this process also work for SLCD's? or is it just for AMOLEDs.
Ta
Mike

Don't know. Wouldn't reccomend trying untilled you have a definate answer to be honest. I don't think slcd devices were out at the time that image made so it probably don't support it.
I would stick with the stock European unbranded rom myself, ignorance is bliss of they ask anything.

Pretty sure it's AMOLED only...there's a chance an Orange RUU might be available soon

Oh really - keep us posted!
There's nothing wrong with my Orange Desire but I like to know what options are available to unroot it if things go pear shaped.
Thanks for the info.
Assuming an Orange RUU doesn't become available, I would imagine the method mentioned above could be used if anyone was available to supply a NAND from an SLCD on 2.1?
Mike

Cant see anythign bar the startup screen on mine that says " Orange " I have taken off all the demo rubbish ... so they would only know .. by looking at the build number etc... the look of the phone lloks like anything else out there ....
as long as you dont put Windows 7 on there !! LOL should be ok

It wont work with SLCD as it was from the nandroid of my phone which is AMOLED.

EddyOS said:
This is where you have a problem. You need to put the Orange ROM back on it and that is the only ROM never to have been leaked...you'll either have to put a stock WWE ROM on it or hope Orange are nice enough to not invalidate your warranty and fix it regardless...
Click to expand...
Click to collapse
Appreciate the link - thanks. I'll have to put that rom back on it and hope for the best.
Worst case scenario, i'll just have to sell the desire on ebay and claim ignorance to the rebooting .. not that i'd do that of course

I wouldn't worry too much I had to send back my last phone, a tocco, I had debranded it and ruined the camera by try to flash new firmware on it, they replaced it with no problem. I remember I saw posted in a forum from someone that works at orange claiming they don't check firmware etc anyway
Sent from my HTC Desire using XDA App

that's encouraging to know craig, thanks.
i got my desire from phones4u initially, but I got the impression from speaking to the manager today that it would be sent back to HTC rather than Orange.
It's going to be a few days before I can borrow a phone to use in the mean time, so i can always decide if i'm going to follow the procedure to re-root and go back to the stock flash.
I might meet them halfway and just get a rom that looks like it's stock - i've unlocked the handset as well so I'd rather not chance paying to do that again.

Ha HA! It worked
Back to the Orange Sense crap Rom.
God it's horrible. I've been using custom roms for so long, i've forgotten how Sense actually looks
Anyway, it's randombly rebooted twice since i've restored the stock rom so the problem hasn't gone away. but at least i'll be happier sending it back for repair now.
(And it's just rebooted itself a third time while i've been typing this )

I'd first get the 2.2 OTA and make sure it's not fixed in that but yeah send it back if still doing the same. Chances are getting a replacement will leave you with an SLCD screen so this roll back won't be possible

The third reboot actually did happen after the 2.2 update.
I don't mind so much if i get an SLCD screen in a way - as long as I can flash another rom back on to it then i won't mind.
I accept it's a gamble in case it goes wrong again but I really don't want to keep this sense on it any longer than I have to.

this isn't good .. i was fiddling with the phone just now and it randomly rebooted - again.
It came up to the white screen with the HTC logo and didn't move. I popped the battery and turned it back on again and it's now stuck at the HTC screen again.
Getting rather concerned it's just died totally ..

I think it's gone .. i can't even get it in to recovery. My only option is to try the "clear storage" option for a factory reset. if that doesn't work ...

Confirm that I bricked my phone please?

... before i shell out for another phone because I'm an idiot.
Anyway, I'd been doing some reading and had a thin history of rooting with my G1 which went rather well.(in that I never bricked it)
I did the same with my phone now, the G2. I got it when it first came out, got comfortable with it and finally decided to root it. I guess I didn't do enough research because I used Visionary to root and I believe I am now bricked. I have been up and down the forums for a solution or even a confirmation that I'm bricked for the last 4 hours. I kid you not. I even went into different phone sections in case I found something that could help but zilch.
So yell at me for not doing enough research and reading before i started rooting, but don't yell about this same question being asked over and over again.
Anyways, I can only get to the first white "HTC" screen and freezes.
I can get to HBOOT and that says:
Vision PVT SHIP S-ON
H-Boot-0.02.0000
Microp-0425
Radio-26.03.02.26_M
cMMC-boot
HBOOT
If I try to go to recovery it goes to that little black phone with the red traingle.
If I try to go to factory reset it goes to a green circle with a load bar that just looks like it's working but then it goes back to the white HTC screen and stays.
I have SDK and even though my computer recognizes that an Android 1.0 device is attached, when I "adb devices", nothing is listed.
So what's my diagnoses pros?
Thanks for any help or any response at all in advance.
Dea.

Its not looking good my friend, what exactly have you done to your phone so far?
If it is stuck in a boot loop and you have S-on the only possible thing you can to do fix it is flash the stock PC10IMG, but this will only work if you had the pre-OTA rom on your phone 1.19 and I really doubt that you did. If you had the wifi calling app you had the OTA 1.22 rom not the 1.19 rom. Trying to flash the stock PC10IMG onto your phone if it had the OTA rom 1.22 will cause it to do exactly what is happening now.

There's a file called "pc10img.zip" (the default firmware) that can be placed in the root of your SD, and should automatically be detected and offer to start flashing. I think this is how I recovered my phone which was in a similar state. Someone here could probably link you to the proper file (I'm sure there's different versions for DZ and G2). Good luck...I think you can probably save it.
I'm pretty sure mine was doing the same thing yours is, and I'm happily rockin' CM7 now, and loving it more than ever.

@joemm, Well I had 1.22 on there since I remember having wifi calling. I know you advised me not to but I might look into the PC10img.zip just because it can't get much worse than this honestly.
@hexapus, thanks for the advise. I'll have to look for my sdcard adapter first though. can't seem to find it at the mo'.
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"

dealunae said:
And when it does its sd card check on HBOOT, by the way, it says that all the files it wants to load, it says "No image!"
Click to expand...
Click to collapse
Thats because its looking for the file named PC10IMG.zip, this is the only file name it will load and it must be on the root of your sdcard.
Check your PM i will message you right now.

This is a link to a page containing instructions for a manual update to 1.22 and a link to the update.zip. Maybe this will work if all else fails by applying the OTA update again.
http://www.talkandroid.com/20232-tutorial-manually-update-t-mobile-g2-remove-google-goggles/

You might be able to hex edit the pc10img.zip so it thinks its version 1.22.
Sent from my T-Mobile G2 running Cyanogenmod.

I also had this same issue, in that I tried visionary and had the same issue. I took mine to the tmobile store and let try to fix it, which they couldn't, and when they asked me what happened I said I was uninstalling an app that was a live screen because it was acting werid. Because I was still under warrenty they help me get a new one sent to me.
Worked out for me, now I read and read and read more. I am rooted via rage and gfree but still run stock.
Good luck
Sent from my T-Mobile G2 using XDA App

Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)

dealunae said:
Well, everyone, after further button pushing, it looks like I can get into stock recovery. Should I do a wipe and flash a manual update of 1.22? The only reason I ask at this point is that if I try to do this, fail and then try to get it replaced, they might see that I tried to root and not replace it. (I have insurance as well btw.)
Click to expand...
Click to collapse
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!

It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App

joemm said:
It won't let you apply the 1.22 update zip because it is not a full rom, people have tried before and it doesn't work, but I guess like you said what have you got to lose.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?

EdKeys said:
joe, check out the second part of that link I provided above. The part about those with the google goggles fix. Do you think that would be a good second choice? I don't know if the OP knows how to do a fastboot flash, but it seems like it is more comprehensive. Do you think that it would reverse the effects of the Visionary perm root attempt?
Click to expand...
Click to collapse
At this point for him I don't see how its gonna hurt to try, but in my experiences in this forum I have not seen anyone able to flash the update 1.22 .zip after being stuck in a S-On Bootloop. Its either gonna work or it wont let him flash it at all, so I really cant see how it could hurt to try. As far as the 1.19 rom it wont let him flash it because it will give a error that the main version is older.

EdKeys said:
The link I gave to you above has some great instructions on applying the manual update again. In my opinion its your best option at this point. BTW I have insurance too. I'm always worried that I might lose my phone!
Click to expand...
Click to collapse
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!

dealunae said:
yea. It's how I realized I could still get into recovery. Thanks for the link. I'm at work right now so I won't be able to work on it till later but Wish me luck!
Click to expand...
Click to collapse
OK, good luck! I hope that it, or something else, eventually works for you. Keep us updated....

So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.

dealunae said:
So ended up getting a new phone. An htc g2. (sigh) I still really want to to root but am not officially terrified. ha. Looks like a lot of research and reading is in my future.
Click to expand...
Click to collapse
Lol... no need aha. If you have the basic concept of rooting you should be fine. Of course u just follow each step for rooting. Wish u luck
Sent from my HTC Vision using Tapatalk

You didn't fix the old one? The pc10img fix almost certainly would have cleared it all up.
Sent from my HTC Vision using XDA App

[Q] Can I still go back to stock?

Is there an updated resource thread for returning the phone entirely to stock? I'm running Skyraider 3.5, incredikernel 2.6.32.27, 2.15.00.11.19 radio, and an updated HBOOT with CWM; all on a launch Inc; and would like to return to complete stock with the most recent updates.
Also, what does a "clean ESN" mean?
Any help would be greatly appreciated as search hasn't yielded anything recent. Thanks.

Dynamic3 said:
Also, what does a "clean ESN" mean?
Any help would be greatly appreciated as search hasn't yielded anything recent. Thanks.
Click to expand...
Click to collapse
I can answer this part of your question.
The ESN is the Electronic Serial Number that is tied to your phone. If one has a "bad" ESN, that means Verizon has flagged that phone as either stolen, or delinquent with billing or some other circumstance. Therefore, if someone was to buy it, Verizon would refuse to activate it. However, it is possible another carrier would activate it, if it were able to be flashed over.
A "clean" ESN means all is well, and that it is all gravy to be activated on the Verizon network.
Hope that helps.

You can go back to stock, just requires flashing the RUU file you can find at www.dougpiston.com
Clean ESN means that the phone can be re-activated on another account. As far as I know, your phones ESN should be fine unless its been reported stolen or your account isn't current. Should be able to Google ESN for more info.
Sent from my ADR6300 using XDA App

I remember seen a thread about this where they had all the instruction on how to do it.. what version of incredible you have..
SLCD Or AMOLED?
if you just wanna lose root download the Skyraider athena 1.2 from rom manager and it will download the November ota.. that work for me before... now S-on thats another story if you have the SLCD i have that file that you need...

1107963 said:
I remember seen a thread about this where they had all the instruction on how to do it.. what version of incredible you have..
SLCD Or AMOLED?
if you just wanna lose root download the Skyraider athena 1.2 from rom manager and it will download the November ota.. that work for me before... now S-on thats another story if you have the SLCD i have that file that you need...
Click to expand...
Click to collapse
I am AMOLED and currently have S-off...

k_nivesout said:
You can go back to stock, just requires flashing the RUU file you can find at www.dougpiston.com
Clean ESN means that the phone can be re-activated on another account. As far as I know, your phones ESN should be fine unless its been reported stolen or your account isn't current. Should be able to Google ESN for more info.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
To flash this do I need to rename it and use the bootloader or something of that sort?

Dynamic3 said:
I am AMOLED and currently have S-off...
Click to expand...
Click to collapse
I never try this but supposedly this will take the s-off from your phone... I am attaching this file ask a dev to check it out to see if you are safe to flash it since i have a SLCD incredible... never try it tho...

1107963 said:
I never try this but supposedly this will take the s-off from your phone... I am attaching this file ask a dev to check it out to see if you are safe to flash it since i have a SLCD incredible... never try it tho...
Click to expand...
Click to collapse
I don't mind if it removes s-off, in fact I want it to be as stock as possible as I'm prepping the phone for sale (getting the Bolt).

Dynamic3 said:
I don't mind if it removes s-off, in fact I want it to be as stock as possible as I'm prepping the phone for sale (getting the Bolt).
Click to expand...
Click to collapse
check this out... and see if it helps...
Code:
http://androidforums.com/incredible-all-things-root/181255-how-downgrade-official-2-2-a.html
Note: why dont you sell your phone rooted that may increase the value... just saying... they person that purchase it may want to root it....

1107963 said:
check this out... and see if it helps...
Code:
http://androidforums.com/incredible-all-things-root/181255-how-downgrade-official-2-2-a.html
Click to expand...
Click to collapse
That's exactly what I was looking for, thank you.
I guess I'm now confused as to what s-off is though. I was under the impression that it allows your phone to remain rooted even after you undergo an ota, however the guide claims that you can unroot and go back to 2.2, yet retain s-off.

Dynamic3 said:
That's exactly what I was looking for, thank you.
I guess I'm now confused as to what s-off is though. I was under the impression that it allows your phone to remain rooted even after you undergo an ota, however the guide claims that you can unroot and go back to 2.2, yet retain s-off.
Click to expand...
Click to collapse
Yeap that right you can go back to the 2.2 but still keep the S-off if I am not mistaken that the Nanunlock that give you total access to the phone once rooted...(please someone correct me if Im wrong...)
but if you wanna have s-on flash that zip file before you unroot... I think thats how that work...

It ain't lookin good for the wifes desire

Ok guys might need a bit of help..
Not too familiar with this handset really but flashed my phones a million times without problems...till I set about the missus's phone yesterday.
Its a 3 UK branded desire..was HBoot 0.83
Went through the S-Off/root/Recovery/Hboot upgrade procedures...and all looked good.
Till I came to actually flashing ROMs.. and tried a couple. Just bootlooped on the AlphaRev screen for all.
So decided to drop back to stock through HBoot... the stock ROM flashes with apparently no errors reported, but again fails to boot. And AlphaRev HBoot doesn't get overwritten..although Recovery's gone.
Anyone know how to proceed?

First of all by reading the tutorials carefully before proceed, to avoid any trouble
Get the latest RUU for your Desire (3UK) and save it somewhere.
Before you flash it, download the HBOOT Downgrader from Alpharev.nl.
Flash the Downgrader first, then the RUU.
And what do you mean the recovery is gone? Are you still S-OFF? You can flash a recovery with the Android Flasher tool in the Development secton.
And What ROMs did you try that all failed you?
You probably forget one ot two steps when flashing.

Ain't no noob buddy so need to cut and paste the standard response guys!
Did all them things so that's why I'm asking..and yes despite being over flashed with the RUU s-off is still there. That's what I meant by the alphrev hboot not being overwritten.
However..the downgradues worth a try....

DJW6927 said:
Ain't no noob buddy so need to cut and paste the standard response guys!
Click to expand...
Click to collapse
And that's how being rude will cut the number of replies you get...

No rudeness intended..but RTFM is no help either under the circumstances.
I've been doing this for years since my tytn.
I really appreciate the help I really do..the downgrade suggestion ain't in the guide...and seems a good idea. Will try soon as I'm home.

Ha. It ain't going well... worse in fact.
Downgraded HBoot and flashed RUU...screen won't turn on. But RUU can still just talk to it. Flashing again. But still the same.
Vol down makes it vibrate now...but not much else!!
Edit: Hum...my first brick I think! Think the wife might be gettin an upgrade.
Edit again: Screen blank but the RUU program still sees the phone. Fails to revive it mind you. Only outward sign of life is a pulse vibrate on the power button being depressed after a battery pull. Anyone seen this?

Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App

timmaaa said:
Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App
Click to expand...
Click to collapse
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.

DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.
Click to expand...
Click to collapse
Which RUU did you flash? If your phone has a SLCD screen, it might be a possibility that you've flashed an AMOLED RUU to your SLCD. Thus you will get a SLCD brick which makes you unable to view anything on the screen but the phone is working normally. It's reversible by following a SLCD unbrick guide.
Sent from my HTC Original Desire using Tapatalk

DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
Click to expand...
Click to collapse
This is all basic, well documented stuff you seem to be completely unaware of. Perhaps RTFM is exactly what's needed here.

Thankyou very much indeed to those who who pointed me in the direction of slcd. Now I know what to search on finding the information I need is straight forward. Really good stuff.
Thanks very much too to those who provided the ex-wife service too. Unfortunately I always know where to get advice like that