Ok, So im sending my phone in for getting the camera lens fixed, im currently unlocked bootloader on 5.0.1 GPE RUU should I RUU the phone back to stock att 4.4.4? or leave it alone? HTC told me they will evaluate the phone and I will need to call them not to touch the software part of the phone. THIS IS ONLY TO REPLACE THE BACK OF THE PHONE WITH NEW CAMERA LENS
I'm planning on doing the same but am afraid that they will send me a bill for the full phone if they see its rooted and running custom software.
Thorin_Stone said:
I'm planning on doing the same but am afraid that they will send me a bill for the full phone if they see its rooted and running custom software.
Click to expand...
Click to collapse
They told me that would not be the case, but they couldn't promise this.
Andrew149 said:
They told me that would not be the case, but they couldn't promise this.
Click to expand...
Click to collapse
Just set your bootloader flag to locked, run the RUU, and go back to s-on (only if sunshine works for you on 4.4.4). Otherwise, do the above, but stay s-off
Related
I'm sending my phone back to Sprint, and I unrooted my EVO and flashed back to stock, but the Recovery now says "LOCKED (OOW)" on the top.
I only get one chance to send it back, what does this mean?
Thank you so much.
alexpete9 said:
I'm sending my phone back to Sprint, and I unrooted my EVO and flashed back to stock, but the Recovery now says "LOCKED (OOW)" on the top.
I only get one chance to send it back, what does this mean?
Thank you so much.
Click to expand...
Click to collapse
that means your bootloader is locked now and OOW means out of warranty
evo4gnoob said:
that means your bootloader is locked now and OOW means out of warranty
Click to expand...
Click to collapse
But my phone still has a few months of warranty... is there anything I can do about that?
alexpete9 said:
But my phone still has a few months of warranty... is there anything I can do about that?
Click to expand...
Click to collapse
I'm not sure sorry but that shouldn't effect taking it to Sprint if your not rooted or anything
Sent from my PC36100 using XDA App
If you're sending out to HTC then the "out of warranty" probably matters. If you're sending it to Asurion (insurance) then it won't make a difference, or shouldn't. Asurion doesn't have anything to do with your warranty through HTC.
Supersonic Evo 4G | MIUI | Tapatalk
alexpete9 said:
I'm sending my phone back to Sprint, and I unrooted my EVO and flashed back to stock, but the Recovery now says "LOCKED (OOW)" on the top.
I only get one chance to send it back, what does this mean?
Thank you so much.
Click to expand...
Click to collapse
It seems to say that by default at the top of everyone's device with the new bootloader. I don't think the OOW is relevant; I think only the "LOCKED" portion is. I got a refurb that said that, even though I had just received it. I think all refurbs say the "OOW", but I don't know if a new device would. At this point, there are no more "new" EVOs, so I'm sure it doesn't matter.
What are you sending it back for? If it is still able to root, then use captains method to revert yourhboot back to 2.10 and you wont have that at top anymore.
Not Sent
lock oow
Look to see if you flashed the newest update for HTC Evo to 2.3.5? if this is the case, they have added security to lock the HBOOT so you cant go in and root the phone. Also if you have unrooted the phone it can be a permanent "fix" and cant be undone.
OOW can mean out of warrantee, however, if the message is coming from the hboot screen then its probably the newer version of the android app.
Hey all,
My current HTC DHD is rooted and running Android Revolution 6.3.2 with S-Off.
Is going back to stock/OEM/out of box as simple as running the following RUU on my computer with device connected?
Will it flash my radio and baseband back to original as well?
http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Thanks in advance!
Yes it will.
Running the RUU will also unroot the device but s-off will remain.
If i remember correctly you can run the original s-off tool to go s-on again. Also it will be able to update your CID back to the one necessary to flash the RUU again.
wbbigdave said:
If i remember correctly you can run the original s-off tool to go s-on again. Also it will be able to update your CID back to the one necessary to flash the RUU again.
Click to expand...
Click to collapse
So I need to s-on before I can flash the original Telus RUU?
Nominee said:
So I need to s-on before I can flash the original Telus RUU?
Click to expand...
Click to collapse
No, but if it was for warranty purposes I would go back to son aswell. Se people have been fine sending back rooted phones while others haven't. It depends on whether the person repairing the phone bothers to look
marsdta said:
No, but if it was for warranty purposes I would go back to son aswell. Se people have been fine sending back rooted phones while others haven't. It depends on whether the person repairing the phone bothers to look
Click to expand...
Click to collapse
Thanks - actually, I'm just doing this because I have to install the 'GOOD for Enterprise' client which requires the phone to be not 'rooted'.
I'm currently running a custom ROM/Recovery. How would I go back to 100% evcerything stock?
kinglime said:
I'm currently running a custom ROM/Recovery. How would I go back to 100% evcerything stock?
Click to expand...
Click to collapse
try the t-mobile htc one forum?
nrfitchett4 said:
try the t-mobile htc one forum?
Click to expand...
Click to collapse
I'm on Verizon...
kinglime said:
I'm on Verizon...
Click to expand...
Click to collapse
(your avatar says t-mobile, throws us off.)
since you did you unlocking through htc DEV unlock (one can only assume anyway) you technically can't go back to full 100% stock.
your boot loader will always say unlocked or relocked.
S-OFF *may* be able to set you back to 100% stock but I forgot.
I would, ADB fastboot oem lock
this will change it back to "relocked" rather than "unlocked"
Verizon will still know you did HTC DEV unlock and technically can deny your warranty as you broke it by doing the HTC DEV unlock.
Personally though, I've sent back MANY HTC DEV unlocked phones to Verizon without re-repercussions.
I've been on Samsung for the past year though, so things may have changed, take what I say with a grain of salt.
hope this helps some.
Sorry! I forgot to change it from T-Mobile to Verizon when I recently switched. Anyways yes I was able to unlock via htcdev. Right now I'm running a custom rom and CWM custom recovery. I don't need to take my phone in or anything like that, I just want to return back to stock. Basically I'd like to go back to the software/recovery/everything that was running on the phone out of the box. How would I do this? Is there a link to the default recovery/rom, is that all there is to it?
kinglime said:
Sorry! I forgot to change it from T-Mobile to Verizon when I recently switched. Anyways yes I was able to unlock via htcdev. Right now I'm running a custom rom and CWM custom recovery. I don't need to take my phone in or anything like that, I just want to return back to stock. Basically I'd like to go back to the software/recovery/everything that was running on the phone out of the box. How would I do this? Is there a link to the default recovery/rom, is that all there is to it?
Click to expand...
Click to collapse
Until/IF, we get an RUU.. (don't hold your breathe for one)
you can't.
Sorry.
You could try and exchange it with another member who is stock and wants htc dev unlock?
AFAIK there is no stock recovery.img anywhere, not 100% though as I haven't searched.
Stock ROM you should have made a nandroid, if u didnt u can flash my stock deodexed ROM.
So with the release of the new S Off exploit is there any updated info to a full return to stock for warranty exchange that would leave you with a locked flag?
Sorry just found info in the General section!
Here is the Verizon HTC One RUU posted in the Android Development section - [RUU] Decrypted VZW RUU
The OP of the RUU mentions this is the decrytped version, and you need to use a tool called ruuveal to re-encrypt the RUU
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
godhamba said:
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
Click to expand...
Click to collapse
There are a few who are worried. But overall there is nothing to be afraid of.
Just whatever you do, DON'T take any OTAs!
godhamba said:
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
Click to expand...
Click to collapse
Basically, it is technically possible to turn a phone S-ON with an OTA. I don't believe it has ever been done however.
Sent from my HTC One
GrayTheWolf said:
There are a few who are worried. But overall there is nothing to be afraid of.
Just whatever you do, DON'T take any OTAs!
Click to expand...
Click to collapse
I was one of those worried. The only reason I had asked is because if I sent my phone in to get S-Off (which I'm pretty sure I will) and development never really takes off after that, I don't want to be stuck on 4.2.2 for the entirety of my time with this phone. I wanted to know if I COULD take that OTA at some point without bricking the phone. I was told if I changed the CID back to VZW__001, then I wouldnt brick if I did an OTA...
crazyg0od33 said:
I was one of those worried. The only reason I had asked is because if I sent my phone in to get S-Off (which I'm pretty sure I will) and development never really takes off after that, I don't want to be stuck on 4.2.2 for the entirety of my time with this phone. I wanted to know if I COULD take that OTA at some point without bricking the phone. I was told if I changed the CID back to VZW__001, then I wouldnt brick if I did an OTA...
Click to expand...
Click to collapse
When 4.3 is released, a rooted version will be available within a day or two. There is literally no reason to take an OTA ever.
sent from my HTC one
m4rk0358 said:
When 4.3 is released, a rooted version will be available within a day or two. There is literally no reason to take an OTA ever.
sent from my HTC one
Click to expand...
Click to collapse
That's what I figured. But better to know than not know
Sent from my Nexus 7 using Tapatalk 4
The fuss is if your phone is ever turned back to S-ON after having been S-OFF, there is a high chance that it will instantly brick itself if you have loaded unsigned firmware onto the device.
If I go S-OFF, proceed to unlock boot loader, install clockwork mid recovery and just debloat my phone or flash a ROM, I should fear bricking if S-ON is switched back on?
CNexus said:
The fuss is if your phone is ever turned back to S-ON after having been S-OFF, there is a high chance that it will instantly brick itself if you have loaded unsigned firmware onto the device.
Click to expand...
Click to collapse
godhamba said:
If I go S-OFF, proceed to unlock boot loader, install clockwork mid recovery and just debloat my phone or flash a ROM, I should fear bricking if S-ON is switched back on?
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but no, no worries with a custom ROM and recovery. Only for unsigned firmware, something like a custom hboot for example.
peteschlabar said:
Someone correct me if I'm wrong, but no, no worries with a custom ROM and recovery. Only for unsigned firmware, something like a custom hboot for example.
Click to expand...
Click to collapse
This is correct. If you flash an unsigned HBOOT and the flag goes S-ON somehow, the phone will refuse to boot because of the failed security check on the HBOOT. Besides that you're fine.
I have a carrier locked M8 that is rooted but S-On.
The vibrator motor on my phone quit and both HTC and my wireless provider have deemed it a hardware error that require repair. The device is under warranty. I need to send it in to get repaired. Given that it's still S-On, do I just need to restore the stock recovery and OS before sending it in?
Probably not safe to assume that because it's a hardware issue, the software doesn't matter?
A lot of times you can get away with sending in a modded phone. Most of those techs aren't smart enough (no offence) to notice things like that unless its major i.e the red text on the boot up screen, or a sense m8 running miui or maybe even GPE stuff. I would flash a sense ROM and a "no red text" bootloader before I send it in.
josh.walker.9242 said:
A lot of times you can get away with sending in a modded phone. Most of those techs aren't smart enough (no offence) to notice things like that unless its major i.e the red text on the boot up screen, or a sense m8 running miui or maybe even GPE stuff. I would flash a sense ROM and a "no red text" bootloader before I send it in.
Click to expand...
Click to collapse
But do you only get one shot at it? If they uncover its modded, surely they make record of it? Not like I could send it in, they send it back because it's modded, and then I could do a deeper clean (100% back to stock) before sending it back again, right?
Am I safer to clean it up entirely before sending it in?
djHandy said:
But do you only get one shot at it? If they uncover its modded, surely they make record of it? Not like I could send it in, they send it back because it's modded, and then I could do a deeper clean (100% back to stock) before sending it back again, right?
Am I safer to clean it up entirely before sending it in?
Click to expand...
Click to collapse
Correct, it would be safer to do a 100% cleasn stock restore just make a backup so you can slrestore it when you get it back.
josh.walker.9242 said:
Correct, it would be safer to do a 100% cleasn stock restore just make a backup so you can slrestore it when you get it back.
Click to expand...
Click to collapse
I'm following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2710735
It says I need to be S-Off to remove the red-text from the bootloader screen but then warns against switching back to S-On.
Is S-Off a flag to techs that the phone is tampered? Anything else I should consider before going S-Off without a way back or is S-Off really my only option to return my phone to a repairable/warranty-able state?
djHandy said:
I'm following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2710735
It says I need to be S-Off to remove the red-text from the bootloader screen but then warns against switching back to S-On.
Is S-Off a flag to techs that the phone is tampered? Anything else I should consider before going S-Off without a way back or is S-Off really my only option to return my phone to a repairable/warranty-able state?
Click to expand...
Click to collapse
This thread explains S-Off - http://forum.xda-developers.com/showthread.php?t=1680928.
Here's another good read - http://forum.xda-developers.com/showthread.php?t=2718106.
I would suggest going S-Off to flash the stock or no red text bootloader, then relocking the bootloader and going S-On until you get the phone back.