Develop Bugs

[Q] No ROM, CMW Recovery + unlocked/s=off (HELP ASAP)

I currently hate myself for my silly failure. Oh jeez, its embarrassing to explain but I was in a rush and didn't realize I was in the HTC One international ROM section and downloaded and installed ARHD not knowing my Verizon HTC One wouldn't work. Sigh, big failure on my part, I was trying to go skate but looks like I'm spending my Friday fixing my issues :crying:
Well, when in bootloader it tells me that my phone is unlocked and currently S=OFF. I have CWM Recovery flashed on it at the moment. I tried sideloading CM11 on, but ADB doesn't detect my device. Yet the strange part is Fastboot does. I have work in a little and desperately need my phone up and running before hand. (as my job revolves around my phone.)
Please, anyone out there know my situation? I've spent all day trying to find my solutions so i decided to turn to the experts. :fingers-crossed:

Find a ruu on this forum
Sent from my HTC One VZW using Tapatalk 4

coldconfession13 said:
Find a ruu on this forum
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
I've actually just recently been looking into that. Can I do it with s=off, the tutorials I've been reading for sprint HTC One's are saying to relock it?

Yea I believe Santod has a thread
Sent from my HTC One VZW using Tapatalk 4

coldconfession13 said:
Yea I believe Santod has a thread
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
I hate to be the n00b, but I already freaked up my phone once. (Thankfully its not really bricked) I can't lie, I'm pretty scared to fully mess it up haha. Is there anyone who can help me through it? I understand the steps on which through fastboot, but its the little things that I am not sure of.

Just do the ruu. No need to relock or s-on. What little things are you worried about? Ive seen threads that say you need to relock it too. But i knkw for a fact its not needed, as i did an ruu yesterday while s-off and unlocked in order to take the kk ota. Never lost s-off and never lost my unlocked status, despite hboot being downgraded and then upgraded.

cmlusco said:
Just do the ruu. No need to relock or s-on. What little things are you worried about? Ive seen threads that say you need to relock it too. But i knkw for a fact its not needed, as i did an ruu yesterday while s-off and unlocked in order to take the kk ota. Never lost s-off and never lost my unlocked status, despite hboot being downgraded and then upgraded.
Click to expand...
Click to collapse
Where do you get the correct Verizon RUU? Just purchased a used phone with S off / Rooted / with custom recovery.
Thanks. Trying to get the OTA Kit Kat to work..

http://forum.xda-developers.com/showthread.php?t=2485319
Bottom of second post.

cmlusco said:
http://forum.xda-developers.com/showthread.php?t=2485319
Bottom of second post.
Click to expand...
Click to collapse
Thank you for the lead. So any of these will work?
1.10.605.08 Decrypted RUU
1.10.605.10 Signed RUU
1.10.605.15 Decrypted RUU
1.10.605.15 Signed RUU
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Decrypted if you are S Off?
Signed if you S on?
Is my understanding correct in that I would need to Re-Lock the bootloader as well?

Yes they will all work, it dosent matter if its signed or not since your unlocked and s-off. 2.10.605.1 is obviously the newst. And no you do not need to relock the bootloader, i dont know how that mith ever got started.

[Q] Back to stock with s-on?

I have been trying to go back to stock and I am sure that I have missed it in the threads but is it even possible to do if I am s on? Iif I can't then is there a s off for 1.54.401.5 that I am missing. I have tried to relock bootloader and tried installing the stock backup but then the phone just stays in bootloader and I can't reboot into the system.

jdmohn12 said:
I have been trying to go back to stock and I am sure that I have missed it in the threads but is it even possible to do if I am s on? Iif I can't then is there a s off for 1.54.401.5 that I am missing. I have tried to relock bootloader and tried installing the stock backup but then the phone just stays in bootloader and I can't reboot into the system.
Click to expand...
Click to collapse
You can't with S-ON, at best, it will show RELOCKED

What have you actually changed? If you want s-off use firewater.

ashyx said:
What have you actually changed? If you want s-off use firewater.
Click to expand...
Click to collapse
Unfortunately I have one of the phones that can't s off with firewater. I have been trying for a wile. Plus I can't find any other way to get s off or that would solve all my problems. I have tried all the dab and fast boot commands and 3 or 4 other all in one programs that say they do it but one of the prerequisite of tho use is to be s off.

I'm not flaming, but S-OFF is not recommended for general users. You can live fine with S-ON. Going back to S-ON is ruled out for now, until someone finds a new way !
Sent from my S-ON unlocked M8

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?

Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.

There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.

jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.

ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.

Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?

ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.

Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????

So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!

ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.

jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?

ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.

jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

Phone now shows S-on and need to flash back to factory stock 5.0.2 Verizon

I need to return my phone to Verizon. I just noticed that in bootloader it now reads ***LOCKED*** S-ON. I am on HBOOT 1.61. I never turned it S-ON. Please tell me that I don't have to use Sunshine. I just bought a license for the replacement phone and just want to get this back to the factory. My CID-11111111 OS-6.22.605.3 I am searching the threads for an answer and can't find one. I did rumrunner, firewater to get there originally but that doesn't look like that is remotely possible. Sorry to start a thread but I think I would rather do whatever I have to do to not pay for my replacement.

Whipping_Post39 said:
I need to return my phone to Verizon. I just noticed that in bootloader it now reads ***LOCKED*** S-ON. I am on HBOOT 1.61. I never turned it S-ON. Please tell me that I don't have to use Sunshine. I just bought a license for the replacement phone and just want to get this back to the factory. My CID-11111111 OS-6.22.605.3 I am searching the threads for an answer and can't find one. I did rumrunner, firewater to get there originally but that doesn't look like that is remotely possible. Sorry to start a thread but I think I would rather do whatever I have to do to not pay for my replacement.
Click to expand...
Click to collapse
A signed ruu on the same level or above should flash fine as long as the phone doesn't have problems ( ie the write protected state they end up in when the emmc fails)
Sent from my Nexus 6 using Tapatalk

dottat said:
A signed ruu on the same level or above should flash fine as long as the phone doesn't have problems ( ie the write protected state they end up in when the emmc fails)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Please tell me how to flash this. Can I use adb and reboot-booloader then flash oemRUU. I'm just confused a little bit because I don't see a rom update utility like sprint that you run from your PC. I haven't seen any threads about phone's showing up as S-ON again so I'm being very cautious. I was able to use the utility to show it as untampered. I tried to run Sunshine and it said my phone was S-OFF. It's very confusing and haven't been able to find a walk through for this situation anywhere.
I found this HSM_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed3y3glpox68e83uf3 (1) (1).zip

I would try Sunshine's tech support first. You paid for their product, so they should walk you through what you need. They were very helpful with me when I accidentally turned my phone back to S-on .

Whipping_Post39 said:
Please tell me how to flash this. Can I use adb and reboot-booloader then flash oemRUU. I'm just confused a little bit because I don't see a rom update utility like sprint that you run from your PC. I haven't seen any threads about phone's showing up as S-ON again so I'm being very cautious. I was able to use the utility to show it as untampered. I tried to run Sunshine and it said my phone was S-OFF. It's very confusing and haven't been able to find a walk through for this situation anywhere.
I found this HSM_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed3y3glpox68e83uf3 (1) (1).zip
Click to expand...
Click to collapse
i need the zip/ruu for lollipop. could you share the link?

el_venga said:
i need the zip/ruu for lollipop. could you share the link?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24367857647223007
Sent from my SM-T810 using Tapatalk

Did you flash a faux locked hboot? Do a fastboot getvar all and paste the results here. Be sure to remove the imei and serial before posting.

Uzephi said:
Did you flash a faux locked hboot? Do a fastboot getvar all and paste the results here. Be sure to remove the imei and serial before posting.
Click to expand...
Click to collapse
I didn't flash an hboot. I used the "locked", "relocked", "unlocked", program by adb and it showed locked in fastboot. The Hboot was incorrect but I was happy. It didn't say relocked or tampered. Everything on the screen was correct.
The problem with doing it with Sunshine...I was fortunate enough to get my phone two years ago and used the other way. My replacement had to flash a previous hboot to be able to use sunshine and flash back to a Santod creation.

Help! After S-ON bootloader shows Software Status: Modified + can't boot

So I decided to use Sunshine to S-off and then root my brand new HTC 10. That all worked great and didn't even need to wipe my data. Unfortunately I just discovered the front-facing camera isn't working (just won't switch at all), so I need to return my phone. I did backups of everything, flashed stock recovery back, then did
Code:
fastboot oem writesecureflag 3
because that's what this thread said to do.
Now the phone only boots straight to the bootloader. It says Software status: Modified up the top and I can't boot up (when I select reboot it goes straight back to the bootloader). What do I do?

If you are currently S-ON LOCKED, just run a RUU to restore your software to fully stock and the "modified" tag will become "official".

Clonkex said:
So I decided to use Sunshine to S-off and then root my brand new HTC 10. That all worked great and didn't even need to wipe my data. Unfortunately I just discovered the front-facing camera isn't working (just won't switch at all), so I need to return my phone. I did backups of everything, flashed stock recovery back, then did
Code:
fastboot oem writesecureflag 3
because that's what this thread said to do.
Now the phone only boots straight to the bootloader. It says Software status: Modified up the top and I can't boot up (when I select reboot it goes straight back to the bootloader). What do I do?
Click to expand...
Click to collapse
Flashing RUU before running the cmd back to S-ON is the safest way to go.
Follow instructions from poster above and all should work out fine.

Ok, I've found the thread with the RUU, but it doesn't list my CID (OPTUS001). Does that matter?

Clonkex said:
Ok, I've found the thread with the RUU, but it doesn't list my CID (OPTUS001). Does that matter?
Click to expand...
Click to collapse
you cant flash any of the others unless you are s-off soooo

I dont know too much about how RUU's are packaged but I wonder if someone could make you a custom RUU that your phone would accept?
Im gonna dig through my zip out of curiousity lol..

REtails said:
I dont know too much about how RUU's are packaged but I wonder if someone could make you a custom RUU that your phone would accept?
Im gonna dig through my zip out of curiousity lol..
Click to expand...
Click to collapse
the RUUs have to be signed by HTC for S-ON phones to accept it

I just ended up sending the phone back (since the front camera was in fact broken) and we'll see what they say.