Related
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App
mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char
If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App
Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.
I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.
Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt
Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.
As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt
happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck
Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....
actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.
Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?
So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium
Hey guys, I'm considering going with they option of rooting my HTC Sensation, but I'd like to clear something up beforehand.
At the moment Im on a pay monthly contract with my HTC Sensation and I pay monthly for insurance on the handset, before I go rooting my phone, if for some reason I need to send this phone off to my provider will my insurance be void? Or is this just the case if I haven't managed to return the phone to stock setup?
Id really like to try rooting my phone, but I dont want to have the problem of not being able to send the phone off for repairs or whatnot in the future. By repairs, obviously Im not referring to any problem that could occur during the rooting process, I mean more in the sense of hardware issues etc.
Any help is appreciated, and I apologise if this has been asked/answered before, I did do a forum search but found nothing.
Thanks.
You can S-Off your device without unlocking the bootloader over HTCdev. This way you can root and flash custom ROMs/kernels without loosing your warrenty.
If you have issues and you have to send the phone in, you can just run an RUU for you phone and S-On it again. Nobody would know that you have rooted it.
And if you want to S-Off take a look at the Hboot version! Hboot 1.2x has a different and more difficult way of S-Off'ing.
Oh right, how would I go about S-off'ing my phone? Would it still require me to go through the whole root process first off?
Thanks for your help
First we have to know your H boot version to direct you to the proper guide. To find out, pull battery, put battery back in, then at the same time press power and volume down button. Hold. Then you will see a screen pop up. Look at the information on Top of the screen. Then tell us your H Boot version. by the
Way, I also pay insurance every month on my device and I'm rooted and S off. If anything should happen I would restore back to stock and S on again. This way they would not know device was rooted. Hope this helps.
Sent from my HTC Sensation
Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks
Gaz1521 said:
Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks
Click to expand...
Click to collapse
Both process are reversible, once its s-off and rooted, just dont change your hboot and your good to go. I had the same concern, yet when i needed to return my phone for the warranty, they never even cared and sent me the other one without question (after i turned back the s-on of course). Follow Ganesh's guide here: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGNDWtlRFM7pBTIlQr-Y6Vd4nJEgw
Very easy and completely safe!
BoB!!
I suggest rooting and S off. I don't regret it for a second! I try all kinds of awesome roms and I'm able to customize to exactly how I want things! It's been a totally positive experience for me. As I mentioned in above post, I too pay the extra insurance monthly. If there we're a issue I'd return to stock. As above member mentioned he did it and didn't have any problems. I think once your rooted and s off you will be very happy. But do take the extra effort to s off because it's worth it in the long run and makes things easier for you, You will have the ability to do more with s off. Best wishes.
Sent from my HTC Sensation
Oh right, thanks you guys. I now feel more able to go ahead and root, now I just need to decide whether I think Im capable of doing it correctly.
Just had a look at that link you posted BobThaBear, it looks abit on the daunting side so Im going to have a long, hard think about it first.
Thanks for all of the help though, its very much appreciated
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
ok so i have an AT&t HTC one xl running the latest jellybam rom and on rohans B6 kernel. last night on my way to work i plugged my phone into my OEM car charger, the phone rebooted and was stuck on the red text screen saying its a development build....the phone has been dead since. I let my phone "charge" for ten hours but nothing. normally when the phone charges on or off it still gives off some heat but ice cold. when i woke up this afternoon i tried to plug my phone into the computer and run adb but no luck. But i know its not completely dead. the phone shows up in device manager and makes a little toggle sound when plugged in. its still under warrenty but im worried that if i send it in they will make me pay for the repair since its rooted and bootloader unlocked. ive attached a picture of my device manager. Anyone know of a way to fix this or where to look?
So your screen still turns on? Or is it dead and unresponsive?
If the latter, it sounds like the power management bug. I've seen a number of phones brick from this.
If your screen still comes on, it's just a matter of getting into the bootloader. Hold down power and vol down until the buttons flash, then release power until the bootloader screen comes on. Once there, you can run a ruu or reflash your rom/kernel.
iElvis said:
So your screen still turns on? Or is it dead and unresponsive?
If the latter, it sounds like the power management bug. I've seen a number of phones brick from this.
If your screen still comes on, it's just a matter of getting into the bootloader. Hold down power and vol down until the buttons flash, then release power until the bootloader screen comes on. Once there, you can run a ruu or reflash your rom/kernel.
Click to expand...
Click to collapse
i guess its the power management bug then. the only response i get from the phone is when i plug into the computer and the computer tries to install drivers but fails. screen wont turn on, no led, and no flashing buttons....is there any fix other then warranty claim?
SkizzyNinja said:
i guess its the power management bug then. the only response i get from the phone is when i plug into the computer and the computer tries to install drivers but fails. screen wont turn on, no led, and no flashing buttons....is there any fix other then warranty claim?
Click to expand...
Click to collapse
You might try the JET tool in the development section.
iElvis said:
You might try the JET tool in the development section.
Click to expand...
Click to collapse
ok would that be in the OG development or the other also thank you for your help.
EDIT: nevermind i found it. ill give it a try before work
Re: [Q] bricked one xl after charging
SkizzyNinja said:
ok would that be in the OG development or the other also thank you for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1966850
Sent from my One X using xda app-developers app
For some reason i couldn't get jet to work so i tried the manual unbricking thread method and couldn't get my partitions to shw up in linux. Im gonn send it in for warranty and pray they dont charge me for root and s off lol thanks for your help anyways guys
is your car charger a real "htc charger" or some generic crap? i've had generic crap kill good phones.
have you volume down + power to get into bootloader?
DvineLord said:
is your car charger a real "htc charger" or some generic crap? i've had generic crap kill good phones.
have you volume down + power to get into bootloader?
Click to expand...
Click to collapse
If he could reach bootloader his phone would not boot to QDL mode. It would boot to HTC Screen and not past that. the HTC boot Screen is comparable to a PC's POST. if no EMMC partition table is not detected, it's HTC replacement or JTAG.
I'm sorry for your bad luck OP. Please post back to let us know if HTC did in fact replace your phone. I am curious to see how things play out.
exad said:
If he could reach bootloader his phone would not boot to QDL mode. It would boot to HTC Screen and not past that. the HTC boot Screen is comparable to a PC's POST. if no EMMC partition table is not detected, it's HTC replacement or JTAG.
I'm sorry for your bad luck OP. Please post back to let us know if HTC did in fact replace your phone. I am curious to see how things play out.
Click to expand...
Click to collapse
it was a legit htc one x charger....its safe to sqy ill never use a car charger again. and ill let you know im a little worried cause ive seen alot of horror storys about their warranty policy but i hope it works out
I did a warranty claim on my first htc one x that was rooted. AT&T gave me no hassle and shipped me out a new phone right away. They asked me what my phone was doing and i said its stuck at the htc screen. I did leave out tho that the phone was rooted.
update
BUMP for an update
So HTC received my phone last Friday and had it shipped back to me by Saturday night and I just got it today. Pretty sure it's the same phone. I had an otterbox on mine day one so it was in mint condition but pretty sure its mine. I'm not rooted or s-off anymore I have 2.20 firmware as well so ether they couldn't see that I tampered with it or they just didn't care lol. Not gonna complain though cause I got my baby back. Thanks everyone for all their help.
SkizzyNinja said:
BUMP for an update
So HTC received my phone last Friday and had it shipped back to me by Saturday night and I just got it today. Pretty sure it's the same phone. I had an otterbox on mine day one so it was in mint condition but pretty sure its mine. I'm not rooted or s-off anymore I have 2.20 firmware as well so ether they couldn't see that I tampered with it or they just didn't care lol. Not gonna complain though cause I got my baby back. Thanks everyone for all their help.
Click to expand...
Click to collapse
Should be able to root and gain everything back. Glad everything worked out.
Sent from my Carbon-ize Evita using xda-developers app
Thanks...I'll probably just update the firmware to get rid of the stupid push notification. My upgrade is ready may 20th so I'll just get an s4 and root that when available lol
SkizzyNinja said:
Thanks...I'll probably just update the firmware to get rid of the stupid push notification. My upgrade is ready may 20th so I'll just get an s4 and root that when available lol
Click to expand...
Click to collapse
Unlock. Root. Soff. Then take use 3.18 ruu. So if the person who you sell it to wants to root they can
Sent from my VENOMized HoxL
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
korext said:
Well I've finally done it. Hard brinked my phone. wont turn on wont flash any notification lights at me. no response at all. Tried to get back to stock through RUUing, definitely did something wrong. because now the only thing that hints my phone has any life in it, is the small connection sound when hooked up to usb to my computer. Just the sound though. No actual picture of device connected in "My Computer", and nothing on the phone comes up.
Im hopping there is still hope out there but I think it's lost. *que in Star wars quote.
any ideas?
Click to expand...
Click to collapse
I'v research a bit and havn't found anything too promising, so if there has been any updates on un-bricking phones in the last few months, it'd be great to know..
First I'm going to kindly ask that you change the title of this topic.
Second I'm going to ask what you did prior to the phone becoming unresponsive ie. What ruu?
Third some details about your phone as in is it s-off what hboot do you have.
XDA Moderator
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
RollTribe said:
Did you try to run the 3.18 Ruu with s-on and superCID? If you did, jtag or replacement are your options.
Sent from my evita
Click to expand...
Click to collapse
i just made the same mistake the other day.. its being sent into repair right now. im just hoping they have no way to tell HOW the phone got bricked and my warranty isn't void.. here's the link to my thread maybe some helpful info for the OP http://forum.xda-developers.com/showthread.php?t=2393960
but as RollTribe said.. only way to fix it is JTAG or replace motherboard lol.