[TUT] How to fix the 'Low Battery' fastboot loop - HTC One X

This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment Fastboot-battery-recharge.rar and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
2. When the battery power level is high enough (Above 30% - 40% or higher is recommended) you can unlock you phone with the HTCDEV Method).
- XDA will tell you how you can unlock/root your phone!
3. Next step is to flash the newest recovery WITH the possibility to charge your phone in the recovery.
- "fastboot flash recovery recovery-clockwork-touch-X.X.X.X-endeavoru.img", get the newest one on HERE.
4. After flashing the recovery boot into it and stay there until your 'LED' gives a green colour, this means the phone is charged 100%.
5. Now you can flash any rom in the recovery or use the fastboot way discribed HERE. (http://paste2.org/p/2061793)
This did the job for me, hopefully for you also!
Thanks to:
Setsuna666 @ XDA - First steps
floepie @ XDA - Reboot script
Koush - Recovery with Charging posibilities
Paulobrien - Root method with HTCDEV
Good luck and please post extra information and tips in commens!
-Laav
PS: English is NOT my main language so sorry for any spelling fault!

Make sure you use a short usb cable and avoid front panel/bracket usb slots or else you might notice the charge doesn't go up steadily.

Sent from my GT-I9100 using xda premium

Worked perfect thanks :laugh:
Wouldn't boot into recovery until i reached over 4000mv though

You are a life saver. Thank you so much for this

thank you for the guide but this should be in the general thread

laav said:
This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment 1161765 and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
2. When the battery power level is high enough (Above 30% - 40% or higher is recommended) you can unlock you phone with the HTCDEV Method).
- XDA will tell you how you can unlock/root your phone!
3. Next step is to flash the newest recovery WITH the possibility to charge your phone in the recovery.
- "fastboot flash recovery recovery-clockwork-touch-X.X.X.X-endeavoru.img", get the newest one on HERE.
4. After flashing the recovery boot into it and stay there until your 'LED' gives a green colour, this means the phone is charged 100%.
5. Now you can flash any rom in the recovery or use the fastboot way discribed HERE. (http://paste2.org/p/2061793)
This did the job for me, hopefully for you also!
Thanks to:
Setsuna666 @ XDA - First steps
floepie @ XDA - Reboot script
Koush - Recovery with Charging posibilities
Paulobrien - Root method with HTCDEV
Good luck and please post extra information and tips in commens!
-Laav
PS: English is NOT my main language so sorry for any spelling fault!
Click to expand...
Click to collapse
i have try it
but i have more then 3478 mv
but when i start my phone it shows me only 2%
i have try it more then 20 times
i have now 3569 mv
still showing me only 2% when i start the phone
i have flashed the recovery mode,but it does not work
(FAILED (remote:battery low)
i need help

ediresta said:
i have try it
but i have more then 3478 mv
but when i start my phone it shows me only 2%
i have try it more then 20 times
i have now 3569 mv
still showing me only 2% when i start the phone
i have flashed the recovery mode,but it does not work
(FAILED (remote:battery low)
i need help
Click to expand...
Click to collapse
you need at least 3,68V to flash the recovery in fastboot

I know this is an old thread and I apologize for bringing it back from the dead but I just recently used this guide and I just wanted to share what worked for me in the event someone else would find this useful.
I tried to flash a rom without flashing the boot.img first and this is when all my trouble began. My phone would not charge as it was stuck in Fastboot mode and thanks to this batch file I was able to change the phone to 3700mV and get it working again. I mistakenly relocked my bootloader and on the top it said "Re-locked"
I used the batch file but then after a few hours it seemed to stop at around 3500mV. So i turned off the phone and let is sit for a little and even changed USB ports and then a the batch file again. I would say it took about 7 hours give or take to get the phone up to 3700mV. After I got the phone to 3700mV I kept trying to flash either a recovery or unlock the bootloader and it just didn't work. I kept getting Failed: not allowed or Failed signature verify fail (when trying to unlock the bootloader. It turns out I was using an old unlock_code.bin file from HTC and so I got a new bin file from HTCDev and flashed the unlockcode.bin successfully. Once that was done I was able to flash 5.8.4.0 recovery.
I apologize if my post is a little unclear but please feel free to message me if you need clarification. I would be more than happy to help. I know what it feels like to have this issue so I would be glad to help out!

So what do I do if I'm not rooted and my phone won't charge and I get no red light indicating its charging I also tried to hard reset no go
sent from a $uperior phone

My log :
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3047mV
finished. total time: 0.100s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.143s]
finished. total time: 0.144s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3047mV
finished. total time: 0.108s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.145s]
finished. total time: 0.146s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3039mV
finished. total time: 0.106s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3040mV
finished. total time: 0.105s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3034mV
finished. total time: 0.108s
...........................................................................
It is going down slow :/ (i normaly want that but not when my battery voltage dose )

laav said:
This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment 1161765 and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
Click to expand...
Click to collapse
I'm a complete noob and don't see how this works/ what to do when this file is in adb folder, could you give more details please?

KiernanConor said:
I'm a complete noob and don't see how this works/ what to do when this file is in adb folder, could you give more details please?
Click to expand...
Click to collapse
you have to run it

matt95 said:
you have to run it
Click to expand...
Click to collapse
Lol thanks, i hadn't marked it executable,

wont turn off
hi
my phone is stuck on the white htc screen with the green logo
when i run the file youve posted here it says : waiting for device//

shefer said:
hi
my phone is stuck on the white htc screen with the green logo
when i run the file youve posted here it says : waiting for device//
Click to expand...
Click to collapse
Because the phone has to be in the bootloader before executing the script

help!!
it doesn't work!! this is my log!
finished. total time: 0.132s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2884mV
finished. total time: 0.101s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2863mV
finished. total time: 0.106s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2842mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2824mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.099s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2793mV
finished. total time: 0.103s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2768mV
finished. total time: 0.100s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.131s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.140s
< waiting for device >
battery-voltage: 2877mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
Click to expand...
Click to collapse
please help me!!:crying:

HollowLeon said:
it doesn't work!! this is my log!
please help me!!:crying:
Click to expand...
Click to collapse
Try using a main usb port on the back of the computer, I had same problem but its charging oh so slowly! At least it is actually charging I hope

Help me please.I cant charge my htc, its getting 3638mU max, and this is not enought to use flash.I have unlocked hboot but cant flash recovery to charge my htc

thanx
thanxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:victory:

Related

Failed at installing new ROM, phone hangs at HTC logo

I've rooted my HTC One X (International version) phone and tried putting cyanogenmod 10.1 onto it but that failed (it came up with an error that I can't remember).
After that, when I started it up, it hanged on the HTC logo screen. I tried to put another ROM onto the memory of my phone but my computer won't recognise my device (I tried putting it in recovery mode [clockworkmod recovery], fastboot mode and hboot mode)
The phone has been relocked (I think that's because I was playing around with it too much) and I don't know how to unlock it again.
When I try the unlock command I get this message:
Code:
C:\Users\----\Desktop\phone>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.218s
So I tried this: http://forum.xda-developers.com/showthread.php?t=1658084 to try and fix the battery message.
It still doesn't work.
Now the phone doesn't start when I try to turn it on (by pressing the power button, holding down the power button, holding the power and volume buttons etc.). When I connect my phone via USB to my computer, it turns on for 3 minutes (into fastboot USB mode), turns off for 3 minutes, turns back on for 3 minutes and so on...
Can anyone help?
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Then after you're good to flash, unlock the bootloader and flash a custom recovery.
Your hboot version is too low for cm10.1. You need to bump it up, just search how to.
Next, make sure you did these two things while installing cm10.1:
1. Flash boot.img
2. Install vendor installer in recovery (read the cm thread)
Sent from my IceCold One X
TToivanen said:
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Click to expand...
Click to collapse
Okay so the script ran for about a minute and then it came with this:
Code:
< waiting for device >
battery-voltage: 2859mV
finished. total time: 0.170s
rebooting into bootloader...
OKAY [ 0.224s]
finished. total time: 0.224s
< waiting for device >
battery-voltage: 2848mV
finished. total time: 0.124s
rebooting into bootloader...
OKAY [ 0.204s]
finished. total time: 0.205s
< waiting for device >
battery-voltage: 2829mV
finished. total time: 0.104s
rebooting into bootloader...
OKAY [ 0.228s]
finished. total time: 0.228s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.102s
rebooting into bootloader...
OKAY [ 0.229s]
finished. total time: 0.229s
< waiting for device >
battery-voltage: 2792mV
finished. total time: 0.107s
rebooting into bootloader...
OKAY [ 0.218s]
finished. total time: 0.218s
< waiting for device >
battery-voltage: 2769mV
finished. total time: 0.105s
rebooting into bootloader...
OKAY [ 0.241s]
finished. total time: 0.242s
< waiting for device >
battery-voltage: 2743mV
finished. total time: 0.139s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
Now the phone is staying off and won't turn on...
(Also, is the battery voltage supposed to slowly drop after each script cycle?)
EDIT:
Nevermind, it's restarting over and over again, here's the continuation:
Code:
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
battery-voltage: 2997mV
finished. total time: 0.167s
rebooting into bootloader...
OKAY [ 0.244s]
finished. total time: 0.245s
< waiting for device >
battery-voltage: 2980mV
finished. total time: 0.183s
rebooting into bootloader...
OKAY [ 0.245s]
finished. total time: 0.245s
< waiting for device >
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Sent from my IceCold One X
TToivanen said:
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Click to expand...
Click to collapse
Ooh... that really doesn't sound good. Um, well firstly I left the script running for an hour. The maximum voltage that it ever got to was 3002mV. I tried the batch file again and again, for like 10 minutes, and still the same results.
Right now, things are looking better.
I realised that my computer's USB won't charge my phone above 3 volts, and will cause it to slowly drop, so I connected the mains battery charger and manually pressed 'reboot bootloader' over and over and over again. This actually charged it. Right now when I check it on my computer, it says 3617mV, and I have successfully unlocked the relocked bootloader using the instructions in htcdev.com.
I can get to the recovery mode.
When I start my phone normally, it hangs on the HTC logo screen.
Would it charge in recovery mode if I only have clockworkmod 5.8.2.7 installed?
I tried updating it to clockworkmod 5.8.3.1 but it says battery low and so I probably have to keep charging it by manually restarting the bootloader?
Right now I'm sorta underway.
I need to update the clockworkmod, update the hboot version, and then somehow copy a ROM onto my phone when it's in recovery mode (I don't know how to do this bit). And then it should install the new ROM...
once you can get into custom recovery there is a option somewhere to mount your phone to the pc.
just copy it to your phone, unmount and flash. might have to do a reflash of the boot.img after the rom.. just try.
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Sent from my HTC One X using xda app-developers app
Is there any way to upgrade the hboot version? When I check the cid I get this:
Code:
C:\Users\----\Desktop>fastboot oem readcid
< waiting for device >
...
(bootloader) DEBUG: cid: TELNZ001
OKAY [ 0.086s]
finished. total time: 0.087s
I can't find a hboot firmware.zip that matches that cid...
Do also
fastboot getvar version-main
Sent from my IceCold One X
davidk-il said:
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Click to expand...
Click to collapse
How do you do that? I have CWM 5.8.3.1 on it but when I select 'mount USB storage' nothing happens. It doesn't mount it.
When I run the command I get this:
Code:
C:\Users\****\Desktop>adb push Slim-endeavoru-4.2.2.build.2.5-OFFICIAL.zip /sdcard/
error: device not found
TToivanen said:
Do also
fastboot getvar version-main
Click to expand...
Click to collapse
Here's the output:
Code:
C:\Users\----\Desktop>fastboot getvar version-main
< waiting for device >
version-main: 1.26.781.2
finished. total time: 0.108s
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
BenPope said:
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
Click to expand...
Click to collapse
Oh thanks, I've upgraded it to CWM 5.8.4.0 and now my computer recognises it!
At the moment I don't know what to do.
Can I update the hboot version? Can I put Cyanogenmod 10.1 onto it? Or another ROM like slim?
If not, how can I restore the old original android on it? Right now it just hangs at the HTC logo if I start it normally.
Here's the info for my phone:
Code:
HTC One X internation version
cid: TELNZ001
version-main: 1.26.781.2
hboot: 0.43.0000
Clockworkmod: 5.8.4.0
Here is the ruu you need to go back to full stock
http://bugsylawson.com/index.php/fi...812-radio-112049013-release-251287-signedexe/
After the ruu you can update with official ota :thumbup:
Put the phone in the bootloader and relock the bootloader.
Fastboot oem lock
Then keep the phone in the bootloader and select the ruu by clicking on it with the right mouse button. Then select : run as administrator
It will bring the phone to full stock and you be able to update after that from witin the OS menu .....
Note : backup what you need. It erases everything
Thanks, everything is fixed now. I have used someone e'se's nandroid backup and it works alright now.
Failed Installation
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Jussi31 said:
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Click to expand...
Click to collapse
You can mount storage from recovery....
For adb -
put the Rom in the adb folder and in cmd - adb push /sdcard/*rom name*.zip
Sent from my HTC One X using xda app-developers app
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Jussi31 said:
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Click to expand...
Click to collapse
Just copy the ROM.zip file in your ADB/Fastboot folder... then run the following code in cmd:
Code:
adb push /sdcard/ROM.zip
Where rom.zip = the zip file you had copied in your adb folder... It will send that file in the root of the sd card
I have tried that multiple times already without any results, unfortunately. I also have made matters worse--I decided to flash a no-touch CWM, thinking that may have been the culprit in all of this, and now it no longer even goes into CWM, and the screen remains blank and dark. Not good. At least I still have the ability to go into bootloader mode.

[Q] Help, my HTC One X won't charge!

HBOOT 1.12.0000
*** Relocked ***
*** Security warning ***
those are my specs and i was trying to Fastboot flash zip firmware.zip when it says FAILED <remote: battery low>>. Problem is it´s need to charge past 30% and thats not happening.
I tried the below method
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
Click to expand...
Click to collapse
it keeps rebooting and guess what, it doesn't even charge above 2899. it stuck there!!! here's my log using that code..
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2884mV
finished. total time: 0.101s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2863mV
finished. total time: 0.106s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2842mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2824mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.099s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2793mV
finished. total time: 0.103s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2768mV
finished. total time: 0.100s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.131s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.140s
< waiting for device >
battery-voltage: 2877mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
Click to expand...
Click to collapse
...and no matter what, after it says "FAILED (status read failed (Too many links))", it still stuck at 2890 something. I hope someone can help me out here, im desperate!!
Custom recovery installed ? If so wich one exactly ?
sent from my venomized piece of technology
I'm about to install CWM but I can't since I'm stuck at "Fastboot flash zip firmware.zip" when it says FAILED <remote: battery low>>. can you help me with this? I tried to charge but it won't work even doing the fastboot battery recharge method below..
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
Click to expand...
Click to collapse
Hmm so the script actually works. Oke try all this if you haven't already.
1: reboot pc
2: use the original HTC usb cable
3: use a genuine usb 2.0 port
Don't use other cables or extenders. Don't use a usb hub or switch of any kind. Plug it in a direct usb 2.0 port !
sent from my venomized piece of technology
tried that, doesn't work also. the log states that the battery keeps decreasing and when it comes to 2700 something it will stop and try again...but it always loops the same. here are the log for your confirmation
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2884mV
finished. total time: 0.101s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2863mV
finished. total time: 0.106s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2842mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2824mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.099s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2793mV
finished. total time: 0.103s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2768mV
finished. total time: 0.100s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.131s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.140s
< waiting for device >
battery-voltage: 2877mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
Click to expand...
Click to collapse
Tried it on a different pc ?
sent from my venomized piece of technology
done that too, doesn't work...and im really stuck here. is there any other way?
Yeah open the hox and charge the battery outside the phone
sent from my venomized piece of technology
how to do that? sorry im a noob at this.
If you have clockworkmod recovery installed, you can get into fastboot and 'power down' your phone. then charge it like normal.
as i said, i couldnt get to the part of installing the cwm because of the battery.
He means that you have to select "power down" from the bootloader menu ! Not to flash anything.
sent from my venomized piece of technology
doesn't work, it still blinking away. even after hours left with the charger.
in the same problem..
HollowLeon said:
doesn't work, it still blinking away. even after hours left with the charger.
Click to expand...
Click to collapse
i am in the same problem , did you fix it ?

Help unbrick honor 7x frp locked, bootloader loked. rescue mode only save me or..?

Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
this needs to come here n the open, not in my PM.
PS C:\adb> fastboot flash rescue_recovery_ramdisk C:\adb\twrp_openkirin_sudeep.img
target reported max download size of 471859200 bytes
sending 'rescue_recovery_ramdisk' (25164 KB)...
OKAY [ 0.854s]
writing 'rescue_recovery_ramdisk'...
OKAY [ 0.031s]
finished. total time: 0.885s
PS C:\adb> fastboot reboot
rebooting...
Click to expand...
Click to collapse
recovery flashed while frp and bootloader locked.
!!!!!!!!!!!!!
---------- Post added at 06:55 PM ---------- Previous post was at 06:16 PM ----------
What happens after reboot, try to boot to recovery with volume button, when you use
Code:
fastboot flash rescue_recovery_ramdisk RECOVERY_RAMDIS.img
recovery_ramdisk
does phone still have your broken twrp or the stock recovery?
JKmamba$ said:
https://ibb.co/nKOuRT
https://ibb.co/ccECD8
https://ibb.co/m1qxfo
for new users prevented post external link sorry .... you can for me?
Click to expand...
Click to collapse
so the fastboot command shows ok flashed, but its not changing the loaded recovery image.
don't know what to suggest next.
JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Thetpcguy said:
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Click to expand...
Click to collapse
let me chek man take a pictures of all single screen you'll see... RECOVERY, AFTER RECOVERY (bootloop logo, black screen ecc), and FAST BOOT MODE.. maybe i help you ... i won't to roll back my device because oreo is very perfomance but so buggy for exemple bluethoot don't worck multy shut on photograf bugged or many root application work and after 5 min close with (root with magisk -_-")... in nougat don't have ever this problem root with only super su and all unlocked....

Question Hello need urgent help please

if anyone online. kindly help ,me..
so i unlock my botloder. i was on global 12.3.0
i downloaded the xiaomi eu rom from https://androidfilehost.com/?w=files&flid=321331.
and tried to flash it with windows_fastboot_first_install_with_data_format command and now my phone is on fastboot for last half hour..
and last line on command prompt are these..
Finished. Total time: 0.047s
Sending 'cust' (418624 KB) OKAY [ 8.975s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 13.371s
please help me what to do now.. what went wrong?
Better read MIUI 12.5 (Xiaomi.EU) thread and ask your question there.
Just reboot into bootloader with volume down and power. Repeat the process. Better yet change or replug your USB from PC. Happens to me sometimes on ryzen
TheBURAQ said:
if anyone online. kindly help ,me..
so i unlock my botloder. i was on global 12.3.0
i downloaded the xiaomi eu rom from https://androidfilehost.com/?w=files&flid=321331.
and tried to flash it with windows_fastboot_first_install_with_data_format command and now my phone is on fastboot for last half hour..
and last line on command prompt are these..
Finished. Total time: 0.047s
Sending 'cust' (418624 KB) OKAY [ 8.975s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 13.371s
please help me what to do now.. what went wrong?
Click to expand...
Click to collapse
Install 15sec adb and retry

Script not returning battery-voltage value

I’m using the script found on this site to power cycles an Android phone when battery is too low to enter into recovery mode (“Stuck in fastboot with low battery. Use this batch file!” by floepie):
@Echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
The script works fine but battery-voltage is blank and I don’t know if battery is charging or not:
battery-voltage:
finished. total time: 1.133s
rebooting into bootloader...
OKAY [ 1.134s]
finished. total time: 1.135s
< waiting for any device >
battery-voltage:
finished. total time: 1.128s
rebooting into bootloader...
OKAY [ 1.128s]
finished. total time: 1.130s
< waiting for any device >
Can someone please tell me why battery-voltage is blank and how to correct?

Categories

Resources