Develop Bugs

Vibrates 7 times

I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.

I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?

I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.

You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/

Computer discovers nothing when I plug in the phone.

Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait

Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.

U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait

Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry

Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry

Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..

Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business

Yea got warranty and reciept and all that, so np there

Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement

Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...

Bricked htc one x!!!!!!!

HELP!!
I bricked my phone after Flashing the Jdroid Exodized rom.
it end up with Bootloop/HTC logo.
My Fault is Before Flashing the rom, my Battery is 10%....
I've Done All the XDA Threads on how to Fix this.
-erasing cache from fastboot mode
-relocking the bootloader(its relocked now)
-Flashing RUU(i can't flash RUU becoz of my Low battery it needs 30%.)
My problem is, How can i Charge my Phone Up to 30%... And how would i know if it is Charging?
coz everytime i plug in my devices USB or Charge, the red light is going on and off,steady,sometimes its Gone...
Im confused.
Please help me T____T
Godbless

Once it gets to the HTC logo and freezes it should charge there.
Are you still able to get this far?

Have a read of this, see if anything helps.
http://forum.xda-developers.com/showthread.php?t=1609190

Try flashing the RUU from Fastboot rather than HBOOT, worked for me.
You may need to put stock recovery on and then lock the bootloader first.

If you're using the latest CWM then turn the phone off and charge it

jfrock25 said:
Once it gets to the HTC logo and freezes it should charge there.
Are you still able to get this far?
Click to expand...
Click to collapse
im doing it right now...
your suggestion is my last Option...
getting far?..no...Just stocked on HTC logo...
but i can run Bootloader mode, and fastboot mode...
the recovery mode is Unavailable because i relocked my Bootloader

craftycarper1 said:
Have a read of this, see if anything helps.
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
yes... i read it already....
but still cant Go any further because of my battery is lessthan 30% to do a RUU...

EddyOS said:
If you're using the latest CWM then turn the phone off and charge it
Click to expand...
Click to collapse
im not sure.i cant flash CWM because i relocked my Bootloader...
Not allowed to Do anything..

You have to unlock bootloader again by the looks of it.

why don't charge your phone, while it's off? You'll see a red light burning.. when it's green, it's 100%..
than try the RUU..

craftycarper1 said:
You have to unlock bootloader again by the looks of it.
Click to expand...
Click to collapse
but again he cant do that because he is under 30%

Balong020 said:
im not sure.i cant flash CWM because i relocked my Bootloader...
Not allowed to Do anything..
Click to expand...
Click to collapse
Boot into recovery, if it's 5.8.3.1 then it's the latest one so just charge the phone when turned off

Try not to panic!!! I went through something similar last week. It should charge there. Leave it be for 3 or 4 hours to charge.
I cant help that much as this is all new to me as well but Im sure some of the smart and nice people of these forums will guide you in the right direction. They certainly helped me out.

Super-Veloce said:
why don't charge your phone, while it's off? You'll see a red light burning.. when it's green, it's 100%..
than try the RUU..
Click to expand...
Click to collapse
That was my thought exactly. Why don't you let it turn off / let the battery die and then charge?
Wouldn't that work?

Electronic Punk said:
Try flashing the RUU from Fastboot rather than HBOOT, worked for me.
You may need to put stock recovery on and then lock the bootloader first.
Click to expand...
Click to collapse
Even my device is under 30% battery life?

Are you using the HTC charger as it requires 1 amp to charge properly. I found this out when I used my Nokia charger and the light flashed but when I used my HTC one the light stayed on and charged quicker.
Sent from my HTC One X using Tapatalk 2

T_______T
n1kon said:
Are you using the HTC charger as it requires 1 amp to charge properly. I found this out when I used my Nokia charger and the light flashed but when I used my HTC one the light stayed on and charged quicker.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yes.. Im using the HTC original charger...
but when i turn my Phone Off...
then i plug the charger, my phone automatically Go on Fastboot mode...
sometimes it goes to Hboot mode, and sometimes on HTC logo...
but in all of that, The RED LIGHT is always present...
when i plug the charger... Still the red light is there..
and when i leave it on HBoot,Fastboot or HTC LOGO...
after a Min. it will shutdown..(Look likes it Drains the battery, and need to press Power up button + Vol down several times)
<--------------- so Confused.
oh GOD please Help me

EddyOS said:
Boot into recovery, if it's 5.8.3.1 then it's the latest one so just charge the phone when turned off
Click to expand...
Click to collapse
i cant... because my Bootloader is relocked..
and i cant unlock my bootloader because lack of Battery life...

jfrock25 said:
Try not to panic!!! I went through something similar last week. It should charge there. Leave it be for 3 or 4 hours to charge.
I cant help that much as this is all new to me as well but Im sure some of the smart and nice people of these forums will guide you in the right direction. They certainly helped me out.
Click to expand...
Click to collapse
Thank you for your Advice...
Sounds Good
Looking for that nice people....
please help me...
i'll pray for you if you helped me out of this.

Have you got the updated cmw recovery coz that charges for me? If not flash it quick and boot into it and leave it on charge for a while
Edit: saying that though my phone charge from flat and off the the older version. As that's how I found out about different chargers coz I panic as I thought I bricked mine.
Sent from my HTC One X using Tapatalk 2

[Q] I think i soft-bricked my phone. need advice on next step

Hey guys, im going to be as detailed as possible.
Couple of days ago i rooted my One X and it was all good, had installed a custom ROM and everything. But i found out that whatsapp doesnt play nice with custom ROMs. Sicne i need whatsapp( Yeah i tried to download LINE but i cant download large apps(?)) i decided to go back to the stock OS. I had a backup of nandroid on clockwork recovery mod and restored it. But it didnt get past the boot screen. Cleared cache etc still no dice. So i thought it would be a good idea to unroot my phone.No,no it wasnt.
I followed all the unrooting steps, locked the bootloader. Well here is my problem, when i tried to run the RUU it aid i had the wrong one. So i think i have found the right RUU but during the searching my battery went below 30%. Everytime i on/reboot the phone it just goes to fastboot. Am i wasting my time with this RUU stuff? or is it the way to fix my phone? If i it means anything, my cid is htc_44.
Thanks in advance
EDIT: Ok guys i really need your help, i cant even re-unlock the bootloader because the battery is too low. Whenever i try and charge it just goes to fastboot. Even if i try and powe it down it goes back into fastboot

what happends when you plug the phone in the wallcharger and boot into fastboot and then choose powerdown .... Does it start to charge and do you see a red charging light come on !
Otherwise you have to search for the batt charge script
This is the one i found
http://forum.xda-developers.com/showthread.php?t=1658084

Dude you should have flashed the boot.img file for stock and none of this would have happened. That was the only step you were missing
Sent from my HTC One X using xda app-developers app

tomascus said:
Dude you should have flashed the boot.img file for stock and none of this would have happened. That was the only step you were missing
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
To late now !

Mr Hofs said:
what happends when you plug the phone in the wallcharger and boot into fastboot and then choose powerdown .... Does it start to charge and do you see a red charging light come on !
Otherwise you have to search for the batt charge script
This is the one i found
http://forum.xda-developers.com/showthread.php?t=1658084
Click to expand...
Click to collapse
It just goes back into fastboot. Im currently charging my battery with the bat file. After its charged what do i do? unlock bootloader and go in clockworld recovery to charge then do the RUU

Well my best guess is that you run the ruu directly after charging
Keep the phone in fastboot USB mode and run the ruu from pc with admin rights !!!

Mr Hofs said:
Well my best guess is that you run the ruu directly after charging
Keep the phone in fastboot USB mode and run the ruu from pc with admin rights !!!
Click to expand...
Click to collapse
Ok cool, how much batter do i need to run the RUU? in volts? is 3.68 going to be enough?

Ai that's a question i can't answer ...

Mr Hofs said:
Ai that's a question i can't answer ...
Click to expand...
Click to collapse
Thanks anyway

any update?

ujiosan said:
any update?
Click to expand...
Click to collapse
Phone is still charging, going to try RUU in a few minutes.

You can charge it from Clockworkmod 5.8.4.0, which is quicker and will charge more than the script.

BenPope said:
You can charge it from Clockworkmod 5.8.4.0, which is quicker and will charge more than the script.
Click to expand...
Click to collapse
True and some people reports charging trouble in that cwm recovery if so you can flash this one
http://db.tt/K8Aoto6o
Its the cwm 6 recovery

Phone won't power on or charge properly

So last night I unlocked the bootloader for my HTC One X. I wanted to get CM10.1 Nightly builds onto my phone, and was able to get all the way to where I have CWM 5.8.4.0 and even installed CM10.1 Nightly release. The problem at the time was that when I rebooted the phone it would become stuck at the bootscreen with the "Quietly Brilliant" quote. I tried everything from there to get CM10.1 working based on what I found around other threads and forums.
At one point the battery started running low and the phone stated that the battery was too low to perform fastboot commands. I thought I was in the clear as forums stated that as long as you have CWM on your phone then you can charge it back to full. I turned off my phone and plug in the wall charger and the red indicator light turned on a solid red.
This morning when I woke up, the red indicator wasn't on so I tried turning it on and nothing happened. I held down the volume button and pressed it, held down power for a minute...nothing seemed to work. I tried plugging my phone into my pc and it made that sound where the computer recognizes a new device and then made the sound that a device has been disconnected shortly after. This time though, the red indicator turned on but was blinking. I check other forums on how to fix this and all of them say to either:
1. Let the phone charge until the red light is solid
2. Hold down the volume button and then click power to boot into recovery.
The problem with that was the first option didn't happen, at a certain point the red light will just turn off. The 2nd option yielded nothing as I can't turn my phone on...
I'm seriously hoping I didn't just brick my phone and am hoping someone out there has a solution to the problem I'm facing.
Please and thank you!
***UPDATE***::: I got it to charge just enough to power on back to the bootloader using a Duracell external battery pack. Stupid me decided to relock the phone and go for the RUU when I clearly didn't have 30% battery life. I ended up looking around forums until I found a fix for that located here: (http://forum.xda-developers.com/showthread.php?t=1658084)
Using that method my battery maxed at 3665mV and I had just enough power to unlock the phone again and then reflash cwm 5.8.4.0 just for safety measures. Now I have the phone booted into the recovery main screen and plugged it into my ac charger. However, there's no LED indicator and I'm not sure if the phone is even charging at this point. Unless someone can help assure me that it is actually charging then I will wait about 2 hours before plugging it back into my pc and checking the power variable. Hopefully this all works out...
***UPDATE 2***::: This is just leading to more frustration. I proceeded with the following tutorial http://forum.xda-developers.com/showthread.php?t=1859714 and got to where I start the RUU exe. Unfortunately for me I ran into a "155: Unknown Error" and I tried the following RUU's: (3.14.707.24), (3.14.401.31) first. My phone code is (3.14.707.24) so I wasn't sure why it wasn't working. I read another thread http://forum.xda-developers.com/showthread.php?t=1660642 that said to try either (1.29.401.11) or (1.29.401.7). Both of these RUU's gave me either a "USB connectivity error" or a "Main battery is below 30%"
Now I wasn't sure if my phone had actually lowered that much since I started working on it, but I checked the mV value and it gave me 4030 which I thought was more than 30%. I don't believe it's the USB cause I can still get to the 155 error for the former RUU's. I just went ahead and started charging the phone again and will try again soon. This is really ticking me off...
***UPDATE 3***::: NOPE! I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
***FINAL UPDATE***::: Mission Accomplished!!! I'm glad to say that I got my phone running back on stock and am not holding a brick in my hands. How I fixed it? This morning I came across this thread here http://forum.xda-developers.com/wiki/HTC_One_X#Disaster_Recovery_-_what_to_do_in_the_event_of_a_bad_flash and I noticed something new in the instructions. It said to run fastboot when executing the RUU, and interestingly enough when I got to the 2nd to the last step the version said "updating from 3.14.707.24 to 3.14.707.24" Before, I ran the RUU while on the "Quietly Brilliant" splash screen since the tutorial I was following never mentioned having to run the RUU while in fastboot. This would probably also explain why, when I ran the RUU in the splash screen, it gave me the (3.14.401.31) version number instead of the correct (3.14.707.24) version.
Well, it's been a messed up roller coaster of a ride and I will try my luck with flashing another rom later this week. I hope I never have to revisit another HOX troubleshooting thread for the remainder of the time that I use this phone. Thanks to all that assisted in my endeavors.

Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
http://d-h.st/487
Sent from my HTC One X using xda app-developers app

davidk-il said:
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
Click to expand...
Click to collapse
I already tried the method you mentioned and that didn't work. The problem with the script is that I assume I would need to have the phone charged somehow and then turn it on. I can't charge the phone at this point so I'm lost...

Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app

The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.

davidk-il said:
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I have tried that too...it didn't work =(
At this point the phone just won't charge properly.

TToivanen said:
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
Click to expand...
Click to collapse
I plugged it into the AC charger last night and this morning is when the problem started. I'm starting to think I should have left the phone on in the recovery screen and charged it that way.
When I try plugging the phone into the AC charger now there's no red led indicator, but there's one when I plug it into the pc (even though the flashing light disappears after 5 minutes or so).

Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app

davidk-il said:
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So last night I checked the millivolt of my battery after charging it through recovery for about 2 hours and it was at roughly 3810mV. I'm not sure what the max mV for HOX is but I let it charge overnight again. This morning I checked and it was at around 4180mV. I'm not very knowledgable on how to convert the 1800mah value over to how many mV it would equal to. I wasn't sure if this was the max so I left it charging and will get back to it once I get home.

~4200mV is equal to 100% charge.

TToivanen said:
~4200mV is equal to 100% charge.
Click to expand...
Click to collapse
Good to know! I'll give the RUU a try when I get the chance later today and post an update. Thanks!

I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.

Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights

Mr Hofs said:
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Click to expand...
Click to collapse
If I'm not mistaken, that's the first one I used last night along with the same steps. It gave me the "155 Unknown Error" and I proceeded to trying other RUU's. I will try again when I get home, where I can only hope it works for some odd reason. Stay tuned.

Well its the only one that should work. A newer one in not out. And this one matches the main version 100%

Mr Hofs said:
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Click to expand...
Click to collapse
I think what I forgot to mention in the updates was that I found something strange. During the RUU steps, after I clicked update, it said:
Upgrading from 3.14.401.31 to 3.14.707.24 which I thought was really strange since 401 indicates Europe version. Is this something to note?
It was the next steps that lead me to the 155 Unknown Error

The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here

Mr Hofs said:
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Click to expand...
Click to collapse
Here's the thing, when I run the command to get the version I receive: (3.14.707.24)
However, when I run the 3.14.707.24 RUU it leads me to a page where it says I'm going from 3.14.401.31 to image: 3.14.707.24
That seemed very odd to me. Can you help explain why this is?

Hmm no i can't ! That's very strange.....try the 707 ruu again. Otherwise try the 401 ruu ?
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Don't exactly know what to think about that

Is there a solution for Droid DNA?
I tried rooting it last night. It was successful. The last step was to reboot according to JCase's method. It hasnt restarted since then. No battery indicator as if its not at all plugged in. "YES IT WAS ON CHARGING THE WHOLE NIGHT". It wont even show me the boot screen. "YES, I PRESSED THE POWER AND VOL BUTTON FOR MORE THAN A MIN".
Any help would be appreciated.
Thank You

Bootloader / HTC screen bootloop help ):

So me being the impatient guy that I am decided to unroot/relock my HoX. I followed this guide http://forum.xda-developers.com/showthread.php?t=1859714
I downloaded the nandroid that matched my ID, HTC_044. Restored the backup, all was fine but the ROM was rooted. Flashed stock recovery and kernel too.
I then deleted the SU files from system/app and system/bin and /xbin. Rebooted, but somehow SU was still there. So I deleted the files again and wanted to boot into stock recovery to do a wipe.
So I boot into the bootloader, tried getting into recovery. Had the red ! exclamation mark. So I flashed the recovery again and that's where the problem started. My phone is going crazy right now.
It's bootlooping at the HTC quietly brilliant screen. 2 seconds and it reboots forever. I tried forcing my way into the bootloader, but then the bootloader has a mind of it's own and bootloops as well. Whenever I manage to get into the bootloader, it boots for 2 seconds then it goes back into bootlooping.
Here's a video of everything happening. I need help! Battery is at 100% last I checked, but it's been bootlooping for 3 hours now ):

Nobody? ): My phone's been bootlooping for 7 hours now D:

ArmedandDangerous said:
Nobody? ): My phone's been bootlooping for 7 hours now D:
Click to expand...
Click to collapse
Can you carry out a fastboot command??
If yes, give the output of
fastboot getvar version-main
Sent from my HTC One X using xda app-developers app

Why fastboot getvar version-main ?
Ow good morning btw

Mr Hofs said:
Why fastboot getvar version-main ?
Ow good morning btw
Click to expand...
Click to collapse
So he can run a RUU??
Good Morning to you too!
Sent from my HTC One X using xda app-developers app

Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc

Mr Hofs said:
Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc
Click to expand...
Click to collapse
So what to do?
Sent from my HTC One X using xda app-developers app

Mr Hofs said:
Yeah good thinking but a bootlooping device can't run a ruu because fastboot usb connection is lost at reboot, therefore no communication between phone and pc
Click to expand...
Click to collapse
As long as I know, RUU can be run while in fastboot
The problem is that he can't stay in it more than 2 seconds... Mmm

Maybe fastboot erase cache will help.
I also have seen reports that it stopped out of its own
Difficult issue

Mr Hofs said:
Maybe fastboot erase cache will help.
I also have seen reports that it stopped out of its own
Difficult issue
Click to expand...
Click to collapse
Let's wait for him to reply....
Sent from my HTC One X using xda app-developers app

Good idea !

I've been trying to get to fastboot at the right time for erase cache to activate but it restarts too fast and fasboot hasn't fully initialized yet ):

Let it drain out, then charge the phone. Hopefully its gone by then. Its the only thing you can do now

Mr Hofs said:
Let it drain out, then charge the phone. Hopefully its gone by then. Its the only thing you can do now
Click to expand...
Click to collapse
It has drained out, but every time I plug it in it starts bootlooping again.

Then there is not much you can do

Mr Hofs said:
Then there is not much you can do
Click to expand...
Click to collapse
So it's a hard brick and there's no way to save it?
EDIT : I got lucky and managed to fastboot erase cache but it's still bootlooping. I've got the RUU ready and rom.zip extracted, but with the bootloader looping as well, I don't know what to do.

Why don't you try running the RUU?? I know the phone needs to be in connection with the PC all the time but still.. worth a try...
If you can't access bootloader on the One X, it's a hard brick!

You can try to start the ruu, hope it works. But i have my doubts.
Nothings else you can do atm, maybe somebody with more knowledge or this experience pops up !

ArmedandDangerous said:
It has drained out, but every time I plug it in it starts bootlooping again.
Click to expand...
Click to collapse
Why don’t try to open it and disconnect the battery. I think letting it drain out doesn’t mean the battery is 0% (no power).

moom999 said:
Why don’t try to open it and disconnect the battery. I think letting it drain out doesn’t mean the battery is 0% (no power).
Click to expand...
Click to collapse
He is full stock ATM and even the bootloader is relocked, he has better chance of claiming warranty via HTC and letting them fix it instead of opening it himself and trying to fix it (which I doubt would be of any help)... again there's a chance that he could damage or tear one of the cables while doing it...
@ OP
If you don't get any solution within two days, it's better you send it to HTC if you are still under warranty... If you have experience opening up the device, then go with @moom999 soln...:good: