[Q] Unable to install OTA update due to Seurity warning in bootloader - One (M7) Q&A, Help & Troubleshooting

while trying to install OTA UPDATE in my relocked HTC ONE [india], bootloader gives the following message TAMPERED>RELOCKED> Seurity Warning >M7_U PVT SHIP S-ON RH>HBOOT-1.44.0000...eMMC-boot... I just want to install the OTA UPDATE anyway. Please bless me with a reliable solution. Thanks in advance

ashimmk said:
while trying to install OTA UPDATE in my relocked HTC ONE [india], bootloader gives the following message TAMPERED>RELOCKED> Seurity Warning >M7_U PVT SHIP S-ON RH>HBOOT-1.44.0000...eMMC-boot... I just want to install the OTA UPDATE anyway. Please bless me with a reliable solution. Thanks in advance
Click to expand...
Click to collapse
Why dont u try Revolutionary S-off to properly lock your handset and also remove the relocked flag. I hope this might help. And are you still on stock rom ?

Re-Unlock your bootloader, security warning is a warning for say you that you aren't in stock rom.
You can relock your bootloader only if you're are stock...

Use revolutionary soff to set the bootloader as locked and remove the tampered flag.
Sent from my HTC One using Tapatalk 4 Beta

If you are S-Off it should not matter if your bootloader is locked or not. In fact your bootloader should stay unlocked. That's the whole point of being S_Off!
As long as you have a compatible (correct model ID) RUU installed and CID 11111111, you should be able to fastboot oem flash any RUU or OTA (that is correct for your base rom).
Otherwise S-Off is not working correctly. Read up on S-Off and what it really means for your device.
Having said that - a lot has changed in these new devices so research thoroughly!!!!!!

Theshawty said:
Use revolutionary soff to set the bootloader as locked and remove the tampered flag.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have a nandroid back up from which i rstored my stock ROM and relocked the bootloader. after that when i checked for software updates i got an update viz. 1.29.707.17,i downloaded it,and while trying to install it bootloader gives the following message TAMPERED>RELOCKED> Seurity Warning >M7_U PVT SHIP S-ON RH>HBOOT-1.44.0000...eMMC-boot....Installing revolutionary can solve this? ie. can i install the OTA update and use it with stock? One more thing is there any source to get the RUU_M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_ 166754_signed_2_4 [i have downloaded this in zip format,but i think flashing it via CWM won't clear the tampered flag/ security warning]
Thanks in Advance.

Guich said:
Re-Unlock your bootloader, security warning is a warning for say you that you aren't in stock rom.
You can relock your bootloader only if you're are stock...
Click to expand...
Click to collapse
if it's not in stock ROM then how it can recognize the OTA and download it?? before flashing the jB HD 4.2.2 rom i backed up my stock ROM via CWM as nandroid back up, which later i restored ,and relocked the bootloader

Pranay Kamdar said:
Why dont u try Revolutionary S-off to properly lock your handset and also remove the relocked flag. I hope this might help. And are you still on stock rom ?
Click to expand...
Click to collapse
Yes i restored my stock nandroid back up,dats y i got the OTA update i think. Using revolutionary can solve this? means can i use it with stock rom whenever i want and get official OTA updates installed timely???

ashimmk said:
I have a nandroid back up from which i rstored my stock ROM and relocked the bootloader. after that when i checked for software updates i got an update viz. 1.29.707.17,i downloaded it,and while trying to install it bootloader gives the following message TAMPERED>RELOCKED> Seurity Warning >M7_U PVT SHIP S-ON RH>HBOOT-1.44.0000...eMMC-boot....Installing revolutionary can solve this? ie. can i install the OTA update and use it with stock? One more thing is there any source to get the RUU_M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_ 166754_signed_2_4 [i have downloaded this in zip format,but i think flashing it via CWM won't clear the tampered flag/ security warning]
Thanks in Advance.
Click to expand...
Click to collapse
Go here and follow the guide in the OP: http://forum.xda-developers.com/showthread.php?t=2314582
Do all the steps and initialize revone, then type ./revone -l -t (-l locks the bootloader and -t removes the tampered flag)

Check out this page http://forum.xda-developers.com/showthread.php?t=2315497&page=7

Theshawty said:
Use revolutionary soff to set the bootloader as locked and remove the tampered flag.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
using revolutionary can help in restoring stock and getting further official OTS's ???

Theshawty said:
Go here and follow the guide in the OP: http://forum.xda-developers.com/showthread.php?t=2314582
Do all the steps and initialize revone, then type ./revone -l -t (-l locks the bootloader and -t removes the tampered flag)
Click to expand...
Click to collapse
I have a similar problem after trying to relock the phone with the latest Revolutionary HD ROM.
I have the *** TAMPERED ***, *** RELOCKED *** and *** Security warning *** message as well and cant' seem to get out of Fastboot mode - everything I try reboots me back in to it.
I have tried going the revone route, but cannot get it installed. Whilst 'Fastboot devices' brings it up, 'adb devices' doesn't recognise the phone.
I've updated the HTC sync drivers but that doesn't appear to make any difference.
Any further suggestions? Thanks.

Related

[Q] - Need immediate help on removing "TAMPERED" and "RELOCKED" text on boot

[Q] - Need immediate help on removing "TAMPERED" and "RELOCKED" text on boot
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEV.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
komsboy_more said:
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEC.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
Click to expand...
Click to collapse
Use the Revone toolkit if you can to gain s-on and to remove the relock and then flash with stock RUU.
This should be sufficiant to fool them in to believing that the phone is stock
gazlufc said:
Use the Revone toolkit if you can to gain s-on and to remove the relock and then flash with stock RUU.
This should be sufficiant to fool them in to believing that the phone is stock
Click to expand...
Click to collapse
Thanks you, but there is no RUU exe !
Version : 2.24.401.1
komsboy_more said:
Thanks you, but there is no RUU exe !
Version : 2.24.401.1
Click to expand...
Click to collapse
Use an older RUU and then try to update the device OTA.
Should work if i'm not mistaken.
gazlufc said:
Use an older RUU and then try to update the device OTA.
Should work if i'm not mistaken.
Click to expand...
Click to collapse
When I use an Older RUU, I receive ERROR! After searching, it seems that can't install older RUU to downgrade!
Even if it doesn't update right away, it's not a crime to have an older o's on your device. My girlfriends dad never updates his phones
Sent from my YP-G70 using Tapatalk 2
dB Zac said:
Even if it doesn't update right away, it's not a crime to have an older o's on your device. My girlfriends dad never updates his phones
Sent from my YP-G70 using Tapatalk 2
Click to expand...
Click to collapse
No it's no problem having older Firmware, aslong as it's not Modified, Has root Access or is S-Off.
So for warranty purpose it should be fine.
I know I accepted devices that haddent been updated when I was a repair agent
gazlufc said:
No it's no problem having older Firmware, aslong as it's not Modified, Has root Access or is S-Off.
So for warranty purpose it should be fine.
I know I accepted devices that haddent been updated when I was a repair agent
Click to expand...
Click to collapse
So do you have any solution for me ?
komsboy_more said:
So do you have any solution for me ?
Click to expand...
Click to collapse
I think you have to have S-off to go back to older firmware/RUU
maxal said:
I think you have to have S-off to go back to older firmware/RUU
Click to expand...
Click to collapse
Can I go S-OFF from whis guide ? :http://forum.xda-developers.com/showthread.php?t=2314582
Is it usable on windows ? ... I think CHMOD command is a linux command.
And for last question... If I go S-OFF then downgrade RUU and then update again, the "TAMPERED" text will removed ? and "RELOCKED" will changed to "LOCKED" as first day?
Regards.
komsboy_more said:
Can I go S-OFF from whis guide ? :http://forum.xda-developers.com/showthread.php?t=2314582
Is it usable on windows ? ... I think CHMOD command is a linux command.
And for last question... If I go S-OFF then downgrade RUU and then update again, the "TAMPERED" text will removed ? and "RELOCKED" will changed to "LOCKED" as first day?
Regards.
Click to expand...
Click to collapse
Yes that's the right guide for S-off The tampered text will not be removed but if you read through the Revone instructions it will tell you how to remove tampered text and lock your bootloader again, but do it before you upgrade to 4.2.2 as people are reporting revone is not working on the new bootloader within the 4.2.2 update.
htcdev.com is the problem I think...
komsboy_more said:
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEC.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
Click to expand...
Click to collapse
I think the problem will be the following :
You unlocked your phone via HTCDEV.com and so, HTC knows that your phone is unlocked...
Will it be accepted??
go figure...
gortys said:
I think the problem will be the following :
You unlocked your phone via HTCDEV.com and so, HTC knows that your phone is unlocked...
Will it be accepted??
go figure...
Click to expand...
Click to collapse
Yeah, but everyone MAY USE NOT the bin file to unlock the bootloader. May just download it. Right ?
maxal said:
Yes that's the right guide for S-off The tampered text will not be removed but if you read through the Revone instructions it will tell you how to remove tampered text and lock your bootloader again, but do it before you upgrade to 4.2.2 as people are reporting revone is not working on the new bootloader within the 4.2.2 update.
Click to expand...
Click to collapse
Thanks for your help man ...
I think that the steps I should fallow is like these:
1 - Go S-OFF through revone guide (I'll see S-OFF and "UNLOCKED" text in hboot after doing it. Right?)
2 - Removed "TAMPERED" text with this command : revone -t
3 - I should relocked my phone to prepare installing exe RUU. Right? How do this? With this command ? revone -l (or) revone -r. Witch one?
4 - Run related exe RUU. My best option will: http://www.androidfiles.org/ruu/?developer=M7
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
(or)
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
5 - Now I should go S-ON. I found this guide : http://forum.xda-developers.com/showthread.php?t=2358738
Is it necessary that I change my CID? My current one is : HTC__J15
Then fallow to S-ON and remove the revone from temp as guide.
After these steps I have a phone that is "LOCKED' with NO "TAMPERED" text in hboot.Right?
And can update it to 2.24.401.1 again from wifi and OTA.
Right?
Regards
htcdev.com is the problem I think...
komsboy_more said:
Yeah, but everyone MAY USE NOT the bin file to unlock the bootloader. May just download it. Right ?
Click to expand...
Click to collapse
Yeah, I think it's right, I already saw it but I think a little bit difficult to put in place. But in this case, HTC knows it
komsboy_more said:
Thanks for your help man ...
I think that the steps I should fallow is like these:
1 - Go S-OFF through revone guide (I'll see S-OFF and "UNLOCKED" text in hboot after doing it. Right?)
2 - Removed "TAMPERED" text with this command : revone -t
3 - I should relocked my phone to prepare installing exe RUU. Right? How do this? With this command ? revone -l (or) revone -r. Witch one?
4 - Run related exe RUU. My best option will: http://www.androidfiles.org/ruu/?developer=M7
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
(or)
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
5 - Now I should go S-ON. I found this guide : http://forum.xda-developers.com/showthread.php?t=2358738
Is it necessary that I change my CID? My current one is : HTC__J15
Then fallow to S-ON and remove the revone from temp as guide.
After these steps I have a phone that is "LOCKED' with NO "TAMPERED" text in hboot.Right?
And can update it to 2.24.401.1 again from wifi and OTA.
Right?
Regards
Click to expand...
Click to collapse
Once you gain S-off just run the RUU Iused 1.28.401.7 then remove tampered and then lock the bootloader folowing instructions from the Revone thread Ithink it's the second post.
Just reread through this thread and I beleive you have taken the OTA 4.2.2 update if this is correct I don't think you will be able to gain S-off as the new bootloader blocks it.
maxal said:
Once you gain S-off just run the RUU Iused 1.28.401.7 then remove tampered and then lock the bootloader folowing instructions from the Revone thread Ithink it's the second post.
Just reread through this thread and I beleive you have taken the OTA 4.2.2 update if this is correct I don't think you will be able to gain S-off as the new bootloader blocks it.
Click to expand...
Click to collapse
OK. Thanks. I don't need S-OFF again on 4.2.2.
I'll try it today and post result here.
komsboy_more said:
OK. Thanks. I don't need S-OFF again on 4.2.2.
I'll try it today and post result here.
Click to expand...
Click to collapse
No, you've misunderstood. As you are on 4.2.2 you cannot S-off so you are stuck with 'relocked' but you can remove 'Tampered' by flashing stock. Without S-off, you cannot go back to 'locked'
Sent from my HTC One using xda premium
drspikes said:
No, you've misunderstood. As you are on 4.2.2 you cannot S-off so you are stuck with 'relocked' but you can remove 'Tampered' by flashing stock. Without S-off, you cannot go back to 'locked'
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
OUW !
As there is no RUU for 4.2.2 also i CAN'T flash to stock to remove "TAMPERED"
I think removing "TAMPERED" will not help me. Because when a phone gone "UNLOCKED", the "TAMPERED" text appeared at same time.
And when a "RELOCKED" shown without "TAMPERED" => They found that it's un-normal.
Right?
komsboy_more said:
OUW !
As there is no RUU for 4.2.2 also i CAN'T flash to stock to remove "TAMPERED"
I think removing "TAMPERED" will not help me. Because when a phone gone "UNLOCKED", the "TAMPERED" text appeared at same time.
And when a "RELOCKED" shown without "TAMPERED" => They found that it's un-normal.
Right?
Click to expand...
Click to collapse
If your hboot is 1.54/1.55 then you cannot currently s-off so you either have to wait or send it back saying tampered/relocked.
However if this is a physical fault with the phone you should still be covered but if it's a firmware related issue then you maybe out of luck.

[SOLVED] CID change and repairs

There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.

[Q] PLEASE help me return to stock URGENT

2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
since you are s-off just download a ruu and flash it s-off allows you to run any ruu
jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Fails every time i try to flash the zip it goes through a couple steps then says failed. . . . :/
jerrycoffman45 said:
since you are s-off just download a ruu and flash it s-off allows you to run any ruu
Click to expand...
Click to collapse
will a ruu remove the tampered and unlocked ??
jande425 said:
will a ruu remove the tampered and unlocked ??
Click to expand...
Click to collapse
will removed tampered but not unocked
jerrycoffman45 said:
will removed tampered but not unocked
Click to expand...
Click to collapse
fu** sake i cant even flash the correct RUU
i downgraded my hboot to 1.44 and got super cid
but i still cant remove unlocked and tampered
alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off
jande425 said:
alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off
Click to expand...
Click to collapse
check my thread, replied to you there

Rumrunner not working on 1.55 / 3.62.206.1 after OTA - O2-UK

I received an O2 HTC One that had had some messing.
Device was S-ON, Tampered, Relocked with FW 3.62.401.1, custom ROM and HBOOT 1.55.
I unlocked the bootloader using HTVDev and ran rumrunner over it to get it S-OFF.
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Because I am a fool I forgot to Lock the bootloader and remove tampered before I went S-ON. I am now on 3.62.206.1 and rumrunner does not seem to work. I get to the same point every time...
Code:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (35/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
and then I get the FATAL error.
Things I have tried so far, all get to the same point:
1. Windows 7 w/ HTC Drivers provided with phone
2. Windows 7 w/ HTC Drivers downloaded
3. Windows 7 w/ CWM Drivers
4. Windows 8.0 w/ HTC Drivers provided from phone
5. Windows 8.0 w/ HTC Drivers downloaded
6. Windows 8.0 w/ CWM Drivers
7. Windows 8.1 w/ HTC Drivers provided with phone
8. Ubuntu 13.10
I am absolutely stumped. I can only assume that after the OTA update to 1.55 my phone is no longer vulnerable to whatever exploit Rumrunner uses.
Unless anyone else knows any reason for it to fail at this point?
Oh, and each OS was a clean install. I have spent a lot of time today on this!
Comedy- said:
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Click to expand...
Click to collapse
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?
nkk71 said:
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?
Click to expand...
Click to collapse
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.
Comedy- said:
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.
Click to expand...
Click to collapse
Have you tried http://firewater-soff.com/
I didn't even know about that one. Thanks very much. It did the job!
Comedy- said:
I didn't even know about that one. Thanks very much. It did the job!
Click to expand...
Click to collapse
:laugh::laugh::victory::victory::victory:

i'm a total htc noob (came from xperia to htc)

Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
cyrom said:
Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
Click to expand...
Click to collapse
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
clsA said:
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
Click to expand...
Click to collapse
so meaning to say, unlocking bootloader is a must, right?
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes if you want perm root
hello
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
clsA said:
Yes if you want perm root
Click to expand...
Click to collapse
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
cyrom said:
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
Click to expand...
Click to collapse
only if you get s-off ... you can not flash a RUU lower than your current software version with s-on
The post above by @sudhirtripathee explains alot
thanks for posting that
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
cyrom said:
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
Click to expand...
Click to collapse
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
clsA said:
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
Click to expand...
Click to collapse
sudhirtripathee said:
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
Click to expand...
Click to collapse
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
sudhirtripathee said:
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
thank you sir!
sorry for bumping this thread..
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
**LOCKED**
M7-UL PVT SHIP S-ON RH
HBOOT - 1.57.0000
RADIO - 4T.28.3218.04
Open DSP - v32.120.274.0909
OS - 6.13.708.1
eMMc - boot 2048MB
Jul 22 2014, 20:59:16.0
Click to expand...
Click to collapse
To gain permanent root access:
I'm gonna need to unlock bootloader first;
Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img);
Install custom recovery and install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.)
flash my stock nandroid
flash stock recovery (if fastboot boot recovery.img didnt work)
lock recovery
fix tampered/relock flag
done.
Thanks!
cyrom said:
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
To gain permanent root access:
1)I'm gonna need to unlock bootloader first; + 2)flash a custom recovery like TWRP
3)Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img); ---> fastboot boot recovery.img command only work on hboot 1.44 so you'll need to make a nandroid backup with the recovery installed on your phone which will overwrite your stock recovery.
Install custom recovery and 3)install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.) --> Firewater or Sunshine if firewater doesnt work.
flash my stock nandroid + flash back /data/preload folder (wiped when unlocking bootloader)
flash stock recovery (if fastboot boot recovery.img didnt work) If you can find your stock recovery somewhere (overwritten by the custom recovery)
lock recovery
fix tampered/relock flag ---> might come back if removed on hboot 1.55 and above
Click to expand...
Click to collapse
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
Click to expand...
Click to collapse
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
cyrom said:
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
Click to expand...
Click to collapse
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
alray said:
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
Click to expand...
Click to collapse
thanks for the heads up. i thought id never find ruu zip for my version.
cyrom said:
thanks for the heads up. i thought id never find ruu zip for my version.
Click to expand...
Click to collapse
just confirm that the ruu match your MID and CID
CID and MID of the ruu can be found in the android-info.txt file of the ruu
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
Click to expand...
Click to collapse
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
cyrom said:
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
Click to expand...
Click to collapse
yes hboot will also be downgraded. You will not loose s-off when flashing a ruu. Only turn s-on back if you must send the phone for warranty.

Categories

Resources