Related
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.
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
MyronJ906 said:
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
Click to expand...
Click to collapse
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
adulel08 said:
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
Click to expand...
Click to collapse
lol you helped with a good laugh. That's genius, dude
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------
Can't seem to edit my post. I didn't realize you were using the other microphone. You should run the ruu regardless to at least try and sort out any sort of software issue.
Sent from my HTC One XL
ECEXCURSION said:
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
Click to expand...
Click to collapse
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
MyronJ906 said:
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
Click to expand...
Click to collapse
The microphone volume is a perennial problem with this phone. No one seems to know for sure what causes it. Reseting and ruu'ing ought to fix it.
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
MyronJ906 said:
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
Click to expand...
Click to collapse
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
iElvis said:
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
Click to expand...
Click to collapse
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
MyronJ906 said:
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
Click to expand...
Click to collapse
Did you relock? An RUU will fail otherwise.
iElvis said:
Did you relock? An RUU will fail otherwise.
Click to expand...
Click to collapse
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
MyronJ906 said:
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
Click to expand...
Click to collapse
Unplug your phone, turn it off, and restart it. Sometimes that helps. It won't boot, but you can get it back into the bootloader.
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
MyronJ906 said:
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
Click to expand...
Click to collapse
Bootloader.
Pretty sure my drivers have just fubarred. I'm not showing up on adb devices either. GRRRRRR this is driving me mad
EDIT: Finally got the RUU to run. Had to replace the standalone HTC drivers with fullblown HTC sync but it's whatever lol. Now to see if the RUU actually fixes the problem
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
MyronJ906 said:
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
Click to expand...
Click to collapse
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
iElvis said:
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
Click to expand...
Click to collapse
Yeah, I meant the microphone still isn't working. I've been on the stock RUU, AOKP, and Nocturnal. All of them have the same issue so I'm expecting that it's hardware.
I just don't know what to do guys. I guess I'll e-mail HTC, swing by the AT&T store in hopes of something, and call it done. I find it ****ty that the guy won't cooperate so far because truthfully I *would* at least cooperate but it's tough when he says it was working when he had it and I say it wasn't working when I had it.
BUT he says that he didn't make any calls that day. However, he "knows it was working when he gave it to me"
Guys, I just don't even know what to do. If I can't get it replaced, he completely won out on the trade. I was originally asking for + $100 and lowered it to + $50 for him. Yet he doesn't want to do anything for me.
I want to handle all of this responsibly, but I also want a completely functional phone
MyronJ906 said:
Can I (legally) mark the S3 as stolen?
Click to expand...
Click to collapse
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
redpoint73 said:
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
Click to expand...
Click to collapse
I did mean for the insurance claim. I didn't want to do it fraudulently which is why I asked. I wasn't sure what the exact definition of stolen (or even lost) in this regard is. But this doesn't count so that's no longer an option. Haha I now see that the AT&T warranty plan doesn't cover user idiocy, just drops and spillage.
I'll RUU again then install an AOSP ROM. I'm pretty sure it's the hardware mic that's busted though. Does speakerphone use a secondary microphone? I imagine videorecording does. If so, do the camcorder and speakerphone use the same mic?
Maybe the noisecanceling mic is screwing things up and that could be software but I think the microphone is just physically broken.
Idiot me, being the hardcore modder made changes to the phone *before* testing for the microphone. In my defense, I've owned the One X before so I knew what the hardware was capable of. I knew the current state of ROMs, so why not pick up where I left off?
I'll send HTC a pity e-mail and see where that gets me. Better to try and fail than to never have tried at all.
EDIT: I wanted to ask as well, does anyone think ROM flashing/BL unlocking etc. Really could have caused this? I mean, if it did there's no reason different software shouldn't fix it. But if it's hardware, that establishes that it's more likely that it wasn't my fault, right?
I bought this phone maybe two months or a month and a half ago. At the time, I had no idea that root was impossible. I also own a Play Store Galaxy Nexus, so after being so free to do what I wanted with it for so long, the One X was giving me anxiety fits (anxiety over a cell phone, yes I know).
I don't really need two phones, so I should sell one. Which one though? The HOX is a monster in every aspect, but I can't fiddle with it. The Nexus is so nice in that arena, but the camera is borderline putrid and the screen is sort of dark. Plus I have good eyesight, so the Pentile nature of the screen boasts its presence at every turn. It runs everything pretty well and gets updates very quickly. The development is second to none. But the HOX. That screen. That camera. It has LTE. That snapdragon. I'm going to have less "spending money" available to me soon, so I want the phone that's most futureproof. That's obviously the HOX. Software is important. So what do I do? Hold out for the next Nexus? Sell both and get a Galaxy S3? I really prefer the HOX over the S3, so I don't want to do that. If only I could root the damn thing and put CM10 on it like I have on my GNex. Damn damn damn. I guess I'll be patient and see if the heroes of legend at XDA can work their magic.
I sift through the forums reading about this and that. CM10 on the HOX has a bunch of wakelocks? Wifi problems? Man, is it worth it to wait or should I just sell this thing while the prices are good? AT&T is purposefully crippling my baby. The one phone I want and I'm at the mercy of damn AT&T. Why can't HTC have the sort of power necessary to stand up to carriers like that fruit company from California? If only.
And just two nights ago, BAM. I worked until 12:30AM and have to return to work the next day at ~4:30AM, not to mention wake up at 3:30 so I can shower and shave with time to pick up a coworker at her place. It's 1:30 and I really ought to get some sleep. But I'm not finished with this delicious beer yet. Guess I'll check XDA in the meantime. Oh god... "Exploit found" says the bounty thread. Welp, so much for going to sleep now. So after fighting with both my computer and my phone for a while, my bootloader is unlocked. I don't know how to root yet because this is my first HTC phone. But we're off to a good start. I get an hour and a half of sleep and come home from work, tired and miserable. Should I nap? Hell no, I need TWRP. To XDA! Hello, custom recovery. Now I need root. What's this? A flashable SuperSU .zip? Hmm... let's try it. Better install a root check app since I don't know how to tell if I have root otherwise. Success! Well damn it, now I'm ready to flash the CM10 zip from Goo manager. Oh, no I'm not. I have to flash the boot.img with fastboot first. I've never done this before (GS2 and Gnex were my previous phones) and I don't know what the hell S-On is, but whatever. Let's do it. Good Lord, it worked. I'm one step closer to the love child of the Gnex and HOX that I've been so long waiting to adopt. Now I can flash the CM10 zip? Alright, let's do it.
And here I am. This is what I've been waiting for. After switching my sim card between my HOX and GNex almost every other day, I can finally leave it in one phone for a while. The ROM I'm running is labeled "experimental," but it really seems to be anything but. Aside from some visual quirks and some in-call echo, I've had practically zero issues using this phone. The battery life is comparable to stock, and while it seems to be lacking some of the butter of the CM10 Gnex nightlies, it's just fine for me. Fast. Stable. Powerful.
So this is me gushing over the devs here at XDA. Thank you for all your hard work and dedication to righting what is repeatedly wronged by the juggernaut telecoms here in the US.
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
cool man , dont forget to try other roms! many of them are cm10 based, you should try paranoid android :good:
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
Lmao
Sent from my HTC One XL using xda app-developers app
What can I say. The OP is a showman haha.. awesome OP, glad to have you here in this awesome community
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
Lol that's just plain funny
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
still fraud. :'(
Sent from my One X using xda premium
To the OP, I felt the same type of excitement when I saw it. I appreciate the time and effort put into this exploit and anyone who may have helped. It's even more exciting that theres awesome people who freely release these to the public so that awesome ROMS can be put on. I was so ticked off with my locked bootloader I almost switched it out for a motorola atrix HD. The first time I took it back was legit though, it had the muffled voice syndrome, and the phone was only 6 days old, the corp store tried to give me a refurbished phone! ... I refused it and got a new one, and that one had battery issues, had to take it back a second time but finally got it straight right on the day of the root exploit. At the end of the week if I got any spare change I am definitely going to donate for the hard work it took and the time and patience.
area51avenger said:
While most people hate AT&T for locking the bootloader, you can understand why they did it if you read the threads here about people flashing incompatible roms and hard bricking their phones. Especially this guy:
Originally Posted by timthatank05:
no... after trying to get it to work all day yesterday, i finally gave up and drove the car over it and then called the insurance on it... no phone for a few days at least...
Click to expand...
Click to collapse
LOL, good quote find.
On one hand yes, I can understand why a company may lock down a bootloader and I am sure many companies going forward may get the same dangerous idea. Maybe its true intentions is to protect people from bricking the phone or wasting their time with claims etc .. but on the other hand imagine if you bought a computer and Dell or HP comes in and says, well we locked down the firmware we dont want you putting any other OS in there but microsoft. Also, on top of that we dont want you using any other video cards besides an ATI card .. to prevent you from this we locked down the firmware. It's poisonous to creativity.
I believe in open source and feel saddened when we get locked bootloaders. I love the Android OS, I feel it should be completely open without any company interferences so that many great devs can continue to create and modify the existing OS/ROMs. Its a two sided coin.
I really am loving XDA, so much useful info, so many things to learn.
Lmao I nearly messed myself when I first saw that thread. That douche is never gonna live it down.
Sent from my HTC One XL using xda premium
Stories like that kind of worry me, I just got the phone and love playing with Nova Prime but have dug into rooting it yet until I read more about it.
Sent from my HTC One X using xda premium
Everyone is guilty of the childlike excitement you get when you successfully root a new phone and see that first Rom you want to try
:fingers-crossed:
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.
Last week on Tuesday I decided to get a warranty replacement, now... I'm well aware that these are refurbished phones and that they can be damaged, etc. T-Mobile, however, assures you that they are to appear "Like-new". Well, the device came the next day as promised and what do I see? 10-12 dead pixels and... spotting behind the screen... like WATER DAMAGE! At this point I'm thinking... "Wtf T-Mobile?" So I give 'em a call, they tell me they'll send out another and that they are sorry for the inconvenience... Well, this time Friday rolls around and the delivery comes... I grab the box and get ready to open it with my Partner, jokingly I say to him... "Let's see how messed up this one is!" and I open the box... Well, the second one they sent has a LARGE chunk out of the MAO in the bottom left corner of the device... like it had been dropped. I'm pissed at this point... I call T-Mobile and because it's a defect in the "hardware" I had to take it down to the store to get a rep to verify that the device was damaged (also still in the warranty box they send out) and at this point they take $25 off my bill and offer me yet another warranty replacement!!! UGH!! So, the new one is coming today... If it's messed up I am demanding that they send me a new one. I'm so upset at this point... My device I sent to them to begin with was damn near flawless other than (from what I could tell) software issues.
What do y'all think? I'm starting to believe they don't even perform these so-called "Quality checks"
Been there done that I had to go through 6 phones. they offered me a brand new Galaxy S 2 . But it's backordered so I decided not to do it
Sent from my HTC VLE_U using xda premium
Spastic909 said:
Been there done that I had to go through 6 phones. they offered me a brand new Galaxy S 2 . But it's backordered so I decided not to do it
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
If I even get one more messed up one I'm gonna make them give me a new One S... I bought this phone, I'm sticking with this phone. They WILL give me a new one. Heh. Also, I came from the GSII... Don't do it... the DPI is weird and everything is HUGE on the screen. Lol. I didn't like it mainly because with the default TouchWiz roms you can't change DPI or the UI is all diff sizes and messed up... Now... On custom CM10 roms, etc you can change DPI and it looks amazing at like 200 DPI or so... but back then the bugs were too much to stay on custom roms.
Went through these with my wifes amaze. I demanded a brand
New one s and got it.
Sent from my SGH-T999 using xda premium
Daiskei said:
If I even get one more messed up one I'm gonna make them give me a new One S...
Click to expand...
Click to collapse
what are you going to do if they tell you to go pound sand?
I don't understand why you are warning people about their warranty...they are doing what they are supposed to be doing. I understand the frustration of having to keep getting a replacement, but at least they are cooperative and doing it. ..sounds like a good warranty to me.
Sent from my HTC One S using xda app-developers app
they sent me 4 defective replacement sensation 4g's until i demanded a comperable android replacement... after a couple of other rep's and explaining to them why a nokia lumina is not a comperable device then asking for a supervisor they sent me my One S free of charge, I offered to send my sensation back but they didnt send a box to return it in.... Thats a Win in my book. I did have to call back twice to get them to take the charge for the One S off my bill, which they did
Yea, I've never had an issue with T-Mobile warranty...that's how I got my One S...I had a Sensation, then complained enough, and they upgraded me to the One S at no charge. It might be a pain to go through numerous phones before getting a good one, but you can't beat the fact that they overnight you a phone with just a simple phone call, great service.
Sent from my HTC One S using xda app-developers app
Your talking about assurion right? cause theyre their own company. theres a big difference. and yea id be pissed to pay a deductible and get a messed up phone. the last time i had my phone replaced by them it was pretty much brand new so im sorry for your luck :/
Im more curious as to why you sent your original back, if all it had was a software issue?
Goatshocker said:
Im more curious as to why you sent your original back, if all it had was a software issue?
Click to expand...
Click to collapse
Agreed. Doesn't make any sense. You would figure that since he's on XDA, that he'd try to flash a new ROM, reflash the original, etc, to get it back to normal.
Then again, some people are hardcore about not wanting to touch their phone's ROM. I on the other hand, am absolutely disgusted by HTC Sense and all the fancy pants bull**** it has. Simplicity, minimalism, and speed are where it's at.
nickmv said:
Agreed. Doesn't make any sense. You would figure that since he's on XDA, that he'd try to flash a new ROM, reflash the original, etc, to get it back to normal.
Then again, some people are hardcore about not wanting to touch their phone's ROM. I on the other hand, am absolutely disgusted by HTC Sense and all the fancy pants bull**** it has. Simplicity, minimalism, and speed are where it's at.
Click to expand...
Click to collapse
It stopped saving screenshots (not a big deal) however, it shortly after started saving all photos taken with the camera as 0byte files. NOTHING fixed it. I even put the phone back to S-On and unlocked, re-rooted, redid the S-Off... Nothing helped. Kinda useless if I can't take pictures. I also tried many different roms.
Also, the warning was to say that if you need a replacement... make sure you can deal with going through 4-5 before you get one that is fully intact. The last one they sent me (#3) had the screen popping up out of the device. You could see the button backlights fron the side if you looked at it, got yet another coming tomorrow.