Idk why, the problem resolved it self. I plugged it up to the cable and did nothing. Screen flashed once, then booted into BootLoader.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ok. So I was going back to complete stock using the RUU method from - http://forum.xda-developers.com/showthread.php?t=1705484
I followed everything and got up to locking the bootloader. I got this message when doing
fastboot oem lock
It said
C:\fastboot> fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.359s
C:\fastboot> fastboot reboot-bootloader
< waiting for device >
And now I have a screen with lines, kinda like a dead TV and a blinking led light. Phone won't respond to buttons or commands.
That means u did not connect the phone via USB in fast boot our ur device is not getting detected try installing htc drivers again
Sent from my One V
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.
So, got a problem with my m8
my m8 is the international unlocked version from amazon, 2 months old.
no root, no s-off, just stock with the last update from htc (4.4.3 i think)
last night, went to sleep, and charge my phone with 20% battery, then this morning when i woke up, the phone was in this screen:
replace the .
h.ttp://i.imgur.com/yYoTilH.jpg
Tried to reboot but with no luck, at the same menu i entered to hboot and some lines with "not found" (like 4-5 files) appeared on the screen, then in the new menu, i tried to enter the recovery menu, no luck and went back to fastboot menu, factory reset, no luck too.
After trying all of the menu options with no luck, i tried to use the fastboot to flash an stock image of the recovery, but always getting a signature verification failed.
Tried to flash the stock roms from here, but also the same error (signature verification failed)
So, if someone knows something to help me, please do
You cannot flash anything if boot loader is locked or you don't have s-off
Open on your pc where adb and fastboot files are a command window when the phone is connected to pc and type on fastboot erase cache...see if something happens and if it worked reboot it
One-M8-Master said:
You cannot flash anything if boot loader is locked or you don't have s-off
Open on your pc where adb and fastboot files are a command window when the phone is connected to pc and type on fastboot erase cache...see if something happens and if it worked reboot it
Click to expand...
Click to collapse
Code:
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.003s
worked (i think), but after reboot, stuck at fastboot again
guess ill have to take it to technical service
Hello everyone.
I am having this error while trying to flash the latest factory image.
Adb and fastboot seem propoerly configured as I have adb devices and fastboot devices working.
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time 5.011s
rebooting into bootloader...
FAILED (status read failed ( Too many links))
finished. Total time: 117.384s
Any help would be appreciated, because I am lost on this one.
SDK is fully updated and doing everything as I did to flash 5.0.1
Thanks in advance.
Can't help with ADB or Fastboot but I can suggest dirty flashing this stock, rooted rom by scrosler found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Worked great for me. Good luck!
Mine failed the first couple of times too, but on the third attempt it went through. However, it turns out that I had failed to turn on the ADB bridge on the first one, and I guess it was still coming up on the second.
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
yosmokinman said:
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
Click to expand...
Click to collapse
Very true, except that it uses adb to initially reboot the tablet into fastboot mode.
It would probably skip that step if you were already in fastboot mode, but if the OS is running, the flash-all script will attempt to restart the device by running adb reboot bootloader.
That said, if ADB isn't working, checking the cable and drivers is the next step.
Getting into the bootloader doesn't require adb. Use the hardware buttons.
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
sorry delete!!! try fastboot flashing unlock_critical
lucky_strike33 said:
did you go to developer and tick on to unlock bootloader?
Click to expand...
Click to collapse
Sure did. OEM unlocking is ticked.
lucky_strike33 said:
sorry delete!!! try fastboot flashing unlock_critical
Click to expand...
Click to collapse
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
Try a different cable?
Unfortunately I am at work and only have the C to C cable that was in the box.
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Az Biker said:
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Click to expand...
Click to collapse
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
xxnirvana69xx said:
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
Click to expand...
Click to collapse
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
canemaxx said:
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
Click to expand...
Click to collapse
Pm instead
xxnirvana69xx said:
Found this to possibly get you an older version of the platform tools...
"Well, you could use direct link, like
Click to expand...
Click to collapse
I started off with what I was using with my pixel XL and that didn't work and I have installed about 10 different version thus far and still nothing
I basically ended up using another cable, different version of adb, and another computer. Hard to tell what the problem exactly was since I changed 3 things at the same time between it not working and working. My guess is the cable and/or the computer.