Hi,
I'm trying to S-OFF my sister-in-law's HTC Flyer and then put a more recent Android OS on it.
The Flyer is currently running OS 3.2.1, software 3.55.405.1 with the 1.11.0011 HBOOT.
I've been trying to research this for the last few weeks and so far I've:
1. Unlocked the bootloader via HTC Dev
2. Installed Revolutionary CWM v4.0.1.4 recovery
3. Rooted
However, I understand that to upgrade to a more recent OS (e.g. 4.x) I need S-OFF. The device is currently S-ON.
I also understand I need to downgrade to an earlier HBOOT and OS which will allow me to use tools to S-OFF. Once I've done that, then I can put a much more recent CFW on it and thus a newer OS.
However, here's the problem. Running an appropriate RUU doesn't work. It does nothing at all. I've donwloaded one from two different sources and neither do anything. They just say 'sending....' for hours on end, and when I give up a reboot I see RUU failed and then reboot again and device is back to where it was before. Nothing's changed.
If what I understand above is correct, what's my next course of action?
It's a P510e HTC Sense 1.1 (Fastboot getvar cid says HTC_16 so it's a PG4110000) with 3G and Wi-Fi.
Thanks in advance!
richych said:
Hi,
I'm trying to S-OFF my sister-in-law's HTC Flyer and then put a more recent Android OS on it.
The Flyer is currently running OS 3.2.1, software 3.55.405.1 with the 1.11.0011 HBOOT.
I've been trying to research this for the last few weeks and so far I've:
1. Unlocked the bootloader via HTC Dev
2. Installed Revolutionary CWM v4.0.1.4 recovery
3. Rooted
However, I understand that to upgrade to a more recent OS (e.g. 4.x) I need S-OFF. The device is currently S-ON.
I also understand I need to downgrade to an earlier HBOOT and OS which will allow me to use tools to S-OFF. Once I've done that, then I can put a much more recent CFW on it and thus a newer OS.
However, here's the problem. Running an appropriate RUU doesn't work. It does nothing at all. I've donwloaded one from two different sources and neither do anything. They just say 'sending....' for hours on end, and when I give up a reboot I see RUU failed and then reboot again and device is back to where it was before. Nothing's changed.
If what I understand above is correct, what's my next course of action?
It's a P510e HTC Sense 1.1 (Fastboot getvar cid says HTC_16 so it's a PG4110000) with 3G and Wi-Fi.
Thanks in advance!
Click to expand...
Click to collapse
First try this http://revolutionary.io/
Basicly follow instructions on site.
If it doesnt help, xda forums are full of threads which will help you.
Hi,
Thanks for the reply, but I've already visited that site. Unfortunately, it isn't of any help to me as I'm not running the required HBOOT version. Mine is later (v1.11.0011) and it needs to be downgraded to an earlier version before S-OFF can be achieved via revolutionary.io.
So, I guess I firstly need to find a way to downgrade from 1.11.0011 to an earlier HBOOT before I can then S-OFF and add a custom ROM running a later Android OS.
richych said:
Hi,
Thanks for the reply, but I've already visited that site. Unfortunately, it isn't of any help to me as I'm not running the required HBOOT version. Mine is later (v1.11.0011) and it needs to be downgraded to an earlier version before S-OFF can be achieved via revolutionary.io.
So, I guess I firstly need to find a way to downgrade from 1.11.0011 to an earlier HBOOT before I can then S-OFF and add a custom ROM running a later Android OS.
Click to expand...
Click to collapse
downgrade from here http://forum.xda-developers.com/showthread.php?t=1307759
Sent from my HTC Flyer P510e
htcflyerhc said:
downgrade from here http://forum.xda-developers.com/showthread.php?t=1307759
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
Hi,
For some reason, the RUU approach isn't working for me.
If I try using the util itself, it never sends the file to the Flyer. I've sourced the RUU from two different locations on the 'net, with the same result. I discovered that the ROM.ZIP in both wasn't a valid ZIP file so I couldn't try the misc_version method (*and* worryingly Kaspersky 2014 detects the misc_version file as Malware and deletes it so I'm concerned about that method anyway).
I've rooted and CFW'd three devices in the past (a G2 Touch, an SII and a TF301T) but this HTC Flyer is a pain in comparison (and I have a Desire HD to do next!).
richych said:
Hi,
For some reason, the RUU approach isn't working for me.
If I try using the util itself, it never sends the file to the Flyer. I've sourced the RUU from two different locations on the 'net, with the same result. I discovered that the ROM.ZIP in both wasn't a valid ZIP file so I couldn't try the misc_version method (*and* worryingly Kaspersky 2014 detects the misc_version file as Malware and deletes it so I'm concerned about that method anyway).
I've rooted and CFW'd three devices in the past (a G2 Touch, an SII and a TF301T) but this HTC Flyer is a pain in comparison (and I have a Desire HD to do next!).
Click to expand...
Click to collapse
did you unlocked the flyer via htc dev?
Sent from my HTC Flyer P510e
---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------
or try this http://forum.xda-developers.com/showthread.php?t=1428104
Sent from my HTC Flyer P510e
htcflyerhc said:
did you unlocked the flyer via htc dev?
Sent from my HTC Flyer P510e
---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------
or try this http://forum.xda-developers.com/showthread.php?t=1428104
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
Yes, unlocked via HTC Dev then rooted by adding the Revolutionary CWM v4.0.1.4 recovery image.
there is no malware on misc file you can use it and open the ruu wizard wait for couple seconds the take the rom.zip, be sure that you have at least 700 mb free memory on your pc before starting the ruu wizard.
Sent from my HTC Flyer P510e
htcflyerhc said:
there is no malware on misc file you can use it and open the ruu wizard wait for couple seconds the take the rom.zip, be sure that you have at least 700 mb free memory on your pc before starting the ruu wizard.
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
Okay, I've followed the misc_version instructions (temporarily turned off Kaspersky so it wouldn't complain) and even though I have now relocked the bootloader etc. the RUU *still* doesn't do anything. It reboots the Flyer, but afterwards it just sits there and says it's sending but never does! There was an error that flashed up sometime during the 'adb' or 'adb shell' stuff - mentioning too many links - so maybe there's another issue somewhere?
richych said:
Okay, I've followed the misc_version instructions (temporarily turned off Kaspersky so it wouldn't complain) and even though I have now relocked the bootloader etc. the RUU *still* doesn't do anything. It reboots the Flyer, but afterwards it just sits there and says it's sending but never does! There was an error that flashed up sometime during the 'adb' or 'adb shell' stuff - mentioning too many links - so maybe there's another issue somewhere?
Click to expand...
Click to collapse
if you do all the steps from the links above it must work i dont know why you cant downgrade try puting the rom.zip on your sdcard and reboot to bootloader be sure that rom.zip is not corrupted and rename the rom.zip to PG41IMG.zip.
Sent from my HTC Flyer P510e
htcflyerhc said:
if you do all the steps from the links above it must work i dont know why you cant downgrade try puting the rom.zip on your sdcard and reboot to bootloader be sure that rom.zip is not corrupted and rename the rom.zip to PG41IMG.zip.
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
I'd downloaded RUUs from different sites on the 'net and Windows reported the rom.zip they contained was duff. However, just tried testing one with 7zip and that reported the zip was fine (and I extracted it as a test), so for some reason my Windows 7 is unable to read the zip file correctly, which might explain why RUU was failing to work?
Anyway, I copied the RUUs resulting rom.zip file to the SD card and renamed it as suggested.
I ran misc_version via adb and set it with the correct RUU version (2.00.405.3) and then exited back to the command line, and told adb to reboot to bootloader. Bootloader loaded and checked the PG41IMG.zip file, and it then reports "Main Version is older! Update Fail!", which I expected misc_version to avoid?
(If I try 'adb reboot bootloader' from the # su prompt rather than exiting first, adb shell reports that it can't find the device. Is that relevant at all? I assumed you had to exit back to the Windows cmd prompt before doing 'adb reboot bootloader' (which works) but could that be where I'm going wrong?)
Just in case it's at all relevant, 'fastboot getvar all' tells me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0011
(bootloader) version-baseband: 3822.10.08.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0950
(bootloader) version-main: 3.55.405.1
...
(bootloader) product: flyer
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4110000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 4191mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f0e1145e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I'm using RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed, which I am guessing would be the correct version as I think I need 405.3 to be able to then get S-OFF and upgrade to a newer OS.
The flyer is 3G and Wi-Fi, HBOOT 1.11.0011, running 3.55.405.1. It's on Talk Mobile (via Vodafone) for 3G data and the device seems to originate from South Africa rather than the UK, but I'm assuming WWE is going to be okay?
did you installed recovery and su before trying to use the misc file?
Sent from my HTC Flyer P510e
htcflyerhc said:
did you installed recovery and su before trying to use the misc file?
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
Yes. The phone was unlocked, new recovery and rooted before I tried misc_version.
i really dont know whats the problem
Sent from my HTC Flyer P510e
htcflyerhc said:
i really dont know whats the problem
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
It's okay, you've been really helpful - and patient - so I'm really grateful for your suggestions. I thought I was getting close up until I got the old version problem!
I'll try again (and again) and see what happens.
Thanks anyway!
richych said:
It's okay, you've been really helpful - and patient - so I'm really grateful for your suggestions. I thought I was getting close up until I got the old version problem!
I'll try again (and again) and see what happens.
Thanks anyway!
Click to expand...
Click to collapse
Your welcome, i really want to help you but i cant figure out what is causing the problem.
Sent from my HTC Flyer P510e
Bricked?
Unfortunately, something very odd has now happened to the HTC Flyer. It was left plugged in to my PC, slowly charging via USB.
We went out for part of the day, came back and the device is now caught in a perpetual loop. Screen goes off for about 7 seconds, then comes back on, stuck in FASTBOOT USB (if I'm connected via USB) or FASTBOOT AC (if I'm using a plug) for about 3 seconds before going off and then repeating the cycle. The power button flashes orange on/off throughout this loop.
I have noticed that apart from the usual info (e.g. S-ON, etc.), it also has one important addition underneath *** RELOCKED ***, which is:
*** Security Warning ***
The options I have are:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
As I only have 3 seconds, I don't have the time to select anything other than BOOTLOADER and the instant the HBOOT screen appears, the device starts the cycle again and I'm back to the beginning.
Any suggestions before I have to inform my sister-in-law that her flyer is now a brick?
put the honeycomb rom on your sdcard and reinstall it.
Sent from my HTC Flyer P510e
htcflyerhc said:
put the honeycomb rom on your sdcard and reinstall it.
Sent from my HTC Flyer P510e
Click to expand...
Click to collapse
Hi,
Sorry to be a bit slow, but I need a few more details?
I've got a backup of my system (via Revolutionary recovery mode) from a few weeks ago. That presumably includes the Honeycomb ROM (the flyer was running 3.2.1), but how do I reinstall it when the Flyer is stuck in this loop?
The backup contains: boot.img, cache.img, data.img, nandroid.md5, recovery.img, system.img
The system.img file will be the ROM as it's 768MB.
I don't see how to get the Flyer to do anything whilst it's stuck like this. It doesn't switch on at all if it isn't plugged in (USB or AC) and it's in this loop if it is plugged in. I don't think it's charging the battery at all whilst it's in this loop, and the battery doesn't seem to have any charge if it's not plugged in!
download the hc rom take the rom.zip and put in on the sdcard
Sent from my HTC Flyer P510e
Related
Need help
Tried to upgrade to HC with the Leedroid HC ROm.
1. Got S-off and root (revolutionary)
2. Installed HC radio and revolutionary hboot
3. unlocked bootloader
4. cleared disk and tried installing the Leedroid Rom with recovery install zip
wont get past white htc boot screen; been at this couple hours now..
My original Hboot Screen:
***Locked***
FLYER PVT SHIP S-ON RL
HBoot - 1.11.0003
MICROP - 0950
Radio - 3809.07.04.06_M
eMMC-Boot
Jul 18 2011, 15:23:21
After S-off Hboot Screen:
--Revolutionary--
FLYER PVT SHIP S-OFF RL
Hboot - 6.10.1002
MICROP - 0950
Radio - 3809.07.04.06_M
eMMC-Boot
May 4 2011, 11:04:45
Current bootscreen after failed HC upgrade:
***Unlocked***
FLYER PVT SHIP S-On RL
Hboot 1.11.0011
MICROP - 0950
eMMC-Boot
Radio 3822.10.08.07_M
My RUU is
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
I can get access to fastboot and recovery,
Tried to downgrade using its original RUU, but its fails at the end with both globaltron methods; I think im doing something wrong here.
Method 1: followed the easy install guide
http://forum.xda-developers.com/showthread.php?t=1307759
When pushing
"adb push misc_version_flyer_wifi /data/local/tmp/misc_version"
it says No such file or directory
but file is in root sd folder
Method 2: Downgrade from HC beta leaks or official HC OTA to Gingerbread
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Im using the "RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20 .3504.30.089BU_3809.07.04.06_M_release_204116_sign ed.zip" file.
Pushed the bootloader, all seems fine, then at after "oem rebootRUU",
it restarts and there is black htc start screen instead of white and hangs.
Restart to go to hboot.
in Fastboot I flash rom.zip
I get fail message:
sending 'zip' (500195 KB)... OKAY [ 94.924s]
writing 'zip'... INFOadopting the signature contained in this image...
FAILED (remote: not allowed)
finished. total time: 94.926s
You want to flash the zip in that black screen
Sent from my HTC Flyer P510e using xda premium
And looks like you never relocked your hboot. And you are using dated method to go to hc, should be using globatron s off hc method
Sent from my HTC Flyer P510e using xda premium
yea I should have gone with globatrons method instead of Pauls. Did not know there was a difference, and the only reason I went with Pauls is that there were some instructions for flashing radio and other files from Leedroids zip package.
Also, did not know you can still access fastboot with the black htc screen.
There are two RUU for Best Buy tablet:
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001 (find out by in fastboot type: fastboot getvar cid )
Frist RUU: 2.27.1540.31
Tried 2.27.1540.31 RUU, which i read is newer latest updated android, but this give me the following error:
sending 'zip' (500195 KB)... OKAY [ 77.920s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 83.743s
Second RUU: 1.36.1540.32
On the 1.36.1540.32 RUU, the extracted Hboot name is a .img file and wont push in adb. Says error device not found and cannot continue. Does this file have to be a .nb0 like the other RUU?
You should not be trying to push hboot anyway and you cannot use adb unless in recovery
Did you OEM lock?
Sent from my HTC Flyer P510e using xda premium
Thank you mcord! flashed worked with the 2.27.1540.31 RUU and it was the due to not locking the bootloader. Thought locking the bootloader only applied to globaltron's method 1 as that says to do so and is absent in method 2 instructions.
will soon write what i learned so that it may help someone else.
mcord11758 said:
You should not be trying to push hboot anyway and you cannot use adb unless in recovery
Did you OEM lock?
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
sorry to hijack but why is it so important to oem lock? it won't prevent you from flashing any of the files?
Sent from my HTC Sensation 4G using xda premium
In this case when attempting to flash the system zip pulled from the ruu.exe you need to relock or it won't flash. There is no longer a need to use HTC dev unlock anymore. Use globatrons s off hc upgrade in development and you do not need to lock before revert, but you then do have to push hboot
Sent from my HTC Flyer P510e using xda premium
keyid said:
Thank you mcord! flashed worked with the 2.27.1540.31 RUU and it was the due to not locking the bootloader. Thought locking the bootloader only applied to globaltron's method 1 as that says to do so and is absent in method 2 instructions.
will soon write what i learned so that it may help someone else.
Click to expand...
Click to collapse
I have sort of the same problem. I upgraded to HC via globaltron. I was having problems with HC and attempted to downgrade via globaltron's method 2. I am a noob and unfamiliar with adb.
How do you lock the bootloader.
When rebooting I am stuck on the white htc screen.
I am able to gain access to the bootloader (HBOOT 6.10.1002 Radio 3809.07.04.06_M) and Rev CWM recovery.
Thank you
BigE-evo said:
I have sort of the same problem. I upgraded to HC via globaltron. I was having problems with HC and attempted to downgrade via globaltron's method 2. I am a noob and unfamiliar with adb.
How do you lock the bootloader.
When rebooting I am stuck on the white htc screen.
I am able to gain access to the bootloader (HBOOT 6.10.1002 Radio 3809.07.04.06_M) and Rev CWM recovery.
Thank you
Click to expand...
Click to collapse
Would need more info on what you did to get to where you are and what is your end goal
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Would need more info on what you did to get to where you are and what is your end goal
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
I figured it out. Thanks for the response.
Sent from my HTC Flyer P512 using Tapatalk
Guys, I can really use some help here.
I upgraded my Flyer to the first Honeycomb leak (I don't remember the exact upgrade procedure I used) and now I want to update to the latest official release.
Tried the simple downgrade guide with no luck, running RUU's give me image errors or even a crashed flyer (distorted screen). Putting the ROM as a zip on the SD card gives me the "Main version is older" error. Tried flashing HBOOTS, ROMs and Recoveries through fastboot, all fail with error "signature verification fail".
I currently have a flyer that only boots to the bootloader and I only have access to it using fastboot. Booting recovery brings me back to the bootloader.
The bootloader shows:
Code:
*** RELOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
Fastboot getvar all:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0006
INFOversion-baseband: 3821.08.00.26_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.10.405.1
INFOserialno: HT159T401521
INFOimei: 354672040168047
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__E11
INFObattery-status: good
INFObattery-voltage: 3972mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 60a0efb2
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I'm out of idea's on what to do, all suggestion are appreciated!
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Search for globatrons thread for reverting to gb. He has a fix for misc older version
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Search for globatrons thread for reverting to gb. He has a fix for misc older version
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
I can't boot to recovery or Android, so I don't have access to ADB to push the misc_version file.
Bluediss said:
I can't boot to recovery or Android, so I don't have access to ADB to push the misc_version file.
Click to expand...
Click to collapse
See my first post
mcord11758 said:
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
I do feel stupid now... I already tried the HTCDEV unlock a few times, but that gave me errors... Doing it again now I discovered I was doing it wrong... I included the "INFO" string that every line starts with... Argh.
I'll flash the unlock.bin later this evening.
mcord11758 said:
To get up and running unlock boot loader again using htcdev unlock, then flash recovery in fastboot and then you can load a rom like lee droid
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
And I was indeed going for LeeDroid!
The unlock was succesfull, but it took me some time to get a working recovery. I finally got recovery working with the recovery image from Globatron's "HC-3G-light.zip".
I'm flashing the GB RUU now, let's wait and see.
Everything working now. All came down to me xopy/pasting a bit to much "INFO" for the HTC Unlock.
Thanks for the help!
Sent from my Galaxy Nexus using xda premium
I'm stuck too, but running into the htcdev s-off bug
I pushed my unlock bin to my flyer, but I can't "continue" past selecting "Yes" in the official bootloader unlock step. I've searched the web, but no answers as to why.
I can't boot into android to run adb, and have no recovery. only fastboot. any ideas?
malaise76 said:
I pushed my unlock bin to my flyer, but I can't "continue" past selecting "Yes" in the official bootloader unlock step. I've searched the web, but no answers as to why.
I can't boot into android to run adb, and have no recovery. only fastboot. any ideas?
Click to expand...
Click to collapse
Are you using the H/W buttons (volume up/down and power button for "Continue")
Explanations:
Have a Best Buy HTC Flyer with OTA stock HC 3.2 and wanted to downgrade to GB and used this method http://forum.xda-developers.com/showthread.php?t=1307759
Followed all directions from Post #1 to #11 using RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20 .3501.30.089BU_3809.05.04.10_M_release_191425_sign ed.exe as my RUU.
Ran RUU and HTC flyer pops up with bootloader screen on computer RUU says sending. Let it run max for 2-3hrs. Still saying the same thing. Unplugged it and now getting
FLYER PVT SHIP S-ON RL
HBOOT-1.10.0000
MICROP-0950
RADIO-3809.05.04.10_M
eMMC-boot
May 4 2011,11:04:45
When I select reboot it restarts and boots up the a white screen with HTC in green and stays this way.
When I try running the RUU again it does the same thing, just sits on sending.......
I am able to get to fastboot and hboot screen.
I am able to use flashboot
I am not able to to use adb
When I click recovery it just blinks and boots back up to Hboot so I'm thinking I don't have a recovery.
I tried running HTC unlock website again but I recieve an error when running the flashbook unlock command.
I'm thinking the since I'm S-ON I can't run recovery from flashboot
Please help......
As I understand from your post, you were S-ON on GB, ran OTA, and were on S-ON HC, right ?
HAVE YOU TRIED THIS THREAD FIRST ?
http://forum.xda-developers.com/showthread.php?t=1428104
Ok, what was your INITAL hBoot version ?
Good explanation. I've seen threads where people go:
i flashed ledroid hc on me gb flyer. it bricked it plz halp!
jaguaralani said:
As I understand from your post, you were S-ON on GB, ran OTA, and were on S-ON HC, right ?
HAVE YOU TRIED THIS THREAD FIRST ?
http://forum.xda-developers.com/showthread.php?t=1428104
Ok, what was your INITAL hBoot version ?
Click to expand...
Click to collapse
I was on stock OTA HC with S-ON. And wanted to go to back to GB.
rkum19 said:
Explanations:
Have a Best Buy HTC Flyer with OTA stock HC 3.2 and wanted to downgrade to GB and used this method http://forum.xda-developers.com/showthread.php?t=1307759
Followed all directions from Post #1 to #11 using RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20 .3501.30.089BU_3809.05.04.10_M_release_191425_sign ed.exe as my RUU.
Ran RUU and HTC flyer pops up with bootloader screen on computer RUU says sending. Let it run max for 2-3hrs. Still saying the same thing. Unplugged it and now getting
FLYER PVT SHIP S-ON RL
HBOOT-1.10.0000
MICROP-0950
RADIO-3809.05.04.10_M
eMMC-boot
May 4 2011,11:04:45
When I select reboot it restarts and boots up the a white screen with HTC in green and stays this way.
When I try running the RUU again it does the same thing, just sits on sending.......
I am able to get to fastboot and hboot screen.
I am able to use flashboot
I am not able to to use adb
When I click recovery it just blinks and boots back up to Hboot so I'm thinking I don't have a recovery.
I tried running HTC unlock website again but I recieve an error when running the flashbook unlock command.
I'm thinking the since I'm S-ON I can't run recovery from flashboot
Please help......
Click to expand...
Click to collapse
put it in fastboot mode and run the RUU again.
from fastboot
fastboot oem rebootRUU
Run stock ruu (only if you have the exe)
do you have the ruu.exe or just the zip?
if its just the zip make sure you run cmd with administrator rights and make sure the ruu zip is in the directory where your fastboot resides. on a windows 7 box (Program Files (x84)/Android/android-sdk/platform-tools)
then:
fastboot flash zip ruu_zip_name.zip
Good luck
wranglerray said:
from fastboot
fastboot oem rebootRUU
Run stock ruu (only if you have the exe)
do you have the ruu.exe or just the zip?
if its just the zip make sure you run cmd with administrator rights and make sure the ruu zip is in the directory where your fastboot resides. on a windows 7 box (Program Files (x84)/Android/android-sdk/platform-tools)
then:
fastboot flash zip ruu_zip_name.zip
Good luck
Click to expand...
Click to collapse
This should work for you, I had similar issues, and had to run fastboot commands to get it loaded right. This is the best explanation I've seen, should be added somewhere in the pinned docs.
Also you may have another option.
hboot 1.10.0000 is a stock hboot for the BB wifi flyer.
From fastboot you should be able to run revolutionary to gain s-off irregardless of your rom state. after you have s-off its just a matter of do you want HC or GB.
You can always relock the bootloader once you have a working rom again.
I have the HC s-off ruu. its buried in a thread somewhere but i'd be happy to host it somewhere so you could download it.
wranglerray said:
Also you may have another option.
hboot 1.10.0000 is a stock hboot for the BB wifi flyer.
From fastboot you should be able to run revolutionary to gain s-off irregardless of your rom state. after you have s-off its just a matter of do you want HC or GB.
You can always relock the bootloader once you have a working rom again.
I have the HC s-off ruu. its buried in a thread somewhere but i'd be happy to host it somewhere so you could download it.
Click to expand...
Click to collapse
None of that is correct.
Is it just me or is the last post from the person with the issue from March 6th?
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Is it just me or is the last post from the person with the issue from March 6th?
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Yes, you're correct. I only replied to the thread to make sure the incorrect infomation didn't waste anyones time.
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i haved done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago..
THIS WHAT HAPPEND:I
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound its been booting with the white "HTC" screen for fews seconds then LOOP again. no recovery boot and niether OS
THIS WHAT I DID:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i have done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago...
THIS WHAT HAPPEND:
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound it’s been booting with the white "HTC" screen for few seconds then LOOP again. No recovery boot and neither OS
THIS WHAT I DID:
I download ruu, rom, and all recovery versions lists above and installed them correctly according the ADB SCREEN, but when I try to enter to recovery it stock in white screen logo HCT
MY REZOUND INFO:
TAMPERED
UNLOCKED
VIGOR PUT SHIP S-OM RL
HBOOT.2.28
RADIO 2.23.10.123R/2.23.10.0124R
INFOversion: 0.5
INFOversion-bootloader: 2.
INFOversion-baseband: 2.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.05.605
INFOserialno: HT1BJS214553
INFOimei: 990000339159446
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 3651m
INFOpartition-layout: Gene
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
RECOVERY INSTALLED AND NOT WORKED:
CWM-6.0.4.4-recovery
openrecovery-twrp-2.8.0.1F-vigor
recovery-clockwork-touch-6.0.3.1-vigor
recovery-ra-vigor-3.15-gnm
twrp-2.4.3.0-vigor
twrp-2.4.4.0-vigor
twrp-2.5.0.0-vigor
twrp-2.6.0.0-vigor ECT...
recovery-ra-vigor-3.14-gnm
I been doing this several times and different method as: rename recovery to PH98IMG.zip and installed from SD CARD, I been used ADB command "fastboot fast recovery recovery.img ect... all succeed but when calling the recovery partition it stuck.
ANY HELP about these issues i will appreciate it.
Hi, I'have same issue with my Rezound. Have you found a working solution
mofazar said:
Hi, I'have same issue with my Rezound. Have you found a working solution
Click to expand...
Click to collapse
What do you mean "same issue"? You replaced the screen and can't do anything now? That is the jist of what the OP said...
Are you locked, unlocked? S-on or S-off? Proper drivers loaded? Hboot loading and can you get a Fastboot response?
A little more detail would help here...
Sent from my MotoG3 using Tapatalk
i'have fastoot acces, device is recognized by PC and detected by fastboot prompt command
it's actually unlocked bootloader and s-on
i'have try to downgrade with unlocked and relocked bootloader but it's failed.
in unlocked the error is in : recovery partition update fail
in relocked : try with true update version.:crying::crying:
---------- Post added at 02:37 PM ---------- Previous post was at 02:32 PM ----------
Device is not rooted. i've try reflash many recovery, operating succefull but it can't boot into any recovery.
Can you boot recovery? Try
fastboot boot twrp.img
But replace "twrp.img" with the name of your recovery image file.
Please attach a screenshot or copy and paste terminal interactions.
Sent from my MotoG3 using Tapatalk
have you found a solution for this problem yet? i might be able to help. i know the rezound inside and out. i have replace the screen both speakers rooted downgraded upgraded flashed multiple roms used fastboot and adb options for sideloading and flashing.my device is s-on bootloader unlocked tampered and security warning. i would in ur situation is rom a stock ruu. one that matches ur hboot and raido. u r suppose to start the ruu from ur home screen with adb debugging on but since ur phone is boot looping i would try it starting off in fastboot usb. i have success starting it straight from there. the ruu installer will say rebooting phone to bootloader but it will be there already. should switch screens to a black background and with white htc logo and progress bar. remember to oem relock ur bootloader b4 starting the ruu. also all fastboot and adb should be installed on ur computer, along with htc drivers. all can be searched for on the forum. i searched minimal adb and fastboot.zip and htc drivers part1 and part2.zip. then make sure ur computer is seeing ur phone. i will reply asap but i is kinda busy. hope this helps if not i can help more.
dirtysan said:
have you found a solution for this problem yet? i might be able to help. i know the rezound inside and out. i have replace the screen both speakers rooted downgraded upgraded flashed multiple roms used fastboot and adb options for sideloading and flashing.my device is s-on bootloader unlocked tampered and security warning. i would in ur situation is rom a stock ruu. one that matches ur hboot and raido. u r suppose to start the ruu from ur home screen with adb debugging on but since ur phone is boot looping i would try it starting off in fastboot usb. i have success starting it straight from there. the ruu installer will say rebooting phone to bootloader but it will be there already. should switch screens to a black background and with white htc logo and progress bar. remember to oem relock ur bootloader b4 starting the ruu. also all fastboot and adb should be installed on ur computer, along with htc drivers. all can be searched for on the forum. i searched minimal adb and fastboot.zip and htc drivers part1 and part2.zip. then make sure ur computer is seeing ur phone. i will reply asap but i is kinda busy. hope this helps if not i can help more.
Click to expand...
Click to collapse
OP is S-on and no RUU exists for this software release... And with S-on no downgrade is possible. Although your points are mostly valid, if you had read the thread you know this had been covered.
Sent from my MotoG3 using Tapatalk
acejavelin said:
OP is S-on and no RUU exists for this software release... And with S-on no downgrade is possible. Although your points are mostly valid, if you had read the thread you know this had been covered.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
i was basically stating that a fresh start is always better. when something goes wrong i always resort back to stock. unlock bootloader root then flash custom rom. but thanks for the condescending attitude brah
dirtysan said:
i was basically stating that a fresh start is always better. when something goes wrong i always resort back to stock. unlock bootloader root then flash custom rom. but thanks for the condescending attitude brah
Click to expand...
Click to collapse
My intent was not to be condescending, in fact out most of your points were completely valid. My point was at that software release there is no RUU, thus no way to go back to a "known good" configuration... Sorry if I offended you, that wasn't my intent.
Sent from my MotoG3 using Tapatalk
acejavelin said:
My intent was not to be condescending, in fact out most of your points were completely valid. My point was at that software release there is no RUU, thus no way to go back to a "known good" configuration... Sorry if I offended you, that wasn't my intent.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
have u tried installing recovery with an adb push. if u have not tried already use windroid universal toolkit.
akura3 said:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i haved done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago..
THIS WHAT HAPPEND:I
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound its been booting with the white "HTC" screen for fews seconds then LOOP again. no recovery boot and niether OS
THIS WHAT I DID:
Hi, i need your HELP with this problem, i have look around this forum looking for a solution about similar ISSUE and i have done STEP by STEP the procedure and when done my HTC wont load THE RECOVERY. I have been reading solutions about 4 days ago...
THIS WHAT HAPPEND:
I replaced the LCD Screen Display correctly and when i turn it on it went directly to the BOOTLODER, since then my Rezound it’s been booting with the white "HTC" screen for few seconds then LOOP again. No recovery boot and neither OS
THIS WHAT I DID:
I download ruu, rom, and all recovery versions lists above and installed them correctly according the ADB SCREEN, but when I try to enter to recovery it stock in white screen logo HCT
MY REZOUND INFO:
TAMPERED
UNLOCKED
VIGOR PUT SHIP S-OM RL
HBOOT.2.28
RADIO 2.23.10.123R/2.23.10.0124R
INFOversion: 0.5
INFOversion-bootloader: 2.
INFOversion-baseband: 2.23
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.05.605
INFOserialno: HT1BJS214553
INFOimei: 990000339159446
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 3651m
INFOpartition-layout: Gene
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
RECOVERY INSTALLED AND NOT WORKED:
CWM-6.0.4.4-recovery
openrecovery-twrp-2.8.0.1F-vigor
recovery-clockwork-touch-6.0.3.1-vigor
recovery-ra-vigor-3.15-gnm
twrp-2.4.3.0-vigor
twrp-2.4.4.0-vigor
twrp-2.5.0.0-vigor
twrp-2.6.0.0-vigor ECT...
recovery-ra-vigor-3.14-gnm
I been doing this several times and different method as: rename recovery to PH98IMG.zip and installed from SD CARD, I been used ADB command "fastboot fast recovery recovery.img ect... all succeed but when calling the recovery partition it stuck.
ANY HELP about these issues i will appreciate it.
Click to expand...
Click to collapse
i have same specs on my phone s-on hboot ect... try this ruu
http://forum.xda-developers.com/showthread.php?t=2094412
after that use windroid universal toolkit for rooting and recovery flash. if u saved ur token u can just skip using windroid for root and just use it for twrp recovery. just flash ur token from fastboot.
Hello!
So I recently replaced my stolen AT&T HTC M8 with an a refurbished one and decided to root it for my first time. Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now. I've spent a few hours researching and trying to understand the process, but there is a lot of technical aspects that I haven't grasped yet. Well, here is my situation:
My phone is currently soft bricked and I am unable to access my phone's UI when I boot it. After the HTC One logo, the phone will be black and consistently bring up, "unfortunately AT&T ready2go has stopped". It will also say that the UI has stopped and I have no choice but to turn off my phone. Prior to this, I had an issue with Superuser where there was no binary so I tried to re-install it thinking that would do something; I then performed a factory reset (thinking it would somehow fix it). I realized after this that TWRP and SU were both out of date and now I'm here not sure what to do. I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that? I'm still learning, and it's a lot to pick up, so bear with me please as I try to piece together everything. I've been searching through the forums, but it hasn't really helped me too much.
Here is what my Hboot says:
*** Software Status: Modified ***
M8_UL_CA PVT SSHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-
eMMC-boot 2048MB
AUG 4 2015, 23:21:05.0
Getvar All (not exactly sure what this is, but I saw other help posts listing it and figured it's useful)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If anyone could give me some guidance/clarity then I would truly appreciate it! Thank you!
mtruong15 said:
Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now.
Click to expand...
Click to collapse
Were you on stock Lollipop or Marshmallow before you started modding the phone? From the radio number, I think its LP, but I'm not that familiar with the weird AT&T radio numbers (and how they correspond to LP, MM, etc.). It would be easy to see your main version, if you had not used an obsolete TWRP (from the toolkit) that deletes that info.
One piece of advice moving forward, and this goes for modding any Android device, is to always research the current methods based on your current Android version, firmware, etc.; and confirm the methods work for your setup, before you begin.
At least you've realized your mistake (outdated toolkit, outdated TWRP, outdated SuperSU), and also properly posted your getvar data. So you're not doing a bad job in that respect.
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
mtruong15 said:
I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that?
Click to expand...
Click to collapse
Do not need to s-off to run RUU.
But you do need to relock the bootloader, with fastboot command: fastboot oem lock
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
After RUU back to stock, you'll need to unlock the bootloader again (try the same unlock bin code, or get another from HTCDev.com) in order to install TWRP, root, etc.
redpoint73 said:
Were you on stock Lollipop or Marshmallow before you started modding the phone?
Click to expand...
Click to collapse
I was on stock Lollipop when I received my phone.
redpoint73 said:
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
Click to expand...
Click to collapse
I unfortunately did not, but will do this from now on. I've definitely learned a lot about the process, after the fact, and feel much more prepared to work on this phone. In the case that I need to do this on another phone I will do my research and take the appropriate steps as well.
redpoint said:
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
Click to expand...
Click to collapse
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU. What do you think is a potential reason for this specific case?
Update: I have already relocked bootloader
mtruong15 said:
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU.
Click to expand...
Click to collapse
Its correct, with s-on, you need to run RUU that is equal or greater version number than the firmware on the phone (in addition to the RUU for your CID,MID so the RUU meant for AT&T M8). Meaning you can't "downgrade" or run the KitKat RUUs (only way to bypass with is with s-off, which is $25 by sunshine). Since you are on LP firmware, you can run the LP RUU.
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Link to details on how to flash the firmware.zip (if you want to RUU to MM) is in my Index thread, as well as all the AT&T RUUs (in the RUUs section): http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Click to expand...
Click to collapse
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
mtruong15 said:
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
Click to expand...
Click to collapse
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Sent from my HTC One_M8 using Tapatalk
grigoriisi said:
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Click to expand...
Click to collapse
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
mtruong15 said:
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
Click to expand...
Click to collapse
Right click on the ruu exe and choose compatibility mode windows 7. It works like that for me on Windows 10.
Sent from my HTC One_M8 using Tapatalk
mtruong15 said:
However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page.
Click to expand...
Click to collapse
You didn't properly describe that issue before (all you said was "haven't had much luck" with the RUU, which didn't really tell us anything), otherwise I could have given some insight earlier. Always be specific as possible when describing errors, failures, issues.
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
redpoint73 said:
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
Click to expand...
Click to collapse
I tried compatibility mode for Win7 and Win8, and attempted through various USB ports, but still couldn't get it to budge. I double checked the C++ Packages and already had the 2008 package and the others listed in another XDA post I found. I ended up trying on a friend's computer who was running Win8.1 and surprisingly got it to work in one go without any errors at all. Figures the problem was my computer that didn't allow me to run the .exe.
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
mtruong15 said:
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
Click to expand...
Click to collapse
You are very welcome, and glad to see you go the RUU to work.
If you still want to root, it looks like you've learned from your mistakes; but to summarize the proper root method:
1) Unlock bootloader again via HTCDev.com. If you still have the bin code from last time, you might be able to reuse it, with the proper fastboot command, to unlock the bootloader. Otherwise, just go through the HTCDev.com process again, and get a new code.
2) Install current TWRP 3.0. TWRP files, and instructions to install by fastboot method are here: https://twrp.me/devices/htconem8gsm.html
3) Download and flash SuperSU in TWRP. Recommend latest stable version SupersSU 2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip