[Q] Fastboot problems - HTC One X

Hi guys,
Basically I'm in a bit of trouble trying to get my one x back to stock. After running the RUU for my phone, it exited with an error saying that the device suddenly could not be found anymore. After this I tried to run the RUU again but now the error message about the battery level being below 30% came up. Anyway, after this I tried unlocking my phone again to go back to a custom rom and at least have a working phone however I can't do anything through fastboot because no matter what command I type in, it keeps telling me the following:
C:\fastboot>fastboot getvar version-main
getvar:version-main FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
C:\fastboot>fastboot oem readcid
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
I checked the usb connection and the device seems to be recognized:
C:\fastboot>fastboot devices
HT24CW105437 fastboot
Could someone help me as to how to move forward? I also can't seem to charge my phone. I left it on AC charging for about an hour in fastboot mode and tried running the RUU again but the same battery level message came up.
Thank you!
uxyyy

For CID command is:
Fastboot getvar cid
For flashing:
Fastboot flash boot boot.img
Fastboot flash recovery recname.img
Cache clearing:
Fastboot erase cache
Sent from my HTC One X using Tapatalk 2

Hey,
Yeah I know the commands but unfortunately I wasn't kidding when I said I can't do anything via fastboot. :/
Even just trying to get the CID or flashing the boot.img returns:
C:\fastboot>fastboot getvar cid
getvar:cid FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4862 KB)...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
So there must be something else that's broken.

Try this..Download fastboot files again,put phone in fastboot..And on fastboot files hold shift and right click and open command prompt here..
Sent from my HTC One X using Tapatalk 2

Still the same problem.
Also, I left my phone to charge overnight and got the green LED to light up however when trying to run the RUU it still tells me that the battery level is below 30%.
Any fastboot commands still return the exact same error message as before. I honestly don't know what I could do atm.

Related

HOX failed start+no dispay

Hi Guys,
I have a HTC One x that wont boot up, I had tried installing a custom rom earlier and not wenever I try to boot up there is no dispaly on the screen except for a vibration and the lights at the bottom of the screen blinking several times.
And one more thing, when I try to charge the battery using this script
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
This, below, is the response I get...
getvar:battery-voltage FAILED (command write failed (Unknown error))
finished. total time: 2.225s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
Somebody, anybody Please Help.
jeffkang said:
Hi Guys,
I have a HTC One x that wont boot up, I had tried installing a custom rom earlier and not wenever I try to boot up there is no dispaly on the screen except for a vibration and the lights at the bottom of the screen blinking several times.
And one more thing, when I try to charge the battery using this script
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
This, below, is the response I get...
getvar:battery-voltage FAILED (command write failed (Unknown error))
finished. total time: 2.225s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
Somebody, anybody Please Help.
Click to expand...
Click to collapse
Can you boot to recovery?
Jontebert said:
Can you boot to recovery?
Click to expand...
Click to collapse
No, I have not been successful. The most I get is the vibration and blinking lights.
jeffkang said:
No, I have not been successful. The most I get is the vibration and blinking lights.
Click to expand...
Click to collapse
Are you using power + vol- to boot into recovery?
Power + vol+ soft resets the phone when held for 10 seconds or so resulting in the buttons flashing several times and the phone vibrating.
If your already aware please ignore!

Wildfire jammed in FASTBOOT

Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1002.0000
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.20.10
Click to expand...
Click to collapse
BukeR00 said:
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
Click to expand...
Click to collapse
Does it boot Into hboot or fastboot specifically? Also do you have an sdcard in the phone? And lastly when you plug in the usb cable to issue commands does the phone change to hbootUSB or fastbootUSB at all and does Windows detect and Install drivers?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
BukeR00 said:
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
Click to expand...
Click to collapse
OK please try without the card in also when you are in fastboot USB can you issue the command fastboot getvar all please and see if it works.
Sent from my Nexus 7 using Tapatalk 4
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ###########
INFOimei: ###########
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
BukeR00 said:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ##########
INFOimei: ###############
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
Click to expand...
Click to collapse
I should have said, block out your imei and HTC serial number like I have. You never know whos watching...
Anyway, your bootloader is still unlocked so ruus wont flash. You can use the command fastboot oem lock to relock the bootloader. But, it's unlikely that it will work as you have an upgraded hboot. If I was you I would I would extract the Rom.zip from the ruu. Then extract that Rom.zip and you should end up with several images and some .nbh files. place the boot.img, system.img, data.img Into your fastboot folder. Then you going to want to format the phone with fastboot and then flash the phone with fastboot. http://androidforums.com/one-s-all-things-root/714676-list-fastboot-command.html here is a command list but I will tell you what I think it should be, and if you hit a snag refer to the link. So the commands should be in this order assuming you are CD'd to your fastboot folder
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
Then assuming it all goes well then issue these commands
fastboot flash system.img
fastboot flash data.img
fastboot flash boot.img
fastboot flash boot.img
fastboot reboot
Yes that flash the boot.img twice is not a typo all going well after this you should able to boot up. if you hit any big problems just hit the thread pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
BukeR00 said:
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
Click to expand...
Click to collapse
Ah. This could be problematic. I should have been clearer, I didn't mean for you to lock your bootloader again, I was simply informing you it would need to be locked for an ruu to run. None of those commands will work while the bootloader is locked. If you were the one to unlock the device the you can unlock it again assuming you have the unlock_token.bin, using the same fastboot command again. If you didn't you will have to go to www.htcdev.com and make an account, then go to bootloader unlock, select wildfire buzz and ignore the bootloader update, as you already have it. (Skip should be near the bottom.) Then follow the instructions and get the bootloader unlocked again. Then issue the commands excluding the lock bootloader one and the flash data data.img as you don't have it. Its not a problem though, I was just covering all bases, incase it did have a data.img in there make sure you still do the data format though!
Sorry for the confusion
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
BukeR00 said:
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
did you get the bootloader unlocked again? fastboot commands will only work on unlocked bootloaders.
Dont worry about the data.img, you do not need it. i simply added it incase the ruu had it and you got confused. again, it is not required.
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
C:\sdk\sdk\platform-tools>fastboot format boot
formatting 'boot' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format system\
formatting 'system\' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
BukeR00 said:
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
Click to expand...
Click to collapse
hmmm. well if we cannot format the partitions then we are not going to have much luck :/
ok lets try a different tactic. download this and rename it to just recovery.img . then place it into your adb folder and then issue the following command via fastboot.
Code:
fastboot boot recovery.img
hopefully this will allow you to boot into clockworkmod recovery. when you enter clockworkmod recovery use the volume buttons to move and the trackball to select, power is back. format everything. then try to mount your sdcard using advanced/mount storage or sdcard, something to that effect. then place this file onto it. all going well you should be able to then flash this rom. dismount the usb storage, then go back to the main menu (power button) then go to flash/install, select choose zip and then the zip file we placed there. hopefully the recovery will install without issue. then, open the copy of the rom you downloaded on your pc and extract the boot.img. reboot the phone into fastboot and then use the command fastboot flash boot boot.img
all going well this rom will boot and you will have a working phone again.
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
BukeR00 said:
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
Click to expand...
Click to collapse
it should boot into cwm automatically, no button intervention required.
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
BukeR00 said:
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
Click to expand...
Click to collapse
Unrevoked doesnt s-off it only roots and flashes a recovery.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

[SOLVED] Won't boot and random fastboot errors after upgrade attempt

Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!

Cannot flash recovery

OK I have a problem. Till now:
1. Installed drivers
2. Bootloader unlocked
3. ADB enabled. PC authorised.
4. OEM unlocking permitted confirmed.
5. Command fastboot devices shows phone connected in fastboot mode.
EDIT: Solved. Experimented with different drivers on different laptop.
Now trying to send official twrp with command fastboot flash recovery recovery.img and I get error:
sending 'recovery' (18680 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
Can't seem to get a solution to this
Any help?

Help! I think I've bricked my phone!!

Hi,
I think I have bricked my old htc one x! I have tried to fix the issue by spending the last few days reading through and trying as many of the solutions on this site as I can but I seem to be constantly running into roadblocks in my attempt at fixing it.
Basically I had cyanogenmod on it for the last 3 years and had lent it to my mother to use (I could never get google play working but everything else was ok), after years of thinking I should really put some stock RUU on it for her, because cyanogen is different to what all her friends had and she couldn't do things in quite the same way.
I relocked the bootloader and started to install an HTC X RUU for t-mobile (first mistake - I am in australia) and this did not work, I then downloaded what I think is a compatible RUU and the battery had dropped below the minimum 30% I needed, and was slowly losing power, I tried to unlock the bootloader again so I could fix it but the battery was too low to unlock it (I tried to use "fastboot flash unlocktoken Unlock_code.bin") and the phone seemed to alternate between a restart loop and just being stuck in the bootloader.
This is the error I get when I try to unlock it
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for any device >
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
OKAY [ 0.138s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s"
After researching and looking at similar issues, the only fix seemed to be to use a bat file
"@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
I've spent all day running this trying to get the phones voltage up to 3680 so I can then unlock the bootloader and put on a customer clockwork or something so the phone can charge from fastboot/bootloader or just black screen, I only need 10% I believe however the bat file works great from 2700-3500 or so, (this takes maybe 3 hours) then the bat file bombs out with errors such as
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>ping /n 6 localhost 1>nul
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>goto start
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot getvar battery-voltage
< waiting for any device >
getvar:battery-voltage FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s"
Is there any help anyone could give me ? I honestly have looked all over the place seeking a fix but am having real trouble
Any help would be appreciated !
Did you at any time think of shutting the phone off, or leave it to discharge until it shuts of by itself? This way you could fully charge it as long as it is turned off, power it on holding volume down and then try to unlock again.
If you succeed you could flash the latest TWRP 3.0.2-0, and flash a CM21.1 (new layout), as well as the according GApps to obtain all needed PlayService files. If done so after a reboot you could setup a Google account and everything else. But make sure to flash ROM and GApps in one run. Don't reboot prior to flashing the appropriate GApps which would, in case of my example, be OpenGApps, ARM, 6.1 pico.
Sent from my HTC Pixel XL using XDA Labs
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?
grim61 said:
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?
Click to expand...
Click to collapse
I'd stick with the latest available CM 12.1 ROM, or alternatively XenonHD found in the original Android development section. I'd recommend to download the appropriate GApps on OpenGApps.org and flash ROM and GApps in one single step. On XenonHD Nova launcher is used as far as I remember. That on is quite stock Android like, and with GApss installed all should work fine. So I'd recommend using XenonHD.
On my One X the battery died two or three month ago and I finally got it opened up. So I'm now waiting for a new battery to install and finally flash it again.
Sent from my htc_pmeuhl using XDA Labs

Categories

Resources