I think my ATT htc one x may be hard bricked...
I was playing around with ROMs and lost track of time. The last recovery I had on there was clockworkmod (was going back and forth between it and twrp).
I was trying to install the new jellybean rom and it kept on giving me an "assert failed" error. At this point, I deleted the assert lines from the recovery script as advised by one of the posters, and ran the install again. Went through... rebooted and...
The phone is completely dead now. I think it may have discharged? I plugged it in to the wall socket and nothing... absolutely no lights, no screen..... Power+ vol down does not work either....
Please help me, is there any way to recover from this situation?
Wrong subforum.
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Rusty! said:
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Click to expand...
Click to collapse
Doesn't seem like a rare thing occurring. Either people are overseeing this or they are not really aware that for you can't flash a rom made for a tegra quad core device onto a dual krait.
I used this....
http://forum.xda-developers.com/showthread.php?t=1763240
Sheesh..... Is this meant for the tegra? I never thought I would do such a thing.... I was aware of the issue/hardware differences....
Is there any hope? Actually, in device manager it shows up as QHSUSB_DLOAD and I heard thats a bad sign?
If it cannot be fixed, does anyone have an estimate about how much HTC would charge to reflash/fix it?
My signficant other is as po'ed at me as can be... especially since I had really pushed for the upgrade.... man...
Yes it's meant for the Tegra One X, that's why it wouldn't install (that, and it's not in the AT&T One X section). You bypassed the check the install script does to make sure you're installing it on the right phone.
In short, yes you have buggered it, QHUSUSB_DLOAD is a state where you can write things to the phone, but whether anyone as done any research into it on the S4 One X I don't know.
As for getting it fixed, I have no idea on cost, however... if you convince HTC that you didn't do it yourself, it might be possible to get it done under warranty.
Edit: Did a bit of research and /system on the Tegra One X is is HBOOT on the S4 One X, that's why it's ruined your phone.
htc would just replace the motherboard and charge for that - loads of people have reported the cost its something like £169 to replace motherboard, which would of course un brick it.
Have you tried to keep it plugged in to a charger for an hour or so? My HOX was dead too but started to flash red light after an hour, moment after solid light and it booted
Sent from my HTC One X using Tapatalk 2
He doesn't have an HBOOT any more, there is nothing he can do.
This is why people should stop being stubborn and call that phone HTC One XL. These kinds of situations would happen sooner or later.
Sent from my HTC One X using xda app-developers app
I guess I did... I actually had come to that page via google and since, perhaps I was a bit sleepy, did not verify the source... should have....
Is there any fix at all? Like loading the drivers and reformatting it or something?
Im a bit confused about the motherboard replacement: since its a software issue, cant HTC fix it with a software update? Ill call them today and post the answer on this group as well, but knowing what I am dealing with may help in talking with them.
Thanks to everyone again
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Rusty! said:
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Click to expand...
Click to collapse
Thanks... Someone in that section has kindly agreed to see if he/she can help me... Keeping fingers crossed... doent feel right to tell att that my phone stopped working for a replacemenf...
Hate to say it but your phone is dead. It's not revivable ar this time and so your only option is jtag or warranty replacement because you overwrote the Hboot.
Sent from my Inspire 4G using xda app-developers app
Don't let morals get you on that one. Lie to them, if not for yourself than for me.
Sent from my HTC One X using xda app-developers app
RobertX1 said:
I used this....in device manager it shows up as QHSUSB_DLOAD ..
Click to expand...
Click to collapse
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Not quite, there is a debricking method for the Sensation that can recover from it.
In most cases though, you're right.
Castellano2 said:
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Click to expand...
Click to collapse
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Please move this thread to the XL subforum
miniterror said:
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Click to expand...
Click to collapse
Thanks... any hope for this being possible for the one XL? Also, could the mods please move this thread to the ATT section (sorry for posting it in the wrong section... but I really didnt know the importance of the difference.... wanna look at my phone? )
Thanks everyone. I think I might send the phone to HTC to get it repaired.... although the s***ty thing with that is that Ive heard they take that opportunity to replace the motherboard instead of just replacing the software, and hit me with a big bill rather than a reasonable/fair price....
So.... trying to be honest (by not returning the phone as defective to HTC) ensures that I get scammed by them... :victory:
Possible? Yes of course, that's the point of that mode as I understand it, with some other HTC phones you can hook it up to a RIFF Box and load it up.
Likely? Probably not, as it'll take people looking into it in depth to figure it out and as far as I can see, no-one has/is looked/is looking into it on the OXL.
It really does look like you'll need to send it to HTC, which (as you sound quite honest) will probably be expensive.
Related
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App
mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char
If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App
Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.
I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.
Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt
Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.
As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt
happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck
Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....
actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.
Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?
So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium
Ok so heres the short of it. I was attempting to root my phone with the Hasoon V1.1 Tool kit and needless to say, everything went wrong. Here's what happened. I did everything to unlock the bootloader. Got my token ID and all that stuff. Next, I loaded the twrp recovery. Cleared everything out of the phone, and went to load a rom. It kept telling me "Failed" when I tried applying the rom. It ended up getting into a boot loop and wouldn't do much. I got it to go back to the recovery when this started and still it wouldn't load any of the ATT Htc One x Roms. I made sure those were the ones I had. Now, at random throughout the process at some point last night, it wouldn't do anything. It has a blank screen. When I plug it in, the status light shows nothing. It was on the charger last night all night, and has not changed. No status light, no screen, nothing! I know you guys are going to ask for more information, but low and behold, like most people you smart guys deal with, I'm a noob. I rooted my google G1, and my HTC inspire without too much trouble, but this is just completely beyond me. As I was doing research I read about problems people were having with the blank screen of death. I'm just worried because I don't have insurance and I'm pretty much screwed without a phone. Does anyone have any input as to what I can do? I'm just beyond aggrivated not having a phone, and I don't have much money to be getting a new one. PLEASE HELP ME
-Mike
Which Rom exactly were you trying to install?
Sent from my HTC One X using xda app-developers app
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
InflatedTitan said:
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
Click to expand...
Click to collapse
This, as well as... Which phone do you have, the X or XL. The XL is specific in which rooting method you can use.
Sent from my HTC One XL using xda app-developers app
-Power and volume down do absolutely nothing
-Rom was Endeavoru Cyanogen Mod
-Kernel was Franco Kernel r21
-Plugged into computer, does nothing. No status light, nothing.
I am thinking it wasn't the software that did it. It was plugged into the usb port of my laptop the whole time, but may have died. I read online somewhere if you completely discharge the phone, you need a special charger to charge it. If I loaded the wrong kernel it could have gotten below it's "dead" percentage. Correct me if I'm wrong, but with Lithium Ion batteries, completely discharging them is not good for the battery. If it had nothing to tell it to stop, and the usb port on my laptop didn't keep up with the amount I was messing with it, it could just be completely dead. I don't know. I'm an idiot and I apologize about all the gapps I'm giving you guys with information. I'm doing the best I can, but bottom line is after it didn't work at first, I tried a few different recoveries with Hasoons tool kit, and a couple different roms but the roms never loaded. Always failed.
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
With your battery being so low and possibly even dead when you tried to do anything with it, could have a problem. The other problem, if my memory is correct in what I was reading the Endeavoru cyanogen ROM is for the X only, international version. If yours is AT&T like you say, if the flash was performed correctly.... I hate to say this but you might have a nice $500 paperweight, for now. I would PM Abdolutelygrim and see what he thinks, unless he isn't already here.. his current project is unbricking Evita.
Sent from my HTC One XL using xda app-developers app
minimac21234 said:
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
Click to expand...
Click to collapse
You have what we call an HTC one xl or AT&T one x. The phones look almost exactly the same but the internal components are completely different. (youre in the right forum)
Sent from my HTC One XL
I went through almost the same thing last night, with the exception of my battery dying. In the event that you are able to get the phone to charge, this guide helped me get my phone working again.
Good luck!
The phone was fully charged when I began, and I periodically connected and disconnected it when I was having my initial problems. I deleted my cache dalvic cache, etc everything after I saved all my important pictures and videos and files etc. so I just deleted everything to start over fresh. I don't know what the hell I did. I just figured this wouldnt be too hard since I did it with 2 of my own phones in the past, and a few friends phones also. I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
minimac21234 said:
I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
Click to expand...
Click to collapse
That is indeed your problem. The One X and One XL use a different partition layout, and international roms will attempt to overwrite the One XL boot partition. Hboot is wp in 2.20 but not in earlier versions. Even so, you can end up with corrupted firmware even if hboot is untouched. Numerous people have done it. Some devs are working on a way to fix this. Here's the thread, you'll need to get yourself in the queue or just see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=1966850
Replacement isn't an option. I didn't get a chance to get insurance on it because I cracked the digitizer within the first 2 weeks of having the phone, and I opened it last night to see if something from when I cracked the digitizer came loose causing the phone to not boot. Thanks for the feedback so far guys. I'm not expecting miracles. I put myself into this mess, I'm just really hoping someone may be able to fix it soon. Not having a phone is really going to put a damper on my side work. Can't get phone calls from people on craigslist if I don't have a phone SH!T
Do you know what firmware your phone was on before you did this........it will be the determining factor if it's fixable atm
Sent from my HTC One XL using Tapatalk 2
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL. I feel like the biggest jackass. I'm the computer/cell phone/electronics guy in my area, and now I feel as if I should go into early retirement. I will stay open minded and hopeful that absolutelygrim and others come up with a solution, but bottom line, for all you guys that have made this process damn near idiot proof for people like me, I want to say thanks, and also apologize for all of us noobs that make something as simple as knowing what you are doing before you do it and following directions harder for the developers. It's awesome you guys do what you do in your spare time, only for people like myself to make it more of a hastle. Once again, thanks for trying to fix this guys. My bad.
18th... I was on 2.20. I read that there is a work around for 1.80(I think that's the firmware), but either way, yes I was on 2.20. I have been looking once a week for a new exploit to be able to root the one x, since there wasnt any options until about a week ago if you had 2.20. I bet that's why there are so many people screwing this up. They, like myself, are probably so eager to root it they don't take their time. I remember the first time I rooted my HTC inspire I took about 3-4 hours because I quadrouple checked what I was doing. And damn it am I kicking myself in the ass that I didn't do that this time around.
The problem was the endeavor Rom....but depending on what firmware you were on, 1.85 or 2.20 it can be fixed. If you were on 1.85 or below, it's fixable right now. If 2.20 then not atm.
Sent from my HTC One XL using Tapatalk 2
minimac21234 said:
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL.
Click to expand...
Click to collapse
The problem with CWM is that the version for the One XL is an unsupported port. So it's buggy, but the worst I've heard of it doing is corrupting people's sd card or occasionally borking installs, both of which are easily fixable.
The only time I've heard of CWM bricking One XL phones is when people use ROM Manager (which isn't supported for this phone, though GP will let you install it anyway) to install the endeavour version, which causes the same problem as flashing an endeavour rom.
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
InflatedTitan said:
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
Click to expand...
Click to collapse
It very well could be just Ice Cold Jelly. There is no guarantee something else I did last night bricked my phone. I know I attempted ICJ, and a few other stupid and ignorant attempts. But, I would guess it was from that.
minimac21234 said:
I know I attempted ICJ
Click to expand...
Click to collapse
There you are. That is surely the culprit.
iElvis said:
There you are. That is surely the culprit.
Click to expand...
Click to collapse
Lol... I knew I could get it out of him
Just jokin, hope everything works out OP... just keep following absolutelygrimm's unbricking thread and hope for a breakthrough
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.
xophere said:
I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.
Click to expand...
Click to collapse
If you had the 1.14 hboot you are Sol. Check my signature
Sent from my One X using xda app-developers app
smh ....... so many of these topics ....
xophere said:
I have an ATT HTC X one I had been running a clean ROM. I searched for a Jelly Bean ROM I thought I correctly identified my phone but...
After installing slim rom I get nothing on power on. And I get nothing with the charger plugged in.
Sucks these devices have such similar names. I suppose things went so well last time I was somewhat more casual.
I am leaving it plugged in over night.
Currently on Linux but do have the Windows 7 boot disk I used to do the rooting.
Can someone point me to a description of possible solutions?
Clearly the take it back to ATT and say it just stopped working one is on the list.
I have seen the attempt to boot and power cycle while watching for auto detect devices. I certainly can put a mini linux on a thumb drive.
I suppose the goal is to somehow write something that can boot strap me back?
I am a Linux savvy person so I can use dd if needed. Just need someone to contact me to point me in the right direction.
Click to expand...
Click to collapse
Still happening...crazy...{banging head}
No one reads all the warnings we put up. Why do we bother?
Sent from my HTC One X using Tapatalk 2
You bricked, and now you're mad. I don't get it? If we put up giant flashing red warning all over this site, it still wouldn't do any good...
Before I get flamed and what not over calling you mad, take a look at the post in the unbrick evita thread.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Unfortunately I've just done the same thing.. Got casual as this fellow previously stated.
So, not sure what to do with it now, any pointers?
voltarian said:
Unfortunately I've just done the same thing.. Got casual as this fellow previously stated.
So, not sure what to do with it now, any pointers?
Click to expand...
Click to collapse
What hboot were you on?....If you say 1.14 I'm sorry but you have a paperweight anything under is fixable
omario8484 said:
What hboot were you on?....If you say 1.14 I'm sorry but you have a paperweight anything under is fixable
Click to expand...
Click to collapse
I'm not sure, but probably. My friend had told me about this Ice Cold Jelly or something that I should get. For some reason I didn't even check that it was international. Though I was wondering more along the lines of warranty, could I possibly take it to an AT&T store and get a replacement?
Searched some forms relating to this and really wish I came here before making the attempt based off of all the warnings. Good excuses I can come up with.
voltarian said:
I'm not sure, but probably. My friend had told me about this Ice Cold Jelly or something that I should get. For some reason I didn't even check that it was international. Though I was wondering more along the lines of warranty, could I possibly take it to an AT&T store and get a replacement?
Searched some forms relating to this and really wish I came here before making the attempt based off of all the warnings. Good excuses I can come up with.
Click to expand...
Click to collapse
None. Honesty is what we promote on this site. Not lying because you were to lazy to read.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
I know i'm sure its been asked before in some way or another,
But to be fair I did some research, and haven't quite come up with an answer that has solved my problem.
So I rooted my AT&T HOX 2.20 today, felt great after I successively rooted my phone, bragged to my GF about how smart I am (not really =/ haha)
Was looking through some custom ROMs and what not, and which works best for myself. I ended up choosing this one below.
onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2
My recovery is TWRP 2.3.1.0 I believe. At least thats what my .Img file is.. (openrecovery-twrp-2.3.1.0-evita.img)
So I installed this ROM by TWRP, did the whole clear cache etc - I DID MAKE A BACKUP of my stock ROM (all caps because I think its important?)
SOOOOO I believe the problem is I missed a step...
I wasn't thinking I guess... and maybe rushed it a little...
But I didnt flash the boot.img file... I now understand HOW... but my phone wont turn on.
I tried holding the power and volume down rocker to put it into recover but nothing happens. No flashing LED's... nothing.
So I know im going to get flamed for being a "noob" but honestly.. this is my first android phone (slow adopter? ) and I really did enjoy it... Would love to have it back. Any and all assistance will be thanked, and hopefully passed on if anyone else has my specific problem.
Cheers gents.:good:
Snuff
SniffSnuff said:
I know i'm sure its been asked before in some way or another,
But to be fair I did some research, and haven't quite come up with an answer that has solved my problem.
So I rooted my AT&T HOX 2.20 today, felt great after I successively rooted my phone, bragged to my GF about how smart I am (not really =/ haha)
Was looking through some custom ROMs and what not, and which works best for myself. I ended up choosing this one below.
onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2
My recovery is TWRP 2.3.1.0 I believe. At least thats what my .Img file is.. (openrecovery-twrp-2.3.1.0-evita.img)
So I installed this ROM by TWRP, did the whole clear cache etc - I DID MAKE A BACKUP of my stock ROM (all caps because I think its important?)
SOOOOO I believe the problem is I missed a step...
I wasn't thinking I guess... and maybe rushed it a little...
But I didnt flash the boot.img file... I now understand HOW... but my phone wont turn on.
I tried holding the power and volume down rocker to put it into recover but nothing happens. No flashing LED's... nothing.
So I know im going to get flamed for being a "noob" but honestly.. this is my first android phone (slow adopter? ) and I really did enjoy it... Would love to have it back. Any and all assistance will be thanked, and hopefully passed on if anyone else has my specific problem.
Cheers gents.:good:
Snuff
Click to expand...
Click to collapse
I'm sorry as of now your phones dead...you flashed a Rom for the international one x not the one xl...I'm sorry:crying:
You chose the best first/last Rom for your new paperweight
Sent from my HTC One XL
a box of kittens said:
I'm sorry as of now your phones dead...you flashed a Rom for the international one x not the one xl...I'm sorry:crying:
Click to expand...
Click to collapse
Whoops!
I linked the WRONG place I got the DL...
Correct one:
onexroot.com/one-x-roms/icecoldjelly-aokp-android-4-2-1-rom-for-htc-one-x/
Hopefully this is not the wrong one... If it is... Oooooops.
You have an ice cold brick now
Sent from my HTC One XL
SniffSnuff said:
Whoops!
I linked the WRONG place I got the DL...
Correct one:
onexroot.com/one-x-roms/icecoldjelly-aokp-android-4-2-1-rom-for-htc-one-x/
Hopefully this is not the wrong one... If it is... Oooooops.
Click to expand...
Click to collapse
Never mind... looks like this is the international one too....
Greaaaat.....
So theirs no way to fix this....
At all?
The options depend on who you got it from or if you have insurance or if you want to be honest and call htc.
Sent from my HTC One XL
Hey man I honestly suggest mobiletechvideos.com they are a great jtag service which what you need for only 60-70 dollars and its fast! That's probably your best route
954wrecker said:
Most people who do what you did enjoy defrauding the company they got it from right away
Sent from my HTC One XL
---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------
Some classics are the guy who ran his phone over after getting mad at it or the guy who dropped it in the toilet or the one who had his kids break it. The options depend on who you got it from or if you have insurance or if you want to be honest and call htc.
Sent from my HTC One XL
Click to expand...
Click to collapse
Yeah.. I'm not lookin into defrauding anyone..
I'll shoot HTC an email and see maybe if theirs anything they can do on their end..
If not, my stupid mistake.
Wish this guy made it a little more clear for us noobs that the ROM was for international versions only =/
Oh well..
Call HTC they are ok sometimes it's free or $100 something depending on if the rep feels sorry for you or respects your honesty
Sent from my HTC One XL
So.. Funny enough... When I bought my phone from the AT&T store... the somehow mixed it up and gave me the one XL (from Australia)
So AT&T is gettin me a new one for free... ?
I called HTC to get them to repair it (with me paying of course, i admitted to rooting my device)
Then she asked for my IEME number or what have you... which I gave her and she said its a ONE XL not one X.. haha
So all in all... new phone cause of AT&T's screw up? win?
I thought AT&T only carried the one xl.. and not the international one x.
exad said:
I thought AT&T only carried the one xl.. and not the international one x.
Click to expand...
Click to collapse
AT&T only carries the One X, not the One XL
Did it have the att logo or the htc logo? No big deal either way, these phones are nothing to them, they just want you to keep paying them that fat monthly bill. I'm sure it had the att logo on the screen, the att box, and the att bloat too.
Sent from my HTC One XL
hello
Yep,
One X box, bloat ware, and AT&T logo.
I explained to the AT&T rep that I ROOTED my phone... he said well thats not the problem.
The problem is they sold me something that was not intended to be used in the US so they are going to replace it
Caught a lucky break!
Well att calls it the one x but in all reality its the one xl...the "l' indicates LTE...att just doesn't like putting down but hmm ok just be happy you got off easy!
Okay, before I get started, I am no noob when it comes to adb, linux, qpst, and htc phones. That being said, I was recently making and flashing several splash screens for my AT&T one x. unfortunately, I made a typo whle "dd" pushing the last one to my phone. In the typo I sent the splash screen to blk0p4 instead of 0p14, so when I typed in "adb reboot" my phone shut down, and never came back up. It now shows as QHSUSB_DLOAD in windows. I've spent countless hours searching xda, android central, and various other sites for a possible fix. I've tried the unbricking project, Jet method, and everything else I can find. The device shows up in linux, but my partitions do not show. So basically what I'm looking for is anyone with any fresh ideas on how to get it back to life. My warranty is void, as my phone is disassembled right now, so the battery didn't die while stuck in this mode. I'm really hoping I can escape this without sending my phone into jtag service. Anyone with any ideas to help? If I'm not around on XDA, you can usually always get me on gtalk @ [email protected]. Hopefully someone with more knowledge than I, can help me get my phone back in working order.
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
iElvis said:
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
Click to expand...
Click to collapse
yes, the phone came to me with hboot 1.14. And the only thing I knew about 0p4, was that I had to hex edit it to htcdev unlock, before s-off. Everything keeps pointing to jtag being the only option to fix my phone.
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Myrder said:
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
kind of figured that. I've searched everywhere trying to find another fix. Looks like I'll be paying $65 to send my phone in for jtag...
Mods can delete this thread if you wish.