Develop Bugs

[Q] How can I recharge my HOX again!

Hello there,
I have HTC ONE X, I was running CM10 Jelly Bean. But now I want to get the stock room back by using RUU!
Now there is NO working rom and Recovery, and my battery is less than 30% (this is what RUU keep saying!)
When I plug my phone to the wall it runs the bootloader even if I press POWER DOWN it keeps running the bootloader again when the phone is plugged to the charger! and the red light is there not blinking!
So, how can I recharge my HOX to be able to run RUU!
Check Attachments!

Dreadroid said:
Hello there,
I have HTC ONE X, I was running CM10 Jelly Bean. But now I want to get the stock room back by using RUU!
Now there is NO working rom and Recovery, and my battery is less than 30% (this is what RUU keep saying!)
When I plug my phone to the wall it runs the bootloader even if I press POWER DOWN it keeps running the bootloader again when the phone is plugged to the charger! and the red light is there not blinking!
So, how can I recharge my HOX to be able to run RUU!
Check Attachments!
Click to expand...
Click to collapse
You should still be able to juice up while the phone is off
so what you will have to do;
plug into mains power
choose power off in bootloader
phone will reboot (but get small amount of charge while its rebooting)
phone will power back on into bootloader
repeat power off cycle until you above 30%
unlock your bootloader again with your unlockcode.bin (fastboot flash unlock_token unlockcode.bin)
flash latest clockworkmod recovery (fastboot flash recovery clockworkmodlatest.img)
reboot into recovery and let it charge to full
then proceed with stock recovery / relock / RUU

bagofcrap24 said:
You should still be able to juice up while the phone is off
so what you will have to do;
plug into mains power
choose power off in bootloader
phone will reboot (but get small amount of charge while its rebooting)
phone will power back on into bootloader
repeat power off cycle until you above 30%
unlock your bootloader again with your unlockcode.bin (fastboot flash unlock_token unlockcode.bin)
flash latest clockworkmod recovery (fastboot flash recovery clockworkmodlatest.img)
reboot into recovery and let it charge to full
then proceed with stock recovery / relock / RUU
Click to expand...
Click to collapse
Do you mean i should keep pressing power down until i get some power to my battery!

check this plz
http://forum.xda-developers.com/showpost.php?p=29546293&postcount=42
now its over 14 hours without a phone, so stupid when im try to be smart

Yeah. Keeping powering down will give it juice. You won't be able to unlock while less than 30%
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
Yeah. Keeping powering down will give it juice. You won't be able to unlock while less than 30%
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
ok, its charging now
thanks a lot

bricked? DHD vibrates 3 times than flashes led

well **** me....
I just wanted to reboot my DHD and now i have thi outcome
Vibrates 3 times flashes orange lede no reaction anyhow
when ich charg it the lede lights up normaly but in intervals its flashing green orange green orrange than permanently again
Was on Blackice rom lightly OC´ed to 1.3 ghz
Well how ****ed am ? there is waranty left but when it´s the platine can thay notice that it was rooted anyhow?
thnx mates
Darkmind

Have you tried to boot into recover by power + volume down?

U hv gone in a different mode i dnt remember whts it called but it happens whn u press volume up and power button. Try taking out the battery n c if it boots..
Sent from my Desire HD using xda premium

Muikkuman said:
Have you tried to boot into recover by power + volume down?
Click to expand...
Click to collapse
adilrenzu said:
U hv gone in a different mode i dnt remember whts it called but it happens whn u press volume up and power button. Try taking out the battery n c if it boots..
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Xeleth said:
Pull out your battery for 2 minutes, put it back and try to boot. If that doesn't work then:
1) Power off your device (pulling out battery is the bulletproof way)
2) Press the volume-down button and hold it, then press the power button until you see a
white menu screen (bootloader)
3) Try to access recovery (navigate with volume-keys and powerbutton). If you cannot
access recovery then:
4) Download this file http://www.multiupload.com/BTJ8KY0KH9 and put it on your SD-card
root with an external memory card reader.
5) Boot to bootloader again and accept the installation
6) See if it works.
Click to expand...
Click to collapse
like to do all of this but it dont boot into bootloader doesnt mater if i push volume up or down and power on either way it vibrates 3 times than flashes led.
still... is HTC able to detect a rooted device even if it dont boot? and if so can they deny the waranty

This has happened to me 2-3 times. I definitely think it was because the battery didn't have enough charge. Try charging it for a little time. Have patience.
If its not getting charged I think there might be some problem with your charger, charging cable, charging port or battery.

if4ct0r said:
This has happened to me 2-3 times. I definitely think it was because the battery didn't have enough charge. Try charging it for a little time. Have patience.
If its not getting charged I think there might be some problem with your charger, charging cable, charging port or battery.
Click to expand...
Click to collapse
wll the battery was charged 100% just before that happened - and i tried another battery after this happend - because i was about to install a new rom. so it checks aut that when i try to hboot that its vibrates 7 times than flashes green led (when vol down + power) when i start normaly or when i try to vol up + power its vibrates 3 times
and flashes a orange led ( normaly it would be red but i was on blackice mod)
i have varanty left on that thing and it was rooted s-off when i send it in are they able to see this?
and could they deny varannty?
it was only slightly oc´ed to 1.3 instead of 1 ghz thera was chainfire installed too
Windows 7 trys to recognice the device when i plug it in per usb but cant find the right driver.
thanks for the ideas

Darkmind82 said:
wll the battery was charged 100% just before that happened - and i tried another battery after this happend - because i was about to install a new rom. so it checks aut that when i try to hboot that its vibrates 7 times than flashes green led (when vol down + power) when i start normaly or when i try to vol up + power its vibrates 3 times
and flashes a orange led ( normaly it would be red but i was on blackice mod)
i have varanty left on that thing and it was rooted s-off when i send it in are they able to see this?
and could they deny varannty?
it was only slightly oc´ed to 1.3 instead of 1 ghz thera was chainfire installed too
Windows 7 trys to recognice the device when i plug it in per usb but cant find the right driver.
thanks for the ideas
Click to expand...
Click to collapse
That's strange. When that happened to me it was fine when I charged up the battery.
Unfortunately, considering the fact that you can't even get into bootloader and that windows cant recognize your device I'd say you are pretty much bricked.
Do you get the splashscreen atleast? the one with the white HTC logo?
Are your volume keys working fine? I mean were they working fine before this happened?
Well I'm pretty sure that if they can't get to the bootloader, they have no way of knowing it was S-OFF. So they can't deny warranty in that case.
On the other hand, if the issue that caused this problem was indeed an issue that could've come only after someone S-OFF's then they might just deny it.
But I'm pretty sure you can fool them by maintaining that you don't know anything about how it happened.

Xeleth said:
Then download Android-SDK, open cmd, plug in your phone and type in "adb reboot bootloader".
See if that works.
Click to expand...
Click to collapse
Nope. Wont work. The computer has to recognize it atleast. In anycase, adb works only after the mobile boots past the splashscreen. And I think he might have already be knowing about adb since he's flashing ROM's.

Xeleth said:
Then download Android-SDK, open cmd, plug in your phone and type in "adb reboot bootloader".
See if that works.
Click to expand...
Click to collapse
see below :laugh:
if4ct0r said:
Nope. Wont work. The computer has to recognize it atleast. In anycase, adb works only after the mobile boots past the splashscreen. And I think he might have already be knowing about adb since he's flashing ROM's.
Click to expand...
Click to collapse
thats the point ther is no splash screen at all. i think this is a great myth the comunity cant solve by now. i read this a bunch of times many post to the 3 vibrations on boot or 7 vibrations ther is suggested that the mainboard passed out but what coused this if so?
otherwise i saw post on peaople were able to fix this bug and therfore could be no mainboeard failure be possible right?
i still try to figure that out gonna make a pol thread in DHD general because i have some suspissions to this and i want to see if this checks out.
thanks anyway

[HELP] Empty battery, no ROM installed

Looking for some help here My battery drained to 0% last evening while i was out. Went back home plugged it in to wall charger, quite sure that it'll boot shortly.. unlucky for me the phone booted for a minute or so and then powered off again. Did a small research today, and found some news about Nova kernel not having an option to charge while off, and an advice of one of the mebers to reflash kernelto one with this option. Dunno why but i did a complete wipe and now im stuck without any ROM and on JB splash screen (i've been using PA ROM) with an empty battery.
Need some help, anybody?

BobbyManifesto said:
Looking for some help here My battery drained to 0% last evening while i was out. Went back home plugged it in to wall charger, quite sure that it'll boot shortly.. unlucky for me the phone booted for a minute or so and then powered off again. Did a small research today, and found some news about Nova kernel not having an option to charge while off, and an advice of one of the mebers to reflash kernelto one with this option. Dunno why but i did a complete wipe and now im stuck without any ROM and on JB splash screen (i've been using PA ROM) with an empty battery.
Need some help, anybody?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2118921
Sent from my LT30p using xda premium

Try puting it to offline charging by,
When it boots turn if off via power button + power up. After the 3 vibrations then plug it in and let it charge.
Sent from my Xperia S using xda app-developers app

cant get in to fastboot nor flashmode. phone charges a bit turns on and then after a while it turns off..
flashtool says that i have no rom no kernel and the other thingy..
will try Li-polymers advice
As I've mentioned, before I wiped the device (dumb ass) i was on Nova kernel, after the wipe "S" im stuck on JB splash and nothing more. After that phone turns itself off and again to the splash..
Need some help desperately :crying:

Trying Hackberry's method atm, device gets listed in terminal when its on the JB splash -
[email protected]:~$ adb devices
List of devices attached
BX9036AF9B device
so it's doing something but i can't get into fastboot mode and flash a new kernel... is there any other way, option?
Or send it on warranty?

BobbyManifesto said:
Trying Hackberry's method atm, device gets listed in terminal when its on the JB splash -
[email protected]:~$ adb devices
List of devices attached
BX9036AF9B device
so it's doing something but i can't get into fastboot mode and flash a new kernel... is there any other way, option?
Or send it on warranty?
Click to expand...
Click to collapse
i had exactly the same same situation as you yesturday..... no rom battery 0%
plug it to your pc, open the terminal window where you got your stock ics17.elf ,type the code to flash it, meanwhile wait for the phone to boot that JB logo, when it does press power button + volume up button till 3 vibrations ( one vibration didnt work for me), the phone will reboot but you keep volume up button pressed, you'll se the blue led on ,press enter key in cmd to flash the kernel .
thats it it will charge.

@Ofcos mate, if it'll work, i owe U a keg xD
EDIT: Success!!!
what i did:
- flashed kernel via fastboot as Ofcos suggested
- waited 'till Nozomi will boot to splash again
- put it into fastboot again
- flashed recovery-nozomi.img
- fastboot reboot
- wait a while for it to boot again
- boot into recovery
- flash ROM zip as usual
Nozomi's charging and running!!!

[Q] "Unfortunately, the process com.android.phone has stopped."

Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.

I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...

MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?

matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.

MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img

matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.

MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly

have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904

ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.

MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging

ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?

MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you

ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).

MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/

ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...

MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go

ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!

MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem

HOX Shutting down,no recovery access [HELP]

Hi everyone,fisrt of all happy new year tooo all the mates in this awesome forum.
Well, my problem is kind of weird, ive never faced such a problem with my hox, or any other smartphone.
My phone was running well, then it turned off,it was discharged (my phone always shuts down whet it hits 10% or below,i need to take out the sim card or airplane mode so it dosent shuts down),ive plugged it to charge, icould see it charging,but..after that....my phone JUSTE DIED.
It suddenly started bootlooping, always says battery is tooo low to flash from the bootloader, and it never goes below the htc quietly brilliant logo,but when i try like a loot of time, it goes trought it, loads my rom, but as soon as i can see the home screeen,it turns off.....always....its been 3 days im stuck ..... ive looked alll arond the forum but couldnt find any fix....
I am able to access bootloader,but no recovery, ive tried to flash several different recoveries, but it always shows black screen(turns off) when loading recovery....
I still havent tried to re-lock the bootlader and go trought it all again flashing a stock rom and all (even if im pessimistic about if it is oing to fix it)
cuz i do really have preecious data on my hox, i would like to save the content of the internal storage before re-locking it.
Is it a software issue? batterie issue? but, ive tried discharging my hox while letting it in the bootloader, and...it just didnt shut off randomly, it kept alive for about an hour..... then i plugged my phone to charge ,left it be for the whole night, got the greeen light, and still the same problem.....
also(when i get the phone to load, ive seen the last time that my battery was like 53%, and then it just shut down..
i have also tried cvharging it via fastboot reboot method...same issue....
Please, help me guys, I really, reaaally need your help,i was ssooo satisfied with this phone, i cannot afford myself another one right know, and i dont have any warranty....im confused :crying::crying:
Phone running on Viperx 4.0.6 with original kernel.
Thanks in advance.

Please Im really stuck out here, i would like, at least, be able to access CWM or the storage so i could backup everything end then Re-lock and stock.

Try 'fastboot erase cache' to attempt to fix recovery shutting down.
Sent from my C6903 using xda app-developers app

tomascus said:
Try 'fastboot erase cache' to attempt to fix recovery shutting down.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Thanks for answering, i already tried that,but it changed nothing.
Now it's WORST, i was rebooting the phone again and again to gain access to the rom, just pushing the buttons and all, and then it rebooted with no screen... its like the screen is dead, the phone vibrates when you power it, but the screen shows nothing.....
Is the screen dead? So i do need to replace it? now my problem has grown worst...

thekkiller said:
Thanks for answering, i already tried that,but it changed nothing.
Now it's WORST, i was rebooting the phone again and again to gain access to the rom, just pushing the buttons and all, and then it rebooted with no screen... its like the screen is dead, the phone vibrates when you power it, but the screen shows nothing.....
Is the screen dead? So i do need to replace it? now my problem has grown worst...
Click to expand...
Click to collapse
go to bootloader and flash Philz recovery 5.15 mount the sd card and backup the information. when you go in Philz and mount the recovery wait 3-4 min SD card to appear on the computer.

Thant said:
go to bootloader and flash Philz recovery 5.15 mount the sd card and backup the information. when you go in Philz and mount the recovery wait 3-4 min SD card to appear on the computer.
Click to expand...
Click to collapse
Well, as i already mentioned, i do not have any access to the recovery, didnt try to flash phillz but now my phone isnt showing anything, means it vibrates but no screen

thekkiller said:
Well, as i already mentioned, i do not have any access to the recovery, didnt try to flash phillz but now my phone isnt showing anything, means it vibrates but no screen
Click to expand...
Click to collapse
Try to charge the phone, maybe from so many restart you f**ck up the battery and for this you have only short vibrate no power for the screen or use battery extendet pack. Second try to go in bootloader not to start the phonejust the volume down +power button

Thant said:
Try to charge the phone, maybe from so many restart you f**ck up the battery and for this you have only short vibrate no power for the screen or use battery extendet pack. Second try to go in bootloader not to start the phonejust the volume down +power button
Click to expand...
Click to collapse
I tried that too,well, i finished opening the phone to check on the battery state and all, everything seemed to be fine, next step is buying another battery and test another set of screen+digitalizer to check for the origin of the problem.
Insane how from trying to access the recovery it became changing battery and screen.
Thanks for all your tips, im going to check on it and keep you informed about my issue

thekkiller said:
I tried that too,well, i finished opening the phone to check on the battery state and all, everything seemed to be fine, next step is buying another battery and test another set of screen+digitalizer to check for the origin of the problem.
Insane how from trying to access the recovery it became changing battery and screen.
Thanks for all your tips, im going to check on it and keep you informed about my issue
Click to expand...
Click to collapse
Good luck from me:good: