Database Info

Bricked my shift, wont boot, need help bad and fast!!!

I was having trouble trying to flash back to the orig sprint ruu. After toying around, I finally got it to flash completely, only thing is...it still had the METRO banner. I ignored it.
So I hit the search bar and was looking for the best way to root it. Several options came up, I clicked one, and proceeded. Now, after trying to restart the phone, it will not boot at all, it wont go into recovery, all it was doing was flashing a steady orange light. After unplugging and replugging for a few hours, now all it does is just flash a blinking orange light.
I tried to use the ruu flash again on the pc, it gets to the point where it says the img version: version-main FAILED (status read failed (Too many links)). I select to update the current Rom version and it just hangs.
Here is why Im having these issues. I used this method http://forum.xda-developers.com/showthread.php?t=858996 which isnt even for the shift, its for a damn htc glacier mytouch. I never browse for other phones except the evo, but i was taken there from the search while I was inside the shift sub-forum. A mistake that could have been prevented if only I didnt trust the search bar that it would stay within the "shift" sub-forums. Feck, Feck, FECK!!!
Then, i went here http://forum.xda-developers.com/showthread.php?t=1010397&highlight=bricked to figure a way to unbrick it, everybody is saying this guy need a new battery. I doubt that will help my cause.
Right now, my epic is activated? Should I switch the shift on that line, and take it in to the sprint store? Swapping phones on sprintpcs.com just involve adding in meid numbers thats on the phone only, or do the phone need to be on (booted up) to add more numbers? Never done it and just trying to figuer out my best option here? Or is there any other way I can atleast get the shift to boot so i can reflash the ruu?

Congrats you successfully truely bricked your phone. There is no way to recover from it. That sucks dude.
Sent from my HTC Glacier using XDA App

TRUE BRICK? thats not what I wanted to hear. By using the flash ruu, doesnt my phone needs to be turned on? Or that doesnt matter?
Im hoping that since its all software based modifications that was made, then it should be as simple as re-writing those software/programming mods?

Head to the irc stickied at the top of the page. If anyone can help you it will be there but I wouldn't hold out hope.
Sent from my PG06100 using XDA Premium App

I'd activate it and go to Sprint. Don't tell them what happened. They'll just order you a new one if you have insurance and if not you'll have to pay $35.

See if you can find a charged battery for a Shift, TouchPro2, Hero, or original Evo and pop that in, it's worth a try. I know someone else with the flashing orange light was able to fix their phone by using a new battery.

mulhiny said:
I'd activate it and go to Sprint. Don't tell them what happened. They'll just order you a new one if you have insurance and if not you'll have to pay $35.
Click to expand...
Click to collapse
That's what I'd do. But they might charge you the deductable ($100) . Just be sure to under no circumstance tell them you did it. Hell if it's truely bricked just tell them you dropped it in water. That way they don't even check it. But, remember that's just my opinion .

If you are using the dropping it in water method make sure you do get the battery wet as there is an indicator on the batteries to see if the phone has been wet. It's a paper strip and will turn pink when it has been in water...
Sent from my PG06100 using Tapatalk

If all else fails and you're planning a drowning defense, why not just drop it in the water (tee hee)?
Sent from my PG06100 using XDA Premium App

Guys, I've worked out an alternative solution, and its way much easier. Will update about my secret weapon in due time, lol.

Eek a true brick. That's scary as hello. I rooted via visionary and the dd method. I've only heard of bricks but never saw one first hand.
Sent from my HTC Shift using XDA App

i have never had to pay a deductible for a defective phone. almost every single phone i have had has had some issue that i havent been happy with, sprint has either replaced or repaired it at no cost to me. so dont get it wet, just take it in and tell them it cut out during a call or something, and now you cant turn it back on. done and done, you'll have your replacement.

Wife's Desire S won't boot, please help!

My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!

Well if your PC is not recognizing the phone, then there's not much you can try I guess (other then factory reset.) Maybe someone is gonna come up with something.
Aren't the gamesaves on your sd card?
There have been hardware issues associated with multiple downloads from the market and pulling the battery. This might or might not be the case. However you are covered with warranty in case it is.
Sent from my HTC Desire S using XDA App

esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
If she created a HTC Sense account and had set it up to sync then her texts would have been saved online.

If no other options download the corresponding to your region RUU (ROM Update Utility) from here. Then reboot to Bootloader (VOL DOWN + POWER Button). Make sure that you have HTC Sync installed. Go to fastboot screen (you should see FASTBOOT USB line). Start RUU.exe. It will handle everything automatically and hopefully you will have a brand new Stock system again.

If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!

olyloh6696 said:
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
Click to expand...
Click to collapse
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.

An boot loop isn't
an real indicator for fried emmc, most of the times you just somehow messed up part of the software or the partitions, this:
http://forum.xda-developers.com/showthread.php?t=1292730 it's an really fried emmc.
Let's try some solutions before destroying any hope!
Swyped from my Desire S

amidabuddha said:
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
Click to expand...
Click to collapse
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium

esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
so, have you tried hard reset/factory reset. let us know what happen than. next time never pull out battery when your phone freeze. just press vol up + vol down + power button (all three hardware button) and the phone will restart. I personally had this problem few times and able to recover my device. start with hard reset your phone.
look at ben_pyett signature. you need the adb+fastboot and htc drivers for your windows pc to detect your device. I'm using linux and I don't need those drivers.

olyloh6696 said:
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.

Update: thanks for all the suggestions. I couldn't get any of it to work, including factory reset.
We are going to send the phone in for a warranty repair, most of her personal stuff is on her Google account or the SD card, so no major problems.
The HTC Sense website with SMS backup never worked for her, there is no option to log in from the phone.
As much as i love Android I am shocked that hitting "update all" in the market and/or pulling the battery can brick a 400 $ phone. Even buggy old Windows ME was fine if you pulled the pover cord.
My iPhone friends will laugh at me well into 2012 if I tell them this.
Do HTC have more faults than other brands? Both our Desires have had trouble. I am about to upgrade mine, maybe should look at another brand?

There is some hope!
amidabuddha said:
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Click to expand...
Click to collapse
+1
I'm afraid that I must agree.
In the early days of this problem, I too was probably guilty of announcing too early to users "that's you've fried your eMMC chip - that's a warranty return" where as over time we've now come to believe that this still a chance of hope, albeit not great or guaranteed, but none the less, fortunately several people have managed to recover from this situation, by a variety of means.
So even though the possible outcome might not be likely, I think that we should attempt to always suggest that there might be hope at least until we've tried all the possible solutions and now luckily the various users have compiled guides of the suggested options so this isn't that difficult.
The only time when I'd suggest that a user should probably instantly return a device, is if they are completely non technical or have a brand new device which is still S-ON. In which case they may as well return the device under warranty and get a replacement device or motherboard which will at least contain the non dubious/faulty chip, and will remove the possibility of future occurrence completely - so they'll actually be better off for the future!
esbenm said:
Update: thanks for all the suggestions.
Click to expand...
Click to collapse
Sorry to hear this. You were just unfortunate and what happened to you is rare, also it's not a fault of Android but, a HTC eMMC chip hardware issue caused by a particular dodgy version of the eMMC chip that comes on some of these phones.
I believe that HTC realised the fault and replaced the chip with another make after a fashion. So hopefully you'll get the different chip on your replacement device/motherboard.
I also think that they've changed the market application so that it downloads one application after rather than all the applications together, which was known to cause a device freeze, which often was followed by a battery user battery pull - which then led to this problem.
Next time... Never pull the battery! there are always other options.
Take care and good luck.

[Q] Phone Bricked...I Think...

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.

[Q] Is my phone bricked???

Okay, I bought a used MT4GS from a fairly reputable phone reseller called CPR (cell phone repair.) I bought it back in March or April of this year. I immediately rooted and installed a custom rom and CWM. A few months ago I upgraded my rom to CM9 and about a month ago I began having problems. The isses were minor at first, the hardware buttons on the outside of the phone would stop working but I could open the phone and use the ones on the keyboard. Then in the past two weeks all of the buttons would stop working. I thought it was a hardware problem so today I dropped it off at CPR and they took it apart and tested all of the buttons. According to them all the buttons tested out fine. So I have a phone that the only thing that works is the touch screen. Here is the odd thing. If I hold the volume down while booting I get the fastboot menu and can navigate it using the volume keys. If I go into recovery mode none of the buttons work same as in the phone. So either this is a software problem or a systemboard problem. Because my power and volume buttons work on the recovery menu I'm inclined to believe it's a software problem but I'm a little lost on how to fix it. I just tried to boot the phone again and it's now stuck on the boot animation and does nothing. Please help!!!

I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.

WeekendsR2Short said:
I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.
Click to expand...
Click to collapse
Yeah I actually did that last night. Got to watch the intro animation from HTC/T-Mobile etc. Still no buttons. I'm guessing that the system board has a bad chip since the buttons tested out okay. That is more consistent with the gradual failure than a software bug. Now if there were a rom made for a phone without buttons then I'd be in good shape. Luckily I found an identical phone on Craigslist for $85 which I feel is reasonable for a discontinued phone. Does anybody have recommendations on QWERTY Android phones for T-Mobile that are better than the MT4GS?

Someone mentioned that Samsung is coming out with one soon but I can't remember the name for squat.

If it's for T-Mobile then I suggest the Samsung Relay 4G. Else better wait for Samsung Stratosphere 2 fior Verizon if you might consider changing networks for the sake of a better phone.

THAAAAT'S the one! Samsung Relay 4G. Thank you kind sir!:good:

Samsung took over for HTC, who took over for crApple.

blackknightavalon said:
Samsung took over for HTC, who took over for crApple.
Click to expand...
Click to collapse
Samsung also.

First off let me say I'm sorry about the death of your MT4GS - mine died over a month ago and I'm still in mourning. However, the Relay is a nice little device. I don't want to be accused of attempting to recruit people again, but at the risk of saying so it is an upgrade from the HTC product in MOST ways - some people don't like the screen as much and the camera is definitely inferior. However, it's a nice device. I'm happy with it honestly. TouchWIZ takes some getting used to but since HTC didn't give us ICS, even ICSense... and Samsung has ICS on here with JB to come... I'm satisfied. If you are still curious we have a thread in the G2/Desire forum that we are using until XDA gives us a dedicated forum.
Sent from my SGH-T699 using xda app-developers app

[Q] Apeared to have bricked my phone. Recommendations?

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