Related
I have been searching the web for how to relock my EVO. This is because i am taking it back to sprint for a screen fix and I have learned from the PPCGEEKS thread all the problems and warranty stuff related to rooting as well as the odds of them discovering that I have rooted it. I just don't want to risk it and I would like to know how to relock, just for the knowledge.
Does anyone have specific instructions how??
PPCGEEKS Thread: http://forum.ppcgeeks.com/showthread.php?t=126849
http://shipped-roms.com/shipped/Supersonic/
Download first and last, and flash in the same sequence.
So thats all?? its done? It's unrooted? That seems simple.
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
redsolar said:
last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Yellowcard8992 said:
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Click to expand...
Click to collapse
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
wow after reading that thread on ppcgeeks i dont think i ever want to leave xda! must be a young crowd over there. i ran the latest 1.47 RUU that i downloaded from HTC before I returned my phone. much to my surprise they didn't even take the phone out of the box! still, since it only takes 10 minutes might as well do it.
barnacles10 said:
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
Click to expand...
Click to collapse
are you talking about just using the volume down and power button method?
redsolar said:
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
joeykrim said:
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Click to expand...
Click to collapse
I was surprised too when I tried first.
The 1.47 RUU just sat on the "waiting for bootloader" screen and timed out after ~90 seconds, "unable to find phone" (tried multiple times) and the screen would get stuck in white bootloader/RUU message (battery pull required) - so i am guessing 0.76.2 bootloader was too low for it. That was flashing from 3.2.2+ DamageControl ROM, didn't try from any other one, since the DC -> 1.36 -> 1.47 stock worked well.
And yes, the PRI caveat is there, but as joeykrim said, that's minor, plus you can always say "PRI what - huh?", right?
OneStepAhead said:
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
Click to expand...
Click to collapse
Running latest OTA makes you seem more of a "dumb user" who wouldn't even know what root is?
Yellowcard8992 said:
are you talking about just using the volume down and power button method?
Click to expand...
Click to collapse
No. RUUs are handled differently. You download the file. And run it on your computer with the phone plugged in. It does everything for you. You DO NOT flash these via recovery.
Update on my phone
I took it to the sprint store yesterday and against everything I have heard the guy at the store turned my phone and checked it. Thank god I used redsolar's posted method. I must have the appearance of someone who would root there phone. It passed his inspection, luckily.
Thanks for the help
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
murdercitydan said:
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Tundricles said:
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Click to expand...
Click to collapse
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
ViViDboarder said:
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
Click to expand...
Click to collapse
It should. RUU replaces everything but PRI
Sent from my PC36100 using XDA App
murdercitydan said:
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Click to expand...
Click to collapse
np glad I could help
Hi guys,
I have a Desire I bought unlocked on eBay. Though initially thinking it was factory unlocked, and having bought it under that pretense, I now think it's been unlocked by some other means. It doesn't appear to be rooted, having no superuser app but I'm not sure how else it could have been unlocked? If any one can shed some light here, that would be great.
I received the OTA update tonight, and after downloading and resetting it simply wouldn't get past 90% on the install before resetting itself. After about 15 minutes I switched it off and switched it on again, and it booted into my homescreen, with a "loading" alert and a rotating circle, no percentage.
Eventually that stopped, and it looked like everything was ok. I checked the version and it said I was running 2.2. Awesome, so I go about my business and realise I have no 3G or wireless connections. I check the settings and under WiFi it says "error", and I can't enable it. My APN is gone too. I can get that online, but it seems like there's an issue with the radio so I haven't bothered. It doesn't connect to the network anyway. It also resets occasionally, it seems when it has to load SenseUI but I can't confirm this.
What could it be? I'm not sure where the phone came from. It's a Black a8181 model with the Orange case branding, but the OS is unbranded. The locale is English (Singapore/Taiwan/a few others), though I thought the Black model was only in the UK. I'm in Australia, on vodafoneAU.
Is there anything I can do?
Cheers guys, I really hope I haven't (basically) bricked it.
Firstly, removing the SIM lock from the phone has nothing to do with rooting. Usually, you just stick in an "incorrect" SIM, and it will ask for an unlock code which you can buy online.
Given that the OTA update was a patch, it sounds to me like you have a partially patched ROM and this is causing your problems.
However, since it basically boots up and works to a fashion, it isn't bricked and chances are it is fairly easily recovered.
IMHO, you have two options.
1. Install a 2.1 RUU to downgrade your phone.
2. Root the phone using UnreEVOked and load a custom 2.2 ROM.
Both of these should be quite easily so long as your previous attempt to upgrade hasn't already updated HBOOT.
Turn you phone off and then power on again whilst holding down the volume down button - your phone should boot into HBOOT.
Look for the HBOOT version on the second line and post back what it says here.
Regards,
Dave
You've received a branded phone that has been debranded (you should have been told this) - you can't upgrade these without a goldcard. What's happened is part of the upgrade has worked, but other parts failed.
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
teppic74 said:
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
Click to expand...
Click to collapse
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
foxmeister said:
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
Click to expand...
Click to collapse
That's true, though it does mean going down the custom ROM route, which might not be wanted.
Thanks guys, that's really good info.
I'm not too concerned about running custom ROMs, I've been thinking about doing it for a while, just don't know enough about how to root and flash. There are some good guides here, I'm just a bit nervous about doing it. I also don't know what the best ROM would be. I'm really just after a factory standard Desire with Sense ROM, the most out of the box it could be.
I assume an RUU is like a rollback? In which case, what would I be rolling back to. I have no idea how it was debranded, so I don't know what ROM I'd need to roll back to.
As for the goldcard, what would that do? Is that rolling back, or fixing what I have now? It doesn't crash too often, I can probably baby it through.
Sorry for the questions guys, just want to know my options. I didn't think it was too badly bricked, but you never know. I bricked my XDA Mini II trying to flash a new ROM, so you can see my hesitation :/
An RUU is an official way to flash the phone with HTC's own software. That is how the phone was debranded in the first place, and you can do the same to get it back to normal. It does require a goldcard though, which is a minor software patch on the sdcard.
If you root and install a custom ROM (and update the radio) you'll have a working phone again, and you can make a goldcard in your own time.
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
foxmeister said:
Look for the HBOOT version on the second line and post back what it says here.
Click to expand...
Click to collapse
Hboot - 0.80.0000
papalazarou said:
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
Hboot - 0.80.0000
Click to expand...
Click to collapse
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
teppic74 said:
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
Click to expand...
Click to collapse
Cool, will the process in the link in your sig do the trick? And the goldcard, will I need to keep it in permanently, or only when updating? Trying to decide if I should use a dedicated card for it, or include it on the card I keep in there.
Thanks for the help, I'll run the RUU tomorrow morning.
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
papalazarou said:
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
Click to expand...
Click to collapse
Yeah, that's my fault for leaving a testing point in the Mac/Linux version of the utility. It was mentioned in the bugs section, but probably not made clear enough. It's fixed now.
I am trying to unroot my Cellular South desire and turn S-On. My phone is currently having issues staying on 3G so I need to make a warranty claim but my phone is currently rooted and has S-Off. I have an OTA update for it I copied to my computer if that will help me any (the OTA update for 2.2 that I can't install because I am on clockworkmod). I have an Alltel ruu if there is anyway to replace files in it with those from the OTA but can't flash it since my carrier has been known to tell me to do a hard reset to fix something and if I demo it in store they will notice it in the store.
fixed, it works well enough at least
There is an RUU on their website.
Their site being cellular south's site? Where did you see an RUU?
tekFishy said:
fixed, it works well enough at least
Click to expand...
Click to collapse
You mind sharing how you unrooted the device?
Just run the RUU from your carrier (goto HTC website, and search through downloads)on a computer with your phone plugged in. Assuming you havent added any developer modified drivers everything should run smoothly and your phone will be returned completely to stock... no root, no custom rom, no custom hboot, no s-off, no nothing.
I have a few questions about s-off and being in the latest OTA.
Here is the short and skinny...
When my wife got the evo when it first was released last year i tried to root it since i wanted to install a program that needed root. i had no real idea on what i was doing and think i might have gotten root, although I am not sure. I never flashed any rom nor did I ever flash that apk and just gave up since I didnt want to break her new phone. (basically got a bit scared)
As for the main screen if you reboot and hold down volume and power, it will display "s-OFF".
She did the two Gingerbread updates OTA and is now on GB 2.3.3. stock.
I noticed that the hboot is set at 2.16...and it still displays "s-off".
I just read that there are different types of "s-off".
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
pretty sure sprint wont notice the s off so dont bother going s on to ttake it in, even if they do, they dont really care anymore, so long as its got the stock os at least, but they really dont care bout it being rooted anymore
but yeah, your phone basicaly kept the root
I agree with LCL22.
Unrevoked does have an S-ON tool, but I've never used it and I'm not even sure it works anymore. Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery. But I've heard people take their phones back with CM6/CM7 on there, MIUI, etc. It probably depends on the store/rep to be honest.
"Rooted" means having access to the SU binary (superuser). It's a linux thing. It's like having Administrator access to a windows computer. This allows complete control over the currently installed phone software.
S-OFF means that the phones protections have been disabled and you are free to flash unsigned ROMs via the bootloader (HBOOT).
S-OFF is nice, because you can flash any ROM you want via the bootloader; there is no need for a custom recovery to be installed. Of course you can also use the bootloader to flash a custom recovery such as ClockworkMod or Amon_RA.
github said:
I agree with LCL22.
Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery.
Click to expand...
Click to collapse
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
amart79196 said:
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
Click to expand...
Click to collapse
S-off only means you are nand unlocked so you can flash a custom recovery and flash a ROM. To be rooted, you have to flash a rooted rom which 99.999% of all the ROMS are rooted on XDA.
S-off just means that you can flash an alternate recovery and custom roms. It doesn't mean that it is rooted.
check in your app list and see if the Superuser app is there. If it isn't, it probably isn't rooted.
S off is perfect! Don't go s on if you can help it.
At my local repair store I chatted with the tech (after running s on tool) if they even check. The guy said not usually. They mainly check if it is stock sense like the Rosie and stuff. And even then they don't usually. They only check if someone brings in their phone with technical or software issues. With hardware they don't bother.
But that is my store.
S off and root are separate things but they kind of depend on each other. To root permanently you need s off, at least for devices with nand.
Sent from my PC36100 using Tapatalk
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
Sprint is currently having issues on their end in regards to texting. I've attached an article that you can read over.
http://m.wired.com/gadgetlab/2011/07/sprint-sms-text-problem/
ENG S-OFF
EDIT: Nevermind, I just took the risk and it paid off.
I was actually about to start a thread asking the exact same thing. I'm selling my phone and I've heard that if it's not relocked it can't be activated on the Sprint network so I've been trying to get S-ON. I have "EVT2-2 ENG S-OFF" right now.
By the sounds of this all I really need to do is flash a good PC36IMG and all should be good, right? No chance of a brick?
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
Click to expand...
Click to collapse
Answers :
1. If you flash a recovery.img it will be.
2. You can't really do anything with the s-off right now because I don't think that any of the tools that would do that have been updated to work with hboot 2.16.
3. I'm not sure if anyone can use what you have but I would write up a post in a dev thread to be sure.
4. There are only two meanings that I know of when it comes to s-off. The first is accepting the OTA while rooted which will put your phone in a weird state. If you can use your phone after then I don't think this applies to you. The other is just not having a recovery installed which will render you just unlocked and not rooted.
amart79196 said:
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Click to expand...
Click to collapse
No. Flashing a regular rooted odex or deodex version of the RUU won't hurt you if your s-off. I would make a nand backup using amon ra recovery before flashing anything just to be safe.
Amon Ra Recovery - http://forum.xda-developers.com/showthread.php?t=705026
Rooted OTA ROM - http://forum.xda-developers.com/showthread.php?t=1133379
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
It doesn't matter what hboot you have so long as you're s off
No bricks don't worry. Bricks usually occur during manual radio updates
Sent from my PC36100 using Tapatalk
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Well they can't really do anything about us rooting phones since the supreme court says we can do whatever the hell we want to devices we paid for, thanks to the Apple lawsuit. However rooting voids your warranty so I suppose the question is why are you returning. If you are returning it because it's in some way physically defective, you *might* be ok. But if it has malfunctioned, it could bite you in the ass. More information would be helpful.
You should also realize that Sprint has been very inconsistent on this issue. There are those who have had warranty work/returns done and had no issues with it having S-Off and even custom roms still installed. Then there are those who have gotten caught. It should also be pointed out that this is in your contract, so please don't be one of those guys that get denied then RAGE about it on these forums. When you rooted, you clicked a box that said "Your warranty is now void" or at least read that somewhere I am certain! Anyway more info pls, or try it anyway and good luck! Worst thing they will do is give you the phone back and void your warranty totally. You could always toss it in the sink for a few hours then file insurance claim on it.
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
I tried returning my Evo with S-Off, and the person who was looking at it recognized it in the bootloader. He said "I personally used Revolutionary too. Sadly, we can't return this."
I was able to find a solution, however. Download the zip file attached to this forum post, rename it to PC36IMG.zip, and place on the root of your SD card. Boot into your bootloader. You will be prompted to update. Choose yes. It should flash quick. When it asks you to reboot, choose yes and reboot back into the bootloader. It should show S-ON with 6.17 HBOOT. From there flash your RUU and you should be back to 2.16 HBOOT with S-ON!
I got a refurb a couple months ago and it arrived S-OFF, so I dunno
Thank you all for your responses. I did try to run the RUU and Captain Throwback's S-ON zip but no luck, I'll probably just unroot and RUU it back to the newest firmware and just return it like that. Since borrowedchief said he received his with S-OFF, its probably a hit or miss as most other things at Sprint...
I just sent my old phone back with S-OFF. My issue though was power cycling. Sprint even credited me the $100 premium for my insurance because they failed to replace my phone before it had water damage. I took the phone in multiple times with no luck. Finally the Tech told me I had good news and bad news. Good news, you are getting a new phone. Bad news you have to pay $100 because you have water damage. The first Rep I talked to said we should have replaced the phone the first time. Credited me the money once they received my old phone.
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Obviously the official rule is that they dont take them back S-off... Some people get lucky and either get a lazy rep or a rep that wants to be nice... It's a gamble
richp1970 said:
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Click to expand...
Click to collapse
I returned mine too but the terms state that they have up to 2 billing cycles to charge us for any damages or whatnot... guess we'll see...
Their policies at sprint are now that they service rooted phones meaning with S-off they just RUU back up to the latest and it usually reflashes over ENG hboot and other things meaning that it's just gonna be s-on when you get it.
I rooted my phone and is s-off too and cant get it back to s-on
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Originally Posted by Captain_Throwback
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Thanks man! I rooted gingerbread 2.3.3 with revolutionary and try to unroot with unrevoked foreverson.zip but no luck because I didn't use there method to root. Hours and hours of research came accross your thread and all I can say thank you.
*****Very important to complete last step because if you don't you will have S-on but your HBOOT will be 6.1... For my last step I didn't flash using HBOOT I just downloaded RUU most current file because my phone came with 4.24.651.1 I just ran RUU booted back to white screen and HBOOT now shows HBOOT 2.1
Here you should use this method. It was origanally posted by captainthrowback and thanks to him now im back to s-on I was rooted and went back to stock but had s-off and I used this method to go back to s-on and it worked. My evo is on hardware v0004 and it worked fine too. Hope this method works for you to. Good Luck. Have any other questions just ask