Develop Bugs

Need help with returning to stock or S-OFF root (issues caused by latest OTA)

When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!

Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app

To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?

You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.

I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?

sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!

Your welcome...

Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app

Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.

It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?

I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!

It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse

Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.

when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery

Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!

[Q] Have S-Off, Unlocked Bootloader, NO Root

I ran Rum runner and seem to have gained they S-OFF and unlocked bootloader but not Root/SU. I tried to flash the TWRP recover and I get a message that says Failed (Remote: not allowed). Can someone point me to or provide the steps I need to get a custom recovery and SU on the phone now?

TCommander said:
I ran Rum runner and seem to have gained they S-OFF and unlocked bootloader but not Root/SU. I tried to flash the TWRP recover and I get a message that says Failed (Remote: not allowed). Can someone point me to or provide the steps I need to get a custom recovery and SU on the phone now?
Click to expand...
Click to collapse
Here ye go: http://forum.xda-developers.com/showthread.php?t=2416431. Steps are pretty straight-forward.

XPEric said:
Here ye go: http://forum.xda-developers.com/showthread.php?t=2416431. Steps are pretty straight-forward.
Click to expand...
Click to collapse
I was following those instructions. When I run the command fastboot flash recovery openrecovery-twrp-2.6.3.0-m7vzw.img I get the error Failed (Remote: Not Allowed).
I have found a few things not specific to the HTC One that indicate I need to move TWRP into a recovery.img file inside a file like PD98IMG.zip that is automatically found in HBOOT. I can't seem to get that to work since I don't know the name the HTC One is looking for ands the ones I've guessed don't work.
Any more ideas?

Are you sure you unlocked the phone? Is there an "*UNLOCKED*" banner in the bootloader?

If you have S-OFF and are unlocked just flash a superuser .zip and you are rooted.
Sent from my 4G LTE HTC One

XPEric said:
Are you sure you unlocked the phone? Is there an "*UNLOCKED*" banner in the bootloader?
Click to expand...
Click to collapse
Positive

jbh00jh said:
If you have S-OFF and are unlocked just flash a superuser .zip and you are rooted.
Sent from my 4G LTE HTC One
Click to expand...
Click to collapse
Same Error trying to flash any .zip. I get the Failed (Remote: not allowed).

Get Flashify from the market and see if you can flash a twrp
custom recovery img. Then flash the superuser .zip.

jbh00jh said:
Get Flashify from the market and see if you can flash a twrp
custom recovery img. Then flash the superuser .zip.
Click to expand...
Click to collapse
I had already tried Flashify. I gave a message about the phone not being supported for flashing recovery images.

Ok, so to post an answer in case anyone else runs into this issue. I did have S-Off, I was Unlocked and I did have Superuser installed. To overcome the Failed (Remote: not allowed) error I had to run the cmd window (Windows 7) as an Administrator.
Thanks for the suggestions. Bone headed oversight on my part.

TCommander said:
I had already tried Flashify. I gave a message about the phone not being supported for flashing recovery images.
Click to expand...
Click to collapse
I was is in the same situation and Flashify worked for me.
I was able to flashTWRP and then flash superuser .zip in recovery.
---------- Post added at 12:45 PM ---------- Previous post was at 12:40 PM ----------
TCommander said:
I had already tried Flashify. I gave a message about the phone not being supported for flashing recovery images.
Click to expand...
Click to collapse
I was is in the same situation and Flashify worked for me.
I was able to flash TWRP and then flash superuser .zip in recovery.

i'm also stuck. i'm on a vzw htc one, s-off worked, but i cannot flash TWRP or CWM and thus, cannot get superuser. i tried the both versions of CWM (touch and regular) and the latest TWRP. no dice.
i am on android version 4.2.2, htc sense 5, 1.10.605.15.
s-off is confirmed UNLOCKED in bootloader menu. i used the correct version from rumrunner. i'm getting really frustrated. firewall, antivirus, etc, is all off. drivers are in tact. ADB commands work and i can navigate between fastboot and ABD when running command prompt as admin.
HELP!

johnfuture said:
i'm also stuck. i'm on a vzw htc one, s-off worked, but i cannot flash TWRP or CWM and thus, cannot get superuser. i tried the both versions of CWM (touch and regular) and the latest TWRP. no dice.
i am on android version 4.2.2, htc sense 5, 1.10.605.15.
s-off is confirmed UNLOCKED in bootloader menu. i used the correct version from rumrunner. i'm getting really frustrated. firewall, antivirus, etc, is all off. drivers are in tact. ADB commands work and i can navigate between fastboot and ABD when running command prompt as admin.
HELP!
Click to expand...
Click to collapse
Can you post a link to which version of the recoveries you are trying to flash?

Trouble with achieving root.
I just got an HTC One, ran rumrunner and achieved S-Off, but not root. I used the correct rumrunner for the ROM I have (1.10.605.15). I realize I could flash a custom recovery, but I'm looking to just root and continue to use Sense with the stock recovery for the convenience of OTA updates.
I tried to use the "fastboot boot" command to load up an image of TWRP (2.6.3.3) and then install root from there, but for some reason my device just freezes on the fastboot screen despite what feedback my console is giving me. I tried waiting and then flushing the cache to see what the result was. Picture below. Any help is appreciated.

Same here. I just got an HTC one from Verizon yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions above. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!

adodson927 said:
Same here. I just got an HTC one from Verizon yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions above. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!
Click to expand...
Click to collapse
The day Verizon does that is the day Google blocks them from using the play store. Either you are doing something wrong or you have corrupted nand memory.
Sent from my One using xda app-developers app

jbh00jh said:
If you have S-OFF and are unlocked just flash a superuser .zip and you are rooted.
Sent from my 4G LTE HTC One
Click to expand...
Click to collapse
Basic question: My recovery screen shows "***UNLOCKED***, M7_WLV PVT SHIP S-OFF RH". Does this indicate a state of S-OFF or S-ON? I ran rumrunner and thought that I had achieved unlocked and S-OFF status but I cannot run fastboot from a command line. I keep getting the reply that "fastboot" is not recognized as a command. So, I cannot flash twrp and I cannot gain root access. I'd be grateful for any assistance.

mordango said:
Basic question: My recovery screen shows "***UNLOCKED***, M7_WLV PVT SHIP S-OFF RH". Does this indicate a state of S-OFF or S-ON? I ran rumrunner and thought that I had achieved unlocked and S-OFF status but I cannot run fastboot from a command line. I keep getting the reply that "fastboot" is not recognized as a command. So, I cannot flash twrp and I cannot gain root access. I'd be grateful for any assistance.
Click to expand...
Click to collapse
From what you said you should be unlocked and s-off. Download twrp image and flash it with Flashify from the Play Store. That is what I did.
Rumrunner didn't jive with my windows 8.1.

jbh00jh said:
From what you said you should be unlocked and s-off. Download twrp image and flash it with Flashify from the Play Store. That is what I did.
Rumrunner didn't jive with my windows 8.1.
Click to expand...
Click to collapse
Thanks for the reply. I tried Flashify but since I don't have root, I can't run it. Apparently, rumrunner did not gain root on my device. I'm currently running rumrunner again to see if I can get some joy.

mordango said:
Basic question: My recovery screen shows "***UNLOCKED***, M7_WLV PVT SHIP S-OFF RH". Does this indicate a state of S-OFF or S-ON? I ran rumrunner and thought that I had achieved unlocked and S-OFF status but I cannot run fastboot from a command line. I keep getting the reply that "fastboot" is not recognized as a command. So, I cannot flash twrp and I cannot gain root access. I'd be grateful for any assistance.
Click to expand...
Click to collapse
M7WLV is the Google Play Edition of the HTC One, but this Forum is devoted to the Verizon variant of the HTC One, namely M7VZW.

[Q] Stuck in bootloader mode. No wifi. Adb can't find devices

Okay so, I had a problem of having no OS and had my htc m8 on soft brick for a while but i finally got that resolved by flashing a new rom on it. ( Here it is if you want to read: http://forum.xda-developers.com/htc-one-m8/help/os-installed-transfer-files-t3018626)
Unfortunately, I wasn't getting wifi on it. I tried 2 other roms and still no dice. I read online that i needed to update my firmware to do that. To do that, I needed to relock my bootloader so I did and the firmware flashed successfully.
Now my hboot is 3.19 instead of 3.16 and my bootloader says RELOCKED.However, when i go into recovery mode, my phone shows a picture of the dead android. I can't get past the bootscreen either so my phone is stuck on bootloader mode.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2497712 to help me get my phone unlocked again cause the unlock code at htc dev wont work again.
However, when i write adb devices, no serial number shows up now. adb shell says no devices connected.
I tried pushing and flashing a new recovery and rom in cmd and it said it failed.
I'm really grasping at straws at this moment since I can't really do anything.

Are you sure you are updated? In the bootloader, what does it say for "os"?
And what roms are you trying to flash? 4.4.4 or Lollipop?

And to unlock bootloader, start over at HTC Dev. See what happens. Instead of trying old code.
You can't flash a recovery with a locked bootloader.

I'm pretty sure it updated because everything looks different. Bootloader's background is black instead of white now too. When I flashed the firmware, everything seemed to be okay as well. . .
my OS says 3.11.1700.5
and i tried it at dev and generated a code, but it gave me an error and didn't give me a file. I tried to use my old file but that didnt work.

Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.

Darth said:
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Click to expand...
Click to collapse
Which RUU do I download from here? I'm confused.

Shiverfire said:
Which RUU do I download from here? I'm confused.
Click to expand...
Click to collapse
Read the whole first post. It tells you how to determine that.
Any help needed after trying, you can ask there. ?

I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001

Shiverfire said:
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery

SaHiLzZ said:
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
Click to expand...
Click to collapse
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/

Shiverfire said:
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Click to expand...
Click to collapse
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app

mikem2273 said:
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said, recoveries wont flash cause its stuck on Relocked mode. I cant fix that because adb devices wont see my phone.
All the other commands on the All-in-One root kit gives me this:" 'C:\Users\Admin' is not an internal or external command, operable program or batch file " regardless of where i do it. I don't understand what I'm doing wrong here.
I tried to put the 0p6bimg.zip file but it wont copy on to my sd card cause of some error saying not responding or disconnected.
I tried flashing it instead but it said the file was too large
I tried the latest firmware but it said Failed! verification error.
I tried using the RUU to update and it stopped on the 1/7 process saying Error 155: Unknown Error.
I think what i need to do and how to fix it but I just need adb devices to find my phone.
If i can do that I can unlock my bootloader, install a recovery, install a rom and be home free but I can't do that until it detects my phone. I've tried everything now including reinstalling my drivers three times now.
Please help :'(

You don't need adb devices to see the device. You need to put the phone in the bootloader and type fastboot devices.
Open the command prompt inside the folder where also the fastboot.exe file is located.

Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...

BerndM14 said:
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
Click to expand...
Click to collapse
No, you guys. I already said this. I already used the htc dev the first time to get my phone unlocked. I had to relock it to flash a firmware. Now I can't unlock it again.The token isn't working. I already used the token once and its not working for the second time. I need adb devices to use adb shell. That way I can adb push revone and unlock my bootloader, but im not sure if that would work either.
Edit: I tried htc dev by generating a code 3 times. It generated different ones, the last one worked.

Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?

Shiverfire said:
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Click to expand...
Click to collapse
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.

Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?

BerndM14 said:
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Click to expand...
Click to collapse
just flashed the boot.img and recovery.
cleared cashe and reinstalled super su.
same thing.

ckpv5 said:
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
Click to expand...
Click to collapse
wait, how do i know if its GPE? (I didnt buy a GPE phone)
I was able to download skydragon and android revolution before, the former was stock lollipop.
So what do I do? how do i install sense roms??

RUU Error 155 despite relocked bootloader

Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.

RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.

If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers

Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.

Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.

RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456

Back to Stock Recovery and Booload lock with S-ON

Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)

pyo[st said:
;73891974]Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
Click to expand...
Click to collapse
Bootloader status does not affect ability to take OTAs.
You need two things mainly to take the OTA:
1. Stock recovery matching your current software
2. An untouched backup image of the system partition matching your current software. This is needed if you're currently rooted.
Both can probably be found in the thread you linked. The backup image is flashed from twrp. The stock recovery is then flashed from download mode using this command:
Fastboot flash recovery yourrecoveryfile.img
But even after doing that, you might still get an error when trying to take the OTA. Easiest way to take it is to start from scratch, backup your phone's contents to your pc or sd card, and then run the latest ruu for your phone. This will bring you up to date, and will also allow you to make a backup system image from twrp before rooting so that you can easily take future OTAs. The ruu will also completely wipe your phone's contents.
So you can try the first method I mentioned, and if it doesn't work go with the ruu.

As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.

I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41

DummyPLUG said:
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, LINK
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
Click to expand...
Click to collapse
This RUU worked perfectly. And no the phone was not rooted, just unlocked Bootloader and TWRP as Recovery.
After flashing the RUU I got the July Security Patch and that is what I wanted.
Thank you very much, Problem solved

$tark3 said:
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
Click to expand...
Click to collapse
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about

DummyPLUG said:
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
Click to expand...
Click to collapse
Nah, i downloaded the exe and the zip file also.
Anyway fixed it. Just restored from a nandroid backup. Now back in stock
PS:In btw, anyone facing any battery drop issue??

So I run in another Problem. I got the latest OTA for Europe (July Security Patch) but now my Phone gets shown as uncertified in the google play app which means I can not download certain apps like Netflix via Appstore.
Now I already figured out why I get shown uncertified: the Bootload is still unlocked. I thought the RUU would fix this as well. And if I wanna go in to the recovery (there was an TWRP Recovery on it before) I just get a red triangle with an "!" in it. It wont boot into recovery. Had to hard reset the phone to be able to boot normally to android then.
Now I wanna flash the stock recovery and lock the Bootload again to get again the certified status from google again.
Now here I need help.
1. Can't find the matching recovery version (EU unlocked, July Securtiy Patch, 2.41.401.41). Can anyone help me find the recovery image I need?
2. How do I get the bootload locked again? My Brother unlocked it via HTCdev.com back then, that I know already. But the command fastboot oem lock does not work at all. It just does nothing.
So how can I lock the bootloader?
Thanks for the help.

If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?

Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.

pyo[st] said:
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
Click to expand...
Click to collapse
Try fastboot devices
Sent from a Glade Plugin.

Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Sloth said:
Try fastboot devices
Sent from a Glade Plugin.
Click to expand...
Click to collapse
Alright this command works and shows my device.
Now I am in bootloader (Shows Software Status: Modified; Unlocked, S-ON). Then I type in "fastboot oem lock" and I get:
FAILED (remote: unknown command)
finished. total time: 0.014s
Well at least now I get something, before just nothing happened. Any clue what I might do wrong here?
*edit*
So I am a big noob
Phone has to be in download mode then the command works and my phone shows me a message if I want to lock again. Unfortunately it will factory reset my phone as well (at least it says that) so I have to backup my data (again) first.
But thank you for your help, appreciate it.
Cheers!

So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?

pyo[st said:
;74318325]So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
Click to expand...
Click to collapse
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"

Mr Hofs said:
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Click to expand...
Click to collapse
Ye found a thread to it. But seems I dont need it. My Phone gets shown as certified again at google play store so I assume just "relocking" the bootloader seems to be enough.

.....