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
Hi Guys,
New to flashing the Sensation, though I've done my HD2 a good few times.
Girlfriend just bought a Sensation and I'm eager to flash a decent ROM to it but failing at the first hurdle.
From what I can tell, there is no HBOOT but instead it has uboot (forgive me if this sounds ridiculous).
When I use Power+Volume Down, I do not get a white screen with options and information but instead get a black screen. There's no sign of an HBOOT version, but there is a uboot version number.
If I press Power +Volume Up I am sent to a recovery mode, but I don't think it's CWM.
If I try to use Revolutionary, it finds the phone (in normal mode, not h/u boot) and says that the phone is not supported.
Phone was bought in China but I think it is a Euro model (T Mobile branding on top of phone)
There is a possibility that a ROM has already been flashed onto it - but it sucks, and I want her to get the best from her new phone.
Also, I cannot get the CID or MID number. Tried CID getter, neither of them were on there. Tried terminal emulator, no response from getprop ro.cid or ro.mid.
So even if I wanted to upgrade the firmware, I am unsure which one to use!!
Has anyone run into this sort of situation? Using SuperTool I was able to get root access, which is at least a step in the right direction but I'm not sure how to proceed. Maybe it's already s-off and I can update the firmware and thus get hboot. But if it's not, then I run the risk of ruining it.
If you think I can go ahead and try to install new firmware, without risk of bricking or semi bricking, then I would probably be inclined to go for it.
Looking around here and also on Google, I haven't seen anyone with the same issue, so any help you can give would be very welcome!!
Many thanks in advance,
Mr Al
two possibilities: your sensation is faked or it has been relocked by the sellor which is called "baikamumaji".
Sent from my Sensation using XDA
Thanks for that, although it's slightly bad news!!
I'll see if we can get in touch with the seller and take it from there.
Ok, we've just spoken (online) with the sellers 'tech' guy.
I think pmbldc is right, it's a fake.
Their guy says that it can be flashed, but only using the roms on their forum.
I think it's bull. Currently feeling ripped off and unhappy, but what can I do?!?!
Never buy any more devices from China??? Jus sayin... Sorry you got ripped off bro.. Sucks that that sort of thing happens...
Haha! A little tricky that one, as I live in China!
I've bought lots of electronics over here, both locally branded/produced and international. Lots of successes.
To be fair (grudgingly) this guy was considerably cheaper than everyone else. That old adage of 'if something seems too good to be true, it is' applies very well in this case.
Pretty disgusted with the whole thing, the conversation my girlfriend had with the 'tech' guy was ridiculous. Both she and I work in tech so his usual line of BS didn't work with us.
So now, having decided to be sensible and not buy the HTC One X, we're going to end up spending about the same amount of money anyway!
All we can do is learn from our mistakes, and at least now I know what to look for when buying a Sensation!!!!
True Story, bro
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
MyronJ906 said:
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
Click to expand...
Click to collapse
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
adulel08 said:
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
Click to expand...
Click to collapse
lol you helped with a good laugh. That's genius, dude
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------
Can't seem to edit my post. I didn't realize you were using the other microphone. You should run the ruu regardless to at least try and sort out any sort of software issue.
Sent from my HTC One XL
ECEXCURSION said:
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
Click to expand...
Click to collapse
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
MyronJ906 said:
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
Click to expand...
Click to collapse
The microphone volume is a perennial problem with this phone. No one seems to know for sure what causes it. Reseting and ruu'ing ought to fix it.
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
MyronJ906 said:
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
Click to expand...
Click to collapse
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
iElvis said:
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
Click to expand...
Click to collapse
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
MyronJ906 said:
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
Click to expand...
Click to collapse
Did you relock? An RUU will fail otherwise.
iElvis said:
Did you relock? An RUU will fail otherwise.
Click to expand...
Click to collapse
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
MyronJ906 said:
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
Click to expand...
Click to collapse
Unplug your phone, turn it off, and restart it. Sometimes that helps. It won't boot, but you can get it back into the bootloader.
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
MyronJ906 said:
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
Click to expand...
Click to collapse
Bootloader.
Pretty sure my drivers have just fubarred. I'm not showing up on adb devices either. GRRRRRR this is driving me mad
EDIT: Finally got the RUU to run. Had to replace the standalone HTC drivers with fullblown HTC sync but it's whatever lol. Now to see if the RUU actually fixes the problem
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
MyronJ906 said:
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
Click to expand...
Click to collapse
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
iElvis said:
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
Click to expand...
Click to collapse
Yeah, I meant the microphone still isn't working. I've been on the stock RUU, AOKP, and Nocturnal. All of them have the same issue so I'm expecting that it's hardware.
I just don't know what to do guys. I guess I'll e-mail HTC, swing by the AT&T store in hopes of something, and call it done. I find it ****ty that the guy won't cooperate so far because truthfully I *would* at least cooperate but it's tough when he says it was working when he had it and I say it wasn't working when I had it.
BUT he says that he didn't make any calls that day. However, he "knows it was working when he gave it to me"
Guys, I just don't even know what to do. If I can't get it replaced, he completely won out on the trade. I was originally asking for + $100 and lowered it to + $50 for him. Yet he doesn't want to do anything for me.
I want to handle all of this responsibly, but I also want a completely functional phone
MyronJ906 said:
Can I (legally) mark the S3 as stolen?
Click to expand...
Click to collapse
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
redpoint73 said:
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
Click to expand...
Click to collapse
I did mean for the insurance claim. I didn't want to do it fraudulently which is why I asked. I wasn't sure what the exact definition of stolen (or even lost) in this regard is. But this doesn't count so that's no longer an option. Haha I now see that the AT&T warranty plan doesn't cover user idiocy, just drops and spillage.
I'll RUU again then install an AOSP ROM. I'm pretty sure it's the hardware mic that's busted though. Does speakerphone use a secondary microphone? I imagine videorecording does. If so, do the camcorder and speakerphone use the same mic?
Maybe the noisecanceling mic is screwing things up and that could be software but I think the microphone is just physically broken.
Idiot me, being the hardcore modder made changes to the phone *before* testing for the microphone. In my defense, I've owned the One X before so I knew what the hardware was capable of. I knew the current state of ROMs, so why not pick up where I left off?
I'll send HTC a pity e-mail and see where that gets me. Better to try and fail than to never have tried at all.
EDIT: I wanted to ask as well, does anyone think ROM flashing/BL unlocking etc. Really could have caused this? I mean, if it did there's no reason different software shouldn't fix it. But if it's hardware, that establishes that it's more likely that it wasn't my fault, right?
I 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.
HTC One M8 on Verizon. Android version 5.0.1. I did a lot of research yesterday, and could not find any working solution to root the phone. It's hard to find anything on Google because generally the information will be outdated (from last year or the year before). So can someone fill me in on what exactly I'd need to do? This is my first smartphone and I've never rooted an Android device before.
ziddy5 said:
HTC One M8 on Verizon. Android version 5.0.1. I did a lot of research yesterday, and could not find any working solution to root the phone. It's hard to find anything on Google because generally the information will be outdated (from last year or the year before). So can someone fill me in on what exactly I'd need to do? This is my first smartphone and I've never rooted an Android device before.
Click to expand...
Click to collapse
Assuming you are still S-On and locked then you are stuck without root for now.
BladeRunner said:
Assuming you are still S-On and locked then you are stuck without root for now.
Click to expand...
Click to collapse
This is what I was afraid of. How can I keep track of when there is an update to the situation?
ziddy5 said:
This is what I was afraid of. How can I keep track of when there is an update to the situation?
Click to expand...
Click to collapse
keep checking these forums and/or follow @teamandIRC on twitter
Rooting the already updated HTC One M8
It's going to be difficult. I've been scouring the webs for weeks looking for the answer to that one. The Sunshine S-off didn't work for me. The only way I can find right now to do this requires finding somone that has purchaced the elusive "HTC java card" sometimes called the HTC S-off card. They can s-off your phone in a heartbeat. Wish I had one, I just can't see forking over 375.00 to get one.
So if your S-off there is a root method available ? I haven't found it if there is.
I'm running 5.0.1 Verizon S-off
Thanks in advance
jjmstang said:
So if your S-off there is a root method available ? I haven't found it if there is.
I'm running 5.0.1 Verizon S-off
Thanks in advance
Click to expand...
Click to collapse
If you're already s-off then just install twrp and flash, reboot recovery and it should ask you if you want to install root
BladeRunner said:
If you're already s-off then just install twrp and flash, reboot recovery and it should ask you if you want to install root
Click to expand...
Click to collapse
It seems you have to be rooted to install TWRP........at least what found
You only have to be rooted to install it with their app. If you are s-off you can download it from their site and flash it with fastboot.
mpappas87 said:
You only have to be rooted to install it with their app. If you are s-off you can download it from their site and flash it with fastboot.
Click to expand...
Click to collapse
I followed this method and I have re-gained root
http://forum.xda-developers.com/ver...ow-to-root-ota-pc-s-off-t3048604#post59750567
Now I'm going to try and flash the Dragon ROM with Sense 7
Thanks again for the help
same boat ; old filmware?
just received this HTC One M8 thru verizon, lollipop 5.0.1 after day 2 OTA update. I've been rooting every device i've owned since 08. Busy with daily tasks I haven't had a chance to sit and try unlocking bootloader until this weekend. I hit a wall when HTCdev returned an error after entering the identifier token \(^~^)/ . I did some reading, couldn't find anything.
I'm coming from a xt912 I've pretty much squeezed all I can get out of it since I got that brand new. I put CM12 on that just recently this HTC makes that the moto seem primitive. After bricking that (moto)spyder a few times flashing bad zips or doing things out of sequence I've put it thru the ringer and used RSDlite to just start from scratch. I have also found these device can put up with a lot and still bounce back. Geeze, I have three years of continuous text and data backed up on SD, lol . Something I haven't tried and wonder, does anyone know, is there any old VZW filmware for this M8 maybe 4.4.2 and try un locking from that point or Does the token id stay the same no matter what filmware?
Htcdev won't work on our phone because it's blocked by Verizon. Also, it's not possible to downgrade firmware or the OS without having s-off. At this time there's no way to get s-off on lollipop so you're pretty much stuck where you're at until an exploit is found by someone. Sunshine works for anything up to 4.4.4 but it won't work on a Verizon phone that's running 5.0.1. About all you can do right now is wait to see if Jcase and Beaups come up with a way to make it work on a Verizon phone too. I know that's not what you want to hear but that's how it is at the moment.
benjdevel said:
I've been rooting every device i've owned since 08. weekend. I hit a wall
Click to expand...
Click to collapse
Okay, glad I didn't spend too much time trying to figure this out, never rooted a device before
Gotcha . ...Stupid vzw ? I glanced at a procedure to unlock SIM. Have no idea if that would help anything. Havent tried it. Ill have to keep a watch out for something. Really compaired to that spider this thing is like a ferrari. Not too much bloatware. Lollipop rocks and knowing Im up to date for the most part calms me a little. I still dont like the idea of not having complete control of my device. I've already received a few notification marketing related from verizon that i could not close unless i looked at it. I did notice control over saving things to my ext sd i do like. I am a student just getting into the ist world.wish there was something i could help with. 5 classes is killing me at the moment though. I did also try to install an imsi catcher apk updates version and it seemed like it ran fine. I could of swore that app needed root access. I could be wrong with the newest version though.
Joint Java Card?
Same boat (Verizon, htc one m8) . . . For some reason I was thinking Lollipop was the update which was still able to be handled by Weaksauce 2. So I accepted the OTA, without thinking. -hadn't gotten around to s-off, etc., before this time around.
So, in some 2013 posts, I saw that some people had tried to pool resources and share a Java Card, etc. But sending phones to a "card keeper", is expensive, and unsafe (besides having to live without your phone for a few days.). jcase, on their company's IRC support channel, indicates that the card is more than just a simple microSD card, which one might be able to dd a filesystem image from (i.e. copy it for distribution). That's entirely possible, since all SD cards have micro-controllers for dealing with failed sectors, etc (check out "Bunnie's Blog"). Basically, the controller could make it tough/impossible to access part of the card, and can take care of decrimenting credits, encryption, signing, etc. Even if it were a basic SD card, the use of signed binaries, and external license/resource server, etc. could still make it tough . . . -although the card I found states it needs no internet connection. It would be much cheaper to send the card, rather than phones. But how to coordinate and pool the cost seems like it could be a pain?
So here's what I'm thinking about:
Someone (me?) could purchase a legit, new htc Java Card. After I use my 2 or 3 credits to s-off/unlock my phone, I could put the card on, say, ebay for maybe $5 less than what I bought it for. Then, another person could use some credits, then sell it again, for a little cheaper, etc. If we want to keep it "in-house", we could just send to each other and pay with PayPal or Google Wallet. But, with e-bay, one could just copy/build on the ad the first person started. Take a picture of your phone's screen, when the remaining credits are shown, and put it on the ad. With 2000 credits, my conservative estimate is that it could cost less than 72 cents, for each unlock. The $5 incremental discount might be close enough to cover re-shipping costs.
The Sunshine guys have, for free, helped many of us over the years. So I was planning to purchase their solution, if it worked for this situation. But their download page states that "Verizon 5.0.x users will have to wait until we update.". They indicate they could get us supported soon, but they also indicate that Lollipop is much more secure, with SELinux updated and better enforced., etc. So I am a little concerned about when that will actually happen. I see they've been posting updates for Motorola, and making sure people are able to pay them via PayPal, etc. But nothing yet for Verizon 5.0.x.
Does anyone know/recall how long after the last android update, someone came up with a root exploit? I'm just trying to get a rough guesstimate about the minimum time people will have to wait this time. -then add time because Lollipop is apparently significantly more secure. I guess I don't completely mind that my phone might be secure enough to not make it tougher for someone to get into the deepest parts of it, without specialized hardware (Java Card), if I were to lose it.
But, really, what Verizon and htc and others have done to these devices . . . They are, essentially, specialized computers. It would be like if Dell or another computer manufacturer sold you a computer, without allowing you access to your administrator account (and no clear/easy way to boot from another drive, to recover/fix things, etc.). That's crap.
I dunno. What do people think? I suppose I could just try it, and see.
Are new devices updated already? If I were to get a phone from verizon today will it already have the Lollipop update or would I get a still root-able device that I can deny the update?
libredroid said:
But, really, what Verizon and htc and others have done to these devices . . . They are, essentially, specialized computers. It would be like if Dell or another computer manufacturer sold you a computer, without allowing you access to your administrator account (and no clear/easy way to boot from another drive, to recover/fix things, etc.). That's crap.
I dunno. What do people think? I suppose I could just try it, and see.
Click to expand...
Click to collapse
I like the idea of that Java card:good: and I completely agree with you on how wrong it is restricting administrative rights, especially considering these things are comparable to a new computer.
dimsumx said:
Are new devices updated already? If I were to get a phone from verizon today will it already have the Lollipop update or would I get a still root-able device that I can deny the update?
Click to expand...
Click to collapse
No guarantees either way.
What is the status on SunShine for our device?
I got the Java Card.
@vazersecurity: still "Verizon 5.0.x users will have to wait until we update.", as of today.
I got the card, as previously proposed, and was able to get S-Off on my USA-Verizon HTC One M8 with the Lollipop OTA.
I needed to download and place two files in the root of the card (now done).
I then (CID changed) was able to use htcdev.com to unlock my bootloader, and ultimately gain root. I'm now happily running a current Cyanogenmod ROM. To regain some functionality from my camera, etc., I installed the htc camera, HTC Gallery, and Zoe apps from the Play store.
So I've already created a listing for the card on eBay. I assume the forum rules won't allow me to post the link. But I, honestly, always intended to use that as a way to make it more convenient to share with a community of people who wish to join in. -not to try and make any money off the card. Again, rather than have people ship phones to one person (with the shipping cost, and being without their phone), if figured it would be cheaper, and less disruptive, to ship the actual card. So, you'd purchase the card from the previous user, then re-list it for a bit less than what you paid for it. With the starting cost and credits, S-Off is about 30 cents, each. As the card credits get used up, it gets cheaper. Maybe each person would end up paying a few dollars for S-Off, when you factor in the shipping.
Maybe a moderator could chime in about whether it might be OK to post a link to this "community-intended" listing. -or suggest a better contribution/distribution method.
Also, since many users in our situations have been out of luck regarding S-Off, for a few months now, might a moderator or someone suggest/implement a way to post/place this information more prominently, in the forums?
Thanks.