Develop Bugs

[Q] phone stuck on htc this build is for development purposes screen

Hi...I have read a lot of threads about this problem and none of them have helped. My issue currently is this "this build is for..." screen will not go away. I have tried down and power, up and power, power by itself and the phone will not do anything. My pc no longer recognizes the phone as connected.
Some history, I successfully unlocked the htc bootloader, using their steps. I have a stock htc one v gsm.
My plan was to install openrecovery-twrp-2.6.3.3-m7.img. I am following custom recovery insructions from here http://forum.xda-developers.com/showthread.php?t=2265618.
The screen on my phone appeared after running the fastboot boot twrp.img command (I renamed the above .img file to a shorter name).
Can you help me?

I was able to get past this screen. I removed my protective cover, removed the sim card/sd card cover, held down button and power button for much longer than normal, maybe 10 seconds and the phone rebooted. I was able to get back to the hboot screen after another power off and down button and power combination.

SOLVED
After more reading, I found I was using the wrong recovery image. I downloaded this one techerrata browse twrp2 primou and it installed without errors. I then powered off the phone, held down button and power button, got to hboot, selected recovery, pressed power button, got that same htc warning, however it only stayed on the screen about three seconds and then TWRP loaded.

Thank you for coming back to say what fixed it. So many people don't.
Remember, if your phone is S-on, to flash the right kernel for your ROM (if you go custom) from your PC
Sent from my Moto G

You're welcome and Thanks for tip mrcorey!

Glad you found a resolution to your problem. We need to pay more attention to these questions,this issue probably could have been resolved much faster. At least for my part I will check the forums Q&A daily from now on.

Did I ruin my phone?

Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?

What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...

mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app

Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.

Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.

mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.

santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.

mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.

santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.

mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.

Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?

mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app

Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?

adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?

synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.

[Q] Total disaster, HOX in bootloop and can't access bootloader or recovery....URGENT

I have htc One x, and i dont know which version it is, no details at all about anything regarding it. My brother got it from someone and screwed up in flashing.
Now its stuck on white HTC quietly brilliant screen, I have tried repeatedly to boot into fastboot or bootloader and nothing works.
It charges properly when its switched off with red led lighting up but after that nothing
I have searched innumerable threads but they all metnion to go into bootloader mode, but my phone doesnt even go there
Please anyone can help me out?
I can pay as well for the services

visheshsahlot said:
I have htc One x, and i dont know which version it is, no details at all about anything regarding it. My brother got it from someone and screwed up in flashing.
Now its stuck on white HTC quietly brilliant screen, I have tried repeatedly to boot into fastboot or bootloader and nothing works.
It charges properly when its switched off with red led lighting up but after that nothing
I have searched innumerable threads but they all metnion to go into bootloader mode, but my phone doesnt even go there
Please anyone can help me out?
I can pay as well for the services
Click to expand...
Click to collapse
No need to pay first try to hold the volume down button and then hold power button untill you go in bootloader after this connect the phone to a computer if your battery is empty the best way is to connect battery pack on the back side pins and try then go in bootloader but if your battery iss complete dead no solution you must to charge ytour phone but this can be done from bootloader with the bat file
EDIT: Next time when you are in trouble ask before discharge the phone

Have you flashed boot.img?
E: se this too
http://forum.xda-developers.com/showthread.php?p=26192390

Hi disaster Again
the above problem i mentioned was solved, i could get my laptop to recognise the phone in ADB and i just had to enter the command adb reboot bootloader.
but now i have even bigger problem. i was running ARHD and everything was going fine unless i decided to upgrade to miui based on 4.4.4
so i went into fastboot by typing adb reboot bootloader and then flashed the boot.img of miui rom, then i pressed power down in fastboot thinking i'll connect and then go into recovery and then flash the zip of the rom
but now i cant get into either recovery or fastboot(bootloader) and neither my phone is recognised in adb.
please guys help me out.

Have you read this and followed all steps exactly?
Can you enter bootloader holding vol down and power button?
Do you have recovery on device?

See i cannot go into bootloader or recovery anyhow, yes i had recovery on my device by which i flashed the ARHD
i Flashed the boot image for the MIUI bases on 4.4.4 but now it doesnt boot up, neither i can nacces bootloader nor it is recognised by ADB

c.e.z said:
Have you read this and followed all steps exactly?
Can you enter bootloader holding vol down and power button?
Do you have recovery on device?
Click to expand...
Click to collapse
Please anyone, please help me out
I think I have totally killed my phone, my parents wont give me a new one in any case.
so anyone please by my saviour

I have a backup of my ARHD rom through CWM internal storage as well, just wanted to inform so that you can all help me just save this device

visheshsahlot said:
I have a backup of my ARHD rom through CWM internal storage as well, just wanted to inform so that you can all help me just save this device
Click to expand...
Click to collapse
if you can't go in bootloader or recovery nobody can't help you. Try on diferent computer with win7 32bit

Phone stuck in reboot loop

Hello,
I installed a custom ROM (ViperOneM8+4.6.1) on my M8, which is the international edition M8QL_UL.
I now suspect this ROM is not compatible, as the phone is stuck in a reboot loop - the white screen with the red text at the bottom appears, and then about 35 seconds later the screen goes blank and it restarts.
I've tried holding the power button down to try and turn it off, but it won't stop restarting.
I've tried holding the volume down + power buttons to enter recovery and it doesn't work.
Adb and fastboot don't work either - the phone isn't on long enough to appear on my PC.
Please let me know if there's anything I can do at this point?
Cheers.

jmh55 said:
Hello,
I installed a custom ROM (ViperOneM8+4.6.1) on my M8,
Click to expand...
Click to collapse
Your device is not a M8 but a different device called M8s ....
Read this thread and get help there if you need to.
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245

ckpv5 said:
Your device is not a M8 but a different device called M8s ....
Read this thread and get help there if you need to.
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
Click to expand...
Click to collapse
Oh dear, I think this is the issue. The ROM I used was for the M8, not the M8s.
Thanks, I'll try posting in that thread.

jmh55 said:
I've tried holding the volume down + power buttons to enter recovery and it doesn't work.
Click to expand...
Click to collapse
There is no button combo that boots into recovery for this device. I believe you mean the button combo to enter bootloader. Folks will often call this recovery, but bootloader and recovery are 2 completely different things (and this is an important distinction), and folks need to stop thinking they are the same.
Since the phone is bootlooping, just hold the vol down button during the next "loop" and you will enter bootloader.
Once in bootloader, then you can select to boot into custom recovery. Then restore your stock nandroid, if you made one before flashing the custom ROM (and you should always make a nandroid of the stock ROM before flashing a custom ROM).
If you didn't make a stock nandroid, you'll need to use RUU or find a stock nandroid that matches your firmware number.
jmh55 said:
Adb and fastboot don't work either - the phone isn't on long enough to appear on my PC.
Click to expand...
Click to collapse
Fastboot only works in bootloader-fastboot mode; adb only works in OS or recovery. So neither is ever going to work while in a bootloop. Get into bootloader as I've described above (and select fastboot); and you should at least be able to use fastboot.

redpoint73 said:
There is no button combo that boots into recovery for this device. I believe you mean the button combo to enter bootloader. Folks will often call this recovery, but bootloader and recovery are 2 completely different things (and this is an important distinction), and folks need to stop thinking they are the same.
Since the phone is bootlooping, just hold the vol down button during the next "loop" and you will enter bootloader.
Once in bootloader, then you can select to boot into custom recovery. Then restore your stock nandroid, if you made one before flashing the custom ROM (and you should always make a nandroid of the stock ROM before flashing a custom ROM).
If you didn't make a stock nandroid, you'll need to use RUU or find a stock nandroid that matches your firmware number.
Fastboot only works in bootloader-fastboot mode; adb only works in OS or recovery. So neither is ever going to work while in a bootloop. Get into bootloader as I've described above (and select fastboot); and you should at least be able to use fastboot.
Click to expand...
Click to collapse
Thanks for the suggestions and advice - I've got the Pandora Rom back on it now and won't be fiddling anymore I think.
I actually managed to get it sorted by holding vol-up and power for a good 15 seconds based on advice from the M8s thread, just in case any one has the same problem and vol-down doesn't solve it: http://forum.xda-developers.com/showpost.php?p=63177320&postcount=658
Thanks again everyone, I'm been amazed by how helpful people on this forum are.

jmh55 said:
I actually managed to get it sorted by holding vol-up and power for a good 15 seconds based on advice from the M8s thread, just in case any one has the same problem and vol-down doesn't solve it: http://forum.xda-developers.com/showpost.php?p=63177320&postcount=658
Click to expand...
Click to collapse
Power+vol up reboots the phone. You stated the phone was already in a bootloop, which means it was already rebooting over and over.
Vol down (just vol down, no need to hold power button) during any reboot will put you into bootloader. If it doesn't, its because you didn't hold vol down long enough.

Stock Boot-Loop, out of options!

I was at work the night before, and my capacitive buttons stopped responding, so I went for a restart in hopes they would kick back on, this just caused my phone to enter a boot loop. Soft resetting and hard resetting both continue the loop, trying to enter recovery mode throws me back into the loop, entering download mode locks the phone on the small HTC screen. I tried to flash the current RUU onto the phone, but it won't proceed with the install due to a low main battery error despite the fact I've had it charging for 6 hours. The only thing I can think of doing now is sending it back in hopes they fix it, but theres a lot of information I ignorantly haven't backed up, and now can't access before sending it back.
If anyone has any helpful tips or ways to move forward I would be grateful.

you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though

silegeek said:
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
Click to expand...
Click to collapse
Doing what you said flashes the grey HTC logo, but then goes back to looping.

Snickie12 said:
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Click to expand...
Click to collapse
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.

silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
Holding Volume up just continued the loop, I can get into the bootloader like you said, but theres not very many options, download locks the phone onto the HTC logo and doesn't proceed, the recovery option just restarts the phone into the loop.

Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU

silegeek said:
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
Click to expand...
Click to collapse
Whenever I plug it in while off, it shows the low battery icon and tries to turn itself on.

I had exactly the same problem...were you able to sort it out?

same problem except I can charge mine will I be able to ruu even if it is locked ?

isaac1993 said:
same problem except I can charge mine will I be able to ruu even if it is locked ?
Click to expand...
Click to collapse
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.

Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
No,it's not. I'm bl ul,s-off,and I can ruu anytime.

Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
I thought it was charging but now fount out it wont charge

isaac1993 said:
I thought it was charging but now fount out it wont charge
Click to expand...
Click to collapse
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.

singlemalt said:
I had exactly the same problem...were you able to sort it out?
Click to expand...
Click to collapse
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.

Snickie12 said:
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Click to expand...
Click to collapse
Did they tell you what they did to fix it by chance? Thanks.

singlemalt said:
Did they tell you what they did to fix it by chance? Thanks.
Click to expand...
Click to collapse
No they didn't sorry.

singlemalt said:
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
Click to expand...
Click to collapse
My friends s7 completly bricked doing the N update. If you havnt done anything to your phone just take it back and get a new one.

Same exact issue here after the Verizon OTA update.
Failed after the first reboot after the update.
The storage was pretty maxed, wonder if that has something to do with it.

silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
I have very similar htc 10 issue : (
https://www.reddit.com/r/HTC10/comments/9j8nyk/htc_10_oreo_stuck_in_boot_loop_i_can_only_access/
how do you do fastboot commands when only at bootloader screen when you cant access download mode or recovery : ( also my htc 10 was low on stoage space I must have corrupted the htc 10 oreo : (