ATT ruu keep hboot 1.44 - AT&T HTC One (M7)

I need to send my phone in for a warranty reason, my bottom mic stopped working. I am currently S-off and on hboot 1.44. I was wondering what att RUU I should use to keep the ability to s-off in the chance that att denies the warranty claim.
What I want to do
- lock boot loader
- change relocked to locked using revone
- run RUU
- go back to s-on
- warranty claim
if warranty denied, is shouldn't be but I would rather be safe than sorry, I would like to be able to get s-off again.
is the the right right ruu or will this leave me with a phone I cannot s-off
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe
From what i can tell it should work, I think it keeps the same hboot but I just want to be sure.

Answered my own question the phone was on 1.26.502.12 already

Flashing an RUU won't return to s-on anyway

gunnyman said:
Flashing an RUU won't return to s-on anyway
Click to expand...
Click to collapse
I was worried about the RUU upgrading the hboot because I need to go back to S-on for a warranty claim.

Related

[Q] Returning to S-ON

Hi,
I have rooted HTC Legend with Alpharev S-OFF.
I want to return the phone to the carrier because I have a problem with the touch screen.
I understood that S-OFF cancels the warranty, but when I return to stock ROM (RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.exe) the HBOOT remains Alpharev S-OFF.
Anyway to flash the original 0.43 HBOOT over it?
Thanks.
amoskas said:
Hi,
I have rooted HTC Legend with Alpharev S-OFF.
I want to return the phone to the carrier because I have a problem with the touch screen.
I understood that S-OFF cancels the warranty, but when I return to stock ROM (RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.exe) the HBOOT remains Alpharev S-OFF.
Anyway to flash the original 0.43 HBOOT over it?
Thanks.
Click to expand...
Click to collapse
since you have alpharev hboot now (1.00) you can't downgrade, you can however upgrade to 1.01, just download the latest ruu and try installing that
According to the warranty, any software update I make, which is not made by the carrier, revokes the warranty, so either way - having S-OFF HBOOT 1.0 or having S-ON HBOOT 1.01 (The option you gave) - I can't repair it through the carrier..
Thanks anyway
amoskas said:
According to the warranty, any software update I make, which is not made by the carrier, revokes the warranty, so either way - having S-OFF HBOOT 1.0 or having S-ON HBOOT 1.01 (The option you gave) - I can't repair it through the carrier..
Thanks anyway
Click to expand...
Click to collapse
you can install the one i gave you so you have hboot 1.01 S-ON, and then you install the one of your carrier
should be possible
It will work, but the HBOOT will remain 1.01, and not 0.43.. So they will probably see that I did install a software on the phone.
amoskas said:
It will work, but the HBOOT will remain 1.01, and not 0.43.. So they will probably see that I did install a software on the phone.
Click to expand...
Click to collapse
Since we can't downgrade our hboot, you are stuck on S-OFF alpharev (1.00) or on
S-ON hboot 1.01
If you are going to send in your phone do it with s-on, i bet they dont even look at the hboot version, but if they do you better have s-on
Sent from my HTC Legend using XDA App

[Q] Help maintaining S-Off

Two lines of my digitizer are dead, so I am sending my unit back to Best Buy for repairs. They don't care about rooting, etc, since it is a clear hardware issue. I plan to send it in with S-Off on the most up-to-date Sprint rom in factory reset state.
My question is this: What is the maximum precautions I can take to prevent an update to HBoot 1.5?
Edit: Would installing the eng hboot prevent any sort of automatic update from reapplying S-ON?
Din65 said:
Two lines of my digitizer are dead, so I am sending my unit back to Best Buy for repairs. They don't care about rooting, etc, since it is a clear hardware issue. I plan to send it in with S-Off on the most up-to-date Sprint rom in factory reset state.
My question is this: What is the maximum precautions I can take to prevent an update to HBoot 1.5?
Click to expand...
Click to collapse
Updating to HBOOT 1.50 does not turn the phone S-On. You can still flash a different HBOOT if you are S-off and 1.50. As long as they give you back your phone (and not a different one), you should be fine.
It seems I am asking the wrong question. Without pushing the "fastboot oem writesecureflag 3" command on purpose, is there any way I could lose S-Off? I haven't heard of anyone having full S-Off and HBoot 1.5
Din65 said:
It seems I am asking the wrong question. Without pushing the "fastboot oem writesecureflag 3" command on purpose, is there any way I could lose S-Off? I haven't heard of anyone having full S-Off and HBoot 1.5
Click to expand...
Click to collapse
No, there is no way to lose s-off by applying any current HTC updates. I updated to HBOOT 1.50 from an S-off phone and it just said LOCKED at the top of the screen while in bootloader. I could still flash things like normal (if I remember correctly). I downgraded my HBOOT to the ENG version using the PG86IMG.zip method. It flashes fine (unlike an S-on HBoot 1.50 device), but I don't think the fastboot method of writing the HBOOT worked for me.
I just want to confirm, flashing the most up-to-date RUU will NOT turn on S-ON, nor will any other update besides a firmware level, targeted command?
Din65 said:
I just want to confirm, flashing the most up-to-date RUU will NOT turn on S-ON, nor will any other update besides a firmware level, targeted command?
Click to expand...
Click to collapse
Was I that unclear? I've flashed both of the ruu's containing hboot 1.50 and am still s-off. I even did HTC's unlock while on 1.50 just for fun. I'm now on the eng hboot. No current update does anything to reset the security flag.
Sent from my PG86100 using xda premium

S-off with locked bootlader...help

i unrooted running the 2.13 RUU and i ended up with s-off and the 1.19 bootloader. When i run the s-on program it says wrong bootloader...what can i do?
i just need to take my phone back to best buy to exchange

Relock phone to S-ON after jbear and HTCDEv

I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
vega312 said:
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
Click to expand...
Click to collapse
You need to start by flashing the 2.89.651.2 RUU, either using the RUU.exe from Windows or an RUU.zip renamed to PG86IMG.zip from the bootloader. If you didn't do the htcdev unlock again after the wire trick, the stock bootloader should show ***LOCKED*** with a version of 1.58. Since you are only getting the phone serviced, it's probably OK to leave it S-OFF, but if you want it 100% stock you need to issue the following command after you have verified that the bootloader is 1.58:
fastboot oem writesecureflag 3
Once you have issued this command your phone will be S-ON and you will have to do the wire trick again after you get it back to be S-OFF. My understanding is that most repair facilities, including Sprint, don't mind if you give it to them S-OFF. However, if you are sending it back to HTC it might be worth doing since with stock software, a locked bootloader and S-ON it will look "factory fresh" to them.
You might also want to test your GPS again once everything is back to stock, just to make sure it's not a ROM problem.
ramjet73
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
jb14813 said:
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?p=19089387

Need to return to stock, S-ON, No stock nandroid back up, have ARHD running

Pretty much subject says everything. But here's is my situation.
What I did earlier:
Unlocked Bootloader
Tried S-on with Firewater - didn't work - gave up- didn't spend money for getting S-off via moonshine
Installed TWRP
Installed custom roms
NOW, I need to go back to slock and claim some warranty issue (speakers too harsh)
Here's is an at&t RUU
http://forum.xda-developers.com/showthread.php?t=2757462
Can I go back to stock from here? Do I certainly need S-off? Do I just run RUU exe?
Please help!!
Thanks!
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Sent from my HTC One_M8 using Tapatalk
Jano342000 said:
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Click to expand...
Click to collapse
That's correct.
Also to the OP, note that AT&T only voids warranty for physical or water damage. They don't care about software mods, although it is a good idea to return to as close to stock as possible before requesting warranty exchange.
RUU is a good way to do so. S-on is fine, but you have to relock the bootloader. The bootloader will then say RELOCKED instead of UNLOCKED or LOCKED. No other evidence of modding should remain after the RUU.

Categories

Resources