Develop Bugs

[Q] Phone stuck on fastboot/hboot, buttons unresponsive

Hi there,
I noticed the back and search physical buttons on my HTC Desire were not working so I rebooted it. However, it now goes straight to the fastboot white screen (or hboot if I power on with vol down) but none of the physical buttons (vol or power) appear to work - I can't select any options. This happens whether the SD card is in or not.
Hboot recognises when I plug a usb cable in (says 'HBOOT USB PLUG').
Can anyone help? Given that I can't actually do anything with the phone I guess I need a PC-based solution - I'm running linux mint 12. I'm willing to try anything at this point as my only other option is to get a new phone!
details are:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
I was running Nick's Phone V1.2 Based on Oxygen 2.3.2, with the Thalamus 2.6.35.14_r4 kernel.
Like I say, everything was running fine till the back/search button stopped working and I rebooted.
I'd be very grateful for any help/advice!
Cheers,
Martin
A bit more info - when I start it up in HBOOT with the sd card in (but not without it), after about 10 seconds a message flashes up really quickly relating to:
PB99IMG.zip .... no image or wrong image!
...so I guess I need to get this zip file on there somehow.
Any ideas?
Thanks,
Martin
More info: the message that flashes up is:
SD Checking ...
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
I tried putting a new PB99IMG.zip on a fresh sd card and starting HBOOT with that - it flashes but then I'm still stuck at the HBOOT screen with no norking buttons/way to select anything. Suppose I need the other .zip and .nbh files.

same problem
Im having the exact same problem. Used Nicks rom aswell and the power button became unresponsive and glitchy..went into hboot..cleared storage.
Now hboot is unresponsive and cant select anything
I flashed differnet hboots back and forth from cm7 r2 to oxygen
currently stuck on oxygen
S OFF
SLCD

I have same problem.. Is there anyone to help us ?

is your phone recognised by 'fastboot devices'?
any back up made prior problems?
fastboot oem gencheckpt - this command will take you to recovery from fastboot usb plug screen
@ Martin:
don't worry about pb99xxx.xxx check everyphone does that approx. for 10 sec.
what recovery you have?
@ Jerome: post hboot version
@Both:
Tried different Roms? (it could be coincident as both of you running the same ROM)
best thing will be revert to stock via 2.29 RUU matching your phone (or WWE with goldcard) and test buttons

Hi, I'm on clockworkmod v2.5.0.7 - couldn't tell you the exact version but it's quite recent. I've got a back-up of my sd card from about a week ago when I was using Mildwild before switching to Nick's phone.
Have copied my back-up to a spare sd card (that PB99IMG.zip file was still on there) and that let me get to recovery - the vol and power buttons started working.
I wiped everything on the phone, flashed mildwild and rebooted - but straight back to unresponsive fastboot and HBOOT is unresponsive too. I thought I was making progress!

Tried to flash 2.3.3 RUU??

Martin Quinn said:
Hi there,
More info: the message that flashes up is:
SD Checking ...
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading...[PB99IMG.zip]
No image!
Loading...[PB99IMG.nbh]
No image or wrong image!
I tried putting a new PB99IMG.zip on a fresh sd card and starting HBOOT with that - it flashes but then I'm still stuck at the HBOOT screen with no norking buttons/way to select anything. Suppose I need the other .zip and .nbh files.
Click to expand...
Click to collapse
Hi Martin,
First of all, the flashing up message and the searching for those files is normal. It scans the root of the sdcard for those filenames and flashes them if found. I remember I once flashed something in this way, but no idea why and what I do remember you need both the zip and corresponding nbh file. Do you think it's possible that your keys are physically broken?
Maybe you can flash recovery files using fastboot but I don't know if that'll help. Do you have fastboot via command line, or in your case terminal working? You might wanna check this out, don't know if it helps: http://wiki.cyanogenmod.com/wiki/Fastboot
Also, trying a RUU flash might be a good idea too, they're links to them in one of the stickies.
EDIT: More on the scanning for zip and nbh files: http://forum.xda-developers.com/showthread.php?t=880268

Thanks everyone for all your help - I've been doing a lot of reading up!
I got the 2.3.3 RUU and extracted the rom, renamed it and flashed the zip file hia HBOOT (it would not work via windows, probably because my phone could not get past HBOOT) however, I got:
Main Version is older!
Update fail
then vol +/- to reboot (the vol buttons work for this)
I think my next port of call will be making a goldcard - would this allow me to 'update' to an older version of android?
Thanks,
Martin
So I don't think I can make goldcard from my device because I can't get a CID code out of it. However, I should be able to make one using my friend's Desire - hopefully this will work and I can downgrade to 2.3.3 - should be able to get my hands on that midweek so I'll keep you posted.
At least I'm reasonably confident that this will work (with a goldcard) because the phone appears to be capable of flashing PB99IMGs (as it at least tried to flash 2.3.3 but couldn't because it was an older version than that currently on the phone).
Fingers crossed!

Goldcard bypasses the Carrier ID check, which usually gets done when one flashes RUU.
If the RUU you want to flash is not older than your phones original state, you should be able to install nearly every RUU.
Sent from my HTC Desire using XDA

update
SO,
I got hold of my friend's working desire (running cyanogenmod) and booted it with a blank sd card in it. When I put this blank sd card into my desire, it booted up (although the back/search button still did not work). I could also reboot into clockworkmod recovery. However, when I then rebooted the device......... straight back to unresponsive fastboot.
However, I've set up the android sdk on my laptop and fastboot recognises my device, so at least I might be able to do something with it tomorrow when I'm less tired!
So, this means that the rom is OK, and recovery is on there. I think my first point of call might be reflashing hboot....
It has also just occurred to me that the back button might be stuck 'on' (ie always pressed) - this would explain why my phone always boots straight into fastboot when you press the power button.
UPDATE - yes, I can recreate my phone's problems on my friends' phone just by holding down the back button and keeping it pressed ie it boots into fastboot by default (with volume buttons unresponsive until i let go of the back button), and I can get it to boot into hboot by also holding vol- and back when powering on, and the vol buttons are then similarly unresponsive while the back button is down. I think I need to look into this!
-------------------------------------------------------------------------------------------------
Right. So I took my phone apart using the guide at tjworld.net -blog -htc-desire-tear-down [if that's helpful for anyone - I can't post outside urls yet!]
and gave the buttons a good clean with Switch Cleaner from Maplins. Put it back together and it was the same.
So I went to fastboot, and fastboot reboot boots the phone perfectly (although the back/search buttons are still unresponsive).
I think that pretty much means the software is fine and I need to replace the buttons, so I've ordered some from ebay ('Genuine 4 Htc Desire G7 Keypad Membrane Flex Trackpad Bravo A8181 Keypad Uk' from Onlinemarket, £15).
Will give this a try when they turn up. In case I'm wrong, could there be any software problem causing this? I can flash a new hboot, recovery and ROM using fastboot so I should pretty much be able to replace all the software on the phone, right?
Cheers
more updates as they come in!

SOLVED
Replaced the button assembly and the phone boots as normal.
The trackpad doesn't work so I've ordered a new one of those too (only ~£5) - guess the whole lot got fried. I can live without a trackpad for a while though!

Stuck in WFS Recovery (White HTC Logo)

It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
I also found that I can't boot when I connect powered off phone to my pc. I have to take off my batery.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.
UPDATE!
I took the original recovery img from http://forum.xda-developers.com/showthread.php?t=1426611 and flashed it. All went well. I did a restart (after doing this I was able to boot power my device while connected to pc) and had another try with CMR recovery, but it didn't work. I also I tried http://forum.xda-developers.com/showthread.php?t=1406321 recovery img, but it didn't help, I still can't get into.

How to root Wildfire S S-OFF the easy way
First download this
Put it in your memory card
then press and hold voldown+Power
It will load the bootloader follow the instructions on the screen and update accordingly
Then Turn off
Remove that PG76IMG from sdcard
After that download this and put in your memorycard and update same way, it will flash the CMR5.0.2.8 (after flashing dont forget to remove this PG76IMG from sdcard as well).
Now download this put it in your mmc and flash this from recovery.
Done.. U have successfully rooted Ur S-OFF device Now In CWM do factory reset install new custom rom according to the way devs say. I can assure U that this process will even remove Ur white screen

im stuck too on the recovery s-on btw and bootloader unlocked

ME TOO
but i m s-on

Same problem here, unlock by htc-dev worked. Recovery flashed but device stays stuck on the HTC logo. So my daughter's phone is unlocked but that's it.

Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.

Let me know
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
I dont understand. If ur splash screen changed means u have installed cwm. Just select recovery and install a rom. Like this one
Download the rom. Put in ur sdcard.
remove battery
press vol down+power
press vol down
press power to select recovery
In recovery to move press vol up/down, to select press power
Wipe data/factory reset
Wipe cache partition
Advanced>> Wipe Dalvik cache then also wipe battery stats
Go back
Install zip from sdcard
Select the romname.zip put in sdcard
that should be it instructions are also found in that rom. thread so simple!!

7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
Here is a flash file you can try since you are S-Off. It should flash the default splash image, CWM 5.0.2.8, hboot 1.03 and re-calibrate the touch panel.
Hope it works for you.

Deleted

Problems persist
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?

Return back to Normal after BOOT-LOOP !
muckz said:
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Click to expand...
Click to collapse
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......

Senthamil said:
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Click to expand...
Click to collapse
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html

For those who want more info, here's another thread:
http://forum.xda-developers.com/showthread.php?t=1725398
It appears that the latest Wildfire S has a slightly different firmware, possibly for the video chip, which causes the CWM Recovery not to work. Perhaps there'll be a fix released eventually, but for now you can follow the thread above for some possible workarounds and more info.

Try mg all in one tool. Here: http://forum.xda-developers.com/showthread.php?t=1697985
It should sort out you guys problems.

muckz said:
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
Click to expand...
Click to collapse
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:

7axew3ku said:
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
Click to expand...
Click to collapse
It appears that CWM 5.0.2.8 actually works, but it doesn't provide any output to the screen. With ROM Manager, you can automate starting into CWM Recovery and installing a custom ROM, so it doesn't matter if the screen is blank.

Stuck - can't get pass the htc logo screen

Hello guys,
I'm newbie here. I'm not a tech guy, to be honest. My problem is that I'm stuck on the HTC Logo Screen. My phone is HTC One M8 Eye.
So this morning, I was trying to root my phone. I unlocked my phone already ( now my phone said "Software Status: Modified" and "***Unlocked***" ). Everything was good until I was installing SuperSU.zip file. It didn't work. So I tried to search for a newer version of SuperSU, I think it's 2.56 or 2.76. I copied that to my phone, trying to install via TWRP 2.7.0.2. Everything was good, I though. It said "successful" and "all done". But when it rebooted, it got stuck on HTC Logo Screen.
I tried to turn it back on and off by holding the lock botton, volume up and volume botton at the same time. Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
Now the problem is that I can get into the recovery screen with options like fastboot, hboot, but I don't have access to my internal storage anymore. And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
I'm pretty sure I messed up...A LOT.
Please, if anyone knows how to solve this, help me? I'm like, here, begging you since this phone is really important to me.
Thank you in advance.

1. Your main mistake is using an outdated tool
2. Bigger mistake you used tool meant for M8 not M8 eye (they are different device)
3. Biggest mistake you used an outdated TWRP and not meant to be used on M8 eye.
You can try :
1. Install correct TWRP for M8 eye - http://forum.xda-developers.com/showpost.php?p=62030698&postcount=144
2. Install SuperSU 2.76
and see your device will boot or not.
If not, you need to restore nandroid backup or RUU

khanhnn said:
I'm freaked out from this point and tried to relock my phone via the toolkit by Hasoon. Then I also returned my phone to S-on.
And I'm stuck with HTC Logo Screen. The closest time was that it said "HTC One tm" but not "HTC". Then nothing happens next.
Click to expand...
Click to collapse
This is exactly what is supposed to happen when you relock the bootloader, it renders the phone unable to boot into OS. This should never be done, unless you are going to flash an RUU.
Along with the other mistakes already pointed out, it seems you are trying things without properly understanding what the result will be, and without researching properly beforehand.
Also, you say you went back to s-on, but were you ever actually s-off? The only working s-off method is sunshine, which requires root. Therefore, I don't see how the phone could have been s-off (unless you received it that way) and it doesn't actually make sense when you say you returned to s-off.
---------- Post added at 10:21 AM ---------- Previous post was at 10:19 AM ----------
khanhnn said:
Then I tried to force it to go into the fastboot mode ( I don't know what to do call that ) where it showed me some options like fastboot, hboot, recovery and stuffs...I'm freaked out from this point
Click to expand...
Click to collapse
That is called the bootloader screen. You were trying to get into fastboot mode, and you got the bootloader screen, which then allow you to select fastboot (use vol keys to move between options, power button to confirm, if fastboot is not already selected) so I don't see what the issue is here?

Hello,
Thank you for your reply. I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Can you help me please?
Thank you very much!

khanhnn said:
I successfully installed the TWRP version you mentioned. But I don't know how to push the supersu zip file into my phone now since I don't have access to the internal storage.
Click to expand...
Click to collapse
Boot into TWRP, and your phone's internal storage should show up if you connect to your PC.

Hello redpoint73,
Thank you for your help.
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
I guess I'm somehow closer to finishing fixing my phone ( or I hope so since this is really important to me ).
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
What should I do now?
Thank you again.

khanhnn said:
But I'm now stuck in a new problem. I'm stuck at the bootloader screen.
Click to expand...
Click to collapse
I can't tell from the (lack of) information provided, what you have done to this point.
You said you installed TWRP 3.0? Were you ever able to boot into TWRP (or it just went to bootloader)?
If you were able to boot TWRP, were you able to use it access internal storage, as I suggested? Then what happened next?
khanhnn said:
I tried to install ROM ( which I downloaded from the HTC website I think ) but it didn't work out well. It said it was about to reboot but when it did, it returned to the bootloader screen. I tried to reboot a 2 times already but it always returned to the same screen.
Click to expand...
Click to collapse
What you downloaded is likely an RUU (ROM Update Utility) not just a ROM, there are distinct and critical differences, and you should take care not the mix up the terminology.
What is the (full and exact) file name of the RUU? You need to make sure its the right one for your device, before proceeding. And to make sure which path you want to take: TWRP to flash SuperSU or restore stock backup, or RUU. As the process is very different for each. RUU required you relocking the bootloader, which in turn prevents the installation of TWRP. So you need to be sure of which way you want to proceed the path forward, otherwise you will be wasting time going around in circles.
Also, you should do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see more info about the phone; in order to proceed properly.

Dear redpoint73,
Thank you for all the help you have provided until now.
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
I think I downloaded both the RUU and the ROM.
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. However, I encountered the error 171 although I downloaded the HTC One Drivers already ( which is HTC Sync ). I couldn't get through this error so I gave up and tried something with the ROM.
Case 2: WITH THE ROM:
So I downloaded the ROM first from someone in xda forum. I installed it via TWRP and it said "Successful" on the screen. It said that I just gotta tap "reboot". But when my phone rebooted, it went back the bootloader screen. I rebooted 2 more times and the results were still the same. So I searched for some ROMs from other sources and all the times, it said "Successful" on the screen. It just always went back to the bootloader screen however.
Anyway, this is my phone info ( I think ) from the command getvar all:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.213311711.15G
version-cpld: None
version-microp: None
version-main: 5.07.425.1
version-misc: PVT SHIP S-ON
serialno: REMOVED
imei: REMOVED
imei2: Not Support
meid: 00000000000000
product: mels_tuhl
platform: hTCBmsm8974
modelid: 0P6B90000
cidnum: HTC__059
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5c9466dd
hbootpreupdate: 11
gencheckpt: 0
I hope this works out well

Case 1 : wrong RUU for your device
Case 2 : wrong ROM for your device
Do you really read what I posted above ? Your device is M8 eye not M8.
Case 1 : there is no RUU available for M8 eye 5.07.425.1
Case 2 : there is almost no flashable ROM for M8 eye
Using M8 RUU you'll get error, using ROM meant for M8 it won't boot, you'll get stuck on bootloader
Until you can find 5.07.425.1 RUU or backup, temporarily fix your device by restoring 5.07.401.1 backup that you can find in my backup thread.

Thank you for all of your help guys!
All sorted and my phone is back, alive!
I really appreciate what you did for me!

khanhnn said:
Yes, I can get into the TWRP ( after I selected HBOOT, I selected RECOVERY and there I was, in the TWRP ). I can get to the internal storage but I'm not sure that is what you mentioned before. Which I can access is that I can select the zip file to install ( in the TWRP screen ) , nothing else I guesss. ( I asked yesterday that how could I access the internal storage because I wanted to copy the ROM file into my phone and install it in the TWRP )
Click to expand...
Click to collapse
When booted into TWRP, you can connect to PC, and the phone's internal storage (as well as SD, if you have one inserted) will show up as a drive on your PC, that you can freely drag and drop files, etc.
If not, go to the MOUNT button in TWRP; and check the "Data" box (and "Micro SDcard" if desired). But these should be checked by default (at least on the TWRP build I'm on).
khanhnn said:
Case 1: WITH THE RUU:
Everything was okay and I'm pretty sure that I downloaded the correct version ( the other two versions said that I had to use the correct one for my phone ). The file name was RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.
Click to expand...
Click to collapse
Not sure how you can be "pretty sure" this is the right RUU, and how you came to think it was. This is the RUU for the US AT&T version. Also, the RUU would need to match the version number in the RUU name (at least have "425" in the position x.xx.425.x as that number is the carrier version identifier).

sir same problem is with me,
i need correct ROM for htc one m8 eye,please help me ,
my email is
[email protected]

Help needed

Hey there all,
I'm kinda new here and have a problem i can't figure out.
Tried to manually install the android 7 image and it went totally wrong, due to my own stupidity:angel:.
Following things:
-Kernel: Lk
-Product: htc_himauhl
-version: 1.0
-version-main: 3.35.401.32
-MID: 0PJA10000
-CID: HTC__031
The bootloaders is unlocked but it have S-on, also I have installed the TWRP. As i said, I don't know what went wrong but now my phone gets stuck in the white bootscreen with te red text: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action." And also, when i want to reboot from TWRP, the message comes up: "No OS installed, are you sure?".
Anyone who can help me? I want my phone back.
Cheers!

"stuck in the white bootscreen with the red text"
onlogisch said:
Hey there all,
I'm kinda new here and have a problem i can't figure out.
Tried to manually install the android 7 image and it went totally wrong, due to my own stupidity:angel:.
Following things:
-Kernel: Lk
-Product: htc_himauhl
-version: 1.0
-version-main: 3.35.401.32
-MID: 0PJA10000
-CID: HTC__031
The bootloaders is unlocked but it have S-on, also I have installed the TWRP. As i said, I don't know what went wrong but now my phone gets stuck in the white bootscreen with te red text: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action." And also, when i want to reboot from TWRP, the message comes up: "No OS installed, are you sure?".
Anyone who can help me? I want my phone back.
Cheers!
Click to expand...
Click to collapse
Hi,
First of all:
Important is that you choose the right Rom Version for your device!!! There are locked and unlocked versions
Your version must be the Unlocked/Developer Version (European Version)
VERY IMPORTANT:
To install Android 7 Nougat you must have installed the latest Marshmallow Version 3.35.617.31 -> To find here under http://www.htc.com/us/support/rom-downloads.html -> choose under Unlocked/Developer this: HTC One M9 3.35.617.31
To get your device going again with Android 6 Marshmallow do the following:
no, you are not stuck, you just erased your OS and that`s why you wil over and over end up on the "the white bootscreen with the red text".
I assume TWRP is still on your device. If not, install the latest version from here: https://dl.twrp.me/hima/
What you have to do:
Download the custom rom of your choice if you haven`t already. (I would recommend "ViperOneM9 5.3.0" from here: http://venomroms.com/htc-one-m9/ )
Put the custom rom (as Zip file) on your external SD card
Boot your device into recovery mode.
Once booted in recovery (i assume you booted TWRP) normal procedure execution:
Hit the Install button
Hit the Select Storage button and choose SD-Card (external SD-Card) and the OK button
Hit the button right next to the Select Storage button once till you read Install Zip on this button
Find and select the OS Zip file you just put on your SD-Card
Swipe to install
You are good to go now.
If you`ve created a backup via TWRP just hit the Restore button, select Package to Restore and swipe right on the bottom
Also read: http://venomroms.com/ruu/

Ok thnx. Gonna try it later tonight. Still have one more question: Does it matter that my phone is s-on?

Okay, so I've tried about evreything. Got a custom ROM up and going while having twrp installed. Now can someone tell me how to go back to original factory ROM, because I'm getting a little frustrated here. Nothing seems to work or I'm not doing it alright. Still need help here.
Thnx

HTC one M8 Bricked in a confusing way...

(downloads were from this guide: https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727)
I was trying to unlock/root the phone through the official way, I successfully unlocked it and installed TWRP 2.8.5.0 and booted the device, everything is working fine so I decided to flash the SU. I booted to the recovery but the UI was flashing, I assumed it was just a visual bug and went on, flashed the zip and afterward every click was lagging. I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader and all the options in it like the fastboot and recovery which is still laggy and has a flashing UI (I made a backup to check if it's working). I considered loading a different ROM on an SD and try to flash it and see if that fixes it but I can't risk this getting worse.
any ideas what to do in the situation? I've been doing this since the GNexus so no need for an ELI5
what Info I currently know:
bootloader info:
software: official
M8_UL PVT SHIP S-Off (was already that I didn't unlock it )
HBOOT 3.19.0.000
OS 6.12.401.4
openDSP 51.2.2-00593-m8974_f0.1015
CID-HTC__A07
Dec 17 2015,14:15:48.90021118
fastboot info:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 6.12.401.4
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__A07
stock HTC Android Rom last Marshmallow update
TWRP 2.8.5.0

That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82

ckpv5 said:
That's is not stock lollipop, that's the latest stock Marshmallow.
TWRP 2.8.5.0 won't properly work on it. You need TWRP 3.x.x.x and make sure to install SuperSU 2.79 the lowest version or use the current one 2.81 or 2.82
Click to expand...
Click to collapse
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?

Abd121 said:
sorry I meant Andriod 6, 'Lollipop' was a mistype (names are changing too fast recently)
I borrowed an SD card and loaded an SU removal script on it and installed the one TWRP had in it, will see if I boots, currently it's displaying the red DEV text in addition to the HTC logo instead of only the logo
if It booted; I should flash a newer TWRP then I clear right?
Click to expand...
Click to collapse
The TWRP version 2.8.5 is really old (over 2 years) and sure to cause problem. Just flash the TWRP version as directed by ckpv5, that guy knows what he is talking about.
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
Abd121 said:
I tried to reboot but now It's stuck on the HTC logo, it doesn't go anywhere, I can't even hold the power to shut it down (Had to freeze it to empty the battery) while it's off I can go to the bootloader
Click to expand...
Click to collapse
To force a reboot, hold vol up + power, may need to hold the buttons for a minute or so in the "stuck condition". Once the screen goes black to reboot, let go of the buttons, and only hold vol down, and don't let go until you see the bootloader screen. If this fails to work (just reboots to HTC logo screen), you just got the timing wrong; either started pressing vol down too late, or let go too early. Just repeat the process, until you get the timing right.