[SEMI-BRICKED] Need help reverting to stock - HTC One X

Hi
Dunno what went wrong, but my phone ran out of battery last night, and when I charged it, and turned it on, it resulted in a bootloop.
I then wiped and reflashed the ROM, but still boot looping, and now I can't get into recovery anymore.
I can get in to bootloader, and I have tried to start the RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe in fastboot og HBOOT compability, but no luck (Check that your cable is connected).
Can't I get another ROM on, stock preferred, anyway?
my HBOOT version is 0.94.0000
I had installed AOKP ICS 4.0.4 custom ROM on the phone.
I'm no noob, but my knowledge isn't sufficient in this case
Thanks in advance
Lars

have u try load boot.img again
har du prøvet at loade boot.img igen

-fluffy- said:
have u try load boot.img again
har du prøvet at loade boot.img igen
Click to expand...
Click to collapse
no, could that help? will try
I was just trying to flsah the new CWM beforehand, but it says batterylevel to low <30% , so I guess i wont get any luck out of flashing with fastboot right now
i'm booted into bootloader now, and charging, but I need to keep the screen alive, otherwise it will stop charging, guess it is going to be a long day.
will try flashing afterwards
EDIT: Bad news, it is not charging in bootloader, its only getting power to stay alive, not charging.

yes it cut

larsn84 said:
Hi
Dunno what went wrong, but my phone ran out of battery last night, and when I charged it, and turned it on, it resulted in a bootloop.
I then wiped and reflashed the ROM, but still boot looping, and now I can't get into recovery anymore.
I can get in to bootloader, and I have tried to start the RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe in fastboot og HBOOT compability, but no luck (Check that your cable is connected).
Can't I get another ROM on, stock preferred, anyway?
my HBOOT version is 0.94.0000
I had installed AOKP ICS 4.0.4 custom ROM on the phone.
I'm no noob, but my knowledge isn't sufficient in this case
Thanks in advance
Lars
Click to expand...
Click to collapse
larsn84 said:
no, could that help? will try
I was just trying to flsah the new CWM beforehand, but it says batterylevel to low <30% , so I guess i wont get any luck out of flashing with fastboot right now
i'm booted into bootloader now, and charging, but I need to keep the screen alive, otherwise it will stop charging, guess it is going to be a long day.
will try flashing afterwards
EDIT: Bad news, it is not charging in bootloader, its only getting power to stay alive, not charging.
Click to expand...
Click to collapse
See this and following posts by me.

larsn84 said:
no, could that help? will try
I was just trying to flsah the new CWM beforehand, but it says batterylevel to low <30% , so I guess i wont get any luck out of flashing with fastboot right now
i'm booted into bootloader now, and charging, but I need to keep the screen alive, otherwise it will stop charging, guess it is going to be a long day.
will try flashing afterwards
EDIT: Bad news, it is not charging in bootloader, its only getting power to stay alive, not charging.
Click to expand...
Click to collapse
found this link in another thread... why didn't I look there in the 1st place
http://forum.xda-developers.com/showthread.php?t=1609190
fastboot erase cache did the job... tried all the other things at 1st of course, as i couldn't see how erasing my cache would solve a charging issue, but now you know. You can boot and charge after that. was almost on my way to buy a new phone :victory:

Related

Black screen, no fastboot

I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..
If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^

I think I just ****ed my phone

All was working fine until I installed the 3-dot removal on ODEXED rom then it will never boot again! just hanging on boot. so i ****ed my recovery aswell. All i have now is fastboot which is always telling me BATTERY TOO LOW no matter how long i keep it on charge. I can't flash anything neither use RUU. When I click "switch off" in boot menu it will just restart and bootloop. I don't know how to charge my battery so I can use RUU again. Please any help will be much appreciated!
Jack Barrett said:
All was working fine until I installed the 3-dot removal on ODEXED rom then it will never boot again! just hanging on boot. so i ****ed my recovery aswell. All i have now is fastboot which is always telling me BATTERY TOO LOW no matter how long i keep it on charge. I can't flash anything neither use RUU. When I click "switch off" in boot menu it will just restart and bootloop. I don't know how to charge my battery so I can use RUU again. Please any help will be much appreciated!
Click to expand...
Click to collapse
This may be of assistance: http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Once you are back up and running, this is the 3 dot removal you need for odexed 1.29.401.11 if that's what version your on
http://forum.xda-developers.com/showthread.php?p=26162691
Sent from my HTC One X using Tapatalk 2
bogfather said:
Once you are back up and running, this is the 3 dot removal you need for odexed 1.29.401.11 if that's what version your on
http://forum.xda-developers.com/showthread.php?p=26162691
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Exactly this version. But I've seen odexed later after I installed it.
I was able just to "erase cache" and unlock it. Then flash recovery. Now its in recovery and I'm waiting for it to charge. Hopefully it will.
Jack Barrett said:
Exactly this version. But I've seen odexed later after I installed it.
I was able just to "erase cache" and unlock it. Then flash recovery. Now its in recovery and I'm waiting for it to charge. Hopefully it will.
Click to expand...
Click to collapse
Once you have the latest CWM you can charge the phone whilst it's off. After that you can flash a ROM/run a RUU and get it back up and running.
rogersnm said:
Once you have the latest CWM you can charge the phone whilst it's off. After that you can flash a ROM/run a RUU and get it back up and running.
Click to expand...
Click to collapse
I was waiting till now and still nothing, ruu starts, erasing everything, sending and when its time to install it says battery low and stops.
still no luck
Jack , take a look here and report back! http://forum.xda-developers.com/showthread.php?t=1609190
Cheers~
I've tried everything. Now im at phase in bootloader - battery very low again. It's not charging from bootloader neither when I start it. Recovery is not working too + I can't unlock it because of the battery. Tried to shut down - not working. HTC made that phone crap because of the internal battery! I hope there will be solution or I have to return it to them,.
Jack Barrett said:
I've tried everything. Now im at phase in bootloader - battery very low again. It's not charging from bootloader neither when I start it. Recovery is not working too + I can't unlock it because of the battery. Tried to shut down - not working. HTC made that phone crap because of the internal battery! I hope there will be solution or I have to return it to them,.
Click to expand...
Click to collapse
To be fair its not HTC's fault, you did do something that they didn't intend.
Also don't charge from the bootloader it needs to be completely off, hold power and volume up to force it off.
Sent from my HTC One X using xda premium
I put it in bootloader to charge - it failed and switched off. Turned on bootloop to charge - same story. Tried with clockworkmod latest - same story. So I was going to send it back. Until I switched the usb port on the PC - then the battery problem was not there! I WAS ABLE TO USE RUU! That's how I fixed it.

[Q] Please Help! My HTC is encountering serious problems!

Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
WasifSal said:
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
Click to expand...
Click to collapse
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Kevin Ma said:
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I Re-Locked the phone
Will that flash the Recovery?
WasifSal said:
I Re-Locked the phone
Will that flash the Recovery?
Click to expand...
Click to collapse
unlock the phone again. flash the latest recovery. then go into fastboot. fastboot erase cache , then flash the kernel, go into recovery flash superwipe, flash rom and reboot and job done..
before you do all that though backup your current rom
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
WasifSal said:
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
Click to expand...
Click to collapse
well then leave it overnight to charge..see what happens in the morning then
Goku80 said:
well then leave it overnight to charge..see what happens in the morning then
Click to expand...
Click to collapse
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
WasifSal said:
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
Click to expand...
Click to collapse
man i am sorry then i wish i had more knowledge to give you help. hopefully someone else with more experience and knowledge can come and advise you different. just never had that issue you see.
if you say you can not go into bootloader or recovery then it does not sound right...maybe take it back to retailer or something might be the best option if no one can help out
have you tried the power button with the volume button down for ten seconds to see if the phone reboots?
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
WasifSal said:
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
Click to expand...
Click to collapse
try what i said to you in my last sentence mate
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
PatsFan1286 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
OK so I managed to get the phone UNLOCKED (Finally)
Now when I flash the 5.8.4.0 recovery it says
"unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'"
So i booted the phone into the recovery mode instead of flashing.
I am finally getting somewhere but how do i know it's charging there? I don't see the red LED turn ON :/
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
WasifSal said:
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
Click to expand...
Click to collapse
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
rayford85 said:
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Woah! That's spot on... I was surely gonna mess up my phone if i had done the RUU.
Its charging while the screen is off as we speak. But I think there is a problem with the charge thingy.
Its off and charging.. but sooner or later it turns off due to low battery (IM SUCH A NOOB I DNT KNW IF THE LOW BATTERY IS CAUSING THE PROBLEM)
I'll wait for it to charge again though and connect to the PC again
In the meanwhile can u answer me something regarding this
1. Does the red light turns on while charging in CWM 5.8.4.0
2. Does the mount USB Drive works? :'( Cuz when the phone was working fine. The mount USB Drive failed and gave an error of having a "lunfile missing" :/
Both of your questions can be found :
http://forum.xda-developers.com/showthread.php?t=1594819
i flashed the boot.img like ray said. then i turned the phone to recovery mode it went there and then mounted the usb it worked etc.
but I didnt flashed just yet.. i wanted it to be charged so i turned it off.. I am again getting that "not turning off" habit again
OH God what am i doing wrong here
PLEASE!! Someone help me! It's got that nasty thing that gets HTC Queitly Brilliant thing again.. It's charging but won't go into the recovery mode now!!!!!!!!!!!!!!!
How can I charge my phone while on Relocked Bootloader. I need help u guys!

[Q] Looking for ORANG001 Nandroid backup

Hey guys, anyone got a 2.17.61.3 stock nandroid backup for ORANG001 (Orange UK)?
Struggling to find it uploaded anywhere.
Need this or the custom ruu to use the downgrading trick to update my hboot.
Thanks!
Its in here
http://forum.xda-developers.com/showthread.php?t=1975140 :thumbup:
The dropbox link is broken sadly
Then you have to wait until its fixed, or when bugsy get the chance to host it on his sire
Yeah :s
Trying to update my hboot, because right now the phone randomly turns off and requires me to hold down the power button. Also gets stuck on optimizing apps.
Thought I'd ask here in case anyone had it floating around in their download folder.
Thanks though!
Maybe there is a JB firmware in the firmware collection thread to update the hboot and then restore the JB nandroid ?
Your cid and firmware is listed here + firmware download
http://forum.xda-developers.com/showthread.php?t=1957376
That could work! Would I flash the firmware in the same way as I would in the RUU/hboot upgrade guides, or can I skip locking the bootloader and stock recovery?
Like:
fastboot oem lock
reboot
fastboot oem rebootRUU
fastboot flash zip <zip>
re-unlock etc.
Yes thats it
Did all that, stock rom crashed, flashed IceColdJelly and that crashed after a while. Phone won't turn on now like before, might turn on after a while, I always have to hold down the button for a long time now.
Thinking maybe this is a hardware / battery problem although everyone was fine before I when from Carbon 1.3 -> 1.5, going back to 1.3 didn't help.
Not really sure what to do now :s
Do the firmware flash all over ! Then reflash the custom recovery, perform a real good wipe and install the rom again. Helped before when i suggested it with someone who experienced similar problems
Did all that, everything went fine until booting into system again, it crashed pretty much just after setup-up. The screen freezes and the button lights go to full brightness.
Would it be worth completely formatting the SD card too?
Trying to think of anything I'm doing wrong.. I do use the Motorola charger rather than an HTC one but I doubt that matters.
Thanks for helping thus far though!
Also for flashing ? Never use another cable then the original !
And yeah its worth the try. Did you perform a full wipe in the recovery....really all stuff ? Caches, dalvik cache....data, system, factory reset. Then install the new rom and flash the boot.img....also wipe cache after flashing the boot.img
Fastboot erase cache
It looks more like a not good wipe problem to me
OK I did a full wipe this time, system, sd card. I've got TWRP on there now which works fine. I flashed ICJ then the boot.img as well as wiping the cache.
Phone booted up fine was working for quite a while before it crashed again, the phone was plugged in using the Motorola plug charger when it crashed. I've been using a battery pack too which uses the power connection on the back.
The phone wouldn't turn on until I plugged it into USB for a while (no led) and held down power + volume down. I'm going to charge it up to full via usb in TWRP then see if it still crashes without charging and without the battery pack on.
I hope it doesn't because then it could just be I need to get the HTC plug/cable and stop using the case.
If it's a hardware problem then I'm not sure I'll be able to get it repaired as I bought this second hand (with a receipt, I could see if I can proof of purchase) and have unlocked the bootloader etc.
I suppose if the phone won't turn on though they can't know that.
Like i said ..... only use original stuff
Any update ?
It crashed in recovery while making a backup and I haven't manage to get it back on yet, I've ordered a HTC cable / plug though. If I get it on I'll just charge it then turn it off, as when I turn it off (as opposed to it crashing) it turns on normally.
Not really looking good though
Sorry to hear this
Got the HTC plug and nothing seems different, still totally dead.I think it is a hardware failure of some sort, as with all the different software combinations I tried it was crashing regardless. (At least that's what I tell myself.)
I'm going to see if I can get it repaired on warranty and hope they don't check the IMEI.
Thanks for all the help
Oke mate ! I hope you get it fixed soon
Good news! HTC have fixed it and sent it back, charging it for a few hours now before I turn it on.
I'm not sure what broke it but I was using the wrong charger for the phone and also a cheap battery case to prolong its daily usage. I'm not sure whether I want to risk flashing roms again but I really don't like sense, it depends if I bricked it or not.

[Q] HTC One X not switching on

Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse
kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?
convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference
convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.
Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat
Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.

Categories

Resources