Related
I have an idea, that I'm willing to test. This is my first post in the Dev Section, so go easy on me if I have made any mistakes.
I'm sure many of you are aware of the issues with the One X, Flickering, Glitchy UI etc. So, I came up with a idea -
I have 2 HTC One X in my possession, one works flawlessly but has a Yellow screen (Because it is possibly made by Sharp), the other which is my first one, has flickering and every problem you can imagine.
So, If I was to get the ROM from my working Yellow screen One X, onto my first One X, is it possible that this would stop all the problems AND work on the clearer screen (possibly made by Acer)?
I'm willing to test it. But my time is running out. Both phones are due back within 3 weeks now as I've filed for a refund from Amazon. And before I do this, will it stop me from getting a refund? Regardless, the phones have issues (I guess the yellow screen is not a bug, but it is not the phone I purchased - if you get me).
So, what do I do? How do I dump my ROM, and how do I get it on my first One X?
All I know is to unlock them both on htcdev.com, but rooting and getting Clockwork/xRecovery (whatever it's name is now), I haven't got a clue. I've done it with all my other devices (around 6 or 7), but this is a different kettle of fish.
Thanks!
DM
Are you assuming the screens are made by Sharp or Acer as they are the suppliers HTC chose for the Sensation?
LadFromWales85 said:
Are you assuming the screens are made by Sharp or Acer as they are the suppliers HTC chose for the Sensation?
Click to expand...
Click to collapse
Yeah, it's just an assumption. It's very probable.
I don't know if it's possible to return an unlocked phone, because unlocking the phone voids some parts of the warranty. But i believe that there's a way to return the phone to it's locked state by re-locking and flashing the stock RUU, but i haven't tried it, and i don't know if it's possible to do with the one X.
You really think the phones have different ROMs? Because that's what you are suggesting, and in that case there would be different RRU's also. And also a clean RRU install would fix the flicker in that case, which I'm sure it doesn't.. And also, I think the screens are made by Samsung, but I'm not sure. The few I've tested have had the same panel ID even though one is warmer (yellower) than the other.
And lastly, you won't be able to return it if you've unlocked it though htcdev.com.. Maybe, if your lucky they don't check, you could re-lock it and hope for the best. But I guess Amazon know's what to look for. You better leave the dev'ing to the devs.
kruppin said:
You really think the phones have different ROMs? Because that's what you are suggesting, and in that case there would be different RRU's also. And also a clean RRU install would fix the flicker in that case, which I'm sure it doesn't.. And also, I think the screens are made by Samsung, but I'm not sure. The few I've tested have had the same panel ID even though one is warmer (yellower) than the other.
And lastly, you won't be able to return it if you've unlocked it though htcdev.com.. Maybe, if your lucky they don't check, you could re-lock it and hope for the best. But I guess Amazon know's what to look for. You better leave the dev'ing to the devs.
Click to expand...
Click to collapse
Your right. Not unless the FW is stored on a server and somehow is locked to you when you download the FW for reinstall. I'll give this a shot. I'm back on Ubuntu now, so I'm not 100% sure how to update my HTC using it... I'll look.
Delusphere said:
Your right. Not unless the FW is stored on a server and somehow is locked to you when you download the FW for reinstall. I'll give this a shot. I'm back on Ubuntu now, so I'm not 100% sure how to update my HTC using it... I'll look.
Click to expand...
Click to collapse
Check the software version number, if it's the same then there is no benefit to "copying" the rom from one to the other.
M.
mattman83 said:
Check the software version number, if it's the same then there is no benefit to "copying" the rom from one to the other.
M.
Click to expand...
Click to collapse
I just thought it might be worth a shot. No one seems to have an answer as to why the screen flickers. I'm just trying to narrow what could be wrong down by doing tests.
Delusphere said:
I just thought it might be worth a shot. No one seems to have an answer as to why the screen flickers. I'm just trying to narrow what could be wrong down by doing tests.
Click to expand...
Click to collapse
The answer is most probably faulty hardware, I've tried loads of roms not one fixes the flicker, mine gets replaced Monday.
Sent from my HTC One X using xda premium
Moved to general as this is not development...
Delusphere said:
I just thought it might be worth a shot. No one seems to have an answer as to why the screen flickers. I'm just trying to narrow what could be wrong down by doing tests.
Click to expand...
Click to collapse
It's surely not software. Maybe if the nand is broken and your screen drivers just happens to be at the bad blocks every time (and don't get remapped) No, don't waste your time and possibly money on this, it's most likely faulty hardware anyway. You could "adb pull /proc/last_dmsg last_dmsg" then open that file in a text editor and check if the both phones hade the same panel ID. If not, then it could be driver-related. Or maybe it's as simple as a loose connection.
I am pretty sure the flicker is software and not hardware. I get it, it normally starts ( but is not limited to ) when on the home screen. If you are experiencing flicker navigate somewhere with the option to bring up a menu. When I bring up a menu over the flickering screen the menu is solid and does not flicker while the activity underneath is still distorted.
I have tried killing sense to let it restart and that normally gets rid of the flicker.
(I call it flicker but it is really more like the image on the screen warps from the bottom but stays still at the top in a fluctuating way.)
Please disable fast boot and try it again. Fixed on my HOX
ozkarah said:
Please disable fast boot and try it again. Fixed on my HOX
Click to expand...
Click to collapse
Did that ages ago, but thanks for the suggestion. This phone is giving me memory's of when I had my Nokia N97.....
broncogr said:
Moved to general as this is not development...
Click to expand...
Click to collapse
Sorry! That was a genuine mistake! I wasn't looking where I was clicking :S
Hi,
I had Sandvold's ICS 0.16 installed and disabled vibration when ring and my Desire reset...
Now, all it does is sit there with a black screen buzzing..
Battery out reset, removed sdcard, etc..
I've tried getting into recovery mode via power+back & power+voldn, etc.
No joy at all.
PC cannot see the phone when plugged in via USB (tried running RUU, that couldn't see it).
My main questions:
Is there any method available to recover from this? I've tried what I can (understand) but obviously no luck..
The phone's under warranty.. but guess this will be void as I'm s-off, etc etc? Will HTC be able to detect this?
See the link in my signature.
Sent from my HTC Desire using Flashes and Thunders
Thanks.. guess you meant the last link 'How the HTC works.."
If so. are you implying that my radio has corrupted and so it's shagged (or the bootloader's knackered... how could that happen?)
How can I tell which of those scenarios is the one I've got? Hpw do I know it the radio hast started?
If it is the radio that's knackered, I flashed that over a week ago and the mobiles been power-cycled many times in that period...
Or am I missing the point here?
I have another working Desire, could that help me in anyway to get the broken Desire to work....?
Oh well, with the lack of responses I guess the phone's bricked :crying:
Main question I have is if it's sent back to HTC, are they likely to fix it under warranty in its current state?
Added to this, anyone know what I did wrong, so I don't do it with my other Desire.
kevcal said:
Oh well, with the lack of responses I guess the phone's bricked :crying:
Main question I have is if it's sent back to HTC, are they likely to fix it under warranty in its current state?
Added to this, anyone know what I did wrong, so I don't do it with my other Desire.
Click to expand...
Click to collapse
As I could see many users are complaining for getting a permanenr brick after installing ICS roms, and most of them after Sandvold one. Just take a look at bricked threads in the past month or so. Am I right?
Sent from my HTC Desire using Flashes and Thunders
Hadn't realised that - would have avoided the ICS route if I had.
Was happy with SuperNova until I thought Sandvold's ICS was stable
Still can't figure what actually went wrong.
It may be that it's not about rom, but you never know.
Sent from my HTC Desire using Flashes and Thunders
Well sending it off to HTC, hoping they'll fix it under warranty........:fingers-crossed:
THIS LIMITED WARRANTY SHALL NOT APPLY IF THE DEFECT WAS CAUSED THROUGH ANY OF THE FOLLOWING:
a) the Product serial number, the accessory date code the IMEI number, water indicator or the warranty seal has been
removed, erased, defaced, altered or is illegible; or
b) deterioration of the Product due to normal wear and tear; or
c) use other than in accordance with the user manual, rough handling, exposure to moisture, dampness or extreme thermal
or environmental conditions or a rapid change in such conditions, corrosion, oxidation, unauthorized modifications
or connections, unauthorized opening or repair, repair by use of unauthorized spare parts, accidents, forces of nature, or
other actions beyond the reasonable control of HTC (including but not limited to deficiencies in consumable parts) unless
the defect was caused directly by defects in materials or workmanship. This Limited Warranty does not cover physical
damage to the surface of the Product including but not limited to cracks or scratches on the LCD screen or camera lens; or
d) the defects caused by the fact that the battery has been short-circuited or by the fact that the seals of the battery
enclosure or the cells are broken or show evidence of tampering or by the fact that the battery has been used in
equipment other than those for which it has been specified; or
e) the defect was caused by a defective function of the cellular network or other system; or
f) the Product software needs to be upgraded due to changes in cellular network parameters; or
g) the defect was caused by the fact that the Product was used with or connected to an accessory not approved or provided
by HTC or used in other than its intended use and where it can be shown by HTC that such defect is not the fault of the
Product itself.
Click to expand...
Click to collapse
kevcal said:
Well sending it off to HTC, hoping they'll fix it under warranty........:fingers-crossed:
Click to expand...
Click to collapse
g) the defect was caused by the fact that the Product was used with or connected to an accessory not approved or provided
by HTC or used in other than its intended use and where it can be shown by HTC that such defect is not the fault of the
Product itself.
Click to expand...
Click to collapse
Reading that makes me think they won't since rooting your phone and installing custom roms is against the intended use by HTC and in this case it really wouldn't be their fault. Having said that, if you contact them and they say they will then by all means get it fixed and I hope it turns out well for you
pawan1993 said:
Reading that makes me think they won't since rooting your phone and installing custom roms is against the intended use by HTC and in this case it really wouldn't be their fault. Having said that, if you contact them and they say they will then by all means get it fixed and I hope it turns out well for you
Click to expand...
Click to collapse
"used with or connected to an accessory"..
Doesn't sound like anything to do with roms to me... just unsupported hardware..?
Ah , reading the next bit I see what you mean:
"used in other than its intended use"... well I used it as a phone ...
Act dumb @ htc shop
Sent from my HTC Desire using xda app-developers app
Exactly.
Mobile's been returned Hopefully repaired(!) - will find out when I get home..!
Still wish I knew what I did though that caused the brick - bit apprehensive about playing around with it now!
Bricks are relatively rare though I guess.
Looks to me that Radio was corrupted - ie no charging light, but it did constantly buzz...
I programmed the radio over a week before it failed.. could it have flashed badly and setting Sandvold's ICS to 'not buzz when ringing' accessed something bad in the radio ROM and caused it to corrupt??
This doesn't sound likely...?
Next question is (bearing in mind I'm gonna avoid Sandvold's ICS just in case it was that!), what do I go for.
Questions I have...
I guess for a fully functioning mobile, the only option is to stick with GB..?
Do I need to go S-OFF any more to install ROMs?
Do I need a custom HBOOT any more?
Kev
kevcal said:
Questions I have...
I guess for a fully functioning mobile, the only option is to stick with GB..?
Do I need to go S-OFF any more to install ROMs?
Do I need a custom HBOOT any more?
Click to expand...
Click to collapse
1. based on your second and third questions, yes, stick with GB. 'fully functioning' definition varies between users, but the fact that the JB and ICS roms have Alpha/BETA status should tell you what you need to know. the choice is still yours though!
2. not strictly necessary, but is much more useful if things go wrong. so use revolutionary to s-off
3. if you're asking this question i wonder whether you know what the custom hboots are? you flash a custom hboot depending on the rom's system size. should be in the first post of each rom, if not search the thread for 'hboot'...strictly speaking you don't necessarily need a custom hboot, but most of the time you'll run out of space much quicker if you don't. once you understand what the hboot partition tables are it will make sense . you need s-off to change hboot, so this pretty much answers question 2.
Okay will stick with GB for now.. then again the JB roms are looking better all the time...
Okay will S-OFF again.. just wondered if it could have had any bearing on why my mobile bricked.
You're right - not really sure what a custom Hboot is.. it allocates different sized partitions for specific roms then?
Will have a read to try to understand things a bit more.
Thanks for clarification or at least putting me on the road to clarification(!)
kevcal said:
not really sure what a custom Hboot is.. it allocates different sized partitions for specific roms then?
Will have a read to try to understand things a bit more
Click to expand...
Click to collapse
http://alpharev.nl/
Sent from my HTC Desire
Typical - phone worked for 24 hours...
Now, doesn't power on.. screen stays black - no vibrate when I push power button.
Green led turns on when plugged into usb, when I press the power button the green led goes off, but screen still black - nothing happening.
Power button with 'back' or 'vol-down' depressed does nothing, black screen only.
Any ideas, or do I return it (again).
This will be the 4th time - will they be amenable to giving me a replacement do you think?
Well mobile back from HTC a second time; ran fine for a couple of days, so installed Supernova and all running fine now.
Gone S-OFF but left flashing radio alone - seems to work with 5.11.05.27 fine.
So that's it, will avoid ICS, etc just in case, but have no idea whether that's why the phone got screwed...
Mmm.. have now installed Mildwild with no problems..
Really think it was something to do with Sandvold'd ICS release, but have no way of knowing..!
Hi everybody,
After having tried to sort this mess out myself for days now, I feel that I am all out of options. I hate to have to bother you with this problem, because I'm sure I'm not the first one that has a fried Desire Z, but I really hope somebody can help me out. It seems that none of the solutions I have seen to revive this phone work for me.
Okay, so after having made that apology for wasting your time beforehand, let's see if somebody has any idea how to make my phones heart beating again.
The phone in question is the HTC Desire Z. It's not rooted and it's S-On. Honestly, before my phone died I did not even know what H-boot, fastboot, rooting or S-On meant. I had never heard of a bootloader before, but I've tried to educate myself on the matter as good as I could.
Anyway, it died after I tried to install a bunch of Market updates. Google taught me that that is how the phone dies for most people.
During the Market updates the phone froze, and I pulled the battery. After inserting the battery again, the phone got stuck in a boot loop. Pulling the battery yet again fixed that issue, and the phone booted fine.
And that's when I got stupid and decided to run the Market updates again. Long story short: Phone froze again, I pulled the battery, and now the phone is stuck displaying the HTC logo (without the "'Quietly Brilliant" slogan underneath) on a white background.
First thing I did was calling HTC support, just to find out the phone is not under warranty anymore. So I'll have to mess with it myself, hopefully with you guys trying to hold my hand during the process...
The phone will still boot in H-boot.
If I select FASTBOOT I can still communicate with the darn thing when it's hooked up to my computer's USB-port. So at least that part still works. I installed the Android SDK on my computer so I have fastboot on it.
Selecting RECOVERY will make the phone reboot. After displaying the HTC-logo for about 5-10 seconds it will display a fancy looking icon of a phone with a green arrow for a couple of seconds (I can try and make a photo of it if anyone wants to see it?), and after that the screen goes dark. Then it will vibrate 7 times, and that's it.
Selecting FACTORY RESET just instantly freezes the phone in H-boot.
I did find a couple of topics on this forum that looked helpful, but I just cannot figure out how to make it all work.
Here is one that looked very promising:
"[GUIDE] Booting an Android System when only Recovery is at your disposal"
http://forum.xda-developers.com/showthread.php?t=1572924
However, my problem is that Recovery is not at my disposal.
And that is where I got stuck. What is also not very helpful is that my phone is not rooted and it's S-on, and I can't find out how to root a unresponsive phone with which I only have FASTBOOT access. I don't even know if that is possible at all.
So yeah, again:
A completely stock Desire S with a fried eMMC chip and no working recovery in H-boot...Any ideas, or am I just really, really screwed? With my own research I've come to conclude the latter, but I so sincerely hope someone can prove me wrong...
EDIT:
For what it's worth, here is the H-boot information
VISION PUT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-boot
Apr 11 2011, 23:36:27
Yeah probably screwed... sorry
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my HTC Vision using Tapatalk 2
Hey, thanks for the reply. You are kinda confirming what I had already found out.
Guess all that is left to do is to take a hammer to my Desire Z brick, and to start to learn how to live life without a cell-phone and internet everywhere you go. Well, I guess we all did that 10 years ago.
Did you try the ruu... unlikely but last hope
Sent from my HTC Vision using Tapatalk 2
Thanks for your reply, demkantor.
No, I have not tried the RUU. And I'm sorry for having to ask this, because I'm sure you have answered this question a million times already, but can you explain to me what you mean by that?
I did run the "fastboot oem check_emmc_mid" command, and my chip showed up as the Samsung. So that doesn't look good.
It stands for ROM utility update or something like that, its what HTC uses for a full update to their phones when not done through an ota.
the thread I linked you too has a heading like stuck in boot loop not rooted
There I suggest trying to boot in same mode, factory reset or flashing latest ruu, unfortunately with a stock phone there isn't much else to do. But if all fails it more or less insures you have the bad chip and it has lost the ability to read and write to it.
Instruction to flash the ruu or in the HTC website, link in that post to it, just simple fastboot commands
Sent from my Nexus 7 using xda premium
demkantor said:
It stands for ROM utility update or something like that, its what HTC uses for a full update to their phones when not done through an ota.
the thread I linked you too has a heading like stuck in boot loop not rooted
There I suggest trying to boot in same mode, factory reset or flashing latest ruu, unfortunately with a stock phone there isn't much else to do. But if all fails it more or less insures you have the bad chip and it has lost the ability to read and write to it.
Instruction to flash the ruu or in the HTC website, link in that post to it, just simple fastboot commands
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks again for replying so quickly, demkantor.
I will look at that thread, and try flashing the latest ruu, and report back here. Although I guess we both kinda know my phone is completely dead already, at least I want to have tried every possible solution for a stock phone.
I'm just kinda upset with this whole business. This was not a cheap phone when I bought it, and all HTC has to say is: Sorry, your warranty ran out in August. There was a 16 month warranty on this phone, but of course the darn thing decided to die right after that.
I can still send it in for repairs, but I'll be looking at 250 dollars to have it fixed. That's money I don't have.
Any other comparable phone I can get on ebay will run about 150-200 dollars, and that's also something I was not expecting to have to shell out, especially with Christmas coming up.
And because I don't have a back-up cellphone, and no land-line, it just means that I'm pretty much completely cut off. I mean, on one hand it's really peaceful not to get any phone calls, but it's mostly just outright frustrating.
I can't believe there is not an extended warranty or something on these phones, because I'm sure that HTC is very well aware of this problem by now. Although the lady from HTC-support told me that I was the first person ever she talked to that had this problem.
Oh well, I'm just venting right now, so I'll stop typing, start flashing the ruu, and report back here in a little bit.
And thanks again demkantor, for your willingness to reply to questions that have been asked a million times already...
May I suggest buying a cheap g1 to have as a backup incase another similar thing happens, they are quite inexpensive now and are probably one of the best made smart phones, not to mention still somewhat developed on. Also consider finding another g2 or mytouch 4g slide if you want a qwerty, or for more money the samsung relay 4g seems promising.
For me personaly, although my opinion on htc has dropped tremedously over the past year or two, the g1 and g2 are just amazing phones for their time and to this day I can not find a better phone to suit my needs then the g2/dz regardless the price.
If you are in desperate need I used to buy and refurbish to sell both g1s and g2s (along with other phones) but have stopped selling for a few months due to school and getting married and all sorts of personal things keeping my side buissness moving (also fix and repair cars, motercycles etc) but if you can't find or need a reputable seller feel free to pm me as this is the last week of finals ill probably do some more of this soon
Sent from my HTC Vision using Tapatalk 2
demkantor said:
May I suggest buying a cheap g1 to have as a backup incase another similar thing happens, they are quite inexpensive now and are probably one of the best made smart phones, not to mention still somewhat developed on. Also consider finding another g2 or mytouch 4g slide if you want a qwerty, or for more money the samsung relay 4g seems promising.
For me personaly, although my opinion on htc has dropped tremedously over the past year or two, the g1 and g2 are just amazing phones for their time and to this day I can not find a better phone to suit my needs then the g2/dz regardless the price.
If you are in desperate need I used to buy and refurbish to sell both g1s and g2s (along with other phones) but have stopped selling for a few months due to school and getting married and all sorts of personal things keeping my side buissness moving (also fix and repair cars, motercycles etc) but if you can't find or need a reputable seller feel free to pm me as this is the last week of finals ill probably do some more of this soon
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Hi demkantor. Well, to be honest, after this fiasco of a phone I'm done with HTC. Needless to say I will never want to buy another Desire Z, because who's to say that one is not just gonna die soon? Also, my previous phone was a TytnII (also made by HTC, running Windows Mobile 6.1), and that thing was incredibly slow out of the box, and gradually got worse and worse over time. Apparently the Tytn II has a graphics chip that HTC never bothered to make a driver for, hence the screen is incredibly slow when doing things like scrolling through a menu or webpage.
HTC has now proven twice to me that they don't give a crap about their products, so neither am I going to.
That being said, I did try to flash the RUU with the link you provided, but it doesn't work. The updater tries to reboot the boot-loader and that makes my phone freeze up.
So I guess that's totally it then? Phone is dead, and that's that.
Yeah that's too bad, phone is shot. The g2/dz had two different chips, one great and one prone to failure. I have been liking the build quality of Samsung a little more as of late, but the older HTC's do seem better. The g1 suggestion is just to have a cheap sturdy backup, but you will probably want a more advanced phone for daily use.
There are always one of the various nexus models, but none come with a hardware keyboard. So if you need one and want to stay away from HTC consider the relay 4g by Samsung.
Sent from my Nexus 7 using xda premium
demkantor said:
Yeah that's too bad, phone is shot. The g2/dz had two different chips, one great and one prone to failure. I have been liking the build quality of Samsung a little more as of late, but the older HTC's do seem better. The g1 suggestion is just to have a cheap sturdy backup, but you will probably want a more advanced phone for daily use.
There are always one of the various nexus models, but none come with a hardware keyboard. So if you need one and want to stay away from HTC consider the relay 4g by Samsung.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi demkantor, Right, that's what I thought. Phone is shot. I'm gonna smack the hell out of it with a hammer now, just to get some frustration out of my system. Thinking about uploading that to Youtube, just to see how many kids out there will reply with a: "why did you kill a perfectly good phone?..."
If only this one would have come with the Sandisk chip. Who would have guessed it was possible for the eMMC to die this quickly? Little over a year and a half old, and always babied the darn thing. Not a scratch on it, never dropped...
Thank you for the G1 suggestion, but I'd rather save up a little longer and then buy a phone I do like. Guess I might have to do without the qwerty-keyboard in the future, because there are not a lot of phone out there with that option anymore.
I'll take a look at the relay 4g by Samsung. In the meantime, I did send you another PM...:good:
EDIT:
Yeah, the 4G looks like a nice phone, but is:
1) Way out of my budget
2) It's a T-mobile phone. I have an AT&T simcard...
Well, I can't believe there's no way out with HTC?!?!?!?
My backup phone is a brand new htc desire Z. ( I guy from my cell pohone provider get rid of it since they are ''old'').
Played some months with it, take it when my daily desirez had some trouble with custom roms...
So my unused back up desire z with stock rom (no-rotted), just get what you described!! Tried everything, looks like fried emmc.
Got the 7 times vibrate, htc logo, freeze on ruu restore...
what a waste...
Hi oVeRdOsE. Yeah, it's just outright ridiculous, how quick these phones with the bad eMMC's die. And HTC just doesn't care.
RUU !
RUU option from fastboot is your best chance of *trying* to save it !!
Else you could try and replace/repair the eMMC yourself !!
the Desire Z is still better then others in the market ! try ur best to save it !
mohnish.killer said:
RUU option from fastboot is your best chance of *trying* to save it !!
Else you could try and replace/repair the eMMC yourself !!
the Desire Z is still better then others in the market ! try ur best to save it !
Click to expand...
Click to collapse
I understantd, but still, my dz is almost new...
RUU is just running for ever, do nothing.
with a fried chip your emmc can not read/write to some or all partitions making an ruu not an option. The only thing to do is boot from sd if you were rooted, if not time to get another phone, it sucks but yeah...
Sent from my HTC Vision using Tapatalk 2
demkantor said:
with a fried chip your emmc can not read/write to some or all partitions making an ruu not an option. The only thing to do is boot from sd if you were rooted, if not time to get another phone, it sucks but yeah...
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Is eMMC replaceable?
If you own a factory machine to solder a new one in, if you were super good at it, soldering by hand would be extreamly difficult and getting a new chip to solder in would be hard as well. Then you would need to JTAG the new firmware onto the new chip... I'd just buy a new phone or buy a new motherboard
Sent from my Nexus 7 using xda premium
demkantor said:
If you own a factory machine to solder a new one in, if you were super good at it, soldering by hand would be extreamly difficult and getting a new chip to solder in would be hard as well. Then you would need to JTAG the new firmware onto the new chip... I'd just buy a new phone or buy a new motherboard
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Asking cuz i saw someone in forum have replaced it for like a 15 euros.I wouldn't try cuz i'm to nervous and will send it to the wall as a result If it was bigger...well i could make it. I know a guy who can do it. Actually he root my phone, cuz i didn't do it right after i bought it and didn't want to lose everything on phone. He has this little toolbox, that attaching to sim port and root in a 5 minutes or less
Yes, you could replace the eMMC chip, but to do BGA soldering you need special equipment and you need to be pretty skilled. Because of the known problem with the HTC Desire phones, the Chinese jumped on the bandwagon and are offering eMMC chips that come pre-installed.
This basically means that you don't need JTAG to put new firmware on the chip. After soldering it'll boot straight up.
You can buy one of these chips here, for example:
http://www.parts4repair.com/htc-desire-s-sandisk-sdin5c2-8g-nand-flash-chip-with-f/
Another fun fact is that the replacement chip is 8GB. But, as others said before: You need skill and the right equipment. I have a soldering iron and some basic skill, but I'm not even going to attempt to do this.
So, here's my situation:
I have a HTC One X that is currently on Straight Talk.
Since Straight Talk doesn't push updates through the BYOP program, I called ATT and asked them what I can do to get the JB 4.1 update.
They told me to get it off the HTC website and do it myself and stuff like that.
So, downloaded HTC Sync Manager, ROM, everything.
Ran the ROM, it installed, everything was lookin' sexy.
Well, everything was working very sexy as well until my phone randomly reboot.
I was like dafuq, thought it must have been a tiny glitch, so didn't pay that much attention to it, until it reboot randomly again 10 minutes later.
This time, however, it didn't get past the ATT logo, and it reboot again. I tried getting it into bootloader, did that, and wiped the phone through bootloader.
Everythin' going dandy, then another random Reboot.
HOWEVER, this time it was just stuck at the HTC logo, and then turned off. Unresponsive. Zero. Nada.
Soooooo. now I have a HTC One X, that's unresponsive, as if the battery is completely dead.
THING IS THOUGH: When I plug it into my computer, it does the ba-dum sound, followed by a da-da-da right after.
Checked DM, apparently it's QHSUSB_LOAD now with an Error 28.
I read on other forums that apparently you have to have S-off to do even a normal update?
How come HTC didn't have it on their website?
It didn't say sh*t on installation windows either about having s-off.
Kinda like someone giving you cake and saying "Oh yeah lol, I **** in there"
Phone is bricked, no doubt, looking for a JTag around my town and Craigslist atm as well, but just wondering, is there anything else that it could be?
I'm 19 and I'm desperate to have my NoLifePartner One X back.
kthxgaiz<3
Wrong forum mate, you need the at&t one x forum, this is for the international tegra 3 one x, known as the endeavouru. Anything you flash or any guides you use in this forum will give you problems
sent from ye olde bum cheeks
My HTC one M7 is acting up very strangely. It is an ebay phone and it does work normally and shows no sign of abuse or damage. The screen however has some sort of random glitching. Horizontal lines appear at the top of the screen near the app drawer and then ghosting vertical lines appear as well especially with icons. The screen will also be a lighter color than normal. This happens about 80% of the time the screen is turned on. The other 20% it looks fine. It happens on boot screen and on Fastboot screen as well.
From what I can tell it had some custom firmware on it as the Fastboot screen showed tampered but it was S-On. Recovery would not load at all, just was blank then reboot. Showed 4.4.3 until I did a factory reset and then it showed 4.2.2. I tried using Rumrunner, and Firewater. I had WeakSauce working but could never get S-Off. I installed HTC Sync and did a repair which brought me up to 4.4.3 Sense 6 and no way to S-Off other than sunshine.
I don't want to shell out the money for Sunshine though if the screen is going to go bad. What do you guys think? I called HTC and it is 3 months out of warranty. Maybe I should try to get it to do a purple tint so I can send it in under that.
isaacws said:
My HTC one M7 is acting up very strangely. It is an ebay phone and it does work normally and shows no sign of abuse or damage. The screen however has some sort of random glitching. Horizontal lines appear at the top of the screen near the app drawer and then ghosting vertical lines appear as well especially with icons. The screen will also be a lighter color than normal. This happens about 80% of the time the screen is turned on. The other 20% it looks fine. It happens on boot screen and on Fastboot screen as well.
From what I can tell it had some custom firmware on it as the Fastboot screen showed tampered but it was S-On. Recovery would not load at all, just was blank then reboot. Showed 4.4.3 until I did a factory reset and then it showed 4.2.2. I tried using Rumrunner, and Firewater. I had WeakSauce working but could never get S-Off. I installed HTC Sync and did a repair which brought me up to 4.4.3 Sense 6 and no way to S-Off other than sunshine.
I don't want to shell out the money for Sunshine though if the screen is going to go bad. What do you guys think? I called HTC and it is 3 months out of warranty. Maybe I should try to get it to do a purple tint so I can send it in under that.
Click to expand...
Click to collapse
I am not sure if it is related to this issue.
https://code.google.com/p/android/issues/detail?id=70846
I was not able to determine what rom setup was on the phone that I couldn't S-Off. It was debloated and tamper flag was on. Tamper flag is off now but screen still is buggy.
Sounds like a hardware issue. Taking the ota to 4.4.3 and sense 6 should eliminate a software issue from being the culprit. Boot into fastboot, select recovery, and do a factory reset ....if that doesnt help, then my money is on a hardware issue.
ccarr313 said:
Sounds like a hardware issue. Taking the ota to 4.4.3 and sense 6 should eliminate a software issue from being the culprit. Boot into fastboot, select recovery, and do a factory reset ....if that doesnt help, then my money is on a hardware issue.
Click to expand...
Click to collapse
He sees the lines even in fast boot which makes me think it is definitely a hardware issue. I doubt factory resetting is going to do any good.
disconnecktie said:
He sees the lines even in fast boot which makes me think it is definitely a hardware issue. I doubt factory resetting is going to do any good.
Click to expand...
Click to collapse
Yea, I agree. But I hate to be the guy with nothing but bad news!
Hey guys thanks for the input. I went ahead and spent the money for Sunshine and I am now on CM11. Still have the same issue. I am thinking it is hardware as well especially since it shows in Fastboot and booting animations. I am thinking it is a memory issue though since it is random as to when it will be clear vs lines. I saw a post about LCD screens on laptops that showed common issues and the one that resembled my problem was a video ram issue. Not sure if there are tweaks I can do in CM11 to control that.
It still wasn't a bad deal since I only paid $100 for it and it has a clean esn.
Thanks guys, if I figure out a work around I'll post it.
isaacws said:
Hey guys thanks for the input. I went ahead and spent the money for Sunshine and I am now on CM11. Still have the same issue. I am thinking it is hardware as well especially since it shows in Fastboot and booting animations. I am thinking it is a memory issue though since it is random as to when it will be clear vs lines. I saw a post about LCD screens on laptops that showed common issues and the one that resembled my problem was a video ram issue. Not sure if there are tweaks I can do in CM11 to control that.
It still wasn't a bad deal since I only paid $100 for it and it has a clean esn.
Thanks guys, if I figure out a work around I'll post it.
Click to expand...
Click to collapse
Sounds to be more like a loose or broken cable to the LCD. That may be why you got it so cheap.