Develop Bugs

[Q] DHD totally stuck in white screen, nothing seems to help.. *SOLVED, MoBo broken

I bought DHD, which won't boot at all, I thought maybe I can fix it, but dunno anymore. Here's what hboot screen says:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24
I've tried to flash recovery from 2 different SD-cards, but hboot doesn't recognize my sd's at all. I have thought, that it should check the card and scan it at the beginning, but that won't happen. Filesystem is FAT32. I've also tried to unlock the bootloader, but it gets stuck to error message 'Command error' (fastboot oem get_identifier_token). When I try to flash recovery, it says 'Signature verify fail' (fastboot flash recovery recovery.img)
RUU is RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
When I try to install another (older) RUU it stops always to signature error (132)
Is there any way to get this phone to working condition again? No need to root nor Custom ROM...
Oh, almost forgot. fastboot getvar_all shows:
version: 0.5
version-bootloader: 2.00.0027
version-baseband: 26.14.04.28_M
version-cpld: None
version-microp: 0438
version-main: 3.12.405.1
serialno: HT0C8RX02173
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4152mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 743ca94a
hbootpreupdate: 11
gencheckpt: 0
region-id: 0

There's always a danger of buying a phone of this nature without knowing its history. Usually when they don't do any flashing and this happens its hardware problem. I bought one with the same problem as yours and i tried every known method sad to say i was resign to having bought a brick but lucky for me i bought another cheap with cracked screen so i took out the main board and switch it over use the best parts of both phones and i got myself a nice working DHD with a spare chrome housing. So maybe yr best bet is to lookout for a cracked screen one and do the same. Put an ad on web for yr area..you never know .....good luck cheers
Sent from my Desire HD using xda premium

ndmuni said:
There's always a danger of buying a phone of this nature without knowing its history. Usually when they don't do any flashing and this happens its hardware problem. I bought one with the same problem as yours and i tried every known method sad to say i was resign to having bought a brick but lucky for me i bought another cheap with cracked screen so i took out the main board and switch it over use the best parts of both phones and i got myself a nice working DHD with a spare chrome housing. So maybe yr best bet is to lookout for a cracked screen one and do the same. Put an ad on web for yr area..you never know .....good luck cheers
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Yeah, I also think that the phone is bricked, I've tried anything, and because it doesn't recognize SD-card in the hboot, I think it's a hardware problem...
Oh, and another thing: Phone LED stays red always when usb plugged, even when I remove USB cable... It turns off when I pull the battery off. I've never seen any other colour, even after all night loading...
Now I'm beginning to search one with cracked screen also. Luckily I didn't pay much for that brick.

Have you tried putting phone in fastboot and running the current ruu. Older ruu won't run on newer hboot.
Sent from my Inspire 4G using xda premium

You need http://www.mobfirmware.com/dl/behtash/imei dhd/rom.zip
Move it to where your adb files are.
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!

luncht1me said:
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!
Click to expand...
Click to collapse
Thank you! I'll try that. I've tried to unlock bootloader, though, but when I type fastboot oem get_identifier_token, it won't do anything, just says 'command error' ...

luncht1me said:
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!
Click to expand...
Click to collapse
OMG, I got the bootloader unlocked, but then what? I tried to flash ROM from RUU, but it stopped to error message "FAILED (remote: not allowed)" ... ? Sorry for my stupid questions, but this is all new for me. I'm fast to learn, though

deezaye said:
OMG, I got the bootloader unlocked, but then what? I tried to flash ROM from RUU, but it stopped to error message "FAILED (remote: not allowed)" ... ? Sorry for my stupid questions, but this is all new for me. I'm fast to learn, though
Click to expand...
Click to collapse
Ruu can not be flashed with unlocked bootloaders.
Sent from my GT-N7000 using xda app-developers app

glevitan said:
Ruu can not be flashed with unlocked bootloaders.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
OK. Can I flash any custom ROM then? What version should hboot be? It's now 2.00.0029, what if I put custom recovery and custom rom in? Do I need to downgrade hboot, or do I need S-OFF, or ENG S-OFF?

deezaye said:
OK. Can I flash any custom ROM then? What version should hboot be? It's now 2.00.0029, what if I put custom recovery and custom rom in? Do I need to downgrade hboot, or do I need S-OFF, or ENG S-OFF?
Click to expand...
Click to collapse
What you,need is to read. You have idea of what you are doing. Use the guide in my signature, it will help.
Sent from my GT-N7000 using xda app-developers app

glevitan said:
What you,need is to read. You have idea of what you are doing. Use the guide in my signature, it will help.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thanks, only problem is that I can't use adb, since it doesn't recognize my phone at all, nor flash anything from SD, it's not recognized either.
I can only use fastboot commands
fastboot flash zip cwm-5.0.2.7-ace.zip --> Failed (Remote: 32 header error)
fastboot flash zip pd98img.zip --> Failed (Remote: 24 parsing android-info fail) OR 41 model id check fail

deezaye said:
Thanks, only problem is that I can't use adb, since it doesn't recognize my phone at all, nor flash anything from SD, it's not recognized either.
I can only use fastboot commands
fastboot flash zip cwm-5.0.2.7-ace.zip --> Failed (Remote: 32 header error)
fastboot flash zip pd98img.zip --> Failed (Remote: 24 parsing android-info fail) OR 41 model id check fail
Click to expand...
Click to collapse
Make sure that you are on fastboot. Are you putting you phone on ruu mode first? (fastboot oem rebootRUU)
Sent from my GT-N7000 using xda app-developers app

glevitan said:
Make sure that you are on fastboot. Are you putting you phone on ruu mode first? (fastboot oem rebootRUU)
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, and yes.

deezaye said:
Yes, and yes.
Click to expand...
Click to collapse
Sorry, do you mind if I have a look over teamviewer? Maybe, there is something missing...
Sent from my GT-N7000 using xda app-developers app

glevitan said:
Sorry, do you mind if I have a look over teamviewer? Maybe, there is something missing...
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
OK

deezaye said:
OK
Click to expand...
Click to collapse
Conclusion: Hardware/mobo failure... Thanks Glevitan for help!

[Q] Please help ! bootloop after OTA of rooted phone

Hi guys,
Please help !
I've bought a new phone, htc one x, from someone. barely had time to install few apps, and got this OTA update message.
Without thinking twice - i did it. But it seems that the phone was rooted ! and as I understand now - it's a big no-no .
I've tried to figure out from the forum what to do , but - all the answers seems to include fastboot and ADB, which in turn require
the drivers of the phone to be installed. But my phone is dead ! so I can' t do it.
I'm new to roms and all, and I really need your help .
How can I make my phone work again ? I don't care which ROM , custom or stock , just to make it work .
Any help will be appreciated.
Gena

You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2

big noob said:
You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Hi , yes, I can access the fast boot, but even trying to restore to factory defaults didn't help.
And I can't istall the fastboot on my pc since it needs to connect to a working phone in debug mode (if I understand correctly)

Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2

big noob said:
Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.

Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file

genaddiy said:
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.
Click to expand...
Click to collapse
You are S-OFF you can install any RUU try with THIS ONE lock the bootloader and run the RUU as Administrator
post result from command fastboot getvar all and delete your S/N and IMEI from the info for any case
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
big noob said:
Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file And try to flash it
Click to expand...
Click to collapse
He can't install OTA from recovery and you can't install OTA from recovery!!!!

Hi Thant, thank you for your help.
So you are saying that big noob's method won't work ?
I've downloaded the RUU, but I did not understand what you've meant by : "lock the bootloader" and when should I post the results of "fastboot getvar all" ? after I run the RUU , or before ?

You should post it before RUU..Well i tryed my method before and .zip flashed successfully..
And you can relock it with this command:
fastboot oem lock

Here's what I've got, no what should I do with it ?
>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.2
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) devpower: 47
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.830s

You can relock your bootloader download RUU and run it as administrator

I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?

genaddiy said:
I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?
Click to expand...
Click to collapse
Try this one
And when you in bootloader what is writen up RELOCKED and ENDEAVORU XE or ENDEAVORU PVT

98552432 231
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL

genaddiy said:
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL
Click to expand...
Click to collapse
ENDEAVORU XE have problems with update you must manually update the firmware and after this to install RUU or custom rom.
Download THIS OTA open the zip and extract firmware.zip to your fastboot folder after this do this
Type: fastboot oem rebootRUU and wait for device to reboot you will see HTC logo
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.

I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?

genaddiy said:
I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?
Click to expand...
Click to collapse
yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go

ok , just to make sure I understand before I do it a screw something up :
"yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go"
my hboot version is indeed 1.39
so I d/l philz custom recovery .
no I should :
fastboot flash zip philz_touch_6.07.9-endeavoru.zip
then go to the custom recovery ? (how ? ? ? )
then d/l some custom rom (any recomendations ? just a good stable one, possibly stock)
then copy it to phone using fastboot
and then , from custom recovery flash it ?
I'm sorry for all these questions, but I'm afraid to touch the damn thing already ))))

Flash the recovery (its a img file NOT a zip, take out the img if its in the zip)
Fastboot flash recovery recoveryname.img
Fastboot erase cache
Enter the recovery by selecting FASTBOOT in the bootloader and then RECOVERY (navigate with the volume buttons and confirm with the power button)
Go to the mounts and storage menu and mount the sdcard as a mass storage disk (wait a few minutes until it pops up on the pc)
Copy the rom.zip to the sdcard. Take out the boot.img and flash it via fastboot
Fastboot flash boot boot.img
Fastboot erase cache
Enter recovery again and perform a full wipe
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache, data and system
Install the rom.zip
Done !
Roms....just check the android dev section. Many roms to choose and read up for yourself. It's not that difficult ...maximus and arhd are very close to stock.

Thank you for the detailed reply !
When doing Fastboot flash recovery recoveryname.img I got the messege :
FAILED <remote : not allowed>
Is the problem that my phone is locked ? (written locked at the top of fastboot screen) tried to do fastboot oem unlock but getting "Command error !" .
I saw this solution : http://forum.cyanogenmod.com/topic/74316-a-solution-to-fastboot-flash-recovery-not-allowed-error/ , but I'm not sure it will fit my phone (as it talkes about a different one) and what is a PD98IMG.zip file ?

[Q] Q: Noob Help - Failed system update - unknown volume

Hello,
I'm really sorry for this post, but I know absolutely nothing about how any of this works and I found almost the exact same issue being posted about on the M7 section of the forum.
Ok, I recently picked up an HTX One X from work (unlocked, old and replaced so sold off) for my daughters first phone and it told me the was a system update available for it which I downloaded. I went to run it and it just kept rebooting so I watched it go through the process and then noted it was coming up with the text shown in attachment 003 (starts with ClockworkMod Recovery v6.0.4.8, E: Invalid command Argument...).
I had NO idea the phone had been modded in any way, and I've only found out what Clockwork Mod is in the last hour. From what I can tell I need to restore the phone back to its original factory 'image' as it were, without CWM?
Obviously I have no idea how to do this, or where to get a copy of the original image (could it possibly be saved in CWM somewhere, there are loads of features in there :S) Can I just use the featured in CWM to adjust the mounting options?
If someone could point me in the right direction that would be very much appreciated, and again my apologies for posting what I'm sure is a very simple thing for those in the know.
Regards,
David

Check sdcard if there is anything inside "clockworkmod" folder. Download fastboot_files. Extract it to C:\ so the path will be C:\fastboot. Open Command Prompt on PC and connect phone to PC and type:
Code:
cd C:\fastboot
and then type
Code:
fastboot getvar all
Paste result here.

denkem said:
Check sdcard if there is anything inside "clockworkmod" folder.
Click to expand...
Click to collapse
There is; a folder called 'backup' and 2 files: .last_install_path and .recovery_version
The backup folder has another dated folder from 2014/08/13 and within that a whole bunch of other files (see attached).

So you can go to Recovery and choose Restore. Then choose this backup to restore. But hard to tell what backup it is If stock rom or a custom rom

denkem said:
So you can go to Recovery and choose Restore. Then choose this backup to restore. But hard to tell what backup it is If stock rom or a custom rom
Click to expand...
Click to collapse
Exactly, the recovery and boot image files are both the exact same size and date as well. I have no idea if that recovery file is just a copy of the initial CWM install or the original system file

Yes, recovery and boot backup image are both same size. But it isn't definitelly backup of stock recovery (as somebody had to install custom recovery to make this backup ). Send me this getvar result.
You can also paste info from
Code:
fastboot getvar cid
Or, if it's just rooted stock ROM, you can try to copy this OTA update from data/media/0/ to sdcard, and install it with Recovery (install zip)...

denkem said:
Yes, recovery and boot backup image are both same size. But it isn't definitelly backup of stock recovery (as somebody had to install custom recovery to make this backup ). Send me this getvar result.
You can also paste info from
Code:
fastboot getvar cid
Or, if it's just rooted stock ROM, you can try to copy this OTA update from data/media/0/ to sdcard, and install it with Recovery (install zip)...
Click to expand...
Click to collapse
Sorry about the delay in response, lunch. work, than a fight with the mobile. I'm getting a (rather well know as it turns out) waiting for device message, so not getting the required info. Mobile is detected by the PC no problem, and HTC Sync is not installed. (USB Debugging is on).

Amenthea said:
Sorry about the delay in response, lunch. work, than a fight with the mobile. I'm getting a (rather well know as it turns out) waiting for device message, so not getting the required info. Mobile is detected by the PC no problem, and HTC Sync is not installed. (USB Debugging is on).
Click to expand...
Click to collapse
Download HTC drivers here. Install, reboot PC, try again.

denkem said:
Download HTC drivers - Install, reboot PC, try again.
Click to expand...
Click to collapse
Ok, got it working eventually. Wasn't drivers, I had to hard restart the phone and select Fastboot as it was in HBoot mode.... Told you I didn't know what I was doing!
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.4
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4157mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.937s
C:\fastboot>fastboot getvar cid
cid: HTC_044
finished. total time: 0.000s
C:\fastboot>

I'm travelling, so will try to reply later properly. For now, you could delete your imei and s/n from your post

denkem said:
I'm travelling, so will try to reply later properly. For now, you could delete your imei and s/n from your post
Click to expand...
Click to collapse
Yep, done, sorry about that.

Amenthea said:
Yep, done, sorry about that.
Click to expand...
Click to collapse
First of all, copy clockworkmod/backup folder to your PC. Then, I would say you got few options.:
First one: copy 2 files from this backup folder somewhere else (let's create some "working folder") - system.ext4.tar.a & system.ext4.tar.b. Rename them to system.ext4.001 & system.ext4.002. Then highlight the system.ext4.001 with "Insert" key, and then merge those files - I use Total Commander for this on Win (Total Commander - File - Merge Files). Then rename output file to system.ext.tar.
Then extract build.prop from this tar (system-build.prop). Find "ro.product.version". If it says "4.19.707.4" should be Stock nandroid backup. So then you can Restore this backup via CWM Recovery. When recovered, don't boot up, reboot to bootloader and copy boot.img and recovery.img to the fastboot folder on your PC. Connect phone to PC and type:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Reboot, done. You are back to stock (with unlocked bootloader, but that's not an issue - you can relock it by
Code:
fastboot oem lock
but that's not necessary)
Second one is to go to this thread, and download 4.19.707.5 ROM (if you wanna really use like it came from manufacturer, you should use odexed one). Install 4.19.707.5 via CWM, then flash boot.img & recovery.img as described above (you can download recovery from link I provided and use boot.img from downloaded ROM).
Done.

denkem said:
First of all, copy clockworkmod/backup folder to your PC. Then, I would say you got few options.:
First one: copy 2 files from this backup folder somewhere else (let's create some "working folder") - system.ext4.tar.a & system.ext4.tar.b. Rename them to system.ext4.001 & system.ext4.002. Then highlight the system.ext4.001 with "Insert" key, and then merge those files - I use Total Commander for this on Win (Total Commander - File - Merge Files). Then rename output file to system.ext.tar.
Then extract build.prop from this tar (system-build.prop). Find "ro.product.version". If it says "4.19.707.4" should be Stock nandroid backup. So then you can Restore this backup via CWM Recovery. When recovered, don't boot up, reboot to bootloader and copy boot.img and recovery.img to the fastboot folder on your PC. Connect phone to PC and type:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Reboot, done. You are back to stock (with unlocked bootloader, but that's not an issue - you can relock it by
Code:
fastboot oem lock
but that's not necessary)
Second one is to go to this thread, and download 4.19.707.5 ROM (if you wanna really use like it came from manufacturer, you should use odexed one). Install 4.19.707.5 via CWM, then flash boot.img & recovery.img as described above (you can download recovery from link I provided and use boot.img from downloaded ROM).
Done.
Click to expand...
Click to collapse
Apologies for the rather long delay in response, life got in the way as per usual. Ok, I've followed the steps as per above and everything appeared to go through just fine; it installed the odexed ROM via CWM and then I restarted in bootmode and used fastboot to flash the boot/recovery as required. The only thing different was the fact that I had a message about 'Root Access is missing' with a Yes/No Q and that it can't be undone (I clicked yes). Once restarted the phone did a check for updates (and saw the version I had just put in as an update...) so I let it try to install said update and was then greeted with the exact same message that started this whole thing to start with. Obviously CWM is still installed however I have run another check for updates and it no longer finds any, so I think it now knows it's up-to-date....

M8 won't boot

Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.

bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.

Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.

bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.

Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.

bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/

twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?

bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?

You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.

I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?

/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?

I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?

bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.

Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'

ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).

htc m8 decrypt storage issue

Hie everyone i am new here and i have an htc one m8 which is bootloader locked , s on and i dont have root access nor custom recovery installed .
All other tutorials i found here are more so related to those htc m8 devices with either bootloader unlocked or custom recovery installed and since the device is stuck on decrypt storage page i cant install an RUU firmware exe i downloaded and also i cant install a custom firmware too .
i found a tutorial on how to unlock bootloader and did got my token id from fastboot since it is the only thing working so far and am stuck with the stock recovery so i cannot get into adb mode.
when flashing the unlock code bin file in fastboot it says successfully and the warning page also appears which prompts me to choose to unlock bootloader or not . and after selecting unlock bootloader the device restarts into recovery mode i which i thought i have to factory reset for the bootloader process to be complete but still after factory reset the device boots straight to the decrypt storage page and when i reboot again into fastboot mode the bootloader is still locked like nothing happened . tried all methods to unlock bootloader and not factory reset in hope of getting better results but still its the same problem . so if there is another solution that might help me to unlock my bootloader or flash custom recovery or force it to install my RUU exe firmware without debugging i would greatly appreciate it
(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: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thats from getvar
and i also downloaded this firmware i dont know if it is the correct one for my device since its showing region as south africa (Region : VODA-Africa-South)
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
any help related to my problem is greatly appreciated

Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
ok let me try it and update you with the results

hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?

cliffordmoyo said:
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
Click to expand...
Click to collapse
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:

cliffordmoyo said:
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
Click to expand...
Click to collapse
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps

xunholyx said:
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
Click to expand...
Click to collapse
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right

cliffordmoyo said:
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
Click to expand...
Click to collapse
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.

xunholyx said:
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
Click to expand...
Click to collapse
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way

cliffordmoyo said:
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
Click to expand...
Click to collapse
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.

xunholyx said:
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
Click to expand...
Click to collapse
tried that last firmware zip but just want to confirm if i did the correct procedure ......
i downloaded this file you linked me : M8_6.12.401.4_WWE_TWRP2870.zip renamed it to 0P6BIMG.zip , copied it to my sdcard and and rebooted into bootloader . i could see the checking progress bar but then it just doesnt give me the prompt screen for vol up to continue or vol down to cancel , its just saying press power to reboot.
then tried fastboot oem rebootRUU but the fone is just stubborn and reboots into normal mode again not in RUU mode so i cant flash the zip firmware with fastboot . Another thing i noticed is when i finish unlocking bootloader and gets the success message with continue to unlock bootloader screen and then phone reboots into recovery (stock recovery) there is a chain of errors like "cannot mount data , cannot mount emmc" too but when i repeat the bootloader unlock process again this time with an sdcard in device i get "no cw files in sdcard" message when it reboots into recovery but still the bootloader wont be unlocked despite of repeating the process several times. the phone is still brand new never opened and i think this is somehow software related for i was beginning to think that its hardware issue but an app cause this "device decrypt storage" after the phone rebooted
Any idea where i can get htc mtp device drivers as i have reinstalled my operating system and installed htc syn too but those are the only ones failling to install now am on 32bit windows os , the ones i have downloaded are not installing maybe if those install i might recieve an "allow usb debugging " screen as i did earlier on before the screen didnt want to show up again

do you have any idea what might cause device to reboot into os/normal mode when executing the fastboot reboot-bootloader same as fastboot oem rebootRUU the device quickly reboots and enter into normal mode and does not hold those command . also if have downloaded almost 17 unlockcode.bin files from htc dev i kept on requesting after the bootloader wont get unlocked , it shows unlockcode flashed successfully in command prompt but when device reboots the bootloader is still locked . i still love my htc m8 but it seems i am the only one in this enter forum who has this problem since other are successfully getting their devices fixed :crying::crying: