[Q] Revone s-off.. - One (M7) Q&A, Help & Troubleshooting

Hellow guys,
My device was S-OFF with Unlocked bootloader.. I made it back S-ON for some reasons and now it shows the annoying black flag on bootloader (*** TAMPERED ***).. I tried S-OFF it again but when I type the command [./revone -P] it gives me failed error -6 !!!
How do I remove the flag and S-OFF it again??
my device is unlocked bootloader with stock 1.44.0000 hboot
Any help would be appreciated

MohammadZkert said:
Hellow guys,
My device was S-OFF with Unlocked bootloader.. I made it back S-ON for some reasons and now it shows the annoying black flag on bootloader (*** TAMPERED ***).. I tried S-OFF it again but when I type the command [./revone -P] it gives me failed error -6 !!!
How do I remove the flag and S-OFF it again??
my device is unlocked bootloader with stock 1.44.0000 hboot
Any help would be appreciated
Click to expand...
Click to collapse
Exact same thing happened to me today!

I think it's a bug. I tried that on mine and I'm getting the same thing. Anyone posted it the dev thread yet?

Androidian10 said:
I think it's a bug. I tried that on mine and I'm getting the same thing. Anyone posted it the dev thread yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2394351
There's no solution for error -6, you have to wait.

The solution to error -6 is to just keep trying.
Also, OP - I've been reading your posts for the past few days, please stop f*cking around with your phone. You have no idea what you're doing and will brick it eventually. Or at least do some reading before you mess around. There's no reason to go S-ON once you're S-OFF unless you're returning for warranty/selling.

me_rashad said:
http://forum.xda-developers.com/showthread.php?t=2394351
There's no solution for error -6, you have to wait.
Click to expand...
Click to collapse
Do we know the cause?
Sent from my HTC One

WorldIRC said:
Do we know the cause?
Sent from my HTC One
Click to expand...
Click to collapse
yes:
daleski75 said:
If you put on the latest OTA then sorry you are out of luck revone will not work.
Click to expand...
Click to collapse

me_rashad said:
yes:
Click to expand...
Click to collapse
That's "a" cause...but considering I am back on original 1.44 HBOOT and firmware from April / May....

If you are on T-Mobile, you may have accidentally applied an OTA which leaves your HBOOT at 1.44 but patches the exploit revone and moonshine use to set S-OFF.
Again, ONLY on T-Mobile, it is possible to be on HBOOT 1.44 with a patched version that will NOT allow revone or moonshine to work. Hopefully they update these tools to get around this patch. They probably will, it's likely a short matter of time.
(If you suspect you're in this situation, don't even try to apply moonshine unless you know how to restore a stock boot image. Moonshine will quit after 10 tries with an error without restoring your boot!! Moonshine *does* back up your original boot in the folder it was run from, though).
I spent an unfortunate day trying to figure this out. Eventually I realized it and went home and swapped phones with my wife (she is just on pure stock anyway and doesn't give two hoots.) Her update was sitting in her status bar, unapplied! *woo*. I relocked and RUU'ed my phone to 1.27.531.11 and swapped sims with hers. Revone worked perfectly on hers right away and now we're all set.

any news on if this is updated? i just got this phone friday and i cannot get it to s off. I keep getting error = -6 also

psycho_maniac said:
any news on if this is updated? i just got this phone friday and i cannot get it to s off. I keep getting error = -6 also
Click to expand...
Click to collapse
Good news or bad news about error - 6?

ATT 1.44 and revone error -6 message
I have ATT 1.44 and revone error -6 message
is rumrunner working on ATT and this HBOOT
Thanks

strazicic said:
I have ATT 1.44 and revone error -6 message
is rumrunner working on ATT and this HBOOT
Thanks
Click to expand...
Click to collapse
yes, http://rumrunner.us/ or http://firewater-soff.com/
use a rooted ROM with unsecured kernel, inline with your firmware... since you're on hboot 1.44, i'd assume it's still 1.xx firmware, so you can use this one:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250

MohammadZkert said:
I made it back S-ON for some reasons and now it shows the annoying black flag on bootloader (*** TAMPERED ***).. I tried S-OFF it again but when I type the command [./revone -P] it gives me failed error -6 !!!
Click to expand...
Click to collapse
Hang on i think mine has always said TAMPERED in fastboot, is this not an ideal state????...what should it say, if rooted, twrp and custom rom installed?

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.

Stuck with error code -6 revone s-off problem

I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
Click to expand...
Click to collapse
Yes exactly. I am using the same hboot version which is 1.44
Also hboot is still unlocked my be thats the problem ?
At what point in the process are you getting the error?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
At what point in the process are you getting the error?
Click to expand...
Click to collapse
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
skylineGTR_34 said:
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
Click to expand...
Click to collapse
I may be wrong, but if you've already s off'd, I don't believe you need to do that step. Try skipping on to:
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
I tried every way, no luck.
similar problem
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Clough85 said:
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Click to expand...
Click to collapse
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Grand rthrues
iElvis said:
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Click to expand...
Click to collapse
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
1. Check that you have hboot 1.44
2. You can try 'Android Terminal Emulator' from PlayStore. and run the same commands there. you need to have the file on the root of your device.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
engage fica1di
dgtiii said:
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
Click to expand...
Click to collapse
Thanks for the clarification.
iElvis said:
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
Click to expand...
Click to collapse
Thanks for the info but that sounds scary to do. I'm still a noob at this i think i'll wait for the rev team to find a workaround.

[Q] Re-locked, s-on, Security Warning, and cannot boot into Recovery. My options?

Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?

Unlocking relocked bootloader fails

I had my bootloader unlocked, device was s-off, and super cid, then decided to sell my HTC one so I went back to s-on, restored my Telus Nandroid ( no RUU for Telus), relocked bootloader and then try to update it, it was then stuck so I pushed on power, went a little bit further, then stucked, power off and it completed. Now I decided to keep the device so I tried unlocking it again with HTC DEV, after flashing the unlock_code.bin it says it's successful but nothing happens on the phone. Any idea how to fix that?
Thanks
Anyone? I just can't think of anything else
Have you tried to push the file another one time?
However, now you're with 1.54 hboot or 1.44?
Guich said:
Have you tried to push the file another one time?
However, now you're with 1.54 hboot or 1.44?
Click to expand...
Click to collapse
I tried with like 10 files requested to the HTC DEV. I'm on 1.44. Thanks a lot for the help
stoned99 said:
I tried with like 10 files requested to the HTC DEV. I'm on 1.44. Thanks a lot for the help
Click to expand...
Click to collapse
Use the revone file and go s-off, after do all you need and stay with s-off also if you will sell it
Guich said:
Use the revone file and go s-off, after do all you need and stay with s-off also if you will sell it
Click to expand...
Click to collapse
I tried to go s-off a few times but it always failed with error -6. I remember when I went s-off (when I got the device) I had to do like 15 times before it finally works, I guess I'll need to keep on trying. Thanks for the help
stoned99 said:
I tried to go s-off a few times but it always failed with error -6. I remember when I went s-off (when I got the device) I had to do like 15 times before it finally works, I guess I'll need to keep on trying. Thanks for the help
Click to expand...
Click to collapse
Sounds like you're on 1.54, double check!
If you are still on 1.44 use a Rom based on 4.1.2 for biggest chance of success.
Sent from my HTC One using xda app-developers app
nkk71 said:
Sounds like you're on 1.54, double check!
If you are still on 1.44 use a Rom based on 4.1.2 for biggest chance of success.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nope, I'm really on 1.44, I checked a few times. And I also have a 4.1.2 rom. Thanks for your help.

[Q] I screwed up, Started S-Off, S-ON'd for a warranty repair, now I cant go back.

It's really all in the title. I originally went S-OFF with rumrunner, set back to S-ON with the HTC1Guru guide for a charge port warranty repair, now I can't get back to S-Off
Running a rooted stock sense 5.5 android 4.3 WWE ROM, from HTC1Guru, unlocked bootloader, HBOOT 1.56. Tried Rumrunner, moonshiner, revone, firewater, all failed! Is there any way to get me back to S-Off?
It's an unlocked One BTW.
Another weird thing is that in HBOOT, my OS line shows up blank, no numbers.
j.gaynon said:
It's really all in the title. I originally went S-OFF with rumrunner, set back to S-ON with the HTC1Guru guide for a charge port warranty repair, now I can't get back to S-Off
Running a rooted stock sense 5.5 android 4.3 WWE ROM, from HTC1Guru, unlocked bootloader, HBOOT 1.56. Tried Rumrunner, moonshiner, revone, firewater, all failed! Is there any way to get me back to S-Off?
It's an unlocked One BTW.
Another weird thing is that in HBOOT, my OS line shows up blank, no numbers.
Click to expand...
Click to collapse
OS line showing up blank isn't quite an issue. However, 1.56 S-OFF is luck. Some succeed, some don't.
If it cant be S-OFF'ed on ARHD 31.6, im afraid you may have to wait a little longer for a solid exploit.
raghav kapur said:
OS line showing up blank isn't quite an issue. However, 1.56 S-OFF is luck. Some succeed, some don't.
If it cant be S-OFF'ed on ARHD 31.6, im afraid you may have to wait a little longer for a solid exploit.
Click to expand...
Click to collapse
Damn. You sure it's not possible?
j.gaynon said:
Damn. You sure it's not possible?
Click to expand...
Click to collapse
What is the exact error message in Firewater?
j.gaynon said:
Damn. You sure it's not possible?
Click to expand...
Click to collapse
you can send your phone to fonefunshop.com and they will s-off it using a java card.
raghav kapur said:
What is the exact error message in Firewater?
Click to expand...
Click to collapse
I get the whelp message, so there's no point following up on that.

Categories

Resources