Related
I've been flashing different roms for awhile, and decided to go from OpenEclair to one of the "new" ones that requires the new SPL and radio. Went fine. No problem. Used the new rom for about a week, but really got screwed by a massive bug I found in it today, so I wanted to go back to my OE nandroid backup.
I went to reflash to my original SPL. It was a ZIP, so I treated it like a ROM and used AmonRa's recovery to flash it. Said it went fine. Rebooted, expecting to get back into fastboot and flash my radio.
I can't get into fastboot. All it does is show Rogers then HTC Magic in a boot loop. ADB devices shows nothing, fastboot devices shows nothing. Back and Power doesn't work. Home back and power doesn't work. Vol down doesn't work.
Am I as bricked as I think I am?
Yes, it sounds bricked. The proper method to go from 6.x --> 3.x radios and matching SPL is to use fastboot. You have to flash radio and SPLs in matching pairs, you can only use the update.zip format for SPL when it already matches your radio (ie. 1.33.2005 ---> 1.33.2010 w/ the 3.22.20.17 radio).
I believe you should normally flash radios first as well. If you don't get it fixed id like to buy it, need parts. Anyways, most the time when you can't get into fastboot or anything else, it is bricked. Best bet is to get warranty if you still have it. Unfortunately the new phones won't be rootable yet
its best to follow guides when downgrading/upgrading spl/radio (cursordroids for example) when not knowing completely what your doing.. sorry my friend.. sounds like your phone is now a boat anchor
i flashed a 1.33.2010 SPL with a 3.?? radio and now all i get is the logo screen no fast boot, i can enter debug mode (action button) but nothing else sounds like its bricked, but hey its been fun
to be honest i was in this situation last week after leaving my phone off for a hour fastboot was working
oh this is sounding more promising, see what happens when i get home, i see there have been a few people about that have been in the same situation and got out of it so fingers crossed
unfortunantly none of the above worked, wow after 10 years of flashing **** i finally killed something !!.... mind you i still have to make up the serial cable this weekend and see if i can fix it like that
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
yeah i was a little distracted at the time, never mind, im going to boot into the radio bootloader and see if i can fix it this weekend, fingers crossed
ruimoura said:
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
Click to expand...
Click to collapse
i have flashed not in that order and never bricked and also i have flash different things like radios in different orders and no brick
Just a (long) update on trying to get the phone repaired...
First thanks to bcrook, KAwAtA and digitaljeff for the prompt replies at confirming my screw up.
Ruimoura, why even post? Nothing helpful, and not even commiserating. "Oh well, you guys should know better ...". I hope someone is there when you make a mistake to rub it in.
Anyway...
This was a Rogers Magic used in the states on AT&T.
Heres what happened if anyone is interested:
I searched the forums and tried every trick I could find, including the gold card method; no luck. To be honest, I'm not sure I did the gold card right, but I tried my best. I even looked into the jtag idea, but it seems like more work then its worth to me, and no one seems to have been successful with it yet.
I then called HTC to find out what a repair would cost. HTC said they don't have that phone in their parts list and can't service it because it is a Rogers phone and they don't work with Rogers. They told me I would have to call Rogers for service.
Called Rogers and explained the situation (carefully; blaming the 911 update ). Rogers lectured me on how dare I take their phone off their network, and that they have no interest in helping me at all and "contacting HTC is easy. Whats wrong with you?". I explained that I contacted HTC and they said to contact Rogers. They said (after some fighting) call this number and then gave me the same number HTC has on their website.
Called HTC again and explained the situation. After checking their parts database, the person I was talking to this time confirmed what the person I previously talked to said. HTC doesn't service the Rogers Magic but he felt, like I, that was kinda crazy and called the repair location directly to confirm. After a bit of time on hold, he came back and said that Rogers phones are serviced through a place called FutureTel in canada, and gave me their contact number.
I called FutureTel and it was a very short conversation. "What store are you calling from?" I Explained I wasn't calling from a store and why I was calling. "We only work with Rogers directly. We won't support you." and they hung up.
I have to say, both times I called HTC the people I talked to were incredibly polite and honestly seemed like they wanted to help. Rogers and FutureTel seemed like they truly resented having to pick up the phone. Maybe its a cultural thing I'm not aware of, but it honestly seemed, from the first word, that they hated talking to me.
So, as near as I can tell, you can't even pay someone to fix a Rogers HTC Magic.
At this point I'm back suffering on my old WinMo phone and desperately hoping that the rumored March 23 release date for the Verizon Nexus One is legitimate since T-Mobile isn't really an option.
How I bricked my Desire S - information on avoiding brick and an indictment of the dubious nature of HTC's S-on policy
The Desire S is a great phone so why did I want to root it?
The main reasons for rooting and s-off for me were:
Titanium backup (android built in backup is weak)
Being able to remove bloatware that takes up unnecessary spaces and unnecessarily reduces battery performance.
To try different ROMs from the community
Video screen capture
And of course I bought the phone so isn't it mine to use as I please.
Having waited a long time for a good s-off tool to come out I was getting more and more anxious to s-off.
Alpharev got together with Unrevoked to create Revolutionary.
I had previously used the Unrevoked tool to root my first generation Desire. The tool worked easily and flawlessly even on my Mac.
I later used the Alpharev bootable CD to s-off and root a later generation Desire. Again it worked smoothly and flawlessly.
Having had this positive experience I felt confident in the new tool, Revolutionary.
I read everything I could find about how the tool worked and how others were finding results. All seemed straight forward and uncomplicated so I proceeded to download and run the tool from my PC because there was no Mac version available.
Temp root and s-off went smoothly. No apparent issuse. Both Hboot and Fastboot had been successfully replaced on the phone, and CWM recovery was working.
So I added su in recovery then ran a nand backup of the whole system at this point.
Then I downloaded a Cyan 7 ported for the Desire S that was getting good reviews and feedback. The rom seemed to flash clean. After running it for a short time it stated crashing, so I decided to try an MIUI ported to Desire S. Again a ROM with good feedback and labeled as stable.
Downloaded the ROM and flashed it after a full wipe in recovery.
This time on reboot the phone hung at the HTC screen on boot for a very long time. So I wanted to do a force shutdown.
Here is where things got ugly.
The Desire S does not have a force shutdown keystroke combo as my old Desire did. So I opted to pull the battery.
Reinserting the battery and booting into recovery nothing worked properly.
CWM wouldn't mount its partitions, wouldn't flash a rom or even do a factory reset.
I tried doing some functions in fastboot mode. But nothing worked. Any command issued in fastboot mode would just lock up the phone and terminal.
At this point I was pretty worried so I got on #revolutionary and chatted with some of the big guns. I got some good feedback to test this and try that but in the end nothing worked. So I got on XDA forum and looked for others with similar issues.
What I found at this point was very troubling.
XDA user opumps had the same issue as me and had done some great research about the problem.
http://forum.xda-developers.com/showthread.php?t=1150917
It becomes clear on reading, that like him, my Desire S had a fried eMMC chip. This is the internal storage device for HBoot. Once cooked your are basically F*ucked. There is no recovering from this by reformatting the eMMC. Pooched.
Doing the tests on the XDA post I found my eMMC to be pooched.
Now the question is, What fried the eMMc? Was it the S=off process or the forced pulling of the battery while the phone was boot locked?
I then took the phone to HTCs warranty center.
They tested the phone and called me back a few hours later. Your eMMC chip is fried they said. Yes, I said, Can you fix it please?
He told me that the eMMc was fried by the s-off tool I had used. Now, maybe he is full of **** and just wants an excuse to void my warranty. And, maybe not.
I told him to go ahead and fix it. He told me it would be a $200 Dollar replacement of the main board. ****. Well, what other choice do I have. Do it, I told him.
Next I got on the phone with the HTC help center. I got friendly with the lady technician on the call. After some nice chat I started probing for information on the Desire S. After a long conversation She told me that the Desire S, Incredible S, Desire HD all have the problem of frying the eMMC chip if the battery is disconnected while power is on. She said she gets calls every day with people who have fried their eMMC chip. Not through S-off but just because the battery came loose and lost contact while the phone was on or charging. The main reasons for the issue are as follows, HTC cheaped out on the eMMC chips in these phones, as the issue is specific to a particular series of eMMc. And because of a design flaw in the way the battery door closes, and because HTC did not include a force shutdown key combination to shut the phone off properly when locked.
So in the end it sounds like a lot of bad design and bad planning and poor foresight on HTC's part led to the fried eMMC on my phone. But they are not willing to stand behind their product and found an excuse to void my warranty and make me pay for the replacement Mainboard.
Now, here is where we get into the debate of should anyone s-off their phone? The main point here is no one should have to s-off. The phones should never be shipped s-on. It's bad policy to lock the bootloader. But having received an s-on phone you may very well want to s-off. If you decide to s-off just remember that you could easily brick your phone by many ways not related to s-off and your warranty will be void.
Another option is to not buy HTC because of the design flaws and their bad locked bootloader policy. To unlock and root a Samsung all you have to do is issue the command fastboot oem unlock. I don't know if Samsung phones also have the eMMc chip issue, so I can't comment there. But I certainly prefer their open policy on bootloaders.
Maybe the whole reason for locked bootloaders from HTC is beacause they are aware that they used sub par eMMc chips and are trying to reduce bricks.
Regardless this experience has made me very dubious of HTC in general.
I hope this is helpful and educational.
Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App
monkey21stc said:
Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Again, thanks for warning.sorry to hear your struggle, disappointed that htc use this tactic, will certainly reconsider buying an alternate make device next time of this issue persists
The volume up plus volume down plus power button combination does work, it's just but published
Very often, although have yet trio try out when the devices has hung, but certainly reboots my device .
Swyped from HTC Desire S using XDA Premium
just fyi in germay they take 184 € to repair a bricked eMMc :-(
Aye, Thanks for Sharing. I'v hade the same problem as you. I'll never buy an HTC phone again. Cheap bastards!
i need to know that every chip is different...bad for u that u got the bad one but i flash phone daily and its ok..i have same procedure every time i do that..to brick phone can happen to experts too...well if u want to risk to get root and all goodies u can say good bay to warranty..thats for sure
thanks for sharing man.
monkey21stc said:
Thanks for sharing, I removed my battery a couple of times while stuck in htc logo screen. Don't think I'll try that move again, anyway I read about holding power + vol up + vol down to force shutdown, wondering whether that works...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
that works on miui
Buy a htc with simlock.
Mine is t-mobile
When I've started my device for the first time, is was already s-off because if I turn my phone on it will show the t-mobile logo
So u can't brick your phone if you will s-off
But thanks for sharing
Next time I won't buy a htc
Sent from my HTC Desire S using XDA Premium App
Just remember though flash memory is extremely volatile, and ripping a battery out of a phone generally isn't a good idea to begin with, although I was lucky to read about the vol up/down + power procedure before I rooted my phone.
Very interesting post, interesting to see the bigger picture behind this issue.
so here's the deal - I am 99.9% sure that the bricked eMMC chip is a problem only in devices with a chip that was faulty in the first place. When the phone first came out, there were MANY threads on the hardware faults like "Battery cover not fitting" and "Misaligned screen". This was an issue that could't be identified easily, so it wasn't reported. Now, many people are having this issue and instead of panicking, we should do some research. I think that all the guys who bricked their phone would be living close to each other, in the same country or at least the same continent ie, this is a local issue. Also, i'm sure they had one of the other issues i mentioned above. I've not seen anyone in India or Asia with any such issues, so i think we need to find out why europe is having problems. Contact the BRICKees, i'll try making a new thread.
^^^.. yes this issue you need to find the Source.. I sold my Desire yestreday to get Hold of the Desire S but my only concern is this Dead eMMC chip.. and that is the reason I am not buying it yet... I want to identofy the ones with this issue..
really I dont want to screw up my 40K Rs on a faulty set..
Got the same problem, accidentally bricked a DS with a faulty Samsung eMMC, barely 3 weeks after buying it and 2 weeks after S/OFF'ing and rooting it... (btw, isn't it strange that Samsung chips that you find in Samsung branded phones don't seem to have this problem, but strangely the chips sold to their competitors seem to always be somehow sub-par ? Clever and sneaky way to undermine the competition, if you ask me. But at the same time, I bought a SGS2 as replacement in the meantime. ^^ even though it heats up a bit, it's way better than the DS )...
Haven't RMA'd the DS yet, I'm trying my damnedest to find a way to S-ON again and trash the remainder of the partition table -so the service center won't gimme **** about it.. So far I've been able to revert back from Alpharev SOFF to PVT ENG SOFF (0.98.2000), but even this has been horribly hard to achieve.. The "secret fastboot command" to totally brick a NAND didn't work, of course. Had to do it all by hand, in the dead of night, losing many hours of sleep in the process.. :/
It's really shameful that HTC is using such deviant ways to cover their own ****ups and to shirk the payment of their dues.. So I really got no qualms about trying to con them into replacing the device under warranty either. "tit for tat", or so they say.. And they shouldn't be surprised if I never ever again buy a phone from them either, that's really bad PR if y'ask me...
PS : I just got one of those mischievous ideas that often occur to me during sleepless nights : I've read here and there about how dangerous flashing a radio is, and it should only be done if necessary, yadda-yadda-yadda... (heck, I was at my 4th radio flash -just for the fun of it, didn't even have any reception or battery problems to justify it- when I bricked my DS, and I can tell y'all that it wasn't what ****ed it up :S)
Let's just imagine -that's a hypothesis, of course- that I attempted flashing a new radio, and one of my cats "accidentally" jumped on the desk and ripped the usb cord away from the phone, making it drop down on the floor, dislodging the battery in the process.. Wouldn't this brick it nice and proper, and render the NAND totally unreadable even for a HTC service center ? xD
I guess they got a XTC device at hand, but would that help in such a case ?
Can someone confirm what exactly is meant by pressing Power and Volume + and - at the same time? Press Power and press both ends of the volume rocker switch at once? Is that it?
first press the two volume buttons and then power until it shuts down.
worked for me at least -I just learned about that trick a trifle too late
your story said that it includes desire HD? wow i didn't know that honestly when my old DHD freezed i always pull the battery out and no problems at all it's just that the constant carmode problem irritated me and ended up selling it and bought a Desire S...not yet rooted and S-Off but will do later...so it's not the S-off process it's the battery thingy...it sucks for that to happen
Thanks for guide. I'm really scare of eMMC chip problems. I never tried to S-OFF coz of eMMC chip problems. Don't wanna to make void the warranty
Thanks for sharing! I have removed my battery a few times already to force shutdown. Don't know if I'll ever try it again. Maybe as a last resort, but at least I know the risks now. Thanks again!
Sent from my HTC Desire S using XDA App
Cool thanks for Sharring
Sent from my HTC Desire S using XDA App
i work my whole life with pc, hardware, software, flashed everything from set-top boxes to mobile phones.
seriously, i can't believe that anybody can fry the eMMC (a ****ing simple NAND-based flash memory) cause he puts SOFTWARE on it - thats what it build for!!!
you can brick your phone if you destroy the bootloader or something without a possibility to fix it, this won't destroy any hardware on your phone - but thats a different story.
the only reason for s-on is to take you the chance to deinstall the bloatware which they pollute their devices.
apairofscissors said:
How I bricked my Desire S - information on avoiding brick and an indictment of the dubious nature of HTC's S-on policy
The Desire S is a great phone so why did I want to root it?
The main reasons for rooting and s-off for me were:
Titanium backup (android built in backup is weak)
Being able to remove bloatware that takes up unnecessary spaces and unnecessarily reduces battery performance.
To try different ROMs from the community
Video screen capture
And of course I bought the phone so isn't it mine to use as I please.
Having waited a long time for a good s-off tool to come out I was getting more and more anxious to s-off.
Alpharev got together with Unrevoked to create Revolutionary.
I had previously used the Unrevoked tool to root my first generation Desire. The tool worked easily and flawlessly even on my Mac.
I later used the Alpharev bootable CD to s-off and root a later generation Desire. Again it worked smoothly and flawlessly.
Having had this positive experience I felt confident in the new tool, Revolutionary.
I read everything I could find about how the tool worked and how others were finding results. All seemed straight forward and uncomplicated so I proceeded to download and run the tool from my PC because there was no Mac version available.
Temp root and s-off went smoothly. No apparent issuse. Both Hboot and Fastboot had been successfully replaced on the phone, and CWM recovery was working.
So I added su in recovery then ran a nand backup of the whole system at this point.
Then I downloaded a Cyan 7 ported for the Desire S that was getting good reviews and feedback. The rom seemed to flash clean. After running it for a short time it stated crashing, so I decided to try an MIUI ported to Desire S. Again a ROM with good feedback and labeled as stable.
Downloaded the ROM and flashed it after a full wipe in recovery.
This time on reboot the phone hung at the HTC screen on boot for a very long time. So I wanted to do a force shutdown.
Here is where things got ugly.
The Desire S does not have a force shutdown keystroke combo as my old Desire did. So I opted to pull the battery.
Reinserting the battery and booting into recovery nothing worked properly.
CWM wouldn't mount its partitions, wouldn't flash a rom or even do a factory reset.
I tried doing some functions in fastboot mode. But nothing worked. Any command issued in fastboot mode would just lock up the phone and terminal.
At this point I was pretty worried so I got on #revolutionary and chatted with some of the big guns. I got some good feedback to test this and try that but in the end nothing worked. So I got on XDA forum and looked for others with similar issues.
What I found at this point was very troubling.
XDA user opumps had the same issue as me and had done some great research about the problem.
http://forum.xda-developers.com/showthread.php?t=1150917
It becomes clear on reading, that like him, my Desire S had a fried eMMC chip. This is the internal storage device for HBoot. Once cooked your are basically F*ucked. There is no recovering from this by reformatting the eMMC. Pooched.
Doing the tests on the XDA post I found my eMMC to be pooched.
Now the question is, What fried the eMMc? Was it the S=off process or the forced pulling of the battery while the phone was boot locked?
I then took the phone to HTCs warranty center.
They tested the phone and called me back a few hours later. Your eMMC chip is fried they said. Yes, I said, Can you fix it please?
He told me that the eMMc was fried by the s-off tool I had used. Now, maybe he is full of **** and just wants an excuse to void my warranty. And, maybe not.
I told him to go ahead and fix it. He told me it would be a $200 Dollar replacement of the main board. ****. Well, what other choice do I have. Do it, I told him.
Next I got on the phone with the HTC help center. I got friendly with the lady technician on the call. After some nice chat I started probing for information on the Desire S. After a long conversation She told me that the Desire S, Incredible S, Desire HD all have the problem of frying the eMMC chip if the battery is disconnected while power is on. She said she gets calls every day with people who have fried their eMMC chip. Not through S-off but just because the battery came loose and lost contact while the phone was on or charging. The main reasons for the issue are as follows, HTC cheaped out on the eMMC chips in these phones, as the issue is specific to a particular series of eMMc. And because of a design flaw in the way the battery door closes, and because HTC did not include a force shutdown key combination to shut the phone off properly when locked.
So in the end it sounds like a lot of bad design and bad planning and poor foresight on HTC's part led to the fried eMMC on my phone. But they are not willing to stand behind their product and found an excuse to void my warranty and make me pay for the replacement Mainboard.
Now, here is where we get into the debate of should anyone s-off their phone? The main point here is no one should have to s-off. The phones should never be shipped s-on. It's bad policy to lock the bootloader. But having received an s-on phone you may very well want to s-off. If you decide to s-off just remember that you could easily brick your phone by many ways not related to s-off and your warranty will be void.
Another option is to not buy HTC because of the design flaws and their bad locked bootloader policy. To unlock and root a Samsung all you have to do is issue the command fastboot oem unlock. I don't know if Samsung phones also have the eMMc chip issue, so I can't comment there. But I certainly prefer their open policy on bootloaders.
Maybe the whole reason for locked bootloaders from HTC is beacause they are aware that they used sub par eMMc chips and are trying to reduce bricks.
Regardless this experience has made me very dubious of HTC in general.
I hope this is helpful and educational.
Click to expand...
Click to collapse
Please change the title of the thread to "how not to brick your desire s". The current one sounds really fun and why any one would want a guide to brick their phone.
Sent from Desire Aj'S using XDA eXtra Premium App!
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 all, So I'm working on a T-mobile comet for the time being while I'm stuck with it. One of the things that I've noticed doesn't seem to exist is the Hboot menu. I've had it on every droid I've ever owned, but this one does not happen to be an HTC, so I'm not sure if maybe that's the reason why.
http://cloud.addictivetips.com/wp-content/uploads/2010/12/s-off.jpg
Is a picture of the menu I'm talking about and I'm just wondering. Is there a way to flash this on the comet?
I don't really see it as being essential to have as I could always just adb reboot recovery, but it'd be nice to have the option if I'm at work or something tinkering and something goes awry. Thanks
morgan5814 said:
Hey all, So I'm working on a T-mobile comet for the time being while I'm stuck with it. One of the things that I've noticed doesn't seem to exist is the Hboot menu. I've had it on every droid I've ever owned, but this one does not happen to be an HTC, so I'm not sure if maybe that's the reason why.
http://cloud.addictivetips.com/wp-content/uploads/2010/12/s-off.jpg
Is a picture of the menu I'm talking about and I'm just wondering. Is there a way to flash this on the comet?
I don't really see it as being essential to have as I could always just adb reboot recovery, but it'd be nice to have the option if I'm at work or something tinkering and something goes awry. Thanks
Click to expand...
Click to collapse
HBoot is an HTC-specific protocol/bootloader. That's why it's not on your Comet. What you mean to refer to, in general, is the bootloader screen. I'm not sure what the button combination is for your device, but a quick Google query should get you the answer
Product F(RED) said:
HBoot is an HTC-specific protocol/bootloader. That's why it's not on your Comet. What you mean to refer to, in general, is the bootloader screen. I'm not sure what the button combination is for your device, but a quick Google query should get you the answer
Click to expand...
Click to collapse
I thought that would probably be the answer. adb reboot recovery still stands as an alternative, just gotta be cautious if I'm toying around and not around a PC (Or not toy around at all. Ha! Yeah right) I did look up some on the bootloader for the comet. It's actually a frozen t-mobile startup screen. Why they would have that as a bootloader I haven't the slightest. Very inefficient and very confusing when attempting to reach a real bootloader at first. Plus side is it's a Comet, so if I break it. Well. Like I said; It's a Comet, Still in the process of debating wether to replace the digitizer and upper portion of my Glacier or just buy a new phone. (Digitizer strand ripped on the Glacier some so not really functional and the power and volume buttons are essentially shot. More effective to just buy a new phone, but I love my Glacier lol)
Does the T-Mobile HTC One S always come S-Off or was I lucky on my trade today? I traded my mint Sony Xperia Play (AT&T) this morning for a HTC One S, also mint. I've traded, bought and sold to the guy before and I know he gets his devices new by special means and knows nothing about rooting, bootloaders or S-Off.
Anyways I got curious in snooping around the bootloader menu and to my surprise found it to be S-Off...
Was this luck or do all/most/many come this way?
...nobody knows??? Just curious...
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
Oh okay. I was surprised to find it S-Off when I got this thing. I couldn't believe my eyes. That will save me a load full of work, especially the part were some of the tools require a Linux OS instead of Windows. Now ofcourse Linux is a download and installation away, but my "temporary" (now permanent) laptop is so old it only packs 128mb of ram (max can ONLY reach 512mb) and any type of Linux installation just hangs and never installs no matter how many hours you leave it running.
Not to mention some of these devices require the "hotwire" trick, and every time i need something (such as a paper clip) it is nowhere to be found.
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
all the devices come with s-on.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
Nah trust me his knowledge on rooting and so on is VERY LOW. It once took me nearly an hour to show him how to flash a rom on a device I sold him and in a day or two he already messed things up since the rom would wipe many key apps when given an old fashion factory reset. ANOTHER good hour wasted explaining to him the process over phone. If he were to buy these devices used already then sell them to me I would believe that perhaps that person did it instead of him. He gets them brand new in a store he works in, instead of commissions/bonuses for his many sales his boss lets him pick a free phone of his choice as long as its not 100% modern (e.g. a Nexus 5. wish I had that type of boss) in which he gets the opportunity to make more money off of that but remember, his boss doesn't have to pay cash, and he's basically stuck with selling it himself.
If he cant flash a simple rom, or even use a simple app to root a device, I doubt he will ever be able to S-Off an HTC. Also if he were younger (lol) I'd consider the possibility. I honestly believe that this thing may have mistakingly been left S-Off or something by the factory. Or maybe it served a purpose back at HTC.
Whatever the case, it was a big surprise to me.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
tivofool said:
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
Click to expand...
Click to collapse
Hey now that you mention it I think thats the race his bosses are. But whats a supercid? Never heard of that before?
Nah definitely not as lucky to have a supercid. I assume CID = Carrier Identification seeing mine is T-Mobile related.
Sent from my LG-LS970 using xda app-developers app