Develop Bugs

[Q] Halfway through rooting, recovery failure flash; boots but inconsistent charging

Environment: OS X 10.7.3; started with stock KF 6.3.1. Added 0x1949 key to ~/.android/adb_usb.ini, confirmed adb working with adb logcat. Plan was to root stock ROM first, get comfortable with the KF's behavior in that state, then eventually get over to CM9, as my Droid Incredible runs CM7 quite beautifully.
Started with procedure at http://forum.xda-developers.com/showthread.php?p=24129239 . Pushed fbmode successfully, chmodded and ran it, adb reboot successful. Continued with the following
Code:
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash bootloader u-boot-firefirefire-1.2/u-boot.bin
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)...
...and everything stopped. Waited there for about 10 minutes before giving up. Eventually powered down by holding power button and then pushed it again to start up; got yellow firefirefire triangle. That screen suggested pushing power to go into recovery; no dice.
I thrashed a little with fastboot oem idme bootmode commands until I got it to successfully reboot. Current boot sequence displays firefirefire triangle for a few seconds, then goes to the 'kindle fire' logo screen, then boots to working stock OS. The first time this happened and several reboot cycles thereafter, it would not charge via stock charger or Mac USB and LED would not light; after another few reboot cycles, it suddenly decided to charge with stock charger and LED lit orange. I'm not inclined to experiment any more until I get (a) some knowledge and (b) better than 36% charge. ;-)
I assume I've got a borked recovery. Question is how to fix and continue on my happy rooting way. Help much appreciated.

VT_hawkeye said:
Environment: OS X 10.7.3; started with stock KF 6.3.1. Added 0x1949 key to ~/.android/adb_usb.ini, confirmed adb working with adb logcat. Plan was to root stock ROM first, get comfortable with the KF's behavior in that state, then eventually get over to CM9, as my Droid Incredible runs CM7 quite beautifully.
Started with procedure at http://forum.xda-developers.com/showthread.php?p=24129239 . Pushed fbmode successfully, chmodded and ran it, adb reboot successful. Continued with the following
Code:
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash bootloader u-boot-firefirefire-1.2/u-boot.bin
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
[email protected]:~/development/android/kindleroot$ fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)...
...and everything stopped. Waited there for about 10 minutes before giving up. Eventually powered down by holding power button and then pushed it again to start up; got yellow firefirefire triangle. That screen suggested pushing power to go into recovery; no dice.
I thrashed a little with fastboot oem idme bootmode commands until I got it to successfully reboot. Current boot sequence displays firefirefire triangle for a few seconds, then goes to the 'kindle fire' logo screen, then boots to working stock OS. The first time this happened and several reboot cycles thereafter, it would not charge via stock charger or Mac USB and LED would not light; after another few reboot cycles, it suddenly decided to charge with stock charger and LED lit orange. I'm not inclined to experiment any more until I get (a) some knowledge and (b) better than 36% charge. ;-)
I assume I've got a borked recovery. Question is how to fix and continue on my happy rooting way. Help much appreciated.
Click to expand...
Click to collapse
What a relief it is to see such a detailed description of someone's problem. Thank you.
When you turn the device on and see the yellow triangle, hold the power button until it turns orange and release. Does it boot into recovery?
I'm sorry if that sounds like a stupid question but you can never assume anything here.

soupmagnet said:
What a relief it is to see such a detailed description of someone's problem. Thank you.
When you turn the device on and see the yellow triangle, hold the power button until it turns orange and release. Does it boot into recovery?
I'm sorry if that sounds like a stupid question but you can never assume anything here.
Click to expand...
Click to collapse
No, good question, and thanks very much for the help. I tried that several times and was not able to even get the power LED to turn orange, which seemed odd to me. Should have put that in my initial post. Thinking about it, I may not have unplugged the USB cable during those cycles; perhaps that caused it not to respond to the power button.
So I just tried it again. Rebooted by issuing 'adb reboot' and, this time, unplugged as soon as screen went dark. At FFF triangle, held power button until LED went from green to orange. At this point, LED stayed orange and the backlight changed intensity two or three times while still on FFF graphics. The kf logo then came up briefly, then the KF rebooted entirely. On that boot cycle, I touched no buttons and it appeared to go normally (FFF triangle, then kf logo static, then kf logo with shimmering animation, then stock lockscreen). Charging from AC continues to work.

Download twrp 2.1 again and check the md5 before reinstalling with:
fastboot flash recovery /path/to/recovery.img
...and see if that gives you a better result.

soupmagnet said:
Download twrp 2.1 again and check the md5 before reinstalling with:
fastboot flash recovery /path/to/recovery.img
...and see if that gives you a better result.
Click to expand...
Click to collapse
Reinstall worked this time -- I issued the command immediately following adb reboot and it flashed successfully as soon as FFF started up. This time the 'fastboot oem idme bootmode 5002' command just yielded '...' though, and 'fastboot reboot' just yielded 'rebooting...'. It's as if the fastboot USB connection just dies for some reason if you don't keep feeding it data.
So I shut down with held power button, pushed power button to boot to FFF screen, held power button to orange LED, held my breath, and TWRP popped up. Steps after that all went perfectly, I Dropboxed Superuser.apk and Root Explorer over from my Inc after the reboot, and we're in business with hot hot root action.
Thanks very much for your help -- it's nice to have somebody who's seen all the weird failure modes around in case I bork something.

VT_hawkeye said:
Reinstall worked this time -- I issued the command immediately following adb reboot and it flashed successfully as soon as FFF started up. This time the 'fastboot oem idme bootmode 5002' command just yielded '...' though, and 'fastboot reboot' just yielded 'rebooting...'. It's as if the fastboot USB connection just dies for some reason if you don't keep feeding it data.
So I shut down with held power button, pushed power button to boot to FFF screen, held power button to orange LED, held my breath, and TWRP popped up. Steps after that all went perfectly, I Dropboxed Superuser.apk and Root Explorer over from my Inc after the reboot, and we're in business with hot hot root action.
Thanks very much for your help -- it's nice to have somebody who's seen all the weird failure modes around in case I bork something.
Click to expand...
Click to collapse
Yeah, after changing the bootmode in fastboot, "fastboot reboot" doesn't work.
I'm glad to see you worked it out though.

Used One X, boot loop then out of battery

Hi,
I really truly tried to resolve my issue (by searching etc.) and learned a lot along the way but I have the problem still.
I bought a used One X. The guy showed me Jelly Bean working on it. I didn't use it at the sale. After I got home I found it was stuck on the HTC start screen. I had to go and it wouldn't turn off so I left it for half a day.
Found the volume down and power trick and booted several times into recovery mode and clockwork. Eventually tried format SD in clockwork. I also found a factory reset or similar button somewhere (can't quite remember if it was in recovery or clockwork). I think it was then that I had no more clockwork. Got a loop into Fastboot, message at the top says "Relocked - Security Warning". Can't switch it off. It occasionally switches itself off doesn't respond to the power button, after a few minutes with a usb plug in it starts again. It turns itself off after 15-20 mins again. When in Fastboot all options just loop back to Fastboot although reboot bootloader takes more time and has more lights.
Eventually started using fastboot cmd. Got an unlock token to flash, received error Failed (remote: battery low). Continued to receive that error with whatever I tried.
Found forums on using wires on the battery to charge and cycling reboots without success. As far as I can tell you can't get to the battery of the one x and I don't get the HTC flash screen mentioned in the cycling solution anymore.
Can I charge this phone? Should I investigate taking it apart to access the battery? Will a phone shop be able to fix this problem by doing things I can't?
Thanks for your time.

Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274

ArmedandDangerous said:
Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274
Click to expand...
Click to collapse
Great! Thank you very much A&D. I downloaded and installed Android SDK, got the file and put it in the right folder, now I need to open a cmd window and type "adb ???? fastboot-battery-recharge.bat" in order to charge the phone. Can you help?
Thanks

Just extract the Fastboot-battery-recharge.bat and put it into your platform-tools folder inside your Android folder (assuming you have downloaded the SDK).
Now enter fastboot (power and Vol Down) and double click the .bat file and let it do it's work
Another source for you
http://forum.xda-developers.com/showthread.php?t=1840156

Great thanks, it's going. I didn't realise it was a batch file.
One problem is that my voltage is going down not up, happy to leave it for a while though. Started at 2877mV and now is 2858mV after about 50 cycles. You can see it going up sometimes and down others but overall is going down...
IMPORTANT: I figured out you need to use a short usb cable and avoid front panel and bracket usb slots

Weird. Your phone is still connected right? It should be charging but takes a long time. If all else fails, HTC is your only help ):

Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?

The battery is up after 30 mins to 2960mV so it does work overall.
fvanommen said:
Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?
Click to expand...
Click to collapse
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight

fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
Glad it's working! Gonna take many hours to get that charge up, but at least it's working xD

fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
From 1% to the required 3474mV was 12 hours of charging (about (8640 reboots :silly
Now i am on 3487mV but this is still not good enough.
I will let is charge for a little while hoping it will work again.

Solved - "FAILED - Remote (battery low)" error
fvanommen said:
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
Click to expand...
Click to collapse
Yep it's a common problem by the sounds and hopefully this thread will stand out as the one to use.
Basically if you receive a "FAILED - Remote (battery low)" error through fastboot you should use the command "fastboot getvar battery-voltage" and find out how far from the required 30% (how low the mV number is / highest mV the battery holds = [> or < 30%]), this will vary from phone to phone. If you are under the threshold and have the older boot loader you will not be able to charge your phone by leaving it plugged in and hoping. You are have 3 options:
1) If your phone has a removable battery you can the wiring from an extra usb cable in order to get charge or just put in a charged one - the One X cannot use this solution
2) If it is close to 30% you might be able to get enough charge by rebooting it 10 or 20 times (this is because for a portion of the boot up time the phone takes on charge). The report of this solution working involved the ph boot looping onto the HTC splash screen, my ph was looping into boot loader only.
3) If it is far enough off the correct mV, you can run a batch file (props to Laav) that loops 2) and reports battery voltage until you are satisfied. This requires a USB connection and you should use a short usb cable and avoid front panel or bracket slots (especially if you notice that the voltage doesn't always increase each reboot).
Once you get to 30% you are able to flash imgs using fastboot and I would recommend (as Laav does) flashing the newer Clockwork Recovery which allows you to charge the phone while in recovery mode. Then let it charge to 100% and worry no more that you'll get caught out.
If you are reading this and don't have this problem, make sure your clockwork is up to date so you don't end up with it (ie. having a problem with your rom and needing flash tools with a battery below 30% leaves you with no way to charge it).
From my experience the batch file method increased my battery voltage 300mV in about 3 hours so 100mV/hr is probably a reasonable guideline.

I'm sorry actually it's not working for me. Just checked the voltage and it's 2960mV. Because it's not my phone I don't know if it had a battery problem or anything. Is there no way around the 30% check?
The receipt says it was purchased on 24.4.12...

This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks

2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Does anyone suggest a change to the batch file/timing to see if that works? To make it longer do I change the "ping /n 6 localhost >nul" to a larger number?
Are other people getting a constant increase when they look over the voltages reported?

fishy12345 said:
2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Click to expand...
Click to collapse
OMG! I found something v. important out, I was using a long usb cable (1.5m) and a usb slot on the computer that is a bracket (rather than the motherboard slots) and once I changed over to a very short cable (10cm - I have it for the car) and the motherboard usb slot I'm almost charged up in 10 mins. I'll edit the longer post now.

Received error "FAILED: remote (not allowed)" when trying "fastboot flash recovery recovery.img"

If your bootloader is unlocked, just flash CWM touch recovery whilst the phone is in fastboot.
http://db.tt/VF9J2eo8
Place it in the same folder as fastboot in Android SDK,
Enter fastboot
Plug in usb cable from PC to phone
Should now say fastboot USB
Open command prompt
cd c:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
Sent from my HTC One X using Tapatalk 2

fvanommen said:
This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks
Click to expand...
Click to collapse
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?

fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
You should still be able to flash ClockworkMod & a custom rom.
You could do this, even if to at least get your phone up and running to charge it fully.
Sent from my HTC One X using Tapatalk 2

fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
I found the same thing, it wouldn't go past this but it was enough to change the message from Battery low to (in my case) Not allowed.
I had locked the bootloader but it wouldn't unlock so I locked it (sent command twice and received 'ok' message). Unlocked the bootloader again, realised how the menus/options on stock bootloader actually work, loaded clockwork recovery through the recovery option (it was on there the whole time), went back out and made sure it was up to date, used it to install a new Jelly Bean copy, charged the phone.
Well, it took 12 solid hours of researching and attempts after I initially bought what was supposed to be a working phone but it's back again.
Thanks to all who contributed to my questions.

[Q] HTC not charging and booting up.

So, yesterday i was flashing first rom for my HOX and it seems it had less battery than 30% and it wasnt done flash rom completely and it is stuck in "HTC" screen and Bootloader says, that there are "Battery level is too low to flash" .... So what i can do now? How I can do to it does work?
How to charge it?
P.s. In Fastboot my computer is not recognize my phone and I cant go into recovery - because it boot in to it and automaticly reboot my device.
++++++ SOLVED - for solution read #8 POST ++++++

it's a well known problem, don't try to charge from usb cable. power off and plug it into the wall charger and leave it charging for about 3 hours or more

I can leave it on HTC screen?
I tries this -
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
But still it not let me in into recovery ...

No, power off completely and plug into wall charger for at least 3 hours

How do i do that? After i power it off (I cant go further than HTC logo and in Bootloader it do the same) he switches off and then starts again and boot till HTC logo ...
P.s. I hold Power button - it turns off, conect to wall charger, red led indicator shows up (in front grill) and after ~5 sec it automaticly turns on.
P.s.s. It turns on only with charger in phone ... w/o charger it stays off.

red led is on, phone comes back on, does the led stay on on wall charger ?

Read my last reply here
http://forum.xda-developers.com/showthread.php?t=2341036

Yep it was on, but full brightness screen ate more energy than changer can give, so phone was discharging.
Problem was this -
Phone was not able to boot up ROM, because there was no energy to flash full rom, flashing failed - not fully flashed rom, so no system to operate;
Pc di not recognize my device, but somehow it still was able to flash from sdk;
When i tried to boot into recovery, it just blinked and rebooted phone.
So what i done -
Pluged my phone via usb to my pc;
Navigete to fastboot, it was showing fastboot USB;
Opened sdk -> platform tools folder, created txt file with code (below), renamed <name>.bat
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
Runed my .bat file;
Script was runing and phone was turning on, then off, on, off ... etc, so the voltage went to 3680mV, somehow not further;
Closed my .bat file ...
Navigated to recovery, boot it, still NOTHING;
P.s. I was using that from General theard "All in one kit for HOX", but seems antivirus was deleted something and i flashed faulty recovery;
So I downloaded new one CRW;
Flashed it - "freeboot flash recovery <name_of_recovery>.img" form sdk tools...
So - it was booted into recovery,
Went to mound storage, but it was not alow me to mount it, some kind of error,
I flashed - TWRP - from rondom sorces;
There I was able to mount storage, put ROM in storage.
SO I Wiped and Format all what neceseary and get back to PC;
There I flashed boot.img via SDK fastboot tool;
Then from recovery i flashed my new ROM;
DONE! That was so hard, but only thing what was foult was recovery and my unclever mind to know it before - but as they say - "If you are not tryed it, you will never know how to do that" ...

Desire HD boot problem and can't reboot

Hi guys
I've got a desire Hd, over 2 years old now so out of warranty. Not rooted, Android 2.3.5 (official ROM), Middle East ROM and relocked.
When i turn it on,After a minute or less, when it would normally show an android screen, the screen goes to bootloader. and when I wanna reboot it or enter to the recovery , the screen goes blank but the phone is still on, and the screen is still on but in a very dark grey. if you hold it on an angle the backlight appears to be on. But from that point nothing happens, the buttons no longer respond, and I have to remove the battery to turn it off.
Although I've tried to reset factory my phone but it didn't work and the screen goes blank again when the backlight is still on.
Thanks for your help.

PLease help me asap.
did u ever experience this problem?

What did you do to get it in this state?

bananagranola said:
What did you do to get it in this state?
Click to expand...
Click to collapse
nothing much. I've just removed the battery many times, because the Volume down didn't respond and I wanted to enter to the bootloader!!

any solution?!! :crying:

try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.

ammo12 said:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
Click to expand...
Click to collapse
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?

Transporter2009 said:
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Click to expand...
Click to collapse
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?

cherhunghow said:
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
Click to expand...
Click to collapse
I did it but unfortunately I faced with this Failure:
Code:
C:\Android>fastboot flash boot boot.img
sending 'boot' (2840 KB)... OKAY
writing 'boot'... INFOsignature checkin
FAILED (remote: signature verify fail)
what should I do then?? :crying:
and about your problem i think the Volume Key is the problem and it can be fix by replacing the volume key or even with a simple cleaning. don't worry

"IMPORTANT" Screen wont Turn on after original Oreo Fastboot Flash

Hey everyone.
I know how to flash and have knowledge with adb and fastboot and so on... but now iam helpless with this situation and googled allready alot.
1: I flashed to RR 7.02 Android 9.0 without Problems. But i had some Problems with Magisk and my Banking app.
2: I tryd to restore with TWRP my OLD oreo 8.1 backup but there it shows Problems with mounting system all the time. After Restore complete it allways says cant mount system - invalid argument and after boot it only goes to Fastboot.
3: I flashed original CEDRIC_OPP28.85-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip with fastboot commands. After finishing flash i did fastboot reboot but Phone gone off.
Now the the Problem: Screen wont turn on again. I had low Battery and thought it maybe its the Problem of no Battery. But now the Phone hangs like 2 Hours on the original Charger/tryd 2 other chargers allready and the Screen wont turn on. It just blinks the white LED when charger is plugged in. No normal power on no fastbooot or recovery power on. The screen wont just turn on. Strange?! Battery or Hardware defekt? But i had no problems before... The Phone is now 18 month old.
Any advise or Help. Thanks
c:\adb2>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.690s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.598s]
Finished. Total time: 1.358s
c:\adb2>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.695s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.635s]
Finished. Total time: 1.403s
and something like this i had never before... (bootloader) is-logical:recovery: not found or (bootloader) Image signed with key bad key ( but this shouldnt be the problem)
NOW it shows this under device manager when i plug it in look screenshot.

If it's a battery issue hold the power button for 30 seconds whilst the charger is plugged in - if you can then see the charging animation don't attempt to turn the phone on until it reaches 5% charge
You can also try these steps
1) Plug it into the charger
2) Hold the VOL DOWN key
3) While still holding the VOL DOWN key, press and hold the POWER key
4) Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
5) After holding the keys down for more than two minutes, release them.
6) The Fast Boot screen will display, and the Normal Reboot option will be highlighted
7) Press the VOL UP key and the device will start a normal reboot.
If it's a firmware issue you may have hard bricked the device from incorrect or incomplete firmware flash
See my hardbrick thread for a possible solution if it is hard bricked else you may require a motherboard replacement
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012

i think its hard bricked. I will try now your unbrick tutorial. Thanks for this

TheFixItMan said:
If it's a battery issue hold the power button for 30 seconds whilst the charger is plugged in - if you can then see the charging animation don't attempt to turn the phone on until it reaches 5% charge
You can also try these steps
1) Plug it into the charger
2) Hold the VOL DOWN key
3) While still holding the VOL DOWN key, press and hold the POWER key
4) Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
5) After holding the keys down for more than two minutes, release them.
6) The Fast Boot screen will display, and the Normal Reboot option will be highlighted
7) Press the VOL UP key and the device will start a normal reboot.
If it's a firmware issue you may have hard bricked the device from incorrect or incomplete firmware flash
See my hardbrick thread for a possible solution if it is hard bricked else you may require a motherboard replacement
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
Your Tutorial with Linux min worked. The Phone is back to life. Good i didnt gaved up early. Thank you very much. I would like to buy you a beer if you dont mind...got paypal? cuz you made my head free now

fenerbuuh said:
Your Tutorial with Linux min worked. The Phone is back to life. Good i didnt gaved up early. Thank you very much. I would like to buy you a beer if you dont mind...got paypal? cuz you made my head free now
Click to expand...
Click to collapse
Glad it's working - I give advice for fun not for money but thanks for the offer