You have a problem when you have ALL of the following conditions met:
1. Your battery level is below 3.68 V (3680 mV) (about 10% charged).
2. You have a custom recovery on the recovery partition AND a custom ROM on the system partition.
3. You have just re-locked your bootloader and you can't re-unlock it because your battery is too low (less than 10%).
Here's the problem: If you want to use a RUU, you need about 30% battery. But, if you have less than that, you need to charge it. But the problem is, you can't charge it because you can't boot your phone into either recovery or the ROM itself in order to accept a charge. A re-locked bootloader will NOT allow you to boot either into the custom recovery or the custom ROM. And, you cannot charge your phone in fastboot. Additionally, you cannot re-unlock your bootloader because your phone has even less than 10% charge (3.68 V). If you have between 10% and 30%, then simply re-unlock your bootloader and boot into recovery and charge as normal to a level somewhere above 30% if you want to flash an RUU. But, if your battery is below 10%, then you will need to bring it back above 10% with the script below.
So you need the following script which power cycles your phone repeatedly in order to turn off your screen long enough to accept a charge. Once you reach 3.68 V, which is 10% charge, you're through the woods, so to speak, as you can then, re-unlock your bootloader.
Run the following script as a batch file while your phone is in USB fastboot mode.
Here is the script:
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
floepie said:
My battery is low and is in bootloader/flashboot mode. I've relocked the bootloader in preparation to flash the newest RUU. The bootloader won't allow the phone to boot with its custom ROM.
I have the phone plugged in and I can't turn the screen off. The LED is showing red, but is the phone actually charging in order to either flash the RUU or re-unlock the bootloader?
Is there a way to see the battery status? I hope I'm not screwed here.
Click to expand...
Click to collapse
You need to reunlock and flash this recovery http://forum.xda-developers.com/showthread.php?t=1594819 to charge the device then re lock and run ruu. Just give it about a half an hour or so on charge.
lmftmf said:
You need to reunlock and flash this recovery http://forum.xda-developers.com/showthread.php?t=1594819 to charge the device then re lock and run ruu. Just give it about a half an hour or so on charge.
Click to expand...
Click to collapse
Thanks but I can't reunlock with the *.bin. It fails with the report that battery is too low!
Any other ideas?
floepie said:
Thanks but I can't reunlock with the *.bin. It fails with the report that battery is too low!
Any other ideas?
Click to expand...
Click to collapse
Uhh ohh. Tat not goood. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1609190
Setsuna666 said:
IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery. So, flash the new recovery and this problem will NOT happen.
Click to expand...
Click to collapse
I can't get into CWM (even the latest) with a locked bootloader.
SOLVED!
This little bad boy of a batch file saved my life. I was in a situation where my phone had a custom ROM with a re-locked bootloader and a low battery. The battery cannot be charged while in fastboot, and there was too little charge to re-unlock the bootloader. If you have a custom ROM with a custom recovery (CWM) and a locked bootloader, you cannot get into recovery.
In any case, if you create a batch file with the following contents, you can make your phone continually boot indefinitely, which allows the screen to be off sufficiently long enough between boots that the battery begins to charge. And, when voltage apparently approaches 3.68V, you have enough charge to re-unlock the bootloader and charge normally without the phone's screen in fastboot continually on.
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Source: http://forum.xda-developers.com/showthread.php?t=1643483
floepie said:
This little bad boy of a batch file saved my life. I was in a situation where my phone had a custom ROM with a re-locked bootloader and a low battery. The battery cannot be charged while in fastboot, and there was too little charge to re-unlock the bootloader. If you have a custom ROM with a custom recovery (CWM) and a locked bootloader, you cannot get into recovery.
In any case, if you create a batch file with the following contents, you can make your phone continually boot indefinitely, which allows the screen to be off sufficiently long enough between boots that the battery begins to charge. And, when voltage apparently approaches 1.68V, you have enough charge to re-unlock the bootloader and charge normally without the phone's screen in fastboot continually on.
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Source: http://forum.xda-developers.com/showthread.php?t=1643483
Click to expand...
Click to collapse
you can charge the battery in the "HTC QUIETLY BRILLIANT" screen, this is not necessary.
wolfraim said:
you can charge the battery in the "HTC QUIETLY BRILLIANT" screen, this is not necessary.
Click to expand...
Click to collapse
Uh, no. Can you remove your post? You can't get to that screen when the following conditions are met: low battery, a newly re-locked bootloader, custom recovery/ROM. The locked bootloader prevents you getting beyond fastboot. Read my source, and you will see other threads where this batch file was posted and where you can't get past an immediate fastboot screen.
floepie said:
This little bad boy of a batch file saved my life. I was in a situation where my phone had a custom ROM with a re-locked bootloader and a low battery. The battery cannot be charged while in fastboot, and there was too little charge to re-unlock the bootloader. If you have a custom ROM with a custom recovery (CWM) and a locked bootloader, you cannot get into recovery.
In any case, if you create a batch file with the following contents, you can make your phone continually boot indefinitely, which allows the screen to be off sufficiently long enough between boots that the battery begins to charge. And, when voltage apparently approaches 1.68V, you have enough charge to re-unlock the bootloader and charge normally without the phone's screen in fastboot continually on.
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Source: http://forum.xda-developers.com/showthread.php?t=1643483
Click to expand...
Click to collapse
thanks
floepie said:
This little bad boy of a batch file saved my life. I was in a situation where my phone had a custom ROM with a re-locked bootloader and a low battery. The battery cannot be charged while in fastboot, and there was too little charge to re-unlock the bootloader. If you have a custom ROM with a custom recovery (CWM) and a locked bootloader, you cannot get into recovery.
In any case, if you create a batch file with the following contents, you can make your phone continually boot indefinitely, which allows the screen to be off sufficiently long enough between boots that the battery begins to charge. And, when voltage apparently approaches 1.68V, you have enough charge to re-unlock the bootloader and charge normally without the phone's screen in fastboot continually on.
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Source: http://forum.xda-developers.com/showthread.php?t=1643483
Click to expand...
Click to collapse
Hi, sorry for my english but is translated by google.
Even I have the problem of the battery, I can not do any flash (recovery, ruu etc.).
I created the batch file by copying exactly what you've written, no ", correct?
I started the file and I get continuous
<Waiting for device>
battery-voltage: 2749mV
finished. total time: 0.153s
rebooting into bootloader ...
every time the phone goes off and reads:
<Waiting for device>
battery-voltage: 2749mV
finished. total time: 0.153s
rebooting into bootloader ...
FAILED (status read failed (Too many links))
finished. total time: 0.238s
<Waiting for device>
again after 1 minute.
Is this normal? the file I do go for 1 or 2 hours continuously?
thank you
Yes, the batch file forces the phone to continue to boot over and over again, and you will see the voltage increasing over time. But, you have enough battery to re-unlock the bootloader. Just go to htcdev.com to re-unlock it, or just flash an RUU to update your radio.
Why are you running this batch file when you have enough battery power?
This batch file is only for those whose battery is low and therefore cannot re-unlock the bootloader and have a cutom ROM with a relocked bootloader.
floepie said:
Yes, the batch file forces the phone to continue to boot over and over again, and you will see the voltage increasing over time. But, you have enough battery to re-unlock the bootloader. Just go to htcdev.com to re-unlock it, or just flash an RUU to update your radio.
Click to expand...
Click to collapse
the voltage increases or fluctuates? exampe 2785 - 2888 - 2985 - 2788 etc.
the message:
rebooting into bootloader ...
FAILED (status read failed (Too many links))
finished. total time: 0.238s
<Waiting for device>
is normal?
floepie said:
Why are you running this batch file when you have enough battery power?
Click to expand...
Click to collapse
I have the problem of battery low, I can not flash the recovery or unlock the bootloader.
Oh, you are right. You're battery is too low. You need to charge it until your voltage reaches 3.68 V (3680 mV). The phone should keep powering off and on, and your voltage will go up, but not at *every* boot. It should take about an hour or so? So, yes, the phone will boot a lot of times, but it's the only way out. Just keep the batch running and keep checking every 10 minutes or so.
As for the batch file, I'm pretty certain the quotation marks (" ") are NOT needed.
floepie said:
Oh, you are right. You're battery is too low. You need to charge it until your voltage reaches 3.68 V (3680 mV). The phone should keep powering off and on, and your voltage will go up, but not at *every* boot. It should take about an hour or so? So, yes, the phone will boot a lot of times, but it's the only way out. Just keep the batch running and keep checking every 10 minutes or so.
As for the batch file, I'm pretty certain the quotation marks (" ") are NOT needed.
Click to expand...
Click to collapse
ok.
keep it going for 1 or 2 hours until it reaches 3.68V
can you attach your batch file? please.
Thank you for now, let you know if it reaches 3.68V
There you go. Change the extension to *.bat from *.txt
same prob exactly
hey guys i saw this while am searching for a fix i have the same **** on my one x i tired almost everything out there but only this didnt yet and its my last hope hope it works
i need more info bout this batch i downloaded it ext, edit to .bat paste it in the adb folder
then copied whts inside it and post it in cmd and heres wht its looks like
is it okay like this ?! should i just leave it and wait !?
plzzz help my phone voltage is getting lower :S :S :S wht did i do wrong :S
floepie said:
Oh, you are right. You're battery is too low. You need to charge it until your voltage reaches 3.68 V (3680 mV). The phone should keep powering off and on, and your voltage will go up, but not at *every* boot. It should take about an hour or so? So, yes, the phone will boot a lot of times, but it's the only way out. Just keep the batch running and keep checking every 10 minutes or so.
As for the batch file, I'm pretty certain the quotation marks (" ") are NOT needed.
Click to expand...
Click to collapse
after 1 hour the voltage does not increment, but change always
battery-voltage: 2768mV
battery-voltage: 2747mV
battery-voltage: 2993mV
battery-voltage: 2980mV
battery-voltage: 2970mV
battery-voltage: 2956mV
battery-voltage: 2796mV
and so on.
It's normal?
well for me its increasing now i reached 3370v now
are u leaving your phone or u keep pasting whts writting in the batch !?
sallam5010 said:
well for me its increasing now i reached 3370v now
are u leaving your phone or u keep pasting whts writting in the batch !?
Click to expand...
Click to collapse
just does not work for me?
EDIT:
Or if anybody knows where I can look for help on this I would really appreciate it.
Hi,
I am searching yesterday and today to solve my problem but no locuk so far.
Yesterday the phone rebooted and since then is staying on "HTC quietly..."
I tried to flash ROM again that was already on my sdcard but recovery said "Bad zip".
Now I cannot access /sdcard from recovery. "Error mounting"
When "fastboot oem lock" I am getting this message:
... INFOLock successfully...
FAILED (status read failed (Too many links))
And then phone reboot and stays at "HTC quitely...."
Flashing boot.img and recovery.img goes OK but the recovery stays the same.
And I have "Low battery level cannot flash". but i can manage to charg the phone a bit.
This is what I have:
HOX Tegra3
hboot 1.39
CWM recovery v5.8.4.0
IC 15.0.1
Does anybody know more about it.
Thank you
EDIT:
Or if anybody knows where I can look for help on this I would really appreciate it.
Re: fastboot oem lock returns error...?
Why do you want to lock the bootloader ?
2 options to charge
1 put the phone inside the recovery, it will charge there
2 put this file in the fastboot folder and boot the phone into the bootloader/fastboot usb mode and execute the bat file ! It will continuously reboot the phone and charge it little by little
http://db.tt/aLqeTpPO
Mr Hofs said:
Why do you want to lock the bootloader ?
2 options to charge
1 put the phone inside the recovery, it will charge there
2 put this file in the fastboot folder and boot the phone into the bootloader/fastboot usb mode and execute the bat file ! It will continuously reboot the phone and charge it little by little
http://db.tt/aLqeTpPO
Click to expand...
Click to collapse
Thank you but charging is not my main issue. Rather that my phone keeps staying on htc quietly... and that i cannot access sd card.
Re: fastboot oem lock returns error...?
Locking the bootloader will not help you, keep the bootloader unlocked and reflash the recovery, try it again after that
Also erase cache afterwards
Fastboot flash recovery recovery.img
Fastboot erase cache
Mr Hofs said:
Locking the bootloader will not help you, keep the bootloader unlocked and reflash the recovery, try it again after that
Also erase cache afterwards
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
I did that...no matter what i flash it says OK but nothing is changed.
I tried flashing other recovery ... nothing.
Thank you.
It seams that I have to take it to a service...
Re: fastboot oem lock returns error...?
Strange ???
try this tool: http://forum.xda-developers.com/showthread.php?t=1924003
It has commands which might help you...
Thank you all
Thank you all for your time.
I did everything, including reinstalling drivers and trying all again, and could not solve it.
I took it to the store hoping they will not mind "unlocked" status.
When I get it back I'll be posting it here if someone can benefit from that info.
Cheers:fingers-crossed:
Hi there, this is a last ditch attempt before I send the handset back to Virgin Mobile.
I successfully unlocked my bootloader and rooted my phone, then tried to flash it with Paranoid Android for the HTC One X. This seemed to work and ended up getting stuck on the X loading screen that comes with Nexus devices. It got stuck so I then read up and it seemed like I needed to flash the boot.img that came in the zip file. DId that and the phone then just got stuck on the HTC "Simply brilliant" loading screen.
Clockworkmod is installed, and I have tried to reset the phone with the appropriate RUU. However, now the phone just sits on the HTC simply brilliant screen - that now has a warning about it being a developer version. It then loads only into the Fastboot menu, and all option either reboot the phone to follow that same path (warning, then fastboot screen) or do nothing.
I can no longer get into Clockworkrecovery, and there is also no way of getting a rom onto the phone to work with.
The RUU also only seems to get about half way through until it tells me there has been a communication error.
Please, I hope someone can give me some help. I've tried countless threads, countless downloads and am now just confused about the whole thing.
Oh, and the battery always seems to be low - at least the fastboot menu tells me it is
Could someone give me a step by step guide on how to resolve in possible?
Thanks in advance!
keeno79 said:
Hi there, this is a last ditch attempt before I send the handset back to Virgin Mobile.
I successfully unlocked my bootloader and rooted my phone, then tried to flash it with Paranoid Android for the HTC One X. This seemed to work and ended up getting stuck on the X loading screen that comes with Nexus devices. It got stuck so I then read up and it seemed like I needed to flash the boot.img that came in the zip file. DId that and the phone then just got stuck on the HTC "Simply brilliant" loading screen.
Clockworkmod is installed, and I have tried to reset the phone with the appropriate RUU. However, now the phone just sits on the HTC simply brilliant screen - that now has a warning about it being a developer version. It then loads only into the Fastboot menu, and all option either reboot the phone to follow that same path (warning, then fastboot screen) or do nothing.
I can no longer get into Clockworkrecovery, and there is also no way of getting a rom onto the phone to work with.
The RUU also only seems to get about half way through until it tells me there has been a communication error.
Please, I hope someone can give me some help. I've tried countless threads, countless downloads and am now just confused about the whole thing.
Oh, and the battery always seems to be low - at least the fastboot menu tells me it is
Could someone give me a step by step guide on how to resolve in possible?
Thanks in advance!
Click to expand...
Click to collapse
Do you know how to use fastboot? If so:
1. Flash stock recovery with fastboot flash recovery recovery.img <--- This file in the same location as fastboot
2. fastboot erase cache
3. fastboot oem lock
4. It may reboot or not. Just load back into the bootloader.
5. run RUU
Thank you for the reply,
Unfortunately I can not seem to flash anything using fastboot at the moment as it always says my battery level is too low to flash. It has been on charge for most of the day so can't possibly be empty. I would usually clear the battery stats to get round this but can not longer get into clockworkmodrecovery.
Any advice on that - thanks again!
keeno79 said:
Thank you for the reply,
Unfortunately I can not seem to flash anything using fastboot at the moment as it always says my battery level is too low to flash. It has been on charge for most of the day so can't possibly be empty. I would usually clear the battery stats to get round this but can not longer get into clockworkmodrecovery.
Any advice on that - thanks again!
Click to expand...
Click to collapse
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Put that into notepad and save it as fastbootcharge.bat
Put the fastbootcharge.bat in fastboot location and run it while the phone is in fastboot mode.
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
:thumbup:
Hello,
I got my Fairphone stolen and I had to get a new one and re-config my os onto it (I had Iodéos).
I followed the official instruction here https://iode.tech/en/iodeos-installation/#1648127755024-cd19692f-431b but got stuck when my phone never reached recovery mode. It is now stuck in the bootloader menu (Start/ Restart to bootloader/ Recovery mode/ Power off/ FFBM/ QMMI) and whatever the option I chose I keep comming back to this screen. The phone don't start normally anymore. The bootloader is unlocked and I never locked it before finishing the installation as I read it can brick the phone, still I'm stuck here. I tried everything I found on the internet (removing the battery and waiting etc). Fastboot commands work fine. Adb commands obviously does not. I'm kind of desperate... Any ideas ?
Thanks a lot in advance !
Better late than never.. when in fastboot mode run command:
Code:
fastboot --set-active=a
Then reboot.
Aanze said:
Better late than never.. when in fastboot mode run command:
Code:
fastboot --set-active=a
Then reboot.
Click to expand...
Click to collapse
Thanks ! I had already done this without result.
But I solved it by flashing FPOS to get out of the bootloop and flashing iodéOS after.
All the steps here if it can help someone.