Related
So I am one of the few that cannot do the goldcard method. I was wondering if anyone has tried to use the G1's one click method on the mytouch 1.2?
I want to try it but I fear that I may just brick my phone (I JUST UPGRADED AND CANNOT AFFORD TO BUY ANOTHER ONE ANYTIME SOON).
I was wondering if anyone out there knew where I could find the motherboard specs and radio / spl specs for the G1? If they are in any way alike I will def be testing the G1 method on my phone but for now...I dont want to risk it.
Any help would be greatly appreciated. thanks
P.S. hope this is in the right section,
There is only the Goldcard method for now, sorry.
whats wrong with the goldcard method?
Its not the easiest our safest way to root, but its worth it.
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
it wasnt that hard... I got through it pretty easily once I spent an hour to realize I didnt have USB debugging turned on
h it was easy for me too, was a general statement. might I ask why you can't do it that way? Is it just you have an incompatible sd?
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
alright so I'm not much of a dev, if anything a noob when it comes to that. But I did work on somethings for the Motorola cliq and have learned quite a bit, but I was wondering, has anybody started trying to get those?? I was thinking if we could figure those out right now then once the bl is unlocked we be good to go.
I don't know much on what is required to figure them out but if nobody wants to do it would you guys be willing to help me along the way?
Sent from my HTC Sensation 4G using Tapatalk
Gone fishing...
GROGG88 said:
Guys, there was another one of these reports about sudden catostrophic failure today:
CLICK HERE FOR THREAD
I think it's high time to get to the bottom of this! To ALL users who have been affected by one of these events, PLEASE post the following information and nothing more:
1. ROM
2. Kernel
3. Firmware
4. Radio
5. OC/UV settings (if applicable)
I'd like to track these stats and tally them up here in the OP to see if we can find a common culprit. I don't really suspect it's a ROM issue since there have been reports on multiple ROMs, but I don't want to rule that out...
-Thanks
Click to expand...
Click to collapse
Hi,
Yes,I have noticed this worrying trend...
One of the things to keep in mind when looking at responses to this kind of poll is to realize that we're looking at an adversely selected population of respondants.
Everyone who posts here about a failure is on XDA.
Everyone on XDA meddles with their phone.
So it's easy to conclude that meddling with your phone causes the phone to fail. (Or that ARHD causes the phone to fail because 90% of custom ROM users are running ARHD)
But that doesn't actually prove anything about the relationship between meddling with the phone and the phone failing because we're not including the 98% of Sensation users who run the stock ROM, don't even know you can replace it, and still have hardware failures.
In order for this poll to be worth any statstical value, we'd need to know what the general failure rate is among all Sensations, including the 98% that aren't rooted, s-offed, or anything else of that nature. (And I'd be willing to bet that someone here is good enough with Google to search out those stats. I guarentee HTC and the Carriers keep that information. It's just a matter of how public they make it.)
If the failure rate among people who flash custom ROMs, kernels, radios, etc is significantly higher than among the general population, then we can conclude that we're doing something risky.
If the failure rate on rooted phones is similar to the failure rate of the total population, then flash whatever you like with joy in your heart. You phone might die on you, but it would have died anyway. You're not the problem.
I would expect the rate of reported failures to be slightly higher on XDA than among the general population even if it's a general hardware fault. That's just because we're more likely to talk about a failed device than the average consumer who has a higher chance of just buying a new one and never talking about it.
Just looking to see if there's common ground between them...
Yes it would help to just narrow it down and try and deal with it unless we want the problem to spread. And now saying that I'm going off arhd to virtuous inquisition after reading previous posts
Sent from my HTC Sensation XE with Beats Audio using XDA
Here is another thread from last week, I think he was running Virtuous before it died on him, but not 100% sure.
http://forum.xda-developers.com/showthread.php?t=1624293
I agree with the failure rate statement, just seems like the folks posting these having been flashing for a while and seems a bit different than the "HELP, I JUST BRICKED MY PHONE" type of thread
Yes..I am not sure if this issue is just a hardware problem and it just happens it died...or if it's related to what we're flashing and modding. And yes...I had flashed ROM a few times before...including insertcoin GB, and ICS...and everything was working....
After I installed ARHD..it seemed fine too...it was running....until I made a phone call.. then it died. So was it just coincidence that it happened after I installed that ROM (include 4ext recovery, radio recommended for t-mobile)...or it's something related to the files we're flashing. I don't think it was from flashing incorrectly since everythig was running for a bit.
If it's just a hardware pb with HTC...then surely there's nothing we can do....but if something is up with the files we're flashing that's killing the phone...as there seem to be much more of these occurences lately with the new ICS roms....then maybe something is up and hopefully someone smart can pinpoint the pb.
Do any of the Devs know this is happening?
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
gustav30 said:
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
Click to expand...
Click to collapse
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
newr said:
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
Hi - I'm just wondering if there is something up with that particular update that is sometimes wreaking havoc with ICS roms for T-mobile USA users.
The reason I pointed it out is because its not a necessary update to install an ICS rom on the Sensation. We just need the latest firmware package and the Rom.
AFAIK, that update is only supposed to enable faster data in the U.S. Probably everyone else in the world outside of the USA, installing ARHD, skips over that update.
I guess it would help to know if the same type of failures are happening to people outside the U.S and who never installed that update.
I know the failure is not limited to just ARHD. So its possible though at one point someone went to the ARHD thread and installed that radio update with ARHD Rom, then jumped ship to say Virtuous and then had a phone failure, because that update is not part of the Rom itself.
This is just speculation - but trying to rule out possibilities.
Hmm..possibly...but I did read mail from someone that's not in U.S. who had dead phone similar to mine....so unless they installed that radio file...it should be ok?
gustav30 said:
Radio recommended for T-Mobile USA in ARHD... I know there was something posted that was supposed to help T-Mobile USA phones be a bit faster in ARHD, is that what you flashed?
Just found this in ARHD:
HTC Sensation 4G (U.S. T-Mobile PG5810000 | T-MOB010) users can flash this for better signal and data speeds!
Wondering if this could cause the problem?
Click to expand...
Click to collapse
That is not a radio. It is rcdata for the radio and the build.prop needs to edited to match. I don't know what the end result of a long term mismatch would be (I suspect nothing bad), but I have run both dish 2 and dish 3 settings with no long term issues on either...
newr said:
Yes, this is what I flashed as part of the update. But it doesn't explain why others have same pb?
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
I know you are one of the affected users. Please do me a favor and post the info specifically requested in the OP... I'm specifically interested in what kernels, and cpu settings the affected users were using!
i flashed that thing too when i was running a different rom then coindroid.. luckily im not one of the affected users...YET lol
This isn't looking so good... I hope the devs will figure this out before this thing catches on like wildfire... eek
I was about to get the Sensation...It seems i will have to think again!
I had installed AOKP and when I format data and sd card to factory reset my phone won't turn on anymore...I have warranty and service changed my motherboard...now I can not unlock bootloader anymore...
I should close this thread since it seems nobody can read the OP and follow directions...
I just think they're all dying now because it's been approx a year that the phone is out now? Maybe time is the killer! Afterall, I wouldn't think that the majority of users baby their phone... I've seen some people abuse the living crap out of their poor phone! Dents, scratches, marks everywhere. I'm not too surprised seeing this kind of issue after a year or so. Mine is slowly causing problems too (only prob at the moment is dust under screen and I don't like the microphone either...) and I baby this thing.
Man the same **** used to happen with the G2 and the myTouch4G, the emmc chip in the phone would just randomly give out after about 1 year. ****ing HTC phones, man.
i as using insert coin sense4 rom when mines stop turning on.........all i get is on and off vibrates
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.
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.