Develop Bugs

Unable to boot into fastboot for custom boot image

I apologize in advance if this a repeat post, I couldn't find any answers and only found one similar thread to this that was still not exactly my problem.
I have an unrevoked evo running 2.2 and I know at one point I was able to fastboot (it's been awhile since I've done anything). While trying tonight to flash a custom boot image, it simply vibrated 3 times and stayed black. The charging light (as it was connected to USB) turned off and my phone wouldn't turn back on normally until I took the battery out and put it back in. I tried this repeatedly with/without USB debugging on, without USB being plugged in and got the same response every time - 3 vibrations, black screen, and inability to turn back on until the battery is removed. When I press vol down + power though I am able to boot into recovery mode just fine. Vol up + power fastboot seems to be my only problem.
Any ideas as to why I can't fastboot but I can access recovery mode?
Thanks!

Volume up and power was removed with the froyo update. Just use vol down and power to get to bootloader and from there select fastboot. What boot.img are you trying to flash exactly? It sounds like you may be doing something wrong with flashing though fastboot or soething. Unless you are trying to use eng commands?

dkdude36 said:
Volume up and power was removed with the froyo update. Just use vol down and power to get to bootloader and from there select fastboot. What boot.img are you trying to flash exactly? It sounds like you may be doing something wrong with flashing though fastboot or soething. Unless you are trying to use eng commands?
Click to expand...
Click to collapse
LOL well I feel dumb. Didn't know this was changed. While that did help me get into fastboot now I'm getting an error "FAILED: remote not allowed" but that's another problem that I do see a few threads on so I guess this can be closed.
Thanks!

[Q] Always boots to fastboot?

I had CM7, S-OFF, CM7 r2 HBOOT I was at home, didn't touch pfone all night, and in the morning, after a call, back key stoped working. I tryed to restart phone, and it went to fastboot. I figured back button was stuck and i pushed back button so it maybe start working, but it didn't. It would always boot to fastboot, and volume keys are not working.
So, i disasembled the phone, took the buttons board out, and it still booted to fastboot.
Then i managed to turn the phone on, via CMD, using command fastboot reboot, and from menu, i rebooted to recovery, made backup and flashed CM7 again.
That didn't work.
In recovery, i tryed key test, back and search button were not working.
I returned everything to stock, still nothing.
I can only start the phone via fastboot reboot...
Help please...

Certainly sounds like back button is stuck down. Did you void your warranty by taking it apart or was it already void?
Sent from my HTC Desire using Tapatalk

No i don't have a warranty...
But i don't understand, if it is stuck, why does it start in fastboot, when i remove the button board...

It's stuck somewhere. To get to fastboot you have to hold back and press power...
Has the phone been wet recently?
Sent from my HTC Desire using Tapatalk

Maybe from tho cold, or moisture...Because of very low temps here, there was a lot of snow, and the phone was in the room with moisture...?

Wouldn't expect that to be enough. Maybe prudent to get a phone shop to look over it...
Sent from my HTC Desire using Tapatalk

That is my last solution...

try
Code:
fastboot oem boot
worked for me while holding back
if you don't have fastboot setup then unzip the file into c:\ and use the following
Code:
cd\
fastboot oem boot

What can i manage with that command?
I have fastboot, and with that command, i can start the phone, but i can do it also with fastboot reboot.
And when i restart the phone it goes to do fastboot, volume keys are not working...

Moca87 said:
What can i manage with that command?
I have fastboot, and with that command, i can start the phone, but i can do it also with fastboot reboot.
And when i restart the phone it goes to do fastboot, volume keys are not working...
Click to expand...
Click to collapse
Exactly.. you can turn on the phone, I thought this was your ultimate goal to do, doesn't fix anything.. just telling you that you can get it started that way.
Have you tried putting it in a bag of rice yet? if it is water damage it might help.

No, i haven't tried that. I put it on radiator, that's not very worm, and it's working, but it's not ok.
It can turn on normaly, but sometimes it's like, back button is pressed continuously and sometimes same thing happen with search button...

[Q] One x touch screen fail

Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.

bump

thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?

Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.

thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2

following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked

thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?

davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?

thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .

ah nice works, thanks. stay with me in case i get stuck again.

thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.

more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.

Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode

Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle

thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?

davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more

Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights

Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.

thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions

finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.

[Q] I can't access Bootloader or Recovery PLEASE Help!

My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!

SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:

BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.

SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.

BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.

sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..

Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)

wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.

SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:

BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.

Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.

Bricked Nexus 5x, bootloop, bootloader locked

Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?

hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...

here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip

I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.

ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!

it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0

I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me

Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.

if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.

I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?

Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.

Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...

Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!

I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!

Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!

No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.

Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.

If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.

bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).

balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?