So using TWRP I flashed my clearROM and went through the installation, all seemed to go well. Once done I clicked reboot in TWRP and then my phone didn't reboot. At this point it was still plugged into my computer and the chargin light was on. I tried to boot it normally and the bottom three buttons flashed a few times and then nothing happened. After that the charging light disappeared. I am unable to boot it into bootloader as well.
I've had it in the wall charger for the last 20 minutes and still no charge light, I've done some searching and nothing helpful has come up so I'm wondering if anyone knows more about this,
You did nothing but flash cleanrom?
Sent from my HTC One X+ p_type 0.91.0
Sorry I should have been more detailed.
I unlocked via HTCdev, installed TWRP recovery, wiped the phone then installed cleanrom.
A little update, the red charging light came on about ten minutes ago while plugged into the computer. When I saw it was lit up, I transferred to a wall charger for 10 minutes. I then held the power button for a few seconds to try and boot it, but the red light just disappeared and now I'm back at square one.
Left it on wall charger all night, no red chargin light upon waking up. Decided to switch it to the computer USB about half an hour and will leave it there while I goto school. After seeing the red light last night I have hope!
Wall charger is better than USB. But if you left it on the wall charger overnight, I don't think you will see much difference with additional charging (regardless of wall charger vs. USB).
Can adb see the phone?
Can you confirm which variant of the One X you have? If you have the Tegra3 (International) One X and loaded a ROM for the Snapdragon S4/North American One X or vice versa then you may have bricked your phone. If you are unsure, which carrier did you get the phone from?
Got home from school and no charging light on. Tried to boot into bootloader and the red light came on. But no boot, or at least screen response. It was still plugged into the computer and no noise response from the computer. Tried to boot into bootloader again and the light turned off. Tried to boot into recovery and the light came on again, but no screen response. Then just held the power button for a normal boot and the light turned off and now it won't turn on again.
I tried to fastboot reboot-recovery and cmd hangs on waiting for device, so I don't think adb can find the device. I got the hox from Rogers Canada, and in bootloader it said evita.
I was tired last night this slipped my mind, but I installed clearkernel as well. In TWRP I selected the clearkernel zip and it flashed it, no installation. It then proceeded to flash the clearrom zip and sent me to the installation for clearrom.
gr3ener said:
Got home from school and no charging light on. Tried to boot into bootloader and the red light came on. But no boot, or at least screen response. It was still plugged into the computer and no noise response from the computer. Tried to boot into bootloader again and the light turned off. Tried to boot into recovery and the light came on again, but no screen response. Then just held the power button for a normal boot and the light turned off and now it won't turn on again.
I tried to fastboot reboot-recovery and cmd hangs on waiting for device, so I don't think adb can find the device. I got the hox from Rogers Canada, and in bootloader it said evita.
I was tired last night this slipped my mind, but I installed clearkernel as well. In TWRP I selected the clearkernel zip and it flashed it, no installation. It then proceeded to flash the clearrom zip and sent me to the installation for clearrom.
Click to expand...
Click to collapse
Leave it "on" and let the battery drain. Then plug it back up to the wall and let it charge. Maybe some funniness going in :-S
Sent from my One X using xda app-developers app
What is the on setting? When the red light is on and not plugged in?
Did you try to press the power button for 10 seconds then see if it reboot? You can do the same but with volume down button pressed and should go to the bootloader.
Sent from my HTC One X using Tapatalk 2
Holding it down ten seconds didnt work for normal or bootloader.
Here's my suspicion, I see in the international forums you had flashed one of their roms. This has been detrimental to several devices, but it seemed your device had somewhat survived it and you had bootloader and recovery access. I'm guessing, when what you needed to do from there is ruu or dd a signed Hboot to the proper partition to get it stable again, you flashed a one xl Rom which sealed your fate.
You may not have know the damage caused by flashing the incorrect Rom, and I mean no offense, simply letting you know that your phone is probably good for nothing but maybe a fancy door prop......
If you plug it into your pc and it comes up as qshusb_dload in your windows device manager, or it comes up as nothing after pressing power for 2-3 seconds it's probably toast
Sent from my HTC One X+ p_type 0.91.0
It didn't actually install the other roms though, it failed when reading build.prop, hence why my phone 'survived'. At least I'm hoping so, I'm a noob with androids right now. It checked to see my device type and I was the wrong device, so it didn't install. Isn't that what the ro checks are for?
Since you got the phone from Rogers it is definitely the North American variant, so at least you loaded a compatible ROM onto your device. If you also flashed CleanKernel, the issue might be that the kernel is overclocked by default and your device cannot handle it. When this happens it is not usually as serious as what you're experiencing, but it is entirely possible. Can you check if the CleanKernel is overclocked by default (as I'm not sure)? If it is, your #1 priority should be to flash a stock kernel. It going to be difficult given the state of your device, but if you manage to get into recovery or issue a fastboot command from your pc you might have a big enough window to do it.
---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------
Oh wait... Is "clearkernel" a kernel for the international One X? I thought it was just a typo and you mean CleanKernel, a kernel for our north American one X.
He means cleanrom I think.....
Ok, here's where I'm conflicting, I've been here on fairly active on this forum since release. I've helped several people with unbricking and a wave of other issues that have come up.......I've NOT seen 1 single one x brick from flashing any roms specific to the device. I've seen DOZENS brick from flashing kernels, roms and recoveries from the international one x. So, seeing that just 3 hrs. before opening this thread, you opened a thread in the international one x forums saying you were having problems flashing a endeavor rom and endeavor kernel. You asked for advise how to edit it so the device would accept the flash. You were then instructed you were in the wrong forum, that you had a one xl evita.
So again, 3 hours later your super bricked, and stating all you did was flash cleanrom. Cleanrom didn't brick the phone, and insinuating that it could have, without fully stating your scenario is obnoxious and flagrant. I also saw you posted in the cleanrom thread that you flashed his Rom and now your x won't turn on.......
XDA is here to help, but your purposeful lack of information, as an attempt to save self dignity and place the responsibility quietly on a brilliant Rom dev is unjust and should NOT be tolerated.
With that said, you have a $700 paperweight and noone to blame but YOURSELF.......Deal with it:beer:
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
He means cleanrom I think.....
Ok, here's where I'm conflicting, I've been here on fairly active on this forum since release. I've helped several people with unbricking and a wave of other issues that have come up.......I've NOT seen 1 single one x brick from flashing any roms specific to the device. I've seen DOZENS brick from flashing kernels, roms and recoveries from the international one x. So, seeing that just 3 hrs. before opening this thread, you opened a thread in the international one x forums saying you were having problems flashing a endeavor rom and endeavor kernel. You asked for advise how to edit it so the device would accept the flash. You were then instructed you were in the wrong forum, that you had a one xl evita.
So again, 3 hours later your super bricked, and stating all you did was flash cleanrom. Cleanrom didn't brick the phone, and insinuating that it could have, without fully stating your scenario is obnoxious and flagrant. I also saw you posted in the cleanrom thread that you flashed his Rom and now your x won't turn on.......
XDA is here to help, but your purposeful lack of information, as an attempt to save self dignity and place the responsibility quietly on a brilliant Rom dev is unjust and should NOT be tolerated.
With that said, you have a $700 paperweight and noone to blame but YOURSELF.......Deal with it:beer:
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
Hop off that horse of yours, I appreciate your help very much. With that being said, I didn't include the other details because as far as I know, and my device showed me, they did not install. As much as I would love to save my dignity on an anonymous online forum.
My red light is now flashing, any ideas?
gr3ener said:
My red light is now flashing, any ideas?
Click to expand...
Click to collapse
If you did install (or try to install) a ROM or kernel for the International One X onto your North American One X then the behaviour you are seeing is a telltale sign that your device has been bricked, very similar to others who have done the same.
"Guys someone please help.....I'm stuck" http://forum.xda-developers.com/showthread.php?t=1755156
"Flashed a ROM for the HTC quad core, ignorantly. Phone now non functional" http://forum.xda-developers.com/showthread.php?t=1905665
I wish you best of luck! Perhaps you can take the phone back to a Rogers store and play dumb?
I would keep it simple no custom kernel. i would ruu and test it for a day before unlocking again and flashing recovery, i know stock hurts but you needa find out if its your phone thats buggerd. then if all is good unlock again and flash recovery, then strip down stock rom to your liking and mess with it for another day or two. then if all is good try another custom rom. i would try jb aosp based rom since they are pretty stable these days.
also ruu should clear out alot of the issues that the international rom might have caused assuming the ruu is successful. i have not misflashed int rom so i dont know all the problems, but most users ive come across flashed an int rom using cwm which is no good our the evita, since you seem to be using twrp the whole time. im guessing you might still be good. also dont do any factory reset, clear storage, etc from the bootloader it fubared my phone to the point where i had to ruu.
if my post makes little sense, please pm me for i have had little sleep. sleepy time and i hope i was of some help.
DvineLord said:
if my post makes little sense, please pm me for i have had little sleep. sleepy time and i hope i was of some help.
Click to expand...
Click to collapse
It doesn't power on to any extent.........
Sent from my HTC One X+ p_type 0.91.0
Related
First off, I am a veteran of flashing and have a decent amount of experience fixing up bricked phones, but this time nothing is working.
I flashed a Jellybean rom to my one x this morning, and now nothing is working. Literally. I can't access bootloader, in fact, I can't even get the screen to turn on. I have tried holding down the power button, as well as entering recovery etc... But nothing is working. Am I missing something simple or am I really in trouble?
Doesn't sound good. Any notification light when you plug the wall charger in?
What were the exact steps you've done to flash? You have unlocked bootloader, installed a custom recovery, then flashed a ROM? Which ROM specifically? Hopefully you didn't flash a ROM ment for the international (Tegra) version to a Snapdragon (AT&T, Roger, etc.) version phone.
At what point did the ROM flash fail? any error messages from recovery?
Did you flash an international one X ROM? Just wondering to get that scenario out of the way.
Sent from my One X using xda app-developers app
redpoint73 said:
Doesn't sound good. Any notification light when you plug the wall charger in?
What were the exact steps you've done to flash? You have unlocked bootloader, installed a custom recovery, then flashed a ROM? Which ROM specifically? Hopefully you didn't flash a ROM ment for the international (Tegra) version to a Snapdragon (AT&T, Roger, etc.) version phone.
Click to expand...
Click to collapse
The steps were in the same order, the rom is this one: http://forum.xda-developers.com/showthread.php?t=1763240. Looking at it, I think there is a good chance that is the problem. Anything I could do to fix it?
teswolf96 said:
The steps were in the same order, the rom is this one: http://forum.xda-developers.com/showthread.php?t=1763240. Looking at it, I think there is a good chance that is the problem. Anything I could do to fix it?
Click to expand...
Click to collapse
It is 100% the problem. If the phone is not recognized when plugging into your PC, I think you're hosed (but maybe others may know more and correct me on this). If it is recognized, get the RUU for your phone and run it.
I ask again, any notification (charging light) come on when you plug the wall charger in?
For the AT&T (Snapdragon) version of the One X, only flash things in this specific forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
Want to see everything in an organized compilation, go here:
http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
It is 100% the problem. If the phone is not recognized by fastboot, I think you're hosed. Any notification (charging light) come on when you plug the wall charger in?
Click to expand...
Click to collapse
Nope - Should I just take it back to AT&T and see if I can get a replacement?
teswolf96 said:
Nope - Should I just take it back to AT&T and see if I can get a replacement?
Click to expand...
Click to collapse
Warranty replacements are for defects by HTC, not for damage that you caused.
If you are asking if you can lie about what happened, and get a replacement, than I'm not going to dignify that question with a response.
Well, I bricked my phone once and went straight to LG, they fixed it for me? Maybe HTC might fix it for you?
Sent from my LG-P930 using xda premium
It's likely your phone is screwed. Strange though that it just died
Sent from my One X using xda premium
Connect the phone to your computer, and see if adb can see it. Of it can't, and the phone won't even show any lights when connected to the charger, I think you're screwed.
Also, leave it on the charger for several hours, and see if there is any change. There is a possibility if just got stuck in a bootloop on on the splash screen, and you killed the battery that way. But you haven't provided enough information for us to really know (what step it stalled on, what was on the screen, etc.).
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
EDIT: Found it on XDA. yes, it is for the international version
The instructions say:
To install, reboot into recovery, do data wipe/factory reset, install ROM, install Gapps, then extract boot.img from ROM zip file and flash with fastboot.
Click to expand...
Click to collapse
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
From the top of my head remembering front the HTC inspire that sounds like a lord clockan Rom...and I know he doesn't dev for us..now you successfully flashed a Rom for the tegra one x.... Which is bad..you might of hard bricked it
Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
Cannot stress this enough, do not flash anything that isn't posted in the dev sections of this forum...I believe IceColdJelly is for the international (Tegra 3) One X and you may have overwritten your boot sector and recovery. If you can't get the charging light to come on then you are most likely out of luck.
Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
Daaaaaaammmmn. Tssk tssk RESEARCH B4 flashing a ROM!. Ur phone prolly fried if it don't turn on for shiz like these fellas mention. Always be careful man don't just go all exited n flash a tegra rom :/
Sent from my HTC One XL using xda app-developers app
stnguyen09 said:
Cannot stress this enough, do not flash anything that isn't posted in the dev sections of this forum...I believe IceColdJelly is for the international (Tegra 3) One X and you may have overwritten your boot sector and recovery. If you can't get the charging light to come on then you are most likely out of luck.
Click to expand...
Click to collapse
But I have the Rogers One X, which I think is Telstra right?
Anyway, I found the rom's page on XDA:
http://forum.xda-developers.com/showthread.php?t=1796340
It is posted in the "HTC One X" forum, so that's not the Telstra version then, right?
Nevermind, I was mixed up about the versions. Yes, the rom is for the wrong version of the One X.
Thanks for the replies guys.
I was searching around and found this:
http://forum.xda-developers.com/showpost.php?p=30572793&postcount=12
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.
Click to expand...
Click to collapse
Might be possible to fix in Linux? I've heard that using the linux-only tools, it is possible to write to a partition even when the bootloader is broken. Anybody ever heard of this?
Karvin said:
Nevermind, I was mixed up about the versions. Yes, the rom is for the wrong version of the One X.
Thanks for the replies guys.
I was searching around and found this:
http://forum.xda-developers.com/showpost.php?p=30572793&postcount=12
Might be possible to fix in Linux? I've heard that using the linux-only tools, it is possible to write to a partition even when the bootloader is broken. Anybody ever heard of this?
Click to expand...
Click to collapse
It overwrit your hboot I think....there was a post I think I saw u have to do something very quickly and restore your boot partitions...but I have no idea ..sorry
Another one bites the dust...
I'll buy it from u
Karvin said:
But I have the Rogers One X, which I think is Telstra right?
Click to expand...
Click to collapse
Rogers is Rogers, Telstra is Telstra. Telstra is an Australian carrier.
Seems like the OP had a fundamental lack of basic understanding of what they were even looking at when flashing ROMs, which is of course a no-no.
Tough crowd lol
I am well aware of the difference between my hoc and the international version. I got mixed up by the "Telstra" thing. I thought it was the same as the rogers/at&t version.
Sent from my X10i using xda app-developers app
Karvin said:
Tough crowd lol
I am well aware of the difference between my hoc and the international version. I got mixed up by the "Telstra" thing. I thought it was the same as the rogers/at&t version.
Click to expand...
Click to collapse
They are essentially the same. Rogers or Telstra makes no difference, they are both the Snapdragon S4 version of the One X/XL. ROMs are interchangeable. How did this have anything to do with flashing a ROM for the international version?
My main point of my previous post, if you are mixed up, confused, etc. about any aspect of what you are doing when flashing ROMs or doing other mods, STOP, DO NOT PROCEED. Figure it out before proceeding, as you see what the consequence of not doing so is . . . a sexy looking paperweight.
redpoint73 said:
They are essentially the same. Rogers or Telstra makes no difference, they are both the Snapdragon S4 version of the One X/XL. ROMs are interchangeable. How did this have anything to do with flashing a ROM for the international version?
My main point of my previous post, if you are mixed up, confused, etc. about any aspect of what you are doing when flashing ROMs or doing other mods, STOP, DO NOT PROCEED. Figure it out before proceeding, as you see what the consequence of not doing so is . . . a sexy looking paperweight.
Click to expand...
Click to collapse
Yes, obviously it was completely my bad... I'm not trying to blame anyone else.
This is has become a pointless discussion...
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Epsilon707 said:
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Click to expand...
Click to collapse
Yes, it's a brick, but there is a fix if you have access to a Linux computer and know what you're doing.
beaups said:
when the device is bricked (qhusb mode), after pushing and holding power for ~10 seconds - in linux shortly thereafter all of the partitions will enumerate and expose themselves to linux for about 5 seconds (you'll see sdX1, sdX3, sdX8, about 30 partitions alltogether). During that quick 5 seconds you can DD whatever you feel like back to those partitions.
.
This is how I've recovered bricks. Corrupt hboot --> Brick device. DD back correct hboot while in this mode --> unbricked
Click to expand...
Click to collapse
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
omario8484 said:
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
Click to expand...
Click to collapse
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
bricked
iElvis said:
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
Click to expand...
Click to collapse
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Epsilon707 said:
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Click to expand...
Click to collapse
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
iElvis said:
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
Click to expand...
Click to collapse
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
I'll try charging it for a few hours. Thanks!
Epsilon707 said:
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
Click to expand...
Click to collapse
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
iElvis said:
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
Click to expand...
Click to collapse
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Epsilon707 said:
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Click to expand...
Click to collapse
Okay, try what InflatedTitan suggested and see what happens.
InflatedTitan said:
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Zero response. I'll keep trying.
Epsilon707 said:
Zero response. I'll keep trying.
Click to expand...
Click to collapse
Let it charge for a few hours and try again.
Still no avail. Any other ideas?
I could really use some help. Anyone have an idea or a suggestion on what to do? I also don't suppose this is covered under my warranty
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
iElvis said:
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
Click to expand...
Click to collapse
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Epsilon707 said:
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Click to expand...
Click to collapse
Okay, one last thing. Open up Device Manager in Windows and expand the whole directory tree. Check "DVD/CD-ROM devices" in particular. Plug your phone in and see what happens.
If nothing happens at all, try leaving it plugged in overnight and see if anything is different. If it's still dead, it's bricked, whatever you did with it. Since it's new, you should be able to return it and get a new one.
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
omario8484 said:
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
Click to expand...
Click to collapse
I'm f'ing baffled myself mate.
So, for some weird reason, after RUUing my phone, updating once to a newer version, then trying to update again for the Jelly Bean update (all within the phone on the stock ROM using the official updater and etc) my phone decided that it felt like entering QHSUSB_DLOAD mode right after the update was done installing, like it didnt even boot once, it just straight crashed to it.
Im kinda lost as of what to do, I already tried the fix on the website unlimited.io and that didnt do it. Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
The phone is a HTC One XL (obviously) hboot 1.09 (at least before the official updates that crashed my phone) from Rogers.
Please help!
Sam.Lambert said:
So, for some weird reason, after RUUing my phone, updating once to a newer version, then trying to update again for the Jelly Bean update (all within the phone on the stock ROM using the official updater and etc) my phone decided that it felt like entering QHSUSB_DLOAD mode right after the update was done installing, like it didnt even boot once, it just straight crashed to it.
Im kinda lost as of what to do, I already tried the fix on the website unlimited.io and that didnt do it. Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
The phone is a HTC One XL (obviously) hboot 1.09 (at least before the official updates that crashed my phone) from Rogers.
Please help!
Click to expand...
Click to collapse
This may be a stupid question but are you sure your phone is rogers... I've only heard of hboot 1.11 for rogers correct me if wrong...head over to the unbricking thread myrder grim or shadow will probably be more than happy to you help you because I think you're still fixable
Did you happen to have superCID?
HTC one s users who had supercid and took the ota bricked somehow.. the one x and one s are nearly identical
absolutelygrim said:
Did you happen to have superCID?
HTC one s users who had supercid and took the ota bricked somehow.. the one x and one s are nearly identical
Click to expand...
Click to collapse
Yes I have SuperCID, this might be why.
And yes my phone is definitely from Rogers, the phone shipped with hboot 1.09 but the updates most probably brought my to 1.11. I'll go see in that thread if anything can be done, thanks!
If your phone is not bone-stock, you should not be taking an ota. Too late for the OP, but maybe anyone else reading this will see why.
Sent from my Nexus 7 using Tapatalk HD
iElvis said:
If your phone is not bone-stock, you should not be taking an ota. Too late for the OP, but maybe anyone else reading this will see why.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have a replacement coming in for a dead speaker on the phone. Let's hope this little problem won't prevent me from having my phone accepted for the replacement.
Sam.Lambert said:
Ive tried everything ranging from letting it plugged for 10 years in my laptop or the wall charger, still nothing, holding volume down + power for 1 year or 2 didnt do anything either.
Click to expand...
Click to collapse
You are in Qualcomm download mode, meaning your hboot is f_cked. The only thing that can be done is to re-partition using a Linux computer (see unbricking thread in General). Other than that, you're pretty much screwed.