Develop Bugs

need some help

i have been searching and reading but i still got no were i want to up date to lolli pop that telus has realed my problem is im on hboot 3.16.0.0000 os 1.54.401.5 bootloader unlocked s-off on super cid .im on m8 ul do ineed to go back to my provider cid wich is telus. i tried updating my firmware with adb and it goes thru all the process and it says ok but when i check all my info is the same.also when i try to install a custome rom they always fail any info would be great thanks

Alright let's give it another shot. Lets start from the beginning and get us the output of :
Fastboot getvar all
Then we can proceed to get it back to stock (and maybe keep it that way)

Mr Hofs said:
Alright let's give it another shot. Lets start from the beginning and get us the output of :
Fastboot getvar all
Then we can proceed to get it back to stock (and maybe keep it that way)
Click to expand...
Click to collapse
C:\Users\Ron\Desktop\saki>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.087s
here is the getvar all results

Delete your serial to begin with. Never post any serials or imei numbers on forums or any board.

Mr Hofs said:
Delete your serial to begin with. Never post any serials or imei numbers on forums or any board.
Click to expand...
Click to collapse
thanksoh oh i missed that one

Change your CID back to Telus: fastboot oem writecid TELUS001
Flash 3.x firmware on your device. You can go to this thread and find it RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
To flash firmware:
Download the OTA.zip for telus 2.23.661.2 -> 3.34.661.4 Which is in that thread. Inside the OTA.zip you'll find firmware.zip extract the firmware.zip from OTA.zip.
Place firmware.zip inside your adb/fastboot folder.
Boot phone into bootloader(If it's not already there after the CID change).
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <<<Yes that's correct, flash the same commad TWICE. First one only updates HBoot, second time around it'll update the rest of the firmware.
fastboot reboot-bootloader
fastboot flash recovery name_of_custom_recovery.img
Place the nandroid backup(3.34.661.4 which you can find in link provided for backups) inside TWRP Backup folder on your device. If the directory doesn't exist. Go into TWRP and make a backup of boot only to create the directory. If needed enable MTP to transfer files from PC to Device through TWRP Recovery.
Restore the nandroid backup.
Inside the firmware.zip in your adb folder you'll find the stock recovery.img for the device. Extract the recovery.img and place inside adb folder.
fastboot flash recovery recovery.img
Boot into system and check for update to 4.x

BerndM14 said:
Change your CID back to Telus: fastboot oem writecid TELUS001
Flash 3.x firmware on your device. You can go to this thread and find it RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
To flash firmware:
Download the OTA.zip for telus 2.23.661.2 -> 3.34.661.4 Which is in that thread. Inside the OTA.zip you'll find firmware.zip extract the firmware.zip from OTA.zip.
Place firmware.zip inside your adb/fastboot folder.
Boot phone into bootloader(If it's not already there after the CID change).
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <<<Yes that's correct, flash the same commad TWICE. First one only updates HBoot, second time around it'll update the rest of the firmware.
fastboot reboot-bootloader
fastboot flash recovery name_of_custom_recovery.img
Place the nandroid backup(3.34.661.4 which you can find in link provided for backups) inside TWRP Backup folder on your device. If the directory doesn't exist. Go into TWRP and make a backup of boot only to create the directory. If needed enable MTP to transfer files from PC to Device through TWRP Recovery.
Restore the nandroid backup.
Inside the firmware.zip in your adb folder you'll find the stock recovery.img for the device. Extract the recovery.img and place inside adb folder.
fastboot flash recovery recovery.img
Boot into system and check for update to 4.x
Click to expand...
Click to collapse
Well if this doesn't work ....... :thumbup:

Mr Hofs said:
Well if this doesn't work ....... :thumbup:
Click to expand...
Click to collapse
do i extract it from ota or just copy and past firmware zip in my adb folder because i get error 42 custom id check fail

ron31 said:
do i extract it from ota or just copy and past firmware zip in my adb folder because i get error 42 custom id check fail
Click to expand...
Click to collapse
Since you are having trouble, I'll give you an alternative method. I'm on Telus as well, and use WWE firmware. It works with no issues.
First off, back up anything that is important to you, like photos and files, because this will wipe your phone's internal storage.
Go back to SuperCID.
Download this RUU zip.
Rename it to 0P6BIMG.zip (that's a zero, not the letter)
Place it onto the root of your extSD (By root of I mean just on the card, not in a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power to reboot when finished) Have a beer, it'll take a few minutes.
After the flash, delete the file from your extSD, otherwise every time you boot into hboot, it'll try to update again.

Edit ....didnt refresh

xunholyx said:
Since you are having trouble, I'll give you an alternative method. I'm on Telus as well, and use WWE firmware. It works with no issues.
First off, back up anything that is important to you, like photos and files, because this will wipe your phone's internal storage.
Go back to SuperCID.
Download this RUU zip.
Rename it to 0P6BIMG.zip (that's a zero, not the letter)
Place it onto the root of your extSD (By root of I mean just on the card, not in a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power to reboot when finished) Have a beer, it'll take a few minutes.
After the flash, delete the file from your extSD, otherwise every time you boot into hboot, it'll try to update again.
Click to expand...
Click to collapse
ok i copied file to my sd card renamed it like you said when i go to bootloader i select hboot and what i get is fastboot recovery factory reset simlock

Mr Hofs said:
Edit ....didnt refresh
Click to expand...
Click to collapse
i downloaded the file as per instruction.i renamed it put it on sd card i choose hboot it loads for a second and goes back to fastboot screen with options fastboot recovery factory reset and so on

ron31 said:
ok i copied file to my sd card renamed it like you said when i go to bootloader i select hboot and what i get is fastboot recovery factory reset simlock
Click to expand...
Click to collapse
You either put it on your internal SD instead of your external SD, or you renamed it incorrectly.

xunholyx said:
Since you are having trouble, I'll give you an alternative method. I'm on Telus as well, and use WWE firmware. It works with no issues.
First off, back up anything that is important to you, like photos and files, because this will wipe your phone's internal storage.
Go back to SuperCID.
Download this RUU zip.
Rename it to 0P6BIMG.zip (that's a zero, not the letter)
Place it onto the root of your extSD (By root of I mean just on the card, not in a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power to reboot when finished) Have a beer, it'll take a few minutes.
After the flash, delete the file from your extSD, otherwise every time you boot into hboot, it'll try to update again.
Click to expand...
Click to collapse
update when i changed the file name i put zip on the end and the file had 2 zips on the end of it its updating as we speak thanks for all the help guys:good:

[Q] Wi-Fi Disabled After Unrooting

Hi,
I have a HTC One M8 and I believe it is the international version (bought in Australia).
I wanted to return it to stock before selling, and it seemed to go well until I did a software update. After the update I cannot turn Wi-Fi on. The on/off switch is permanently greyed out.
I have a feeling it was because I could not match my version-main when picking the backup file. My CID is TELST001 and my version-main is 3.32.something (I don't have my computer on me).
However there was only one option to pick from which was something like 1.12
Any ideas?
Thanks, Mitch.

You can't use that very low version of backup for hboot 3.16.0000 when you have hboot 3.19.0000
The lowest you can go is one version below that is 2.23.841.1 that is for hboot 3.18.0000
Unfortunately I don't see any of Australian backup shared on XDA other than 1.xx
I have only OPTUS backup for all versions but not TELSTRA ... maybe if I have time I'll make some for TELSTRA this weekend.

Thanks for the reply.
Is there any way I could downgrade the android version such that I can use the very low version that is available for my Telstra HTC?

Not possible without S-Off.
Furthermore there's nothing much being shared for Telstra.

Would my best bet be to root the device again?
I found a "Stock Telstra WWE (Australia) ROM 2.24.841.1". Would this help? I can't link it yet.
Cheers.

If that's for M8 then that's the right one.
Yes you need custom recovery to restore backup
EDIT:
Just checked, that's for M7 not M8 don't use it.
I'll try to find time to make a backup for you.
Check back tomorrow
Meantime.. can you post your fastboot getvar all (minus serial no. & imei no.)
I need to make sure I make a right backup for your device version

Thank you, I really appreciate your assistance.
Is there anything I can do tonight that will be on the right track to fixing it? I have a buyer for the phone lined up and he wants it asap.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.841.9
(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: 0P6B11000
(bootloader) cidnum: TELST001
(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: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

I'll post 3.32.841.9 backup and its recovery tomorrow.
Nothing much to do now. Just flash TWRP 2.8.3.0 because you need it to restore backup

I'm having trouble flashing TWRP because it has changes since I last did it. Android Studio has come in?
Anyway I installed Android Studio but it threw an error "Failed to install Intel HAXM".
Haven't found a solution to this, and hence I cannot run Android Studio and thus cannot flash TWRP.
Or is there a simpler way to flash TWRP I am overlooking?
Thanks again.

Android Studio ? Intel HAXM ? What are those ?
Download TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
Put the downloaded openrecovery-twrp-2.8.3.0-m8.img in the same folder that you have fasboot.exe
(You have that right ? You did run fastboot getvar all before)
Put your device in bootloader/fastboot mode
Run command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img

Android Studio is the package online when you wanna get the SDK, Google have hidden the normal SDK package!
OP, you want this is you need to update adb/fastboot - http://dl.google.com/android/installer_r24.0.2-windows.exe

EddyOS said:
Android Studio is the package online when you wanna get the SDK, Google have hidden the normal SDK package!
OP, you want this is you need to update adb/fastboot - http://dl.google.com/android/installer_r24.0.2-windows.exe
Click to expand...
Click to collapse
Ok .. thanks for info .. never use full SDK so don't know much about that

Okay all good, TWRP is flashed.
Haven't played with this stuff for a while so I am pretty rusty as you can see.
Cheers.
EDIT:
So theoretically all I need to do is restore from a GOOD backup which you are kindly working on creating?
Once I restore from that, should I re-lock bootloader and remove TWRP? Then do OTA updates to get it up to date software wise?

MitchellGray said:
So theoretically all I need to do is restore from a GOOD backup which you are kindly working on creating?
Once I restore from that, should I re-lock bootloader and remove TWRP? Then do OTA updates to get it up to date software wise?
Click to expand...
Click to collapse
Yes but no need to relock bootloader but it's your choice. If you do the bootloader will show RELOCKED instead of LOCKED. Unfortunately there is no update for TELSTRA currently. The last one as at today is 3.32.841.9

Gotcha.
Okay, well whatever the latest version is works for me. Or will updating the version conflict with the backup file you are going to share?

MitchellGray said:
Gotcha.
Okay, well whatever the latest version is works for me. Or will updating the version conflict with the backup file you are going to share?
Click to expand...
Click to collapse
No conflict as this is a clean non rooted stock backup for Telstra
Below is the general steps. You just skip what ever that already done.
1. Install TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
2. Download TWRP backup 3.32.841.9 - https://mega.co.nz/#!EJ4TxBYa!qtV7OUIBWmqtWD6KFlQcSUGkerLpNUsA5C4yj6QEQ7c
3. Download stock 3.32.841.9 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/3.32.841.9_recovery.img/download
4. Extract the downloaded 3.32.841.9_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. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.841.9 folder (not 3.32.841.9_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./3.32.841.9
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
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.841.9_recovery.img
12. reboot - check for OTA, download, install (if any)
13. done
Optional : to relock bootloader, boot to bootloader/fasboot - run command fastboot oem lock
Gotta go now ... be back in 3 hrs

ckpv5 said:
No conflict as this is a clean non rooted stock backup for Telstra
Below is the general steps. You just skip what ever that already done.
1. Install TWRP 2.8.3.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
2. Download TWRP backup 3.32.841.9 - https://mega.co.nz/#!EJ4TxBYa!qtV7OUIBWmqtWD6KFlQcSUGkerLpNUsA5C4yj6QEQ7c
3. Download stock 3.32.841.9 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/3.32.841.9_recovery.img/download
4. Extract the downloaded 3.32.841.9_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. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.841.9 folder (not 3.32.841.9_ckpv5 folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./3.32.841.9
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
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.841.9_recovery.img
12. reboot - check for OTA, download, install (if any)
13. done
Optional : to relock bootloader, boot to bootloader/fasboot - run command fastboot oem lock
Gotta go now ... be back in 3 hrs
Click to expand...
Click to collapse
oh my god is that TWRP backup the one you built for my version? Thank you so much.

All done. Phone is up to date and everything is functioning perfectly.
Cannot thank you enough ckpv5.

Great :good::good:
Glad to help

ckpv5 said:
Ok .. thanks for info .. never use full SDK so don't know much about that
Click to expand...
Click to collapse
Its so much easier to install adb/fastboot with one of the "minimal" install packages available on XDA.

WI-FI won't work after flashing custom ROM

Dear all,
After I flashed my HTC One M8 with a custom ROM (btw I did everything by the book according to Hasoon's All in one kit.) WI-FI doesn't work, it won't turn on.
Recovery: It was TWRP at first, but then I tried clockworkmod as well, after several flashing with other custom ROMs it still won't turn on.
Can you help me find out what the problem is?
Note: After several flashing attemps, although it was rooted at first, my phone somehow got unrooted.

Your firmware is outdated.
You need a 4.xx.xxx.x or 6.xx.xxx.x firmware to have a working wifi.
Check your bootloader, you should see the OS- no. there. If it is blank because you used an outdated recovery, see the hboot version .. must have 3.19.0000

I checked and this is what I have found:
***Tampered***
***Unlocked***
S-On
Hboot : 3.16.0.0000
OS - this area is blank
But I also checked my firmware number it starts with 6.xxxxxx

6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.

ckpv5 said:
6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.
Click to expand...
Click to collapse
Getvar results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.153s
I added the getvar all results. Unfortunately I don't have the non-rooted backup :/
And I'm sorry I'm new to this all. What exactly is sn OTA or RUU and how do I do it?

ongunpitir said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.

ckpv5 said:
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.
Click to expand...
Click to collapse
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?

kiuqxy said:
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?
Click to expand...
Click to collapse
This is usually due to your PC's configuration. Win7 and USB 2.0 for the best chance of compatibility.

I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.

ongunpitir said:
I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.
Click to expand...
Click to collapse
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.

ckpv5 said:
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.
Click to expand...
Click to collapse
I tried what you said this is what gives me;
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>htc_fastboot flash zip rom.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 4.28.502.2
found large-zip header, file count: 6
processing file 1/6...
sending 'zip' (57600 KB)...
OKAY [ 2.748s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Process Process-1:
Traceback (most recent call last):
File "C:\Python34\lib\multiprocessing\process.py", line 254, in _bootstrap
File "C:\Python34\lib\multiprocessing\process.py", line 93, in run
File "E:\largezip\htc_fastboot\htc_flashzip.py", line 207, in _do_extract
File "E:\largezip\htc_fastboot\largezip.py", line 61, in extract
MemoryError
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 16.911s
htc_fastboot finished. total time: 18.191s
C:\adb>

BTW, i wouldnt rely on toolkits either to flash the M8, should always be done manually either thru recovery methods, RUU or Fastboot, i never use any of the avail toolkits to flash anything.

ongunpitir said:
I tried what you said this is what gives me;
FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)

ckpv5 said:
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
View attachment 3711349
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)
Click to expand...
Click to collapse
Thank you so much! After many failures, I have finally managed to make it work. After relocking my device and flashing with a RUU using command prompt option, it finally worked. Now I can use my wifi again. Now I will try to flash a custom ROM, but you said I need to update my firmware right? So how do I do that? Or have I just updated it already by flashing the latest RUU?
Thanks in advance

The RUU already updated your firmware to the latest ... but still a Lollipop as there is no Marshmallow update for AT&T yet but that should be enough for now, your wifi should work on any custom ROM.

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.

If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.

ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?

That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.

Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.

Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?

I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.

Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
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
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?

Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?

downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip here : http://androidruu.com/?developer=M8

Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!

HTC M8 stuck in fastboot only showing RUU

Ok this is what happened.
I had the rom Android Revolution installed on my HTC M8.
Today I installed the new ROM Revolution, Android 6.0, but when I could not turn on wifi.
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot. He won't let me into recovery anymore, if i chose it, he trows me back to fastboot menu
SCREEN IN FASTBOOT:
Tampered *** ***
*** *** Relocked
M8_UL PVT SHIP S-ON
HBOOT-318.0.0000
RADIO 1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS 2.22.161.6
eMMC boat 2048MB
RUU
anyone have a solution?
Do i have to update firmware now, really don't now wich steps i should take right now.
Thanks for the effort

C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
C:\mini-sdk>

Mcdrug said:
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot.
Click to expand...
Click to collapse
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?

redpoint73 said:
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
Click to expand...
Click to collapse
download
M8_6.12.401.4_WWE_TWRP2870.zip
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
rcdata.img
rpm.img
sbl1-8974AA-1.img
sbl1-8974AB-1.img
sbl1-8974AB-2.img
sdi.img
sensor_hub.img
splash1.nb0
tp_SYN3508.img
tp_SYN3528.img
tz.img
wcnss.img
adsp.img
android-info.txt
error message:
i thought it was something like (FAILED (remote: 12 signature verify fail). maybe have to do it again to make sure what error message i got?

Mcdrug said:
download
M8_6.12.401.4_WWE_TWRP2870.zip
i thought it was something like (FAILED (remote: 12 signature verify fail).
Click to expand...
Click to collapse
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

redpoint73 said:
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)

Mcdrug said:
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
You need to unlock the bootloader again, in order to flash custom recovery.

Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?

Mcdrug said:
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Click to expand...
Click to collapse
You have to follow all the steps through Step 14.
Again, the goal is to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM

Can't get true this step:
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)
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
solution might be: Are you mounting the MTP in recovery mode ? It won't work this way.
You need to transfer them on a working OS (I mean you have to be on homescreen)
Try use an external sdcard.
I have put an external sdcard inside, i can put the files on the card
But then the files aren't located at the TWRP/BACKUP map.
What to do?

Mcdrug said:
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
What to do?
Click to expand...
Click to collapse
when you select boot to backup, you can select which storage the backup goes to .. select microSD instead of internal (read all menu in the backup section on TWRP)
then you can use a card reader to mount your microsd to PC and transfer the extracted contents of the backup zip to the same folder that you made with the boot backup and replace all files when PC ask you.

All done, back in stock rom, thank you very much!!
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
I choose in this step do not install, but he rebooted me direct into the stock rom.
Tried some things to get into the bootloader again, volume down and power, cmd with adb fastboot, but nothing really worked.
What's the reason i can't get back to bootloader, and how do i get step 11 fixed and flash stock recovery?

To go to bootloader when on OS running ... press power button and select restart. When the screen turn black .. hold volume down button .. that will take you to hboot screen, press power once will get you to fastboot/bootloader
To go to bootloader when on OS running ... you need to enable USB debugging in settings - Developer options. To enable Developer options, go to settings - about - software information - more - click build number until the developer options is enabled.
Once usb debugging is enabled, you can run command adb reboot bootloader to get to fastboot/bootloader

It works, did the last step:
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
but now can't entering recovery anymore, just showing a red trangle with an exclamation mark? And in some minutes he boots to OS.
Have to do step 1 again? Maybe go to a higher version? I want OTA to MM 6.0

You don't need to get into recovery after you installed stock recovery.
what you need to do ... boot to OS .. go to settings - about - software update - check for update, download and click install let the system do its stuff to update. After reboot, repeat the checking & install process.
And you need to do the checking & install, multiple times to update :
2.22.161.6 --> 4.19.161.2 --> 4.19.161.3 --> 6.12.161.4 --> done.