Hi
Now that HTC has announced the One series which feature Sense 4 and Android 4 ICS, do you think the Desire S will get an official update? Will it get custom ROMs that feature Sense 4?
My Desire got stolen and i am thinking about purchasing a Desire S, I dont feel like waiting for the One series to become available.
there wont be official sense 4,however they are releasing a ics sense 3.6 official rom later this year,yeah there prob will be ports of sense 4.0
Appl_Usr said:
Hi
Now that HTC has announced the One series which feature Sense 4 and Android 4 ICS, do you think the Desire S will get an official update? Will it get custom ROMs that feature Sense 4?
My Desire got stolen and i am thinking about purchasing a Desire S, I dont feel like waiting for the One series to become available.
Click to expand...
Click to collapse
Can you live that long without a phone? If you can, i suggest you do... and wait for the new lineup of devices post MWC. But if you want a phone pronto, either get the DS (we'll have all sorts of sense and ICS on xda anyway) or buy a cheap nokia/samsung feature phone to keep you connected for the time being and wait a little longer to get a better device.
P.S : WTF is up with the Apple 3GS and the washing machine+dryer!!?? Made me laugh
Thanks for the input, and whats all this about a faulty eMMc chip in the Desire S? Has HTC addressed that issue? Sorry for the off-topicness
Appl_Usr said:
Thanks for the input, and whats all this about a faulty eMMc chip in the Desire S? Has HTC addressed that issue? Sorry for the off-topicness
Click to expand...
Click to collapse
Well, there is on deep dark dreaded fear that all DS owners have, and that is the eMMC bricking - most commonly associated with pulling out the battery while the phone is powered up.
No solution for the issue yet.
HTC has not, and will not address the issue, because the DS will soon go out of production (going by the dried up supply chain here in India - retailers have been told not to expect any more Des S or Inc S)
They do however replace the mainboard/device if you brick it that way (shamefully acknowledging their cheaped out SMDs), BUT only for S-On devices... and i have a feeling after reading your post and signature, that you are not one to sit calmly on your ass without S-offing a phone, if that's the first thing you do with it!
So heads up!! Choose wisely.
enigmaamit said:
Well, there is on deep dark dreaded fear that all DS owners have, and that is the eMMC bricking - most commonly associated with pulling out the battery while the phone is powered up.
No solution for the issue yet.
HTC has not, and will not address the issue, because the DS will soon go out of production (going by the dried up supply chain here in India - retailers have been told not to expect any more Des S or Inc S)
They do however replace the mainboard/device if you brick it that way (shamefully acknowledging their cheaped out SMDs), BUT only for S-On devices... and i have a feeling after reading your post and signature, that you are not one to sit calmly on your ass without S-offing a phone, if that's the first thing you do with it!
So heads up!! Choose wisely.
Click to expand...
Click to collapse
I think this has happened to me this morning the battery has been loose and turned off a couple of times in past, but a small piece of cardboard fixed that, however I think it must have slipped loose today and will now not power on.
My phone was S-OFF and rooted so would I be right in thinking HTC will not fix it for me, or should I just send it off and hope for the best.
DP4 said:
I think this has happened to me this morning the battery has been loose and turned off a couple of times in past, but a small piece of cardboard fixed that, however I think it must have slipped loose today and will now not power on.
My phone was S-OFF and rooted so would I be right in thinking HTC will not fix it for me, or should I just send it off and hope for the best.
Click to expand...
Click to collapse
I suggest you run this test for eMMC integrity first :
adb shell
dmesg | grep mmc0
Read from this excellent post by amidabuddha :
http://forum.xda-developers.com/showthread.php?t=1284196
enigmaamit said:
I suggest you run this test for eMMC integrity first :
adb shell
dmesg | grep mmc0
Read from this excellent post by amidabuddha :
http://forum.xda-developers.com/showthread.php?t=1284196
Click to expand...
Click to collapse
thanks for the suggestion but the phone isn't responding when I connect it to computer, it just vibrates 7 times and still has a blank screen and doesn't respond to anything
Okay I have decided to buy a Desire S!
But let me get this straight: as long as I don't pull the battery I should be okay?
Appl_Usr said:
Okay I have decided to buy a Desire S!
But let me get this straight: as long as I don't pull the battery I should be okay?
Click to expand...
Click to collapse
yeah just dont pull the battery when its powered up and you wont have a problem
Sense 4
The first question of this topic was about sense 4 on our Desire.
If our phones are too old to be officialy upgraded by HTC we can hope custom Rom.
You probably have seen like me a video of this new version of sense running on the HTC One X.
Do you think this new version is really going to improve our phone (usine dropbox, feature on the camera apps, ...). ?
---------- Post added at 07:32 AM ---------- Previous post was at 07:24 AM ----------
In the new sense 4, the car mode with a specific landscape screen per application is probably the best news because it can be usefull to avoid accident !
Related
I consider buying this phone. But I don't want to before it's rooted. Thought we could discuss it here. Or is it delivered open?
sindrefyrn said:
I consider buying this phone. But I don't want to before it's rooted. Thought we could discuss it here. Or is it delivered open?
Click to expand...
Click to collapse
Yesterday I was searching for the direct quote from Paul (modaco) regarding this; at least I think it was him who said this...
Basically, unless I made this up in my head, he (if it were him) stated that the oem unlock functionality built into the bootloader has been removed.
Of course this is all speculative until I can find that damn quote
I strongly doubt that this has the same oem unlock features as the Nexus. The OEM unlock is most likely only requested by Google, and I do not think that HTC will do the same thing. It would be awesome, no doubt about it, but hey, lets be realistic.
I guess we'll just have to wait until the device gets sent out to review.
Zappza said:
I strongly doubt that this has the same oem unlock features as the Nexus. The OEM unlock is most likely only requested by Google, and I do not think that HTC will do the same thing. It would be awesome, no doubt about it, but hey, lets be realistic.
I guess we'll just have to wait until the device gets sent out to review.
Click to expand...
Click to collapse
Guess you're right. Hope there will be some kind of exploit we can use. Or a leaked RUU with eng SPL or anything.
Do we know who is going to root / make a custom rom for it?
Lukehluke said:
Do we know who is going to root / make a custom rom for it?
Click to expand...
Click to collapse
I think (and hope) someone will manage to root it, unless it's delivered open. But at the moment we don't know.
Altoguh, I've heard that it's using the same radio and hboot as Nexus One. Therefore, they should be able to use the same ROMs.
hey it's almost 100% that it will be rooted! is there anything in the world of computers that is not hacked ??? if it's not like the same day of it's release like the nexus (which was even before its release) it will be rooted in some days!!!
lambrospower said:
hey it's almost 100% that it will be rooted! is there anything in the world of computers that is not hacked ??? if it's not like the same day of it's release like the nexus (which was even before its release) it will be rooted in some days!!!
Click to expand...
Click to collapse
I just hope that it's not that every good developer have bought Nexus One, and therefore doesn't bother trying to root the Desire.
i don't think so, as every enthusiast will try to have this phone. Also i see many "hackers" being involved in more than two or even three mobile phones very often in this forum so we hold our chance
This should prove to be interesting to watch unfold...
random thoughts...
-The usual suspects seem to be fully wrapped up in Nexus development. Hard not to be with such a fun device What does this mean for the desire? Not sure.
-oem unlock appears to not be present in the desire's rom. if the desire is built on the same everything else (with sense on top) as the nexus, which has not bee rooted any other way beyond oem unlock, I'm not sure how someone will circumvent the lockdown. Perhaps without oem unlock, people will be forced to get creative? *shrug*
-The desire's rom works on the nexus; to me this says one thing...there is little->no reason for anyone with an n1 to look into a desire as long as desire images keep leaking.
All random thoughts but it would seem that possibly the desire may wind up being a consumer product rather than a hobbyist product...only time will tell though
I hope it will be more then a consumer product. The reaseon I'm buying the desire is that it will be released in belgium the nexus one isn't.
Yeah, I'm intrigued about this too- ordered an HTC Desire earlier today for delivery beginning of April, but no idea if i'll be able to root it and stick a Nexus rom on it!
Will be keeping an eye on these threads, just about to pre-order the Desire.
Hi guys
preordered one too, coming from a Touch HD. Til now on the online shop I ordered its stated to arrive at the end of march. Hope they can hold this date. Cant wait to see this device beeing rooted
Ascenca
hmm, I really want a snapdragon+ phone with sense on t-mobile usa. or even just a snapdragon one that is for consumers.
It needs time, I think. Because it´s not to buy, I mean before the HTC Hero came out, do we know it has root? NO When it´s out it needs a little time, and we have root believe me.
sorry for my bad english
I have a few questions, i want to buy a htc desire but i come from winmo world so i don't understand everything...
If the phone doesn't get rooted...
-will it be still possible to install .apk directly on the phone ?
-will it be still possible to upgrade 'operators' roms to official or cooked roms ?
tibey said:
I have a few questions, i want to buy a htc desire but i come from winmo world so i don't understand everything...
If the phone doesn't get rooted...
-will it be still possible to install .apk directly on the phone ?
-will it be still possible to upgrade 'operators' roms to official or cooked roms ?
Click to expand...
Click to collapse
-yes.
-no.
Nexus
I've got the Nexus One, and just wanted to point out a few things (from my perspective)
The Nexus one runs Desire / Sense - BUT flash in the camera is bad, and so is bluetooth. (I used to have a HTC Magic, running HTC Hero / Sense on it, never really worked as good as my friends Hero, so history repeats itself - even with my friend selling his Hero to buy a Desire
So there are a difference in the hardware
the Nexus was rooted very fast, but this is because Google intended the phone to be rooted, this is Google behavior, and clearly not HTC behavior.
I don't see why a developer finding a root method in the Nexus without using the google "practices" to root, would publish their findings for the Nexus, so there might be a couple of ways to root the Desire right when it comes out.
thats just my 2 cents. (For what they were worth)
deprecate said:
-yes.
-no.
Click to expand...
Click to collapse
But if the desire is rooted will it be possible for the custom/official roms ? are there custom "hardspl" who can be built like in windows mobile ? What are the requirements ?
(It scare the **** out of me to be stuck with an operator rom as you can see xD)
Hello everyone,
Im planning to get this phone off craigslist but im afraid that the phone that i am about to purchase is going to have the reboot/freeze issue. Im not worried about the screen bleeding though. So can you tell me an easy way to identify if the phone has this problem? I know il come to know eventually once i purchase it but i wanted to see at the time of purchase from the seller. So please any suggestions are welcome. (some specific manufacturer date, or packaged date or location on the box etc ) any details that will help me if there is any specific pattern for this.
Thanks in advance.
U'll only know after u buy the phone.Save ur $ money,Sensation is just around the corner.
Sent from my HTC Vision using Tapatalk
Hmm
Thanks for the response. yeah i have seen that it is coming soon (and i like the way it looks) but i dont want to wait for it a month more(to be available with out contract by the same way).
Also,
1) i want to have an unlocked bootloader as a precautionary measure just incase i get to start to flashing roms
2) Heard that Sense eats lot of RAM and i want an option to remove it if i feel the same
3) Im sure it is gonna cost lot more than the G2x.
4) And i feel G2x's GPU would be powerful than the sensation.
Wat say?..
http://forum.xda-developers.com/showthread.php?t=720500
This has some juicy info.
Sent from my LG-P999 using XDA App
Sorry, I meant this one...
http://www.tested.com/news/hummingbird-vs-snapdragon-vs-omap-vs-tegra-2-arm-chips-explained/1704/
Sent from my LG-P999 using XDA App
Tq
Yeah tq for the link. it is indeed informative for choosing g2x vs sensation. I am biased towards g2x and stock android. (i have a G2 and i love it). So wanted to know if i can live with those problems incase i get stuck with a bad phone :S. I dont want that to happen
Aneelll said:
Hello everyone,
Im planning to get this phone off craigslist but im afraid that the phone that i am about to purchase is going to have the reboot/freeze issue. Im not worried about the screen bleeding though. So can you tell me an easy way to identify if the phone has this problem? I know il come to know eventually once i purchase it but i wanted to see at the time of purchase from the seller. So please any suggestions are welcome. (some specific manufacturer date, or packaged date or location on the box etc ) any details that will help me if there is any specific pattern for this.
Thanks in advance.
Click to expand...
Click to collapse
The only thing I can think to do to check the phone is ask the owner not to reboot the phone for any reason and when you go to purchase it look and see how long the phone has been on since reboot and If it doesn't match up with what the owner says it is probably rebooting. I have had two so far and had no real reboot issues plus from what I have read LG is aware of the issue and will be issuing an update soon for the bugs. I also debated on the Sensation but decided to stick with the G2X. Hope this helped
So here's a guy who has gotten both the galaxy s 2 and the htc sensation.
http://www.youtube.com/user/samjpullen
From what hes been saying on twitter and the videos Ive watched i think apart from the animations and ui I think id rather have the g2x
The ui is very ram heavy but its very beautiful so I guess its a trade off.
Apologies if I'm breaking any forum rules here, but Costco currently has the G2X for $49.99 if you are adding a line. You might use this info when dealing with your CL seller! Comes with a car charger and BT headset. I'm off to Costco right now to get one!
tq
bls2633 said:
The only thing I can think to do to check the phone is ask the owner not to reboot the phone for any reason and when you go to purchase it look and see how long the phone has been on since reboot and If it doesn't match up with what the owner says it is probably rebooting. I have had two so far and had no real reboot issues plus from what I have read LG is aware of the issue and will be issuing an update soon for the bugs. I also debated on the Sensation but decided to stick with the G2X. Hope this helped
Click to expand...
Click to collapse
That is a nice idea. Thank you. I know i saw this option somewhere but im only able to find "Last unplugged time".. can you help me out where i can chk this?
Found it
Found it... it is called Uptime in About Phone - > Status. will keep an eye on that.
Aneelll said:
Thanks for the response. yeah i have seen that it is coming soon (and i like the way it looks) but i dont want to wait for it a month more(to be available with out contract by the same way).
Also,
1) i want to have an unlocked bootloader as a precautionary measure just incase i get to start to flashing roms
2) Heard that Sense eats lot of RAM and i want an option to remove it if i feel the same
3) Im sure it is gonna cost lot more than the G2x.
4) And i feel G2x's GPU would be powerful than the sensation.
Wat say?..
Click to expand...
Click to collapse
I have confidence that the sensation will get root access eventually, but the process to root may be harder compared to say the G2 or the G2x, and that's still an if it gets rooted. Htc and battery life is always an issue, and the sense ui plain sucks. It does not even look good and I don't know why htc insists on making it so you are forced to use it...it should be optional.
Sent from my HTC Vision using XDA App
if you havent already seen this guy post a lot of videos on the sensation.
http://www.youtube.com/user/samjpullen
My take is I know the dev's will work it out if people actually back it.
but I am un interested....
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!
First, I am sorry for the thread, I know most of them can be found by searching, but I have a friend coming from USA (in which the phone prices are less than half of what they are in my country) who asked if I want a phone. I have to decide very quickly, his plane will take off in a few hours I think. I have a Galaxy S now and I have to ask these questions:
1-) Is installing a stock ICS rom possible? I've seen a thread which says S-Off is not possible so I don't know what is going on. Actually I've never heard of S-off, I've never used a HTC phone. Just guessing.
2-) Is the micro arc oxidation problem solved? Will I have problems too?
3-) How is the screen?
4-) What is the difficulty of installing ROM's in HTC devices? It was easy for Samsung phones.
5-) Do you recommend it? Any major flaw other than Micro arc oxidation failure?
Thanks, please quick!
Had more problems on the galaxy s while flashing.
display is similar to the galaxy s
Have no real problems
Gesendet von meinem HTC One S mit Tapatalk 2
Inagalaxyfaraway said:
First, I am sorry for the thread, I know most of them can be found by searching, but I have a friend coming from USA (in which the phone prices are less than half of what they are in my country) who asked if I want a phone. I have to decide very quickly, his plane will take off in a few hours I think. I have a Galaxy S now and I have to ask these questions:
1-) Is installing a stock ICS rom possible? I've seen a thread which says S-Off is not possible so I don't know what is going on. Actually I've never heard of S-off, I've never used a HTC phone. Just guessing.
2-) Is the micro arc oxidation problem solved? Will I have problems too?
3-) How is the screen?
4-) What is the difficulty of installing ROM's in HTC devices? It was easy for Samsung phones.
5-) Do you recommend it? Any major flaw other than Micro arc oxidation failure?
Thanks, please quick!
Click to expand...
Click to collapse
dude I'm telling you HTC phones are the eazyest phones to flash and there unbrickable I'm telling you I had a mytouch 4g and I did so much things to that phone and it never ever bricked until where I can't use it anymore it was so eazy to get out of it
sent from my sensational sensation 4g'z
Well your 1 hour deadline is long gone !! But if you still want my answer here it is:
-The One S Comes with ICS so no need to worry about that, S-OFF is in development so you also dont need to worry about that
-Micro Arc Oxidisation is only for the black One S, So if you get the silver version you will be fine, Otherwise, Im not sure this issue has been addressed, It depends on the batch version, If its a newer one it *could* be fixed.
-The screen is awesome, Some people dont like amoled, But i guess you do (having SGS1) its better than the SGS1 its a lot more vivid and sharp
-Flashing ROMs is easy, Just as easy as the Samsung, Just be sure to READ ALL THE GUIDES first, you should be ok, We have a very helpful crew in these forums.
-I would highly recommend it, Some users consider the 16gb memory a flaw, as only 10gb is for the user, However you do get 25gb dropbox space with this phone, So if memory isnt a huge issue for you...... GO FOR IT !!!
azzledazzle said:
Well your 1 hour deadline is long gone !!
Click to expand...
Click to collapse
Well, I've waited for an answer in pain for an hour, and went ahead and told my friend to buy it. It is very nice to see that all of my concerns have been addressed.
I am looking forward to it. Thanks a lot my friends.
azzledazzle said:
Well your 1 hour deadline is long gone !! But if you still want my answer here it is:
-The One S Comes with ICS so no need to worry about that, S-OFF is in development so you also dont need to worry about that
-Micro Arc Oxidisation is only for the black One S, So if you get the silver version you will be fine, Otherwise, Im not sure this issue has been addressed, It depends on the batch version, If its a newer one it *could* be fixed.
-The screen is awesome, Some people dont like amoled, But i guess you do (having SGS1) its better than the SGS1 its a lot more vivid and sharp
-Flashing ROMs is easy, Just as easy as the Samsung, Just be sure to READ ALL THE GUIDES first, you should be ok, We have a very helpful crew in these forums.
-I would highly recommend it, Some users consider the 16gb memory a flaw, as only 10gb is for the user, However you do get 25gb dropbox space with this phone, So if memory isnt a huge issue for you...... GO FOR IT !!!
Click to expand...
Click to collapse
A big +1 for all! One S rules!!! (even if your 1hour is outdated... lol) - Just in order to confirm that your probably made the good choice
I think my ATT htc one x may be hard bricked...
I was playing around with ROMs and lost track of time. The last recovery I had on there was clockworkmod (was going back and forth between it and twrp).
I was trying to install the new jellybean rom and it kept on giving me an "assert failed" error. At this point, I deleted the assert lines from the recovery script as advised by one of the posters, and ran the install again. Went through... rebooted and...
The phone is completely dead now. I think it may have discharged? I plugged it in to the wall socket and nothing... absolutely no lights, no screen..... Power+ vol down does not work either....
Please help me, is there any way to recover from this situation?
Wrong subforum.
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Rusty! said:
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
Click to expand...
Click to collapse
Doesn't seem like a rare thing occurring. Either people are overseeing this or they are not really aware that for you can't flash a rom made for a tegra quad core device onto a dual krait.
I used this....
http://forum.xda-developers.com/showthread.php?t=1763240
Sheesh..... Is this meant for the tegra? I never thought I would do such a thing.... I was aware of the issue/hardware differences....
Is there any hope? Actually, in device manager it shows up as QHSUSB_DLOAD and I heard thats a bad sign?
If it cannot be fixed, does anyone have an estimate about how much HTC would charge to reflash/fix it?
My signficant other is as po'ed at me as can be... especially since I had really pushed for the upgrade.... man...
Yes it's meant for the Tegra One X, that's why it wouldn't install (that, and it's not in the AT&T One X section). You bypassed the check the install script does to make sure you're installing it on the right phone.
In short, yes you have buggered it, QHUSUSB_DLOAD is a state where you can write things to the phone, but whether anyone as done any research into it on the S4 One X I don't know.
As for getting it fixed, I have no idea on cost, however... if you convince HTC that you didn't do it yourself, it might be possible to get it done under warranty.
Edit: Did a bit of research and /system on the Tegra One X is is HBOOT on the S4 One X, that's why it's ruined your phone.
htc would just replace the motherboard and charge for that - loads of people have reported the cost its something like £169 to replace motherboard, which would of course un brick it.
Have you tried to keep it plugged in to a charger for an hour or so? My HOX was dead too but started to flash red light after an hour, moment after solid light and it booted
Sent from my HTC One X using Tapatalk 2
He doesn't have an HBOOT any more, there is nothing he can do.
This is why people should stop being stubborn and call that phone HTC One XL. These kinds of situations would happen sooner or later.
Sent from my HTC One X using xda app-developers app
I guess I did... I actually had come to that page via google and since, perhaps I was a bit sleepy, did not verify the source... should have....
Is there any fix at all? Like loading the drivers and reformatting it or something?
Im a bit confused about the motherboard replacement: since its a software issue, cant HTC fix it with a software update? Ill call them today and post the answer on this group as well, but knowing what I am dealing with may help in talking with them.
Thanks to everyone again
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Rusty! said:
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
Click to expand...
Click to collapse
Thanks... Someone in that section has kindly agreed to see if he/she can help me... Keeping fingers crossed... doent feel right to tell att that my phone stopped working for a replacemenf...
Hate to say it but your phone is dead. It's not revivable ar this time and so your only option is jtag or warranty replacement because you overwrote the Hboot.
Sent from my Inspire 4G using xda app-developers app
Don't let morals get you on that one. Lie to them, if not for yourself than for me.
Sent from my HTC One X using xda app-developers app
RobertX1 said:
I used this....in device manager it shows up as QHSUSB_DLOAD ..
Click to expand...
Click to collapse
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Not quite, there is a debricking method for the Sensation that can recover from it.
In most cases though, you're right.
Castellano2 said:
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.
But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
Click to expand...
Click to collapse
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Please move this thread to the XL subforum
miniterror said:
i already revived 2 sensation xe's from the qhusb_dload.
need linux though but it definetly is possible:-o
Click to expand...
Click to collapse
Thanks... any hope for this being possible for the one XL? Also, could the mods please move this thread to the ATT section (sorry for posting it in the wrong section... but I really didnt know the importance of the difference.... wanna look at my phone? )
Thanks everyone. I think I might send the phone to HTC to get it repaired.... although the s***ty thing with that is that Ive heard they take that opportunity to replace the motherboard instead of just replacing the software, and hit me with a big bill rather than a reasonable/fair price....
So.... trying to be honest (by not returning the phone as defective to HTC) ensures that I get scammed by them... :victory:
Possible? Yes of course, that's the point of that mode as I understand it, with some other HTC phones you can hook it up to a RIFF Box and load it up.
Likely? Probably not, as it'll take people looking into it in depth to figure it out and as far as I can see, no-one has/is looked/is looking into it on the OXL.
It really does look like you'll need to send it to HTC, which (as you sound quite honest) will probably be expensive.