Develop Bugs

[Q] HTC one M8 (dual sim) stuck on bootloader! What can I do?

Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!

Flash it again via adb, the flashing command must be executed twice.

I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!

Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.

Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!

Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s

Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.

OP - Do you want it back to Sense?

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.

Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...

EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.

We should be able to sort things out, but I'll need to get to a proper PC and get links together

EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!

OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!

EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.

I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!

The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you

At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?

Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.

[Q] HTC One M8 won't boot.

Some one please help me.
I have the HTC One M8 which I updated to Android 5.0.1 through OTA updates about 2 weeks ago.
Yesterday, I successfully unlocked the bootloader and rooted my device. I also have the TWRP Recovery v.2.7.0.2 installed.
Everything was working fine until after the root when I noticed that the internal storage had some kind of write protection on it. Like even the default "DCIM , ANDROID, Downloads etc... folders weren't there". I discovered the write protection on the internal storage when I tried to download a file using Chrome on the phone and it replied with "No SD Card".
Funny thing is apps from the Play Store were installing perfectly fine.
So I booted back into TWRP recovery and did a factory reset thinking I must've messed up while rooting.
After the factory reset when I try boot up my phone the Setup Wizard constantly crashes so I can't do anything.
My HTC One M8 is the international variant Model: 0P6B100.
Someone please help

1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard

ckpv5 said:
1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard
Click to expand...
Click to collapse
I installed TWRP 2.7.0.2 using All in one tool v2.0 by Hasoon2000. The tool needs usb debugging to be turned on which I can't turn on because I can't get past the setup wizard because it keeps crashing.
Is there a way to install it manualy using fastboot?

I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned

ckpv5 said:
I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned
Click to expand...
Click to collapse
Okay I got my serial number. Now what do I do with it?

bolajiibrahim7 said:
Okay I got my serial number. Now what do I do with it?
Click to expand...
Click to collapse
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.

ckpv5 said:
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.
Click to expand...
Click to collapse
I did that. Then it started the "Android is upgrading - Optimizing apps splash.
After that I'm back to the Setup Wizard which keeps crashing.

Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)

ckpv5 said:
Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)
Click to expand...
Click to collapse
My software version is 5.0.1 Lollipop.
I don't have a stock backup. RUU is my only option.
Here's my fastboot getvar all
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\adb>

I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.

bolajiibrahim7 said:
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.
Click to expand...
Click to collapse
You don't need S-Off to run RUU, relocked bootloader before run RUU. Read thru that thread, there are many discussion.
Read this, this guy also doesn't have S-Off device : http://forum.xda-developers.com/htc-one-m8/help/one-m8-htc001-cid-firmware-wifi-problem-t3031656 and he managed that.
Or just restore backup that linked to you if you don't feel to relock bootloader.
You need to read all those thread. Without reading, this is going no where .. good luck

ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
What does RUU mean? and how do I use it?
Also does applying RUU restore my phone to the way it was before root as in With Android 5.0.1 and Sense 6.0?

RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.

ckpv5 said:
RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.
Click to expand...
Click to collapse
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s

bolajiibrahim7 said:
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s
Click to expand...
Click to collapse
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot

Thank You.
ckpv5 said:
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot
Click to expand...
Click to collapse
Thank you so much for your help. My phone is now on Lollipop and rooted and working fine.

Kinda in the same problem...
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43TWM0xxxx
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
TWRP 2.7.0.1 - I know it's old and buggy but flashing a newer one, even though it flashes ok, it wont load.
The phone is Tampered - Unlocked with S-On
After unlocking and flashing TWRP, I flashed custom ROM MaximusHD, it worked but as I didnt that it needed newer firmware, wifi wasnt working, tried to restart the phone and it entered in a boot loop.
Then flashed: http://forum.xda-developers.com/showthread.php?t=2699186
But it wont boot...
Could you please help me?
Thanks in advance

macdo said:
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version-bootloader: 3.16.0.0000
product: m8_ul_ca
modelid: 0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)

Thanks for the fast answer, I'll it and report back!
---------- Post added at 02:20 PM ---------- Previous post was at 02:16 PM ----------
ckpv5 said:
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)
Click to expand...
Click to collapse
After fastboot oem lock, I got this:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.139s
And rebooted to bootloader now, it says:
Tampered
Relocked
Security Warning
Is it ok? (btw, im downloading ruu)
Thank you so much!

[Q] Stuck in fastboot and no connections in ADB

Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi

ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.

riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?

Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app

elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?

PLS can anyone help me ? :crying:

themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?

FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.

themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.

FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..

Can't get my m8 to boot anymore

I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.

bavman said:
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
Click to expand...
Click to collapse
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).

DavidYouKnow? said:
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
Click to expand...
Click to collapse
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup: https://mega.nz/#!mYxDWApA!JbdLZAhYkz8fas5MpPfOQqGScikCLCmG21KBsjRJKQQ
Then use latest twrp recovery 3.0.2-0: https://dl.twrp.me/m8/twrp-3.0.2-0-m8.img.html and install it.
Here is the Stock Recovery that you need later: https://mega.nz/#!SUATBBbQ!-IUlr_tqnpkYFUM0bedRSRH3w__nCZjEAYls-5zncX4.
Then do this taken from this page: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
The basic idea is : fastboot flash recovery NameOfRecovery.img
2. Download TWRP backup - link in post #2 & post #3
3. Download stock recovery - link in post #4
4. Extract the downloaded x.xx.xxx.x_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
12. reboot - check for OTA, download, install
13. you may have multiple OTA when your device currently on a lower version
14. done
If you want to flash TWRP again, use the latest TWRP after last OTA
NOTE : There is no need to relock bootloader when doing the nandroid way to revert to stock and do OTA.
Click to expand...
Click to collapse
..............................................................................
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?

DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup:
********
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
Click to expand...
Click to collapse
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0

DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
Click to expand...
Click to collapse
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.

redpoint73 said:
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
Click to expand...
Click to collapse
No i didnt guessing at the version number, i thought that he have a higher Firmware version. Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.

ckpv5 said:
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
Click to expand...
Click to collapse
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.

bavman said:
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
Click to expand...
Click to collapse
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------
DavidYouKnow? said:
Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
Click to expand...
Click to collapse
Restoring by RUU versus nandroid are two completely different things, and you should be careful not to confuse the two:
RUU re-writes all partitions, including firmware, so there is no chance of a mismatch between firmware and ROM. Therefore, you don't need to match the RUU version to firmware, as long as the RUU is equal or greater number than the current firmware on the phone (no "downgrading" with s-on). And with s-off, this requirement is removed entirely, so you can run any version RUU that matches your CID, MID.
Restoring by nandroid is a completely different animal. Nandroid just contains the ROM and kernel. It needs to match the firmware on the phone, otherwise it won't work properly.

redpoint73 said:
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
Click to expand...
Click to collapse
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).

ckpv5 said:
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
Click to expand...
Click to collapse
Now I understand. Its confusing, since the 2 methods (both of which have you to credit) to return to stock are both referenced in this thread (another user references the nandroid method); and folks often use the term "firmware" incorrectly to refer to the ROM.
It also means that the user did not follow your instructions in Post #5 in the proper sequence. So RUU failing was inevitable, and easily avoidable; if they had followed your instructions in the proper order.

HTC 820 Desire Flashing Firmware Tutorial

So basically I made this guide for myself and though that It would be good for sharing it.
My problems started when phone just started restarting after one of the components failed. Sometimes it would be google play services, sometimes htc backup, sometimes others.. Plus, phone didnt wanna recognize my SIM card. Okay, tried with other roms here (sadly, there are only a couple of roms for this phone). None of them worked fully, while I could get rid of random restarts SIM still wasnt recognized. I was starting to lose my mind here, but hopefully found the solution. Here is a process of it:
Important note: Its really important that you read through everything first (especially useful links in the last section "Useful guides" ) and then to try and fix your phone
1. Usefull commands:
fastboot.exe getvar all -gets info about device, but you need to be in fastboot mode
Result:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U10305041_08.01.50512
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MB622YC03068
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ40000
(bootloader) cidnum: HTC__032
(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: 1be89947
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
fastboot.exe oem readcid -gets CID from device. List of CIDs(https://forum.xda-developers.com/desire-820/general/htc-cid-list-t3359862)
Result:
Code:
(bootloader) cid: HTC__032
2. To unlock bootlader:
You need Unlock_code.bin file from htcdev.com(obtained by pasting the result of a command
fastboot oem get_identifier_token -gets you code for generating Unlock_code.bin.
Code:
<<<< Identifier Token Start >>>>
7AC0E35FE034FCAB88DEC6B8E650EC33
63556D84723B05EE4B2CE16AA8E6B1A4
B3E94B50C50EF1F6016D39CD16021F03
CBB2BEF798EE9FE77E395895449C4AC7
017E71B15D5E2C9AEBEBB41C491BA255
6D3F7E66005B5A36856DE0F59CCAE258
C944A80FACD0DBBD684297F15BE4AE26
183302EFBA2BF7A99B7A5CB1D4895E39
818A3F562FBCC159568F77C54C27EC16
6FD4F5200326F2B0E6E2B417A4145D85
1C692E7E62BDF4EC1B34A12CEB98E0EC
AB09CECABCDC11E60A3EAA28F0C81A0A
688F2A62591B21EEA7560DD07D14CBC8
9E536469D50C1DD79D5ACA6858D12155
199C47F8951658C98D11314467138082
787381ECA7DA832308497380A53EE403
<<<<< Identifier Token End >>>>>
After pasting that code into htcdev.com (you need to register), and getting Unlock_code.bin in your mailbox...
Run this command to unlock your bootloader.
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
And, to relock it, run this:
Code:
fastboot oem lock
Important: After the first unlock you will never get a status "LOCKED" in hboot.
Only "RELOCKED". Some say that to get trully again "LOCKED" status you need to S-OFF (Security-OFF)
3. To update firmware (not the same as rom
I was before on marshmallow.
First you need to download a firmware, which is in the zip format. Note that it cant be extracted and its not supposed to.
File name is in a like this format:
0PFJIMG_A51_UL_M60_DESIRE_SENSE70_MR_HTC_Europe_3.17.401.3_Radio_01.01.010_U10305041_08.01.50512_release_476105_signed_2.zip
Note the part A51_UL - matches the "product" property of "fastboot.exe getvar all" command;
M60 - i can only assume that it is a code for Marshmallow 6.0;
SENSE70 - HTC Sense version;
Europe - I can assume that this has to match your CID. (mine is 032 which is EastEurope);
3.17.401.3 - My assumption is that this has to match your bootloader version. Mine is 3.19.0.0000 so you should find a closest version to yours
Radio_01.01.010_U10305041_08.01.50512 - this is important also! Its the radio version and *must* be the same as the one you get from "fastboot.exe getvar all" command.
4. Flashing:
There are two ways to flash the firmware. Via usb(adb/fastboot) and directly copying firmware to your sdcard and booting into bootlader.
Keep in mind that your bootlader has to be either relocked or locked. It wont work if you have "UNLOCKED" status.
For both ways you have to rename that long file name to a short, in exactly following manner:
Mine, from "0PFJIMG_A51_UL_M60_DESIRE_SENSE70_MR_HTC_Europe_3.17.401.3_Radio_01.01.010_U10305041_08.01.50512_release_476105_signed_2.zip" became "0PFJIMG.zip". You only need to keep that first parameter as the file name.
4a. Via usb (boot into fastboot mode):
fastboot oem rebootRUU - Reboot into RUU mode, you will get black screen with silver htc logo
fastboot flash 0PFJIMG.zip -this will flash your file and take a while. However, you might get an error like me(failed remote: 32 header), or similar header number. If so, try the other method (4b).
4b. Via sd card:
Copy the 0PFJIMG.zip in the root of your sd card;
Reboot your phone into hboot and it should automatically recognize that file and start flashing.
It takes a bit, aroound 10-20 minutes? I forgot, but as long as the bar is moving you're good.
After that, phone will prompt for a restart and go into usual procedure of first start.
Keep in mind that your data on microsd card will not be deleted, so you're good.
5. Where to find image for your device?
This took me long to find but you have it on gsmdevelopers in this big thread:
For example I found mine on
You need to search through it by your product(model), radio, bootloader and android version. These three should match. Also, the CID too (or take the region closest to you if previos four parametres are matching and you cant find your specific cid).
6. Drivers:
The usual adb/fastboot binaries are required as well as the special "Htc special fastboot Driver" from here.
I dont think your fastboot will recognize your device without these drivers. If the link gets broken those drivers can be found on XDA too.
So if you are getting an error where fastboot cant recognize your device - check the drivers first from that and other sources as well.
7. What after?
You can now safely again unlock the bootloader and install twrp and after that root your phone if you need it.
8. Installing twrp:
Unlock bootloader(check 1.) and follow this guide:
For rooting I havent tried SuperSU, but used Magisk root.
9. Useful pages:
Flashing guide:
http://forum.gsmdevelopers.com/htc-...-file-flashing-via-sdcard-flashing-guide.html
https://www.hardreset.info/devices/htc/htc-desire-820/faq/firmware-flash/update-change-repair-htc/
To obtain Unlock_code: https://www.htcdev.com/
Firmware mention in this guide: https://androidfilehost.com/?fid=24572369242687630, taken from this page:http://forum.gsmdevelopers.com/htc-firmware-unified/42090-htc-desire-820n-a51-ul-firmware.html
Extremely useful guide: http://forum.gsmdevelopers.com/htc-...t-unrevealed-complete-guide-informations.html