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.
Related
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Hi! Have you tried to leave the phone without the battery for 1-2 minutes and tried a reboot?
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
bortak said:
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
Click to expand...
Click to collapse
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Ryther said:
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Click to expand...
Click to collapse
Really no idea, and what I told you to do is not guarantee'd to work, it may help though.
And thanks, it sure has cut down repeat posts about repeat problems by about 90% here.
Thank you all for your replies.
I did leave the phone without battery for several days - same problem.
But I did not try to press the pwr for 30 secs without battery. I will try when I get home.
I tried following:
- take battery out and reset it. then hold vol dwn + pwr -> Nothing
- take battery out and reset it. then hold back + pwr -> Nothing
By the way, if I press pwr to turn phone on, it does not come up, but leaving it for a while it gets warmer.
It looks like the CPU is trapped in a loop and running at full speed!
Could a riff box repair it?
do a battery pull then hold back & power. That usually boots into fastboot mode, see if the phone is recognised with
Code:
fastboot devices
if it is run the 2.3 RUU.
Dear bortak
I have tried. It does not enter fastboot.
command "fastboot devices" returns blank.
command "adb devices" returns empty list
command "adb reboot-bootloader" givers "device not found error"
RUU gives usb error.
have you installed the proper drivers on your pc for it to connect with the phone?
If so, when you attempt boot into fastboot and connect your phone through USB do you get the "device connected to windows" sound, like when plugging in and external driver or usb?
Because if not even that sound gets played it most likely means that your phone isn't even able to get into fastboot or hboot...
windows does NOT play any "device connected to windows" sound at all.
I have all drivers installed correct on my windows 7. My other HTC devices (desire s, wildfire, wildfire s) connects correctly to the PC and I can get the serial numbers of them using "fastboot devices" command.
Now on work, I tried a windows XP - same problem no connection - no sound.
This desire does NOT get into hboot nor fastboot. I think taht the "bootsector" is correpted.
I even used a Goldcard (made thru wildfire) - not working either.
So fixing it thru USB the normal way is not working.
Is there any way to force the device to boot up from SD card??
I have several backups of the phone system on my 8GB SD card.
You have to find a way to re-flash the hboot. That causes the blank screen display. May be a bad hboot install or something :0 Unless you have S-off and can be detected in fastboot, you can reflash hboot, otherwise you will have to try the blind flash method using PB.IMG. Best I could think of.
Sent from my PB99400 using XDA
@Jonicraw, thank you for your suggestion.
Where to get the HBOOT PBxxxx.IMG for this desire?
And how to flash it blindly, since I have black screen and no connection to PC.
AbuTarboosh said:
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Click to expand...
Click to collapse
im also same problem wont to solution
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Had the same problem. Mine could not charge at all and could not enter fastboot/recovery. Send the phone to HTC. I got back the phone with a new battery.
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Same s**t for me ... I tried everything you try and no results !
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
AbuTarboosh said:
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
Click to expand...
Click to collapse
No such things exists for the Desire.
Tell me what state the phone is currently in now?
Yet no solution for this problem...
STATUS for my device is:
Problem solved by changing the motherboard.
I hoped we could find a good solution for this.
I have the same problem but my phone is already on it's 3rd motherboard. I suspect the battery might be the problem but cannot get any answer as to what the voltages should be. I have already submitted a post headed Battery Voltage but it hasn't attracted a reply.
Hi there,
I got the same problem.
Can I send the phone to HTC even if I have rooted it? I also opened it a few weeks ago to replace the broken touchscreen. Do I still have warranty?
Greetings
Mika
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" ...
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Saenchai said:
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Click to expand...
Click to collapse
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
hkgrob said:
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
Click to expand...
Click to collapse
No, because i thik i have to unlock the bootloader fist to do that, or not?
Edit: Yes it is like that. Cannot flash roms without unlocking bootloader first. It gets stuck and command line shows error after "boot" command > bootloader locked.
I cannot do anything in ADB, only fastboot-menu (Advanced Utilities > Launch). But btw, i found this here, im just a bit afraid to use it. Rooting/flashing Roms WITHOUT unlocked bootloader and ADB
http://forum.xda-developers.com/showthread.php?p=43993722
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Pandae said:
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
Click to expand...
Click to collapse
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
xdhall said:
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Saenchai said:
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Click to expand...
Click to collapse
That confirms it. You're beyond my help. I'm fairly certain there's a way to unbrick from where you are. You'll just need someone with more experience than I have.
Sent from my Nexus 6 using Tapatalk 4
Saenchai said:
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
Click to expand...
Click to collapse
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Pandae said:
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in abother post here there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Saenchai said:
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in this post (and a few others) there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Click to expand...
Click to collapse
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
GSLEON3 said:
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
Click to expand...
Click to collapse
Thank you very much for this tip. I heard of it but was afraid that it would break seals. I will keep this in mind should i have another problem like this.
The device is now send to repairs. i hope to get it back soon...
Good luck! Sorry we couldn't give you a working remedy to do yourself.
Hey all, I'm just continuing on from this thread now I know its a KF2
So, my fastboot cable came today and was able to get to fastboot fine.
I haven't been able to find any fastboot commands to perform a full backup and currently cant boot normally to run the adb backup commands.
I have no idea what software version its running either or if it was in the middle of an OTA thats failed and caused this etc etc
Personally I'm convinced that its the battery that is the cause of the problems and am just looking for confirmation as I don't know that much about the Kindles.
This is the closet video I can find of the problem, except that you can press power and it will show the logo animation before 'dying' and showing the red battery symbol again: http://m.youtube.com/watch?v=JK3fjMZ3BjQ
So, a few questions:
Is it the battery that is dead?
Are there fastboot backup commands that I have overlooked?
Is there any point trying to continue with a OS restore?
Appreciate any help
;edit;
RARRRRR!!!!!
Ive had it in fastboot mode all day today and left it plugged into the mains.
Took a risk and threw some restore files at it. It booted fully this time and settings tell me its at 100% charge!
I'm now going to leave it overnight on standby and see how the battery level is in the morning.
If the battery turns out to be fine then Im considering rooting it and putting on the 2nd bootloader as a precaution.
If its dead then at least she can query Amazon about a battery replacement.
Im sure the battery was the cause of the bootloop as no matter how long it was charging for it never went off the red icon When I first tried this morning, even in fastboot mode it couldnt hold a charge long enough to get recongized by my PC.
I presume charging in fastboot has 'bypassed' anything else telling the battery its dead and to charge?
Hi everyone,
If your phone does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it.
If you have a last version of Windows 10 you can easily check if it is your case (You will have "Qualcomm HS-USB QDLoader 9008" device at your Windows devices' list.
How to Fix:
1. Download Drivers Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip and install it.
2. Download firmware link1 or link2
3. Install the driver
4. Unpack a firmware archive
5. Power off your phone by pressing Voice Down + Power Buttons (If your phone would be in this state too long the script would not works).
6. Start update_image_EDL.bat script - it will recreate all of the partitions
7. After the script will finish you will see the bootloader
8. Start script flashall_AFT.cmd - it will install firmware to the new partitions
9. Download fresh official firmware from asus site and put the archive at your memory card.
10. Start bootloader
11. Go to a standard recovery mode and install this firmware form the card
12. restart and repeat 10-11 (it will install software at the second state)
13. The problem is fixed. Congratulations!
Common problems:
Exception: System.DLLNotFoundException: DLL "QMSL_MSVC10R.dll": Module was not found. (HRESULT: 0x8007007E) can not be loaded.
Solution: You need to install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC. Thanks to Genim
can you please update the post with the links to the software? thanks
admirdante said:
can you please update the post with the links to the software? thanks
Click to expand...
Click to collapse
I tried, but this was my first message, so I could not manage to do it (I need at least 10 messages). However, I report it to a moderator teams. I hope they will do it for me.
Hi OP,
I have edited the links into first post for you. Enjoy.
Jerry
Forum Moderator
Thank you so much OP. You saved my phone. It's been in Edl mode for about 2 months. Now it's up and running again.
Guys if I can add one thing to the OP post .. Make sure you plug the phone in and let it charge for awhile before attempting. Once you get to the fastboot mode it will not allow you to continue if your battery is too low. I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process. I had to stop when I got to the fastboot stuff. And then continue after 2 hours on the charge.
st3wart said:
Thank you so much OP..
Click to expand...
Click to collapse
You are welcome. It took some time, so I decided to publish it.
st3wart said:
I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process.
Click to expand...
Click to collapse
In fact I can. I intentionally bricked my phone 3 times to write the simplest possible tutorial (my first solution was too long, because I could not understand why the problem was fixed).
I could not implement this solution when I had 6 per cent of battery, but it worked ok when I had 11 per cent. I can guess, that if it more than 10% - it is ok to implement this tutorial.
st3wart said:
Thank you so much OP. You saved my phone.
Click to expand...
Click to collapse
I'm glad it worked for you! I made it into FastBoot Mode, but when I select Recovery, it puts me back into FastBootMode.
Am I missing something or did something not work properly? Don't know how to flash the official firmware now.
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
st3wart said:
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
Click to expand...
Click to collapse
I did click it. It opened and closed cmd too fast for me to read though.
That's what it did when my battery was low... Go plug your phone in with the original charger for an hour and then go directly to your PC and plug it in and double click that file and it should do it's job.
Also check to make sure your antivirus isn't blocking the file. Mine blocked access to it for whatever reason.
I did click it. It opened and closed cmd too fast for me to read though.
Click to expand...
Click to collapse
It looks like st3wart's answer is correct. I faced the same behavior when my phone had 6 per cent of battery. This problem was fixed as soon as my phone had 11 per cent of the battery. Thus you should try to charge it before starting the script.
Furthermore, if you would still face this problem you can copy files fastboot_.log and test1.txt and share all of logs with us (or just find the error by yourself).
error from fastboot_.log:
"Writing 'partition:0'...
FAILED (remote: Warning: battery's capacity is very low)"
I did charge it for 2+ hrs with the original charger though. When I unplug it, turn it off and back on again it gives a low battery error. When I plug it back in, it goes straight back into FastBootMode.
But it seems to not charge the battery for some reason.
I did charge it for 2+ hrs with the original charger though.
Click to expand...
Click to collapse
Did you charge it in EDL mode?
For some reasons it did not work for me either. I just booted to bootloader, then power-off the phone and saw the animation of charging. You can also try to flash TWRP (using their instructions) and charge your phone in this mode.
If it does not work - please check your charger.
goldman1993 said:
Did you charge it in EDL mode?
Click to expand...
Click to collapse
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Click to expand...
Click to collapse
It is a bit abnormal behavior. I'm not sure, why it happens, to be honest. Have you tried to use different cable or charger (I'm not sure what is the reason, so I would try to change something)?
Genim said:
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
Click to expand...
Click to collapse
Press power button for long time to power off.
Then try flashing every image of that link:
https://forum.xda-developers.com/ze...ne-6-proton-kernel-v1-0-t3963948/post80405617
goldman1993 said:
Have you tried to use different cable or charger?
Click to expand...
Click to collapse
I have.
I unplugged the phone and let the battery run comepletely empty until the phone shut off.
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------
EMJI79 said:
try flashing every image of that link
Click to expand...
Click to collapse
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Genim said:
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Click to expand...
Click to collapse
Not good...
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
Click to expand...
Click to collapse
Well, we can try to brick it one more time (put it into EDL mode). Then you can try to power it up in this state and unbrick it one more time.
Firstly you need to load to bootloader and write
.\fastboot.exe --set-active=b
Then you need to reboot your phone.
I believe, that you would not successfully load to bootloader (IT would be the same EDL mode), so you can try to charge it in this state or try tutorial one more time. (After a 30 minutes of your charging process you can try tutorial one more time).
goldman1993 said:
.\fastboot.exe --set-active=b
Click to expand...
Click to collapse
I ran that command and it bricked the phone again.
But I did wait too long before running the script. I'm getting an Sahara error.
How should I proceed? Can I just run that line again?