Hy everybody,
I ve got a weird trouble.
What i wanted to do was to flash hboot so i went to bootloader and then i had to go and leave the phone on bootloader screen
without turning it off and with no power connected to it. When i came home again i noticed that the phone was off and now i got this trouble.
I m stuck at bootloader. If i try to get to recovery it fails and then the phone just reboot constantly
When i try to flash a new recovery over cmd fastboot flash recovery rec.img i get this message failed battery low.
When i adb oem rebootRUU i get to the black htc screen but when i try charging it turns also off after a while and if i try sending
the updated firmware it also tells me low battery.
Ok so i need to charge my battery but thats the trouble, when i plug the cable (over pc or power) the phone begins to charge (red light turn on)
and then it turn on my phone to bootloader and then after a few minutes it turns off because i think the battery is dead again.
Any good advice that could help? I m sure i could recover my phone again but as long as i can t charge it i think i m stuck.
Is it possible over fastboot or maybe adb to tell the phone to just simply charge my battery?
If im not wrong my cid is htc_102, if a RUU could help me it would be good but i don t really now which one to download for my
device. I used to have cyanogen mod 10 and i wanted to change to try some sense roms but i need needed to flash hboot
in order to get things working and now ..... u already know.
Thanxxx in advance.
Okay i fixed it.
Related
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...
FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up
hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)
Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA
Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.
Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/
hello guys im having a problem with my HTC ONE X i tried to flash it with android HD ROM and then my phone died i cant enter bootloader or recovery its stuck on HTC logo and every 1min lets say it restarts i also cant charge my battery when i try to flash with RUU it says 30% battery
now i cant go into bootloader im not able even to use RUU but even if i use it says 30% battery error
now like i said its Stuck ON HTC logo and keeps restarting i cant enter bootloader or recovery im totally STUCK!!!!
can someone please help me i ****ed up my new phone
ps: i tried with volume down and power but still cant enter bootloader or recovery..
keep your phone turned off,charge your phone(till 100%) then try to enter into bootloader menu..
Trying my hardest to flash my HTC One X back to stock in order to sell it, but am hitting brick walls (pun not intended) all over the place. I tried to install the RUU earlier, but it failed as the version I have is newer than the version it was installing, and with S-On seeminlgy it won't ignore that fact.
After this process failed, the phone has been stuck in a Hboot loop, no matter what i choose it reboots constantly to hboot. The phone is hardy gaining charge even powered by mains, and as such i have been unable to unlock the phone again as yet, is that something i need to do before i can get any further?
My current plan as explained by someone on here is to flash a nandroid backup of my CID at stock, but to do that i need to somehow get the display to turn off and let the phone charge, and hopefully escape this boot loop.
Any help appreciated, as soon as i plug the usb cable in, the phone turns on into hboot with the BRIGHT white background and all the options, so uses quite a lot of power / gets quite hot
Bootloader unlocked, flash this recovery asap !
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
Enter it and put the phone on charge. Leave it alone, it will charge the battery while the phone sits in the recovery.
If the bootloader is relocked you unlock it by flashing the unlock code.bin file which you got from the HTC dev site the first time (maybe it's still in your email)
Sent from my HTC One X using XDA Premium 4 mobile app
Im stuck during root.. I did the bootloader unlock.. and when I was loading the recovery in softboot mode, it was done, after that when i booted in hard boot, I think probably (I'm not sure) my data cable might unplugged for a while.. after this my cell got stuck and back light of the cell was on.. And it was stuck.. After that battery got drained and phone is dead now.. what to do Im so much worried now.. Please help..
How to charge and switch the mobile to normal state?? cause its not charging with charger now, charging light keep on blinking..
So Im out of this misery now, I have managed to reboot my device via adb, and its working but now when I enter into recovery mode, it just shows a black screen, it does not give any option to select zip file, I have already put in the root of device.. How can this be solved??
If you have CWM recovery here is a alternate way -----> when I had flashed CWM recovery it was showing me black screen as u see. I don't know how to solve that. but you can flash TWRP recovery. I have successfully overwritten TWRP recovery over CWM...!!!!
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?
Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.