I am currently sitting with a device that has 4.4.2 and is S-On with the bootloader displaying *RELOCKED*.
I had the phone rooted and s-off from about a year ago using firewater/weaksause from about a year ago and put ViperRom on it and have just been using the Viper OTA updates. I am returning the phone and wanted to put it back to stock. I first used the 0P6BIMG.zip RUU with HBOOT to go back to stock. Then i tried to relock the bootloader but in adb it kept saying that I didnt have su installed. I tried to reinstall supersu and it still gave me the same error. I then loaded up hasoon2000 all in one kit and relocked the bootloaded and s-off-ed from there. I Thought everything was fine but now i loocked and it says *RELOCKED* not *LOCKED*.
From my understanding i cannot change from *RELOCKED* not *LOCKED* without s-off, and i tried reinstalling firewater/weaksause to get s-off but im not having any luck. It is currently at version 4.4.2. Can someone help?
desitdt said:
I am currently sitting with a device that has 4.4.2 and is S-On with the bootloader displaying *RELOCKED*.
I had the phone rooted and s-off from about a year ago using firewater/weaksause from about a year ago and put ViperRom on it and have just been using the Viper OTA updates. I am returning the phone and wanted to put it back to stock. I first used the 0P6BIMG.zip RUU with HBOOT to go back to stock. Then i tried to relock the bootloader but in adb it kept saying that I didnt have su installed. I tried to reinstall supersu and it still gave me the same error. I then loaded up hasoon2000 all in one kit and relocked the bootloaded and s-off-ed from there. I Thought everything was fine but now i loocked and it says *RELOCKED* not *LOCKED*.
From my understanding i cannot change from *RELOCKED* not *LOCKED* without s-off, and i tried reinstalling firewater/weaksause to get s-off but im not having any luck. It is currently at version 4.4.2. Can someone help?
Click to expand...
Click to collapse
AFAIK HAsoon does not support verizon devices so I'm not sure what you may or may not have done using that tool. when you say "not having any luck" with firewater/weaksauce, what does that mean?? What messages/errors is it giving you? Firewater hasn't worked for a while now so not sure it would necessarily work for you even on 4.4.2. You should probably try sunshine.
IF you can get s-off again follow this guide to get you to stock, s-on: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Try looking at this: http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
Oops, it says you first need to be s-off, sorry...
---------- Post added 25th March 2015 at 12:05 AM ---------- Previous post was 24th March 2015 at 11:49 PM ----------
Just some further info. I am brand new to HTC One M8, as in I am waiting for mine that I bought on swappa to ship. But I had quite a bit of experience playing with the HTC Rezound and S-off. On those, you had to be S-off to reset the H-Boot stuff. If you were S-Off, you had to relock the bootloader first and then run the RUU for the previous version. That reset all hboot warnings and changed the Hboot to read ***LOCKED***. That was the only way to do it. From browsing in this forum, BladeRunner offers a good option. Try using Sunshine to S-off. Only downside is that it will cost you $25 but should work for you: http://theroot.ninja/index.html
Related
Hi,
I'm very familiar with flashing ROMs on phones and have flashed a fair few in my time. I flashed my sisters Desire S a while ago but recently the phone has stopped detecting the SIM card and subsequently has to go back for warranty.
I've flashed a Stock rom over it - trouble is, I now have the locked HBOOT v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade HBOOT to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
I cannot for the life of me downgrade the HBOOT version - I've tried every method out there!
I am very familiar with working in command line on Windows and Linux so don't be afraid to get technical!
Any help is very much appreciated!
Daft question, but have you tried a different Sim?
Does she still have the box?
Swyped from my Desire S using XDA Premium
Haha I spent hours debugging the sim card issue and finally came to the conclusion it's a hardware fault!
Yes - tried several different sim cards from two different carriers (this household only uses 2 carriers!)
Also tried several different ROMs/Radios - she was happily using MIUI for months then she just told me it stopped detecting her SIM card - she certainly hasn't been playing with ROMs so I know it's nothing she has done.
Update: Box is long gone
I've flashed a Stock rom over it - trouble is, I now have the locked bootloader v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade bootloader to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
Can I skip the first step? I guess not.
What has me confused is that you flashed the 0.98 hboot and you said it was s on, now you ran the RUU, and its s off....
Did you use revolutionary to get s off or was it s off to start with?
The correct steps would be.. (if you use revolutionary)
1. Use fastboot to flash 0.98.2000 over the revolutionary one.
2. Run correct RUU.
Problem you could run into are cid's of the RUU (make a goldcard to avoid error) and two misc version being higher than RUU.
Thanks for the reply. I never said it was S-on, the phone was running a custom MIUI ROM with S-Off, I flashed a stock rom straight over the top of it by running the RUU (pretty sure I shouldn't have done!) now I have stock ROM with S-Off and locked HBOOT v2.00.0002
I cannot remember if I used revolutionary to get s off originally - it was many months ago, more than likely though. I remember the phone came with S-On and I had to make it S-Off.
I just want to get S-On again with stock rom but it's proving impossible!
So just to clarify, it is currently running stock rom with LOCKED HBOOT v2.00.0002 and S-Off.
I've tried manually overwriting the version with miscinfo, I've also tried the zerg method - all to no avail.
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
foX2delta said:
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
Click to expand...
Click to collapse
Haha want screenshots? I assure you that's what I've got.
Ran an older RUU which has downgraded my HBOOT to 0.98 or 0.68 (can't remember off top of my head) and am running stock rom, HBOOT says ***locked*** at top and also says S-OFF.
I think I'm getting there now.
I have previously rooted my device, but was bothered by the bootloader saying
Tampered
Unlocked
I then decided to restore it to factory/stock rom, which I was successful in doing, and bootloader is now relocked
I used Hasoon2000's toolkit and followed all the steps correctly, everything said it was successful but when i boot into bootloader says that it is still relocked
What could be causing this?
I'm running 2.20 btw, h-boot 1.14
htc one x evita AT&T
i am new to this as well but im pretty sure it will stay "relocked"
as you tampered with it already and there is no way of getting it back to normal (from what i read in the forums) more knowledgable people correct me if im wrong
i believe the only way to get it not to say relocked is with s-off
I think he's trying to unlock his bootloader again, not trying to get rid of the relocked message.
Sent from my HTC One XL
The only way to change that in the bootloader is to s-off then some other fun stuff.
Sent from my HOX w/CM10.1 4.2.2 s-off
ECEXCURSION said:
I think he's trying to unlock his bootloader again, not trying to get rid of the relocked message.
Sent from my HTC One XL
Click to expand...
Click to collapse
Yeah that's what I'm trying to do...
I just went through the toolkit process again, and same thing. still says relocked
Radio S-Off was mentioned, what are some of the basic steps required for that?
swagglikerichie said:
Yeah that's what I'm trying to do...
I just went through the toolkit process again, and same thing. still says relocked
Radio S-Off was mentioned, what are some of the basic steps required for that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38174259
Sent from my HTC One XL
sorry i misread your post
Hello,
So I have a HTC One XL Telstra (Australia) evita phone. I purchased it already rooted and I want to take it back to stock. I managed to RELOCK my phone back and now it only boots into the bootloader.
I have found the following RUU RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed but when I try to load it onto my phone I get an error that my bootloader is too new for this file. For the last two days I have been searching for a newer RUU but come up with nothing. Also CID hasnt been changed.
Now I am stuck, I am quite switched on with all OS but this is a first for me with Android. The following are the details in my bootloader:
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
Any help would be greatly appreciated. Also I don't have any backups.
Cheers!
You can't RUU backwards while you're s-on, that's your problem. Unlock your bootloader again, flash a custom rooted ROM, get s-off, then you can run any Evita RUU you want to.
Sent from my Evita
timmaaa said:
You can't RUU backwards while you're s-on, that's your problem. Unlock your bootloader again, flash a custom rooted ROM, get s-off, then you can run any Evita RUU you want to.
Sent from my Evita
Click to expand...
Click to collapse
Now this is where the fun starts, I thought of that but when I got to unlock it in htcdev the identification token is invaild for some unknown reason even though the CID hasnt been changed.
The idea is to just get it back to all stock.
Do you still have the original unlock token?
Sent from my Evita
Scratch that I just got a valid token but the whole purpose was to keep the bootloader locked with the stock OTA
Unlock. Twrp. Jb Rom. S-off. Ruu to older. Relock. Take stock otas.
Sent from my VENOMized HoxL
I know what your purpose is, and the instructions I detailed will get you there. Now that you've unlocked, flash TWRP, flash rooted ROM, get s-off, run the RUU you want to run, relock bootloader, take OTA's. It's the only way to do it after the mistake you made.
Sent from my Evita
timmaaa said:
I know what your purpose is, and the instructions I detailed will get you there. Now that you've unlocked, flash TWRP, flash rooted ROM, get s-off, run the RUU you want to run, relock bootloader, take OTA's. It's the only way to do it after the mistake you made.
Sent from my Evita
Click to expand...
Click to collapse
Half way there, up to s-off. Do you know of any tutorials specifcally related to the one xl? Btw thanks for all the help.
There are two s-off methods for our phone, Facepalm and Rumrunner. Facepalm won't work for you because it requires SuperCID, so Rumrunner is the one you want. Just go to that website and it explains everything. I haven't personally used it because I got s-off ages ago but it looks like a piece of cake.
Sent from my Evita
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
You're welcome by the way, happy to help.
Sent from my Evita
timmaaa said:
There are two s-off methods for our phone, Facepalm and Rumrunner. Facepalm won't work for you because it requires SuperCID, so Rumrunner is the one you want. Just go to that website and it explains everything. I haven't personally used it because I got s-off ages ago but it looks like a piece of cake.
Sent from my Evita
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
You're welcome by the way, happy to help.
Sent from my Evita
Click to expand...
Click to collapse
Rumrunner is definitely the way to go if you want to S-off your phone its so easy! Do you know of any RUU later than 1.89 Telstra? Most links I have a broken.
I believe the 1.89 RUU is the latest one, you can double check at androidRUU though.
Sent from my Evita
timmaaa said:
I believe the 1.89 RUU is the latest one, you can double check at androidRUU though.
Sent from my Evita
Click to expand...
Click to collapse
Yeh it is the latest one. I followed your instructions and now Im back to stock firmware which can receive OTA. Thank you so much for your help!
Hey guys,
My phone died from the dreaded "qhsusb_dload" issue, and since I cannot afford the replacement phone I really want, I bought another AT&T One X.
I had my previous one since March of last year and I have gotten everything done with no issues, including S-OFF, upgrading Firmware to 3.17 to use JB 4.2.2 and trying various Radios and Kernels, so I do have experience.
With this phone, completely stock, I unlocked the Bootloader, and at the top it shows TAMPERED and UNLOCKED. I now have two issues:
1. I cannot get into the Recovery. I flashed it manually from "Fastboot USB", as well as with EZ Toolkit Advanced (Evita) and WinDroidXL Tookit and it showed it was successful with each method, yet when I try to access it, I get the boot screen with the HTC logo for about 3 seconds then it just powers off completely.
I researched and tried TWRP 2.6 as well as CWM from WinDoidXL toolkit. I have also ran the "fastboot erase cache" command after installing the Recovery yet I still have the problem. I installed gapps to accomplish the same thing but I don't wanna use it just yet.
I am asking for help as I am afraid of bricking this phone as well. When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Please help me get this working as I am afraid to try it again with the fear of having it bricked.
I do not have root access (I need recovery to flash t he Super User zip file first, correct?) and my HBoot is 2.14 (can't remember what it was on my last phone). Do any of those play a part in the problem i'm having?
Thanks so much in advance
Does the phone boot up into the OS? What are your bootloader details?
Sent from my Evita
Hello again, timmaaa.
timmaaa said:
Does the phone boot up into the OS? What are your bootloader details?
Click to expand...
Click to collapse
badbwoydes said:
When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Click to expand...
Click to collapse
My phone works fine with stock ATT 4.1.1 that it came with, it's just the Recovery that won't launch, even though it appears to install fine when I flash it with fastboot.
My Bootloader shows:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14-1
Thanks
Are you checking the md5 after downloading the recovery?
Sent from my Evita
timmaaa said:
Are you checking the md5 after downloading the recovery?
Sent from my Evita
Click to expand...
Click to collapse
No, but I have tried 2 different versions from here, the one I had on my previous Evita, and I have also used the ones embedded in the WinDroidXL and EZToolkit Advanced (Evita).
I've seen others saying their phone ends up booting normally after selecting Recovery from the Bootloader but mine just powers off when I select it and I can't find a previous thread with this issue.
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
timmaaa said:
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
Click to expand...
Click to collapse
Would this be what you're referring to? http://forum.xda-developers.com/showthread.php?t=2390405
And if so, I can try S-OFF even though I don't have root access?
My CID is all 1's
My HBOOT wouldn't cause this prob?
You can disregard all that. I ran the install for TWRP 2.6.3.0 from the EZToolkit Advanced (Evita) then cleared the cache with the automated option in the same Toolkit, which I have tried like 10 times a few hours ago and now it's working... I swear all I did differently was leave the phone idle and plugged in for a while.
I'd still like to get the S-OFF done at this time. When I run "fastboot getvar cid" it returns "cid: 11111111" which means I have SuperCID and I can go through with S-OFF?
Finally, I cannot find a S-OFF guide for HBOOT 2.14 and ATT Firmware 3.18. This is for my HBOOT but not my Firmware http://forum.xda-developers.com/showthread.php?p=42631876
I found this http://forum.xda-developers.com/showthread.php?t=2485865 which states it's for 3.18 Firmware but shows nothing for my HBOOT.
I also found this http://forum.xda-developers.com/showthread.php?t=2540232
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
timmaaa said:
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
Click to expand...
Click to collapse
You have no idea how terrified I am right now, modding a phone that is basically the same as the one that got bricked a few days ago.
Thank you for your assistance. I will indeed go with Facepalm as that's the one I used in the past
In trying to update the HBOOT from 2.15 to 2.18, I tried to flash ATT 3.18 RUU on an S-OFF, Bootloader unlocked ATT One X.
Everything seem to go fine until I rebooted. Now all I can do is notice is that the top line reads as "RELOCKED" and the radio and everything else updated fine, but it won't go beyond the HTC logo now.
Tried flashing a recovery via FASTBOOT which seems to send the file but do nothing, I also tried to unlock it again using the original bootloader unlock.bin from HTCDEV, but that is failing as well. I can't go into recovery at all now to flash any custom ROM as well.
Any guidance on getting around this, I have seen some "Relocking" threads but none for AT&T HTC One X. Appreciate the forum's guidance in getting through this mess up.
Did you actually relock the bootloader yourself? An RUU can't normally do that.
Transmitted via Bacon
No, For some reason, my ADB/Fastboot commands didn't get response from the Phone, and then I simply flashed the RUU. That's where it started showing as relocked. After breaking sweat over what was happening, I went ahead and flashed it again and it seems The RUU was not successful in the 1st attempt since it booted nicely after the 2nd flash.
Currently I had to request a new unlock code to unlock the bootloader again and now it is unlocked successfully and the phone is alive and getting a rest before I flash 5.0 ROMs on it. I have renamed it Phoenix due to the 2 bricks it went through and still able to function as my primary device after 30 months of purchase.