Related
I'm currently running a custom ROM/Recovery. How would I go back to 100% evcerything stock?
kinglime said:
I'm currently running a custom ROM/Recovery. How would I go back to 100% evcerything stock?
Click to expand...
Click to collapse
try the t-mobile htc one forum?
nrfitchett4 said:
try the t-mobile htc one forum?
Click to expand...
Click to collapse
I'm on Verizon...
kinglime said:
I'm on Verizon...
Click to expand...
Click to collapse
(your avatar says t-mobile, throws us off.)
since you did you unlocking through htc DEV unlock (one can only assume anyway) you technically can't go back to full 100% stock.
your boot loader will always say unlocked or relocked.
S-OFF *may* be able to set you back to 100% stock but I forgot.
I would, ADB fastboot oem lock
this will change it back to "relocked" rather than "unlocked"
Verizon will still know you did HTC DEV unlock and technically can deny your warranty as you broke it by doing the HTC DEV unlock.
Personally though, I've sent back MANY HTC DEV unlocked phones to Verizon without re-repercussions.
I've been on Samsung for the past year though, so things may have changed, take what I say with a grain of salt.
hope this helps some.
Sorry! I forgot to change it from T-Mobile to Verizon when I recently switched. Anyways yes I was able to unlock via htcdev. Right now I'm running a custom rom and CWM custom recovery. I don't need to take my phone in or anything like that, I just want to return back to stock. Basically I'd like to go back to the software/recovery/everything that was running on the phone out of the box. How would I do this? Is there a link to the default recovery/rom, is that all there is to it?
kinglime said:
Sorry! I forgot to change it from T-Mobile to Verizon when I recently switched. Anyways yes I was able to unlock via htcdev. Right now I'm running a custom rom and CWM custom recovery. I don't need to take my phone in or anything like that, I just want to return back to stock. Basically I'd like to go back to the software/recovery/everything that was running on the phone out of the box. How would I do this? Is there a link to the default recovery/rom, is that all there is to it?
Click to expand...
Click to collapse
Until/IF, we get an RUU.. (don't hold your breathe for one)
you can't.
Sorry.
You could try and exchange it with another member who is stock and wants htc dev unlock?
AFAIK there is no stock recovery.img anywhere, not 100% though as I haven't searched.
Stock ROM you should have made a nandroid, if u didnt u can flash my stock deodexed ROM.
So with the release of the new S Off exploit is there any updated info to a full return to stock for warranty exchange that would leave you with a locked flag?
Sorry just found info in the General section!
Here is the Verizon HTC One RUU posted in the Android Development section - [RUU] Decrypted VZW RUU
The OP of the RUU mentions this is the decrytped version, and you need to use a tool called ruuveal to re-encrypt the RUU
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
JJGLive said:
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
Click to expand...
Click to collapse
You don't have to replace hboot unless you want to get rid of certain firmware messages, like the tampered flag. Unless you are sending your phone in for warranty work, you won't likely care about it, since you only see it in fastboot/hboot mode. The only thing the token does, besides unlock the boot loader, is remove certain preloaded apps, like the flashlight, which will screw up further OTA updates.
However, I would suggest you look into going S-off, as it makes locking/unlocking the boot loader possible without contacting HTC at all, and without messing up OTA updates. You also gain the freedom to change your CID (if you ever want to convert to stock Developer Edition), SIM unlock, and revert to older firmware if necessary (such as restoring an older RUU to go back to stock) However, S-off is "security off", so there is an increased chance of bricking the phone if you aren't careful.
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Click to expand...
Click to collapse
I would suggest you use this guide.
Im going to use it this friday to root my phone.
Ok so if I understand correctly now...using that guide I will not need to use htcdev and it will not be neccesary for me to flash boot.img after every rom flash?
JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
Click to expand...
Click to collapse
Not quite. To flash a custom ROM, all you need to do is unlock the bootloader, install custom recovery, and flash a ROM. In addition, I highly recommend you make a nandroid backup before flashing anything
S-off is only needed if you want to avoid the bootloader unlocking method via HTCDev.com (and HTC therefore having a record of you unlocking by IMEI); or to flash hboot, radio, firmware, or a few other things (such as SIM unlock). S-off is not needed to flash a ROM.
One caveat, if your phone presently has older firmware, you will experience some severe bugs on any Sense 2.x based ROM (long boot times, broken WiFi or Bluetooth) and having S-off is required to manually update the firmware. So, while in literal terms, S-off is not needed to flash a ROM. But if the above applies to you, you need s-off to manually update the firmware and get the ROM to work correctly. Alternately, you can OTA to the latest firmware before modding the phone. You will need to list your phone's hboot and present software version for us to tell you what firmware you are on.
Also, its not necessary to root before flashing a custom ROM. You will be rooted after you flash a custom ROM.
JJGLive said:
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
Click to expand...
Click to collapse
Definitely not correct. That guide is for the M7. Be careful what device forum section you are in, and stay in the M8 section.
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
JJGLive said:
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
Click to expand...
Click to collapse
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
redpoint73 said:
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
Click to expand...
Click to collapse
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
JJGLive said:
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
Click to expand...
Click to collapse
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
redpoint73 said:
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
Click to expand...
Click to collapse
Thank you very much...I feel much more welcome in the htc one m8 thread than I did when I first started on the samsung s4 thread. You have made me feel very welcome!
Thankfully we have freegee for LG OG. Bootloader is really dangerous please keep in mind before you go for any tutorials
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!
It been a long time.. Well maybe 3years since i been on xda. I still remember how to root and flash this n that n etc... But yesterday i wanted to get started on flashing my verizon m8 onto a rom. Yeah little complicated. I tried everything to unlock my bootloader i keep getting the 172 error. Still considered S-on, So i just left that alone and tried to go #oldschool. I tried to update using htc sync manager. But I had to leave and go to the store. Left this on the computer to finish updating. came back 20-30mins later its on a black htc screen with the green line across. So i thought it was just finished But my computer had been frozed for 10mins. (ive checked the time) but Now it gotten bricked. i can only boot into hboot... Fastboot... And ruu.. But not recovery... I Already downloaded the rom, and the latest twrp recovery on my pc. But im still s-on.. I really don't got time to start from scratch and just factory reset this.. And im no longer worried about my data and shxt because i know im eventually going to losed them anyway. So right now its on fastboot. My win7 detects it in fastboot usb. So where do i go from here? Anybody? No worries though :fingers-crossed: :angel:
You can't unlock the bootloader on the VZN version by HTCDev.com, you need to s-off by sunshine, then use sunshine to unlock the bootloader.
Unfortunately, sunshine requires a working OS. So first you'll need to RUU back to working stock. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
After that, you will need to root (think kingroot is the mot common method) then you can load the sunshine app ($25 license) to s-off and unlock the bootloader: http://theroot.ninja/
Once the bootloader is unlocked, you can load custom recovery TWRP and flash a custom ROM.
But keep in mind, there are kernel differences between the VZN version and most other M8 versions. Meaning, you will need to either flash a ROM that explicitly states it supports the VZN M8; or you can flash other ROMs, but you will need the proper kernel.
You'll want to read up in the Verizon M8 forum section, as this version has some peculiarities, as I've mentioned: http://forum.xda-developers.com/verizon-htc-one-m8
I am completely new at this and figured out how to unlock, root, and s-off using Sunshine. I received a new HTC 10 because my original phone's speakers cracked. I know I need to S-on, then run the ruu, and then s-on agian. I just cant figure out where to get the ruu for my phone.
I backed up my phone before on TWRP before changing the ROM and cant seem to find the file. I have three days to return my phone or Ill get charged for the phone. I need help please.
lou8414 said:
I am completely new at this and figured out how to unlock, root, and s-off using Sunshine. I received a new HTC 10 because my original phone's speakers cracked. I know I need to S-on, then run the ruu, and then s-on agian. I just cant figure out where to get the ruu for my phone.
I backed up my phone before on TWRP before changing the ROM and cant seem to find the file. I have three days to return my phone or Ill get charged for the phone. I need help please.
Click to expand...
Click to collapse
I believe you'll need to grab the system image from someone that backed it up and restore that way? I'm not sure as I'm new to this device.
Sent from my HTC 10 using XDA-Developers mobile app
both stock tmobile recovery and rom are in the stickied guide to root/recovery. I just recently sent my device back for warranty replacement.
stock recovery is here : http://forum.xda-developers.com/showpost.php?p=67248508&postcount=505 and stock rom is in OP.