Database Users

[GUIDE] Return your European M8 to 100% Stock - S-OFF REQUIRED

*** I HAVE SOLD MY M8 BUT I WILL TRY AND KEEP THIS UP-TO-DATE WHEN NEW RUUs COME OUT ***
*** NEW GUIDE AS WE NOW HAVE AN RUU!!! ***
This guide is for Windows-only. The reason for this is because the htc_fastboot file used is a Windows binary and there doesn't appear to be a version for Mac/Linux
This guide will allow you to return your EU, unbranded M8_UL device to 100% stock (inc. locking the bootloader and removing the tampered flag) for resale purposes or to return to HTC. It does not cover carrier-branded handsets and does require you to be S-OFF but Step 3 can be done on an S-ON EU M8 so long as your bootloader is relocked and you match one of the CIDs listed below. A lot of this can be used to restore a US carrier M8 as the RUUs are available, though, but you'd have to get the relevant RUU.zip from the EXE (which is very easy)
This process applies to the following CIDs:
HTC__001
HTC__102
HTC__203
HTC__E11
HTC__405
HTC__Y13
HTC__304
HTC__A07
HTC__032
HTC__J15
HTC__016
HTC__M27
HTC__K18
HTC__A48
HTC__002
You need the following files stored in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (renamed to ruu.zip - not ruu.zip.zip!)
md5:4e03845aeab375746b4553e610047680
htc_fastboot.exe - *** REMOVED DUE TO HUGE AMMOUNTS OF SPAM REQUESTS ***
md5: 7343C5BCEC64373F83D69BD074954759
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (renamed to recovery.img) md5:
e51c6ce8db0b7318ef31e1e7bd03c96e
And you'll also need HTC Sync Manager - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it for the drivers and then uninstall it but leave the drivers on your PC)
All commands in bold are to be done in a command prompt window in your fastboot folder
1. 'Lock' the bootloader and reset the tamper flag
We know we can relock the bootloader by using the command 'fastboot oem lock', but it will show 'RELOCKED' on the bootloader and still show the phone has been unlocked in the past. With S-OFF we can set it back to 'LOCKED' . To do this, we need to use TWRP and adb shell
Flash TWRP in the usual manner by connecting the phone to the PC whilst in the bootloader and flash by using the command fastboot flash recovery recovery.img. Once flashed, boot the phone into TWRP and connect to your PC and make sure the drivers are successfully installed. To confirm it's working type adb devices and it should be listed with your devices serial number. Assuming you can see the device, we can now use adb shell to change the flag from 'UNLOCKED' to 'LOCKED' by using the following commands:
adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Once the command has finished, we can continue using adb shell to reset the tamper flag by using the following command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
Once this has finished, we can exit out of adb shell by simply typing exit. Then reboot the phone into the bootloader through the menu in TWRP so we can confirm the flags are set back to stock.
2. Change the CID (if required)
Now we're in the bootloader and are 'LOCKED' and not listed as modified (but still S-OFF) it's best we reset the CID so moving forward things are easy. To do this, you just need to use fastboot oem writecid HTC__001, or whichever CID your device originally came with from the list at the beginning of this guide. Once you've reset the CID, reboot the bootloader to confirm the changes using fastboot reboot-bootloader
3. Flash the RUU
We are now at the point where we can flash the RUU and restore the phone to 100% stock. To do this, we first need to boot the phone into RUU mode using the command fastboot oem rebootRUU. Once in RUU mode, you'll see a silver HTC logo on the phone and that's it. At this point, we now use the HTC fastboot package to flash their RUU.zip file using the command htc_fastboot flash zip ruu.zip. This process will take a few minutes, and the phone will reboot a few times but once done it'll say complete. At this point, reboot the phone back to the bootloader using fastboot reboot-bootloader
4. Factory reset the device *** OPTIONAL ***
Having flashed the RUU, I always prefer to do a factory reset to make sure everything is in order. To do this, boot into the stock recovery and once at the black screen hold volume up and press power to get into the menu and then select 'wipe data/factory reset' using the volume buttons and use power to select the option.
5. Reboot the phone
Pretty obvious this - just select 'reboot system now' and you should be good to go!

Reserved in case I need it

To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app

exad said:
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Because there aren't any pre-packaged ZIPs for any other build - only Nandroids. Now, I'm sure someone could make a flashable ZIP out of a Nandroid but I don't have the time for that! Plus, you've then got to make sure the right FW package is available as well as the stock recovery. I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
As I have an unbranded EU handset I did this guide - if anyone wants to use it as a template then please feel free to do so!

EddyOS said:
I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
Click to expand...
Click to collapse
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.

EtherealRemnant said:
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
Click to expand...
Click to collapse
It says it already!! I didn't flash it twice as I was already on the correct FW. I've made it bold so people will notice it
EddyOS said:
e. Type: fastboot flash zip firmware.zip and wait for process to complete. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Click to expand...
Click to collapse

EddyOS said:
It says it already!! I didn't flash it twice as I was already on the correct FW
Click to expand...
Click to collapse
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.

EtherealRemnant said:
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
Click to expand...
Click to collapse
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock

Text changed to make it a bit more obvious to do it twice, although this is different to flashing an RUU ZIP (where you HAVE to flash it twice as that's how the RUU ZIP works). Surely if it needed flashing twice it'd tell you to do it (as an RUU ZIP does)?

EddyOS said:
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Click to expand...
Click to collapse
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
EddyOS said:
Text changed to make it a bit more obvious to do it twice
Click to expand...
Click to collapse
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.

EtherealRemnant said:
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
Click to expand...
Click to collapse
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up

EddyOS said:
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
Click to expand...
Click to collapse
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works. I don't have the time to mess with it right now so I'd still suggest the old way. You know what they say about things that aren't broke...

EtherealRemnant said:
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works.
Click to expand...
Click to collapse
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)

EddyOS said:
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
Click to expand...
Click to collapse
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:

EtherealRemnant said:
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
Click to expand...
Click to collapse
It's all good! I've made one last change to that point to highlight that although it's not strictly required it's strongly recommended to do it twice as a precaution
Not sure what else you can out as no doubt someone will get it wrong at some point...

EddyOS said:
Not sure what else you can out as no doubt someone will get it wrong at some point...
Click to expand...
Click to collapse
It wouldn't be XDA if they didn't! :highfive:

Is it possible on my phone with CID HTC__J15 and S-on??

sari94 said:
Is it possible on my phone with CID HTC__J15 and S-on??
Click to expand...
Click to collapse
You can use parts of the guide but not the parts with (REQUIRES S-OFF) next to it (basically 1 and 5 are what you need, so long as you have an unbranded handset)

Added CIDs that will work with this guide to help users - if it's not listed then it won't work

Im guessing that once your back at stock you'll get OTA updates?

Gpe back to sense m8

i bought a google edition htc m8, so i wanted to get it back to sense aswell as i prefer the usability of it + the phone was made to run on that software
this took me hour to work out and hours of research on xda and other websites, so here im trying to simplify everything into one post, so people can get back to sense
so first of course root your phone if u have a google edition, if you converted to GPE from sense you will already be rooted and you can start the process (with TWRP installed)
i did it successfully but it was a huge process as there are limited resources atm to help me do it, as to why i am posting this
1. first i downloaded HTC one m8 all in one toollink)
http://forum.xda-developers.com/showthread.php?t=2699065
once you download this program you will be able to put the phone into bootloader, with this program you wont have to use comand prompt on windows to change the cid in bootloader.
2. you need to change the phones cid from goog to CID-11111111, of the m8 all in one toolkit it enters it in for you and writes it straight to your phone.
3. once you do this you need to download -
Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
NOW YOU NEED TO USE COMAND PROMPT- TEST PHONE WITH - FASTBOOT DEVICES- SHOULD GET A NUMBER CODE IF YOUR PHONE IS CONNECTED PROPERLY
1.FIRST ENTER fastboot oem rebootRUU
THEN- fastboot flash zip (whatever you name it).zip REDO IT TWICE 1ST WILL FAIL )- THEN SUCCESSFUL
-Boot back into Bootloader
-Boot into Recovery
-then in twrp (MUST)
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
IF I HELPED PLEASE LEAVE A THANKS
(i have been pretty brief in my explanation, everything you need is there for the tricky parts, but if you have problems with toolkit or anything else look it up on xda) but this post will cut down the process time!
thanks. i am not resposible for any faults or problems with your phone but if you do it correctly all should be good :good:

KKRES said:
i bought a google edition htc m8, so i wanted to get it back to sense aswell as i prefer the usability of it + the phone was made to run on that software
this took me hour to work out and hours of research on xda and other websites, so here im trying to simplify everything into one post, so people can get back to sense
so first of course root your phone if u have a google edition, if you converted to GPE from sense you will already be rooted and you can start the process (with TWRP installed)
i did it successfully but it was a huge process as there are limited resources atm to help me do it, as to why i am posting this
1. first i downloaded HTC one m8 all in one toollink)
http://forum.xda-developers.com/showthread.php?t=2699065
once you download this program you will be able to put the phone into bootloader, with this program you wont have to use comand prompt on windows to change the cid in bootloader.
2. you need to change the phones cid from goog to CID-11111111, of the m8 all in one toolkit it enters it in for you and writes it straight to your phone.
3. once you do this you need to download -
Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
NOW YOU NEED TO USE COMAND PROMPT- TEST PHONE WITH - FASTBOOT DEVICES- SHOULD GET A NUMBER CODE IF YOUR PHONE IS CONNECTED PROPERLY
1.FIRST ENTER fastboot oem rebootRUU
THEN- fastboot flash zip (whatever you name it).zip REDO IT TWICE 1ST WILL FAIL )- THEN SUCCESSFUL
-Boot back into Bootloader
-Boot into Recovery
-then in twrp (MUST)
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
IF I HELPED PLEASE LEAVE A THANKS
(i have been pretty brief in my explanation, everything you need is there for the tricky parts, but if you have problems with toolkit or anything else look it up on xda) but this post will cut down the process time!
thanks. i am not resposible for any faults or problems with your phone but if you do it correctly all should be good :good:
Click to expand...
Click to collapse
As I read this, immediately under your thread in the index is this thread....
http://forum.xda-developers.com/showthread.php?t=2733523
^^^^^ The thread is for those who have flashed @graffixnyc Google Edition RUU conversion and want to get back to sense. (In effect what you written about)
Plus, and this is just a personal thing, I would stay away from tool kits until you know what to do should the whole thing mess up. Toolkits are good but if the process screws up and your knowledge of adb etc is limited to the toolkit you could be in trouble (This is a general reference to ANYONE using a toolkit - not you specifically!)
EDIT - Having said all of that I have just noticed that you posted this in the RUU thread 5 minutes before STARTING this thread. Why did you start a new topic?

grentuu said:
As I read this, immediately under your thread in the index is this thread....
http://forum.xda-developers.com/showthread.php?t=2733523
^^^^^ The thread is for those who have flashed @graffixnyc Google Edition RUU conversion and want to get back to sense. (In effect what you written about)
Plus, and this is just a personal thing, I would stay away from tool kits until you know what to do should the whole thing mess up. Toolkits are good but if the process screws up and your knowledge of adb etc is limited to the toolkit you could be in trouble (This is a general reference to ANYONE using a toolkit - not you specifically!)
EDIT - Having said all of that I have just noticed that you posted this in the RUU thread 5 minutes before STARTING this thread. Why did you start a new topic?
Click to expand...
Click to collapse
sorry accident with posting a new thread, how can i delete it
thats fair enough, i understand i guess i was just sharing how i did it, and possibly the easiest was to return to sense

KKRES said:
sorry accident with posting a new thread, how can i delete it
thats fair enough, i understand i guess i was just sharing how i did it, and possibly the easiest was to return to sense
Click to expand...
Click to collapse
You can request for a moderator to close it, then join in with the other thread

[GUIDE] Convert your HTC One into a dev edition - Get Sense updates faster!

Looking to get the latest updates from HTC faster than the International LTE, GSM and American Carriers AT&T and T-Mobile variants, well here is a guide to help you convert your HTC One into a developer edition. I can confirm that it works with the European HSPA and LTE bands. Doing this will also update you directly to 5.0.2 Lollipop
Read This First:
You must be S-OFF
You must be HTCDev Unlocked
You must have CWM or TWRP recovery installed
You must charge your phone to AT LEAST 50%
You must know how to use ADB and Fastboot
You must have any KitKat or Lollipop firmware installed
Your SD Card will be WIPED, so make a backup of your files
This WILL NOT work on the CDMA HTC One
Even though this is 100% safe, I am not responsible if you break your phone
Part 1: Changing your CID and MID (Model ID)
Reboot into bootloader
Enter fastboot mode
Open a CMD window and type (without quotes) "fastboot oem writecid BS_US001
Then type (without quotes) "fastboot reboot-bootloader"
To confirm you have the above CID type in (without quotes) "fastboot getvar cid" or "fastboot oem readcid"
If it shows "cid: BS_US001" then you are ready to continue to the next step
Now you have to change your Model ID (MID) (Skip this if you have the AT&T or GPE variant), you now have to download this: MID Change tool
Now boot into Android and place the MID Change tool on your SD Card
Now reboot into recovery
Then find and flash the MID Change Tool
Once inside Aroma Installer you have to select the MID PN0712000
Then tap next and your MID will be changed
Part 2: Downloading and running the RUU
Firstly, download the RUU from here: RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
Now open the RUU file
Follow the steps in the RUU, accepting any agreements. Meanwhile make sure your phone is in Fastboot mode
Now let the RUU do its work and about 4-10 minuites later you will have a full Developer Edition HTC One (M7)
Please press the thanks button if this helped you

Thanks! But what's the difference? I mean the normal edition and this?

alomex21 said:
Thanks! But what's the difference? I mean the normal edition and this?
Click to expand...
Click to collapse
Well by normal, you mean the International version and the developer edition gets updates before anyone else
Heres how the updates go to variants from first to last
1. HTC One GPE > 2. HTC One Developer Edition/Unlocked Edition > 3. International HTC One > 4. Carrier Variants (Like EE in UK and Verizon in US)

Since the Lollipop Sense update is imminent, I have updated the thread with the latest RUU, the 4.4.3 Sense 6 RUU.

dd98 said:
Since the Lollipop Sense update is imminent, I have updated the thread with the latest RUU, the 4.4.3 Sense 6 RUU.
Click to expand...
Click to collapse
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...

alray said:
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...
Click to expand...
Click to collapse
its on their actual website but i only found it yesterday

alray said:
:good:
I wasn't aware they had released a signed RUU for 6.07.1540.2. Not even able to find it on HTCDev.com...
Click to expand...
Click to collapse
dd98 said:
its on their actual website but i only found it yesterday
Click to expand...
Click to collapse
Yeah it's crazy the M8 DE Lollipop RUU is already out also
it's here in case you need the link
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe

clsA said:
Yeah it's crazy the M8 DE Lollipop RUU is already out also
it's here in case you need the link
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Thanks, but I WANT LOLLIPOP SOON!!!

dd98 said:
Thanks, but I WANT LOLLIPOP SOON!!!
Click to expand...
Click to collapse
lol, well I bet theirs an M8 right down the street with your name on it

clsA said:
lol, well I bet theirs an M8 right down the street with your name on it
Click to expand...
Click to collapse
I cant, I love beats too much

dd98 said:
I cant, I love beats too much
Click to expand...
Click to collapse
The M8 has BOOMsound, I never noticed a difference between it and my m7

Hi there & thanks for the write-up! Thought I´d share my experience from following your guide.
At first try I thought I had bricked my device. It all started off good, but when I ran "fastboot reboot-bootloader" prior to executing the RUU, my device didn´t boot. No LED, no display, nothing. It was dead!
During the last year I´ve been going back & forth between different firmwares (GPE, Sense etc) and today I had apparently hit a dead end. The device showed typical symptoms of being hard bricked. After trying all kind of imagenable key combinations & gooling, I found dexter93´s [UNBRICK][BETA] HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=2770684
Ran the unbricking tool which recorgnized my device and started processing. When done I tried to power on the device without success. At this time I had givven up. But for some unknown reason I tried to get into fastboot mode once again. And to my surpise it worked!
Now I knew that it was possible to restore the device to some operation state. With that in mind, I went for a second try of converting it to dev edition. The procedure went fine until I started the RUU which abruptly crashed. I´m running Windows 8.1 x64. Turned out I needed to install Microsoft Visual C++ 2008 Redistributable Package (x86) http://www.microsoft.com/en-us/download/details.aspx?id=29 to be able to successfully run the RUU.
After the RUU I rebooted into the new installation only to find out that my mobile network didn´t work! It suprised me since OP wrote that the release was supposed to work in Europe. After some more depressing thoughts of failure I realized the I had removed (as instructed) the SIM when running the HTC Unbrick Project tool. Reinserted the SIM and I was able to connect to my cellular network provider.
The guide well structured and easy to follow. One minor suggestion for improvement could be to alter step #5 in the second part from:
5. Then type (without quotes) "fastboot flash zip firmware.zip"
to:
5. Then type (without quotes) "fastboot flash zip 5.11.1540.9.zip"
Just a minor note. Thanks for the guide & keep up the good work!

gechu said:
Hi there & thanks for the write-up! Thought I´d share my experience from following your guide.
At first try I thought I had bricked my device. It all started off good, but when I ran "fastboot reboot-bootloader" prior to executing the RUU, my device didn´t boot. No LED, no display, nothing. It was dead!
During the last year I´ve been going back & forth between different firmwares (GPE, Sense etc) and today I had apparently hit a dead end. The device showed typical symptoms of being hard bricked. After trying all kind of imagenable key combinations & gooling, I found dexter93´s [UNBRICK][BETA] HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=2770684
Ran the unbricking tool which recorgnized my device and started processing. When done I tried to power on the device without success. At this time I had givven up. But for some unknown reason I tried to get into fastboot mode once again. And to my surpise it worked!
Now I knew that it was possible to restore the device to some operation state. With that in mind, I went for a second try of converting it to dev edition. The procedure went fine until I started the RUU which abruptly crashed. I´m running Windows 8.1 x64. Turned out I needed to install Microsoft Visual C++ 2008 Redistributable Package (x86) http://www.microsoft.com/en-us/download/details.aspx?id=29 to be able to successfully run the RUU.
After the RUU I rebooted into the new installation only to find out that my mobile network didn´t work! It suprised me since OP wrote that the release was supposed to work in Europe. After some more depressing thoughts of failure I realized the I had removed (as instructed) the SIM when running the HTC Unbrick Project tool. Reinserted the SIM and I was able to connect to my cellular network provider.
The guide well structured and easy to follow. One minor suggestion for improvement could be to alter step #5 in the second part from:
5. Then type (without quotes) "fastboot flash zip firmware.zip"
to:
5. Then type (without quotes) "fastboot flash zip 5.11.1540.9.zip"
Just a minor note. Thanks for the guide & keep up the good work!
Click to expand...
Click to collapse
Thanks, i forgot to change it after updating the RUU and firmware, but I just realized that flashing the 5.11.1540.9 firmware causes problems for users on lollipop firmware, Im going to re-write the guide soon!

Instructions re-written to ensure people on Lollipop firmwares don't get bricked in QHSUSB_DLOAD mode

dd98 said:
Instructions re-written to ensure people on Lollipop firmwares don't get bricked in QHSUSB_DLOAD mode
Click to expand...
Click to collapse
Thanks for your Work
Did you see these >> http://forum.xda-developers.com/showpost.php?p=58224092&postcount=6780
http://forum.xda-developers.com/showpost.php?p=58224358&postcount=6782
It's almost here !!

I'm guessing ii don't need to run the change MID if my MID is already PN0712000? Or should I run it anyway?
Working for me. Thanks!

I can confirm that I came from GPE Lollipop and got the device recognized as QHSUSB_DLOAD.

gechu said:
I can confirm that I came from GPE Lollipop and got the device recognized as QHSUSB_DLOAD.
Click to expand...
Click to collapse
Was this before or after I posted the new guide, because with the new guide I came from GPE 5.11.1700.3 down to the developer edition 6.07.1540.2 without any problem, twice. Try this to unbrick your phone, use Ubuntu 14.04 and it should work without problems

I used the initial guide, and brought the device back to life using the tool you referenced.

gechu said:
I used the initial guide, and brought the device back to life using the tool you referenced.
Click to expand...
Click to collapse
Ok well now in future, you should not get bricked using this guide

Unbranded Stock Firmware - Available now - Desire 626s only

Not sure if anyone encountered this issue, but a few years ago, I bought the developer version of the Desire 626s directly from HTC (aka with a CID: BS_US001).
Something happened to the phone recently when I let my friend borrow it for development purposes, and he flashed the "Sprint debloated Marshmallow" rom that seems to be floating around. It turns out there wasn't a way to return it to the stock unbranded because all RUUs that are publicly available from HTC are for the branded version. (e.g., T-Mobile, MetroPCS, Sprint/Boost, etc.)
Just wanted to let the community know that if you do want the stock HTC firmware that is factory unbranded, or to use as a base for development, go ahead and google:
0PM9IMG_A32E_UL_L51_DESIRE_SENSE70_NA_Gen_Unlock_1.11.617.1_Radio_01.01_U113251011_32.04.50622G_2_release_446244_signed
It's a zip file (1,283,787 KB / 1.22GB) you can download. You can then rename it to 0PM9IMG.zip, place onto the root of your SD card, boot the Desire 626s into download mode (press and hold volume down when powering up), and flash directly within download mode (Vol up to initiate flash when in download mode)
I should note, this stock firmware is only available if you have CID: BS_US001, or if you have S-Off/SuperCID: 11111111 already. If there is any interest, I may consider just performing a TWRP backup of this image on my phone, and releasing it as a flash-able zip through TWRP Recovery. However, I'm pretty sure since this is such an old phone, there's really no need. Anyone that really wanted to do this probably is more technical and would have already just followed directions I noted above.

i would be greatly interested and apreciative if you could.I have four 626. one for each teenager.

Unable to flash
12 RU ZIP ERROR.
HTC_a32eul pvt s-off
Cid-111111111
mid-0PM912000

Primalmudcat said:
i would be greatly interested and apreciative if you could.I have four 626. one for each teenager.
Click to expand...
Click to collapse
https://super-firmware.com/index.php?a=browse&b=file&id=12649
See if that works for you.

Seeking advice on rooting Smart Tab M10 FHD Plus 2nd Gen

Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.

Brotinger said:
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Click to expand...
Click to collapse
If you download the lmsa tool, plug in the tablet and go to recovery it will download the full stock firmware. Then you can find it c/program data/LMSA/downloads.
I did that then downloads magisk manager. Extract the boot.img from firmware and put in storage of tablet. Then used magisk manager and patch the boot.img it will tell where it is stored. Extract from tablet and put it in same folder as adb/fast boot. Then put tablet in fastboot and fastboot flash boot magisk-patched.img. then fastboot reboot. The will be rooted with magisk
I forgot. You must unlock bootloader to do this.

Dear 11mackey11,
thank you so very much for caring enough to share your knowledge with me!
So the guide I mentioned earlier is pretty much applicable for the newer model as well? What a relief!
I am also grateful for the hint on how to obtain the stock firmware. For all the dirty things I did to my devices in the past, it never became necessary to put the LMS-Assistant to use, but I will gladly change that now.
As soon as my device arrives, I will try to root it as you suggested and will report back how I fared.
Again, many thanks!

It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!

Brotinger said:
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Click to expand...
Click to collapse
Hi. I just purchased the same tablet. I would appreciate it if you could write up a guide on this forum. It would be a help for everyone.
I'm not even sure how you unlock the bootloader on this thing!

Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).

Tutorial
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it

b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I want to apply it to my device, have you tried this method?

Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.

b4nd0ler0 said:
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
Click to expand...
Click to collapse
thanks, I'm waiting for news from you. The tablet is sold very much in our country. like this in the world. I'm sure the developers will do something about this device.

b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I rooted my device with this method

this method doesn't work
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?

adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
This method is working!
Use the Official Lenovo website to access your original "rom" file and get the "boot.img" file.
Program: Lenovo Rescue And Smart Assistant https://lnv.gy/3d8FHLi
For an article on how to download the Rom file via the program, see here. (Step 3)
https://bit.ly/2yE1nQf
Good Luck!

adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
You did not enable Magisk Hide

mingkee said:
You did not enable Magisk Hide
Click to expand...
Click to collapse
That was it! Thanks! You're smarter & more helpful than Google!!! ))

Hi.
After i root the tablet, i tried to delete youtube and gdrive. Then i restart the tablet but it stuck in fastboot mode. Not booting.
i couldn't install stock rom. What i must do

I did this..
i patched the boot img from the lenovo program. and i like to shut down my devices when i dont use them and now i cant make it boot. im stuck in a bootloop and its says orange alert when i boot the device. i can only get into the fastboot menu. when i try to boot with vol + and power nothing happens and when i release it starts up again in a bootloop. i cant shut it down either. it just loops and loops. cant do the rescue thing with the program either.. anybody that knows how i can fix this?

I have an out of topic question regarding this tablet.
Can The Lenovo M10 Plus (2nd Gen) 10.3" TB-X606F Output Display via HDMI to TV ???
I tried using a powered USB-C to HDMI adapter to output/mirror the tablet to a TV, but it didn't work.

Brotinger said:
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Click to expand...
Click to collapse
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.

unlock not possible
CMX939 said:
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
Click to expand...
Click to collapse
I have the same issue, "waiting for device" and adb dies.
I assume, the latest lenovo updates (Android 9) block unlocking.
The current! LMSA tool does not allow to restore an old separately downloaded firmware