• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help My HTC One X wont charge or power on but when plugged in boots into bootloader!

  • Thread starter Thread starter Android Question
  • Start date Start date
A

Android Question

Guest
Hi, I have noticed that I can not reboot my phone to install updates ect... and when I try to reboot it takes me to the bootloader menu. Then a few days ago it went completely dead on me and I went to turn it on but it wouldn't. So naturally i plugged the charger in and it booted up after 5 seconds but into the bootloader. I then pressed reboot on bootloader.. turns of then launches back into bootloader. The same is for the other options like factory reset and recovery. I plugged it into my pc but my pc would not recognise it. Help?:(
 
I'm around but on the road until later.

I'll check back this afternoon and help if I can, unless someone else has helped sort it out first.

Were you rooted or did this just hit you out of blue, and you're phone is stock?

Will answer later.

Welcome to the forums!
 
I'm around but on the road until later.

I'll check back this afternoon and help if I can, unless someone else has helped sort it out first.

Were you rooted or did this just hit you out of blue, and you're phone is stock?

Will answer later.

Welcome to the forums!
Its rooted and its the endeavoru model. My phone is stock but has recovery to factory reset from
 
Its rooted and its the endeavoru model. My phone is stock but has recovery to factory reset from
OK that's an answer about recovery but not to my question. :D

Are you on stock or custom recovery and if custom, which one and which version?

And I'm not clear - if you try to enter recovery, it reboots? Is that correct?
 
OK that's an answer about recovery but not to my question. :D

Are you on stock or custom recovery and if custom, which one and which version?

And I'm not clear - if you try to enter recovery, it reboots? Is that correct?
im on stock and when i enter recovery it reboots into bootloader
 
OK, so I take it you rooted with some method other than HTCdev.com unlocking?



No pressure, but I'm not going to be able to help until I have a clear picture of the status, cheers. :)
I think what's happened is that my version of android I am running currently is damaged but I have no recovery to factory reset from. To root the phone I used an app called SuperSU. There is a very likely chance that it is bricked because when it was working It would lag allot and applications would crash/force close for no apparent reason. maybe if I some how downloaded the stock rom for the phone and install it it would start working again. Do you know any good tutorials on youtube or a forum that show me how to get the stock rom on the htc one x? cheers :thumbsupdroid:
 
I asked for the top of your bootloader screen contents twice. No answer.

I asked if you used HTCdev.com - I got SuperSU and other theories why it's broken.

I asked for good reason, I help unbrick several HTCs a week, week in, week out, but no matter. Let's do it your way.

Let me answer your three questions - can it be recovered to stock factory, can I recommend another forum, and is there a youtube.

The stock rom to recovery everything that you've asked for is called an RUU.

It's important to know the details at the top of your bootloader screen (as a beginning, there are more things to know too) to know which one will work and not turn your phone into a paperweight.

Here's a guide I found googling, it looks pretty good, be careful because it's not up to date, and as requested, it's at another forum -

http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone

Here's a youtube.


Best wishes!
 
I asked for the top of your bootloader screen contents twice. No answer.

I asked if you used HTCdev.com - I got SuperSU and other theories why it's broken.

I asked for good reason, I help unbrick several HTCs a week, week in, week out, but no matter. Let's do it your way.

Let me answer your three questions - can it be recovered to stock factory, can I recommend another forum, and is there a youtube.

The stock rom to recovery everything that you've asked for is called an RUU.

It's important to know the details at the top of your bootloader screen (as a beginning, there are more things to know too) to know which one will work and not turn your phone into a paperweight.

Here's a guide I found googling, it looks pretty good, be careful because it's not up to date, and as requested, it's at another forum -

http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone

Here's a youtube.


Best wishes!
***UNLOCKED***
ENDEAVORE PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MI CROP-None
RADIO-5.1204.163R.30
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot: enabled
MODEM PATH :OFF
Nov 16 2012< 18:32:39
Battery level is too low to flash

FASTBOOT USB


Sorry I'm being daft I some how missed the messages were you asked for what it says at the top of your bootloader screen. And I did use www.htcdev.com
 
OK, thank you! :)

That just saved a lot of time, believe me.

From that, it's *possible* that we can find the right RUU.

All I need now is your phone in FASTBOOT USB mode (connected to your pc) and the results of this run from a command window in whatever folder your pc fastboot is installed -

fastboot getvar all

Alt+space, E for edit, select all and copy from the command window, paste results here.

Be sure to remove your meid and serial numbers - never post those ok.

You must have had fastboot in order to HTCdev.com unlock. If you got yours from HTC directly, it may have a modified name so the command might be -

htc-fastboot getvar all

Windows Explorer, shift+right click on the folder containing fastboot, choose Open command window here if you're not comfortable navigating inside the command window.

If you got unlocked using an all in one tool, I'm sure it was very nice but I simply never trust them for this level of work based on past experience. In such a case, download the Mini-SDK here, unzip the sdk-tools.zip file, and your fastboot will be in the sdk-tools folder. All above instructions and tips will apply.

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

I'm helping others with their phones (one of which is another One X fwiw) so I'll respond after your reply as soon as possible.

Don't hesitate to ask questions on any of the above!
 
OK, thank you! :)

That just saved a lot of time, believe me.

From that, it's *possible* that we can find the right RUU.

All I need now is your phone in FASTBOOT USB mode (connected to your pc) and the results of this run from a command window in whatever folder your pc fastboot is installed -

fastboot getvar all

Alt+space, E for edit, select all and copy from the command window, paste results here.

Be sure to remove your meid and serial numbers - never post those ok.

You must have had fastboot in order to HTCdev.com unlock. If you got yours from HTC directly, it may have a modified name so the command might be -

htc-fastboot getvar all

Windows Explorer, shift+right click on the folder containing fastboot, choose Open command window here if you're not comfortable navigating inside the command window.

If you got unlocked using an all in one tool, I'm sure it was very nice but I simply never trust them for this level of work based on past experience. In such a case, download the Mini-SDK here, unzip the sdk-tools.zip file, and your fastboot will be in the sdk-tools folder. All above instructions and tips will apply.

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

I'm helping others with their phones (one of which is another One X fwiw) so I'll respond after your reply as soon as possible.

Don't hesitate to ask questions on any of the above!
I think my phone is done for because i try to install fastboot drivers but in cmd when i type adb devices it cant find my phone. So basically even though my pc knows my phone is connected as is shows up in device manager as htc android interface it dosent show when in the fastboot cmd. Thanks anyway :)
 
I think my phone is done for because i try to install fastboot drivers but in cmd when i type adb devices it cant find my phone. So basically even though my pc knows my phone is connected as is shows up in device manager as htc android interface it dosent show when in the fastboot cmd. Thanks anyway :)
OK, I'm very confused because at no point did I ask you to use adb.

Did you put the phone into FASTBOOT USB mode?

Power off, then hold volume down while powering on.

The phone should say FASTBOOT at the top. If it says HBOOT at the top, tap the power button as instructed on screen to select FASTBOOT, then plug in to PC.

If your pc could see and for example download pictures before you probably don't (or didn't at this point) need fastboot drivers.

In fact, because you unlocked using HTCdev.com, I'm absolutely certain that your phone needed no other drivers - and that's why I didn't mention them in my original instructions.

I'm very sorry if you read about the drivers in the Mini-SDK post and that led you to that step.

But I said nothing about adb - because it's not involved for any of you required.

If you want to try again, great, I'll try to help. As I said above, last thing - ask questions if you're not sure. That means ask in advance.

If you want to insert other commands, search for other ideas out there, or tinker around instead of trying it as I request, then yes - your phone is done for and sorry about that.
 
OK, I'm very confused because at no point did I ask you to use adb.

Did you put the phone into FASTBOOT USB mode?

Power off, then hold volume down while powering on.

The phone should say FASTBOOT at the top. If it says HBOOT at the top, tap the power button as instructed on screen to select FASTBOOT, then plug in to PC.

If your pc could see and for example download pictures before you probably don't (or didn't at this point) need fastboot drivers.

In fact, because you unlocked using HTCdev.com, I'm absolutely certain that your phone needed no other drivers - and that's why I didn't mention them in my original instructions.

I'm very sorry if you read about the drivers in the Mini-SDK post and that led you to that step.

But I said nothing about adb - because it's not involved for any of you required.

If you want to try again, great, I'll try to help. As I said above, last thing - ask questions if you're not sure. That means ask in advance.

If you want to insert other commands, search for other ideas out there, or tinker around instead of trying it as I request, then yes - your phone is done for and sorry about that.

what do you mean by pc fastboot and i may not have it as i have changed pc since unlocking the phone
 
what do you mean by pc fastboot and i may not have it as i have changed pc since unlocking the phone
OK.

You got the Mini-SDK I linked?

The pc fastboot (as opposed to the phone's fastboot mode) is in there.

Try the fastboot getvar command after getting into FASTBOOT USB mode, following the steps I listed.
 
OK.

You got the Mini-SDK I linked?

The pc fastboot (as opposed to the phone's fastboot mode) is in there.

Try the fastboot getvar command after getting into FASTBOOT USB mode, following the steps I listed.

F:\Windows Apps\Desktop\sdk-tools\sdk-tools>fastboot getvar
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.

default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

F:\Windows Apps\Desktop\sdk-tools\sdk-tools>
 
I'm not going to repeat commands on every post for you.

When I said "the fastboot getvar command" I meant what I said the first time.
i did. I entered the cmd and typed fastboot getvar and hit enter and this is what it came up with...


F:\Windows Apps\Desktop\sdk-tools\sdk-tools>fastboot getvar
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.

default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

F:\Windows Apps\Desktop\sdk-tools\sdk-tools>
 
F:\Windows Apps\Desktop\sdk-tools\sdk-tools>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s

F:\Windows Apps\Desktop\sdk-tools\sdk-tools>
 
Back
Top Bottom