Exuse me for my bad English, because A'm from Russia ...I want to return to the offiсial rom of HTC ONE X. But i have any problems... When I do
cd c:\Android \Android>fastboot flash recovery recovery.img
sending 'recovery' (5742 KB)...
FAILED (remote: (00120000))
finished. total time: 0.002s \Android>fastboot oem lock ...
FAILED (unknown status code)
finished. total time: 0.000s \Android>fastboot oem lock ...
OKAY [ 0.000s]
finished. total time: 0.000s \Android>
Then i run official rom and it has problem...mistake [140] Wrong version of loader. Is it anybody help me what to do with it?
http://forum.xda-developers.com/showthread.php?t=1660807
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 ?
Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
filking said:
Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
Click to expand...
Click to collapse
That looks bad, try a different USB port, if possible a different cable and even a different PC, don't use a usb hub or usb3 port, if none of that helps, it's probably a bad EMMC, see this thread and see if it is.
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
filking said:
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
Click to expand...
Click to collapse
Did you try the thread I linked and do what it said to test if you eMMC is fried? If it is, only a hardware repair will fix it.
Hi,
I tried that link. I go through the recovery mode and get the android system recovery and the :
e:cant mount /cache
......
etc.
I issue the adb shell command and get
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Any more hints?
filking said:
Any more hints?
Click to expand...
Click to collapse
Mate, there is obviously some connection problem between your PC and your device. The most likely of all: it is a USB driver related problem. I'm trying to help last few days to another forum mate @PieceofSlice who has almost identic problem. He is on 04.01 bootloader and uses Windows 7 PC.
Please take my advice and don't try to flash bootloader anymore until you are 100% sure that the fastboot connection works perfectly fine. If your bootloader gets erased and the new one doesn't get flashed, the Tab is hard-bricked and only JTAG service will can revive it. As long as your bootloader is OK, you will get your tab working again, don't worry.
Actually it would be worth it to install Linux besides Windows and execute fastboot directly from there. Linux needs no drivers and always works. IDK if Ubuntu could also work if you run it in a Virtual Machine in Windows.
tetakpatalked from P5110
Thanks for your reply.
Actually, the more I think about it, the more I think it is the connection socket on the tablet that is faulty, rather than the link/pc.
I've had occasions when moving the cable near the socket, (which appears a tad loose), has caused the tablet to stop charging then start again.
This tablet is a replacement for a broken N7 (2012) that I got from a retail shop in the UK. As they gave me a new receipt, this tab is covered under year warranty. If I take it into the shop, they will refund and replace, no problem.
My last question is, how can I ensure that all info is wiped. (pretty sure it already is), but as the stock/unroot failed, it prob didn't actually overwrite anything.
ta
Just one crucial question: is your bootloader locked?
If it is, you can give it back. They will unbrick it the way that they will totally wipe whole internal memory before they flash a factory image.
tetakpatalked from P5110
It is unlocked.
Not sure this retail shop will know what to look for when I return it, turn it on, and it doesn't boot. That in my mind is broken and they will prob see it that way.
If they do spot it, or refuse.. I will take it away, rethink, and return to another branch, lots locally.
Unless, NRT will let me remove the lock... maybe....
filking said:
It is unlocked.....
Click to expand...
Click to collapse
Try to execute in the bootloader mode "fastboot oem lock"
tetakpatalked from P5110
OK, all guys with fastboot conectivity problems, it really makes me sad to read about your issues and I hate to hear about bootloops and desperate forum mates!
Therefore, I think this will be solution for most of you: I will post here a new guide within less than 24 hours how to install ADB and fastboot in Ubuntu/Linux OS. If you already have installed Ubuntu OS, it takes only 2 min to install ADB and fastboot.... and IT WORKS THERE!
Linux is in general much better than Windows for flashing Android devices. And it needs no stupid, nasty drivers so the things can't go so easy wrong.
Use this time and already install Ubuntu aside your Windows. In most of cases it works flawlessly. You will have dual boot possibility. Please check WWW how to do it, it costs bit of time but it is really easy afterwards.
tetakpatalked from Nexus 7
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Yep, connection problems....in very most of cases it is related to unproperly working drivers = as I said: not Windows but "Loose-dows"
tetakpatalked from Nexus 7
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Mate, here is my promissed thread:
http://forum.xda-developers.com/showthread.php?t=2726287
If Ubuntu won't flash successfully, we have a hardware related problem and it has to be fixed in the service.
tetakpatalked from Nexus 7
Looking now..
Thanks a lot.
no upgread mode vol up+ + vol- + power / no fastboot to ececovery
fastboot info
bootloader)
OKAY [ 0.005s]
finished. total time: 0.006s
Reading Mobile Version Info
...
(bootloader) :Error: /preas/xxx not found in /product/hw_oem/EVR-AL00/par
FAILED (unknown status code)
finished. total time: 0.006s
Reading Mobile Bootloader Lock Info
Could Not Find C:\Program Files (x86)\Bonjour\mdnsNSP.dll.dat
The directory name is invalid.
...
FAILED (command write failed (Unknown error))
finished. total time: 5.001s
Reading Mobile Battery Info
...
FAILED (command write failed (Unknown error))
finished. total time: 0.000s
Reading Mobile vendor and country Info
< waiting for device >
vendorcountry: all/cn
finished. total time: 0.021s
all is done
Top
Hi all, really annoying problem where my phone is stuck in a fastboot loop. The phone loads into fastboot and if it is plugged into the PC via USB it keeps rebooting into fastboot. I can use this command 'fastboot oem fb_mode_clear' when it's about to load and it sometimes causes it to stop rebooting. As soon as I input another command like fastboot devices, it begins the loop again. It also only shows ?????? as the device name.
Is there anything I can do if I do manage to get it to stop rebooting while it's connected to the PC? Thanks.
An example of the rebooting -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Here's what happens when I try and flash the factory image:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
W/ziparchive(133904): Unable to open 'image-taimen-opd1.170816.010.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.010.zip': I/O error
Press any key to exit...
This is the best I've done I think...
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.009s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.199s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1866 MB) to disk... took 9.931s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.077s
archive does not contain 'vendor.sig'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.012s
Press any key to exit...
Hi, in case you stumble on this self-rambling thread looking for an answer, it turns out changing the port fixed it. In my case I plugged it into a usb-c hub that had usb-a ports and that allowed it to work properly. God knows why, but worth a shot if anybody is having issues with their PC's usb ports.