Develop Bugs

[Q] Need some help

Hello,
I am extremely new to this process and recently just rooted my EVO and would like to know the proper procedures to return my phone to stock if there is an issue eventually with my phone. I rooted using UnrEVOked3 and have the custom recovery installed when it was rooted. I did run a back up recovery right after I rooted.
I tried to figure it out on my own by flashing the RUU that was on theunlockr's site and it worked but was hesitant to run the OTA software update with "S-OFF" still activated. So I rerooted my phone and tried their "S-ON utility but now can’t run the RUU due to a bootloader error. I tried searching but there is so many threads about it that it gets confusing so I figured I would ask directly what my steps should be.
A couple questions:
Should my next step be rerooting the phone and then running the RUU?
Will running a RUU and then running an OTA update be ok if “S-OFF” is still activated?
Will running an OTA update turn “S-OFF” back to “S-ON”?
After I return complete stock can I reroot in the future if I want?
My Bootloader at this time looks like this:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-04if
TOUCH PANEL-ATMEL224_16ab
RADIO-2.05.00.06.10
Oct 15 2010, 10:07:00
Sorry for being so new about this but any help will be appreciated. Thanks.
(EDIT: I just read the first post in this thread topic and I'm going to try that since it seems like I'm halfway there. Sorry for killing a kitten lol)

Lol its all good man did you get all your answers or you need help?
~ d3rk

The real only question is can I reroot after I return to stock from unrevoked?

b2project said:
The real only question is can I reroot after I return to stock from unrevoked?
Click to expand...
Click to collapse
Yes you can! Many people unroot when they drop by sprint for whatever reasons, then they root all over again. Me, I'm a rebel, I give the reps my phone with cm7 on it lol.
~ d3rk

b2project said:
The real only question is can I reroot after I return to stock from unrevoked?
Click to expand...
Click to collapse
Yea you can. Just re-run unrevoked.

Thanks, if I run into any issues when I run the PC36IMG I'll be back

[Q] Questions about warranty repair (BravoC)

Hi All,
I have a US Cellular BravoC that needs to go in for repair. I am one of the unlucky ones who are experiencing the overheating/forced resetting while doing CPU intensive tasks.
I currently have S-OFF, CWM Recovery 3.0.2.4
I know that I can download 2.2 RUU in fastboot and that will return my phone to unrooted, S-ON... and my warranty repair should go through fine. The problem is, I want to be able to return to CM or Oxygen when I get my phone back.
1) If I return a phone with S-OFF and CWM recovery is it likely that HTC will deny the warranty repair?
2) Does anyone know if there is an RUU for 2.1?
3) Is it possible to flash the stock recovery and leave S-OFF as a back door?
4) Is it even likely that I will get the same software back? In other words... should I not even worry about because I will likely get back something different (Just flash the 2.2 RUU and say screw it).
I still do not really understand the whole "goldcard" thing or how to really use fastboot effectively, so I don't have the untouched ROM that came with the phone. Only the rooted one I created with nandroid backup before installing CWM
Sorry, I know that is a lot of questions but they are all very closely related. I have searched through the forum and did not find anything that really answers these.
Thanks for any advice you may have!

When you get your phone back you can just reroot and S-OFF again. You need to find the US Cellular ruu and run it.
Maybe someone else can help you with that.

So if I understand this correctly, even if I have 2.2 installed (which, as of now, can not be rooted) I could find and install the 2.1 RUU and then root the phone? I think the problem is HTC never released a 2.1 RUU. I am pretty sure I go to 2.2 (or HTC upgrades my phone to 2.2) I will lose the ability to root it.
Man, I just hate the stock ROM so much I want to try avoiding it at all costs.

[Q] Help, please. Need to Root 2.3.4 DINC

Ok, a few users here have offered advice/assistance, but I fear this problem has been forgotten.
I am stuck with an S-ON, 2.3.4 Droid Incredible, and am looking for a way to acquire root again.
This happened a few weeks ago, with the leak of the 2.3.4 OTA. Flashed S-ON via CWM (not aware I would permanently lose Root), then flashed the OTA as PB31IMG.zip in HBOOT.
Now, Unrevoked no longer roots the device. HBOOT will not allow downgrading to a 2.2 IMG, nor will it flash any downgraded Radio/HBOOT versions. I've tried them all from Dougpiston.com, even the signed ones.
I've attempted to contact the folks at Unrevoked about this issue on IRC, but I can't ever get a reliable dialogue going with anyone, and I believe they are busy working on Revolution, for Incredible 2/S & Newer devices.
Throwing my hands up, I even called Verizon, gave them an excuse to send me a replacement, just so I could start fresh with a 2.2 phone, but I am out of warranty.
I really want to enjoy Sense 3.0/MIUI, even Cyanogenmod, but the outlook is not so good.
Is there any solution I haven't tried yet? Please help.

Unless Unrevoked or someone else finds a new root method you're pretty much out of luck.
Sent from my Droid Incredible 3D using XDA App

Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4

resyek83 said:
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
Click to expand...
Click to collapse
That's most likely true. 2.3.4 is being pushed out to the Incredible now, so they would probably run the newest RUU on their Incredible devices.

I feel your pain deadsoulboy, and I've seen your posts lamenting your situation on other threads. Only solace I can offer you is that generally the source code and RUU are made available within 30 days of the OTA, at which point the developers are completely free to tear into them with reckless abandon and hopefully the folks at unrevoked figure things out.
It's also distinctly possible that HTC will unlock the bootloader the way it has with others of its handsets, in which case you'll be back in business.
Until then, my friend, I believe you are rootless.

i have the same problem. its been a couple months.... am i still hosed?

Have you tried this? http://forum.xda-developers.com/showthread.php?t=1306400

I used Scotty1223's instructions a few weeks ago and it worked like a charm.

So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.

alexyaz said:
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
Click to expand...
Click to collapse
Check this out. http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html

[Q] Return phone with S-OFF ok?

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

S-ON wipe Recovery?

Okay, this is a quick and probably stupid question. I just used jcase's method to return my phone to stock (now it's running Froyo, and I declined the GB upgrade). I have to return it under warranty, but I just want to confirm that they won't find anything wrong with it. Is the recovery overwritten? I know I am S-ON so is that enough? Thank you so much for your help!

DalekCaan said:
Okay, this is a quick and probably stupid question. I just used jcase's method to return my phone to stock (now it's running Froyo, and I declined the GB upgrade). I have to return it under warranty, but I just want to confirm that they won't find anything wrong with it. Is the recovery overwritten? I know I am S-ON so is that enough? Thank you so much for your help!
Click to expand...
Click to collapse
if ur s-on ur good.

S-On
I'm going to follow up with another stupid question.. if i get S-Off from Alpharev, is there a way to return it back to S-on? i know with the original Dinc there was an S-on Zip.. i know they're completely different phones, but can i use that to S-on again? is there something in ADB to redo it?
If i get S-off.. i DO want to keep it, i'm just talking about warrenty purposes..
Ya I found that out right after.. my Googling skills were weak for a little bit then i realized i couldnt find anything to return it to stock because i had Dunc 2 written instead of Dinc 2... and Google apparently found it funny to not give me the Suggested search...

Go to http://www.youtube.com/watch?v=tnlnWW8tsvo and follow it with jcase's guide (link in video description). I was anxious about messing something up but this was really easy.