Related
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
and1kar said:
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Nope i used the tmous 1.50.
I am pretty sure you forgot to run the RUU, and sadly yes I have to inform you that it is bricked :/
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
Sounds like you bricked it, yes :s
Thanks for the replies guys.
Since i got it from craigslist my only hope is paying htc to repair it i'm assuming?
It should still be covered by the original warranty right?
LooieENG said:
It should still be covered by the original warranty right?
Click to expand...
Click to collapse
Just got off the phone with HTC. It is still covered under their warranty. Hopefully since all my void stickers in good standing, I have no physical damage, was able to get the CID back to Tmous and the write secureflag3 went through, there will be no reason to deny it. Here is hoping! I think EXT4 recovery is still on there though. Hopefully it will be so bricked that they will have to reset it and reload the software to be able to do anything with it
Hope you manage to get it fixed!
A question, I have yet to root my XE, but is SUPERCID a must on a sim free phone if you want to flash roms?
the fact is that if it is so bricked that it won't turn on at all they won't check it further. many members achieved to get a new phone as replacement
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
bonesy said:
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
Click to expand...
Click to collapse
I definitely didnt mention xda or flashing roms or anything, and I told them i received it as an anniversary gift (even though i really did get it from craigslist). Told them i rebooted the phone and it just never came back on. Which really is what happened while leaving out a few details lol.
I wonder what would them HTC guys think if they are already among us
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
poktangju said:
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
Click to expand...
Click to collapse
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went. I have read some HORROR stories about people sending there phone to HTC and it become missing in action for MONTHS. I really pray to christ that does not happen to me.
O/T a little bit, but how come with just about any other "thing" in life a warranty is good and is tied to the object and not to the person. Even though i got this phone off of craigslist, why should that have ANYTHING to do with it. The phone is the phone and the warranty is the warranty regardless of whose possession it is in. I just don't think tmobile should be able to do that. Also i think it's BS that if you buy a brand new phone and it breaks 2 days later, they give you a refurb and not a new one. How do they get away with this ****!
i think im gonna take my chances as well...the person i talked to at htc did say that if the damages were caused by me then i would have a choice to pay them to fix if not i would have to pay $35 to get the phone back...so this could end up costing the shipping to send phone and the $35 to get the phone back.
xsteven77x said:
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went.
Click to expand...
Click to collapse
Just wondering how this has progressed. Did you send your phone to HTC? Did they say what the potential repair costs could be?
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
did you get your phone back?
xsteven77x said:
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
Click to expand...
Click to collapse
Hey guys. I have a chance to pick up a mint sensation locally for a cheap price. The seller is under the impression it is bricked. I've read through the threads for a while now but thought I would ask for some help/advice. The seller told me that he bricked the phone by trying to unroot it but has also said he was trying to "flash boot or something." He has made it clear that the phone will not turn on or show any signs of life. He has tried multiple batteries as well.
So, is there any way to ensure it is bricked? I had thought that maybe he messed up flashing a new rom.
If it is clearly bricked, what would be a good price to snag it for?
Would it be possible to buy it and contact HTC in regard to the warranty? What would this cost?
Thanks in advance,
PS; I have read about the inablility to charge after flashing CWM. I'm not sure if CWM was installed or not. I will ask that asap.
Sounds like an inappropriate file was flashed to hboot, in which case it's dead. Short of jtagging there is no way to fix it.
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
MRpeabodyia said:
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
Click to expand...
Click to collapse
No, they wouldnt as it was from user error.
Matt
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
MRpeabodyia said:
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
Click to expand...
Click to collapse
Well,morality aside you can always tell them that the OTA update bricked it.If you are a TMOUS customer you can try and contact T-mo first.They are usually easier to deal with than HTC.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
Well I bought my "bricked" sensation. I spoke with the seller for a while and it seems he had rooted it, received notification of the OTA, and attempted to unroot it. He didn't give me specifics on the procedure he used but I'm going to read as much as I can, depending on when my monster child will let me, and attempt to fix this thing. I read about the battery tricks and will try those tonight. Any suggestions as this point guys?
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
MRpeabodyia said:
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
Click to expand...
Click to collapse
Well if it's a QHSUB brick that means the phone is truely DEAD.If you can't boot into bootloader,can't charge it and can't connect to a PC,then i don't see how could they tell if it was rooted or not.There is no way for them to tell.You just tell them you bricked it while trying to install the OTA update,or do as i did and contact T-mobile.
Good luck!
Thought I would update this thread for anyone who may stumble across it at a later date. I went ahead and sent my bricked phone into HTC. They repaired the phone and sent it back. I was suprised to see that they didn't send me a refurb.
I have to say that HTC were very easy to work with were quick in returning my phone.
Hello,
I'm brand new to the forums, been reading up on my phone and things to do with it. I've just been running stock everything, unrooted and using GO overlays which I really like. I was thinking of rooting my phone and let me friend play around with it... BIG MISTAKE. My phone won't turn on, boot, power up or anything... Have they bricked my phone and is there ANYTHING at all that I can do to recover it? I was using Kies and have my phone backed up and everything... but assuming it won't even turn on... Does anyone have any advice on some options?
Galaxy SII SkyRocket I727
Rogers - Canada
-Pixie
If it wont turn on it sounds like a hardbrick, what did your friend flash? my guess he probably flashed a SGS II rom. You will have to repair it using jtag for 50$.
If you still got warranty you could try using it.
Going Crazy!
Holding down the volume key doesn't work, I can't download emulators to get it up with the phone unable to function or device drivers be updated or detected at all... I've read and read and read and NOTHING is working... I can see if I can create a jig, I think the parts are all around here somewhere... But is that the ONLY option? If it's hard bricked and they've completely messed it up, does anyone know of ANY potentials whatsoever of how to rebuild this thing back to normal?? Please help, I'm going to ASDLKDJLSKDJ someone up... !!! In the meantime I need to see if I can save this thing!
As I said for hardbrick you'll have to find a jtag repair service nearby and send your phone nad pay 50$.
kishke said:
If it wont turn on it sounds like a hardbrick, what did your friend flash? my guess he probably flashed a SGS II rom. You will have to repair it using jtag for 50$.
If you still got warranty you could try using it.
Click to expand...
Click to collapse
I'm pretty sure I'm under warranty... Pretty sure they're going to be extremely peeved when they find out it's hardbricked from god knows what...
It took a while but I finally found the ordering site for jtag... Going to try that route I s'pose, thank you. Good thing I have an old crap phone as a back-up in the meantime... They don't require the SIM do they? I don't really trust sending that off...
Pixielated said:
I'm pretty sure I'm under warranty... Pretty sure they're going to be extremely peeved when they find out it's hardbricked from god knows what...
It took a while but I finally found the ordering site for jtag... Going to try that route I s'pose, thank you. Good thing I have an old crap phone as a back-up in the meantime... They don't require the SIM do they? I don't really trust sending that off...
Click to expand...
Click to collapse
No sim required. When you pull the battery out and put it back in and hold power do you even get a Samsung logo flash on the screen?
Sent from my SGH-I727 using Tapatalk 2
Pixielated said:
I'm pretty sure I'm under warranty... Pretty sure they're going to be extremely peeved when they find out it's hardbricked from god knows what...
It took a while but I finally found the ordering site for jtag... Going to try that route I s'pose, thank you. Good thing I have an old crap phone as a back-up in the meantime... They don't require the SIM do they? I don't really trust sending that off...
Click to expand...
Click to collapse
go the warranty way. you got nothing to loose
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.
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.