Related
OK I have a T-Mobile Dash with Kavana's WM 6.1 and it *was* working just fine. I flashed the ROM about a week ago, installed SmartToolkit, and it's been running fine for a few days.
Today, out of the friggin blue, I now have a bunch of white lines on my display. They start at the very top of the screen, and fill up a little more than 1/3 of the screen. Each line is 1px thick, and it skips every other line.
I did a screen capture, but it didn't pick the problem up (the captured screen looked great), so I photoshopped the screen shot to show you folks EXACTLY what it looks like on my phone.
This morning, it was fine. I made some calls, sent some emails, and it was working fine. Just about 20 minutes ago, I noticed this problem. I have NOT adjusted any settings, added new software, dropped it, submersed it, or modified it in ANY way. I didn't power cycle it, plug it in, or do anything more than let it sit on my desk next to me.
After I noticed the problem, I reset it, and it was there. I took the battery out, let it sit for a few minutes, rebooted it, and it was still there. The lines DID appear in the windows splash screen as well as the HTC boot logo (the boot logo is not pure white, more like a light grey, so if you angle the phone down a little to darken the grey, you can see the white lines)
These lines appear above ALL screens, including running programs, system menus and messages, and even when shutting down. It does NOT, however, seem to affect the phone's performance, so I can live with it for a few more hours until I see some replies here.
Unless this something that is easily remedied, I figure these should be my next few steps (unless a guru tells me otherwise):
- Soft reset (tried, not solved)
- Soft reset including battery removal (tried, not solved)
- Re-flash ROM with Kavana's 6.1
- Re-flash ROM with T-Mobile factory install (link, anyone?)
- Call T-Mobile for device replacement.
That's my battle plan for now... any thoughts, anyone? Thanks in advance for your help.
Attached picture in my first post updated... I used photoshop to make it look *exactly* like the actual screen. That's the best I could do without actually taking a picture of the phone itself. :\
"Bump" <-- Sorry... don't know if that's against the rules here, but at this point I'm ripping the hair out of my head. Can someone please help?
I had the same problem except it was with i screen I purchased on ebay. It looked exactly the same as yours right after i installed it. It seems the screen was defective. I couldn't fix it so I got the vendor to replace my screen and the new one worked like a charm. So you may, unfortunately need to purchase a new screen.
Like hell I will... the damn thing is less than a month old!!!!!!!! T-Mobile will buy a new screen! LOL
Hey, thanks a lot, I really appreciate that!!
for sure. I wouldn't void my warranty either. Unless someone else has another solution, I would just reflash the t-mobile rom and get replaced. That's a bummer man. Hopefully you get it worked out. Glad I could be of assistance.
Thanks again!
I'm on the phone with TMo right now, and I'm starting to get pissed. I originally signed into t-mo in October last year, so it's been what, 6 months? Since then I've done 3 warranty replacements with the Wing, then they did a "Multiple exchange" to the Dash (which I cant figure out, seeing as the Dash is cheaper) and now this, with a dash less than a month old.
I think I'm going to start a new topic about this so everyone can see what kind of run-around t-mobile is giving me.
Can you say that in plain english now.
Mikey1022 said:
Can you say that in plain english now.
Click to expand...
Click to collapse
I left Sprint for T-mobile in October of 2007 (last year), when I bought the Wing. Since then, I have had to replace it 3 times. Then, on the last warranty replacement (about a month ago) I asked for an alternate model. They sent me the Dash.
Better?
SpringfieldXD45C said:
I left Sprint for T-mobile in October of 2007 (last year), when I bought the Wing. Since then, I have had to replace it 3 times. Then, on the last warranty replacement (about a month ago) I asked for an alternate model. They sent me the Dash.
Better?
Click to expand...
Click to collapse
Yeah like i said in your other post...which i think one of these should be closed. Maybe it's you not the phones.
Mikey1022 said:
Yeah like i said in your other post...which i think one of these should be closed. Maybe it's you not the phones.
Click to expand...
Click to collapse
Dude, who put sand in your shorts??? How the HELL do you work out this is ME?? The phone was sitting on a DESK when this happened. It's never been dropped, submersed, abused, struck, anything...
Oh wait, that's right... When I asked T-Mobile about this and they said it's a KNOWN PROBLEM, I suppose that's my fault too, right?? I think you should do a little less talking, because you're a pretty ignorant and useless member that just likes to reply to posts with meaningless, unhelpful, rude messages.
You know, I love the way some people act on this board... (Don't get me wrong, most of you are excellent and helpful, and I'm grateful) But some of you just like to sit here and make absolutely no useful contributions... you just like to chastise people and act all superior without giving any real advice or help.
Ever think maybe people come here for help? If you can't ask for it, or you can't give it, then what are you doing here?
Both of you should mellow out. I adore my dash, but I'm on my third one, (my first refurb) and it has ...issues. My last one died in it's sleep in my pocket. It isn't exactly the toughest phone around, nor the most stable. I suspect the wing is even less reliable, as I researched one at length before choosing dash.
Of course, every time one bites the dust, I think, "is it me?" It isnt that unreasonable for someone else to wonder the same.
Peace love, and good luck with TMo. I've gotten a lot more help from them with sugar than I ever got from Sprint or Verizon with any approach. Don't loose your cool.
Even though I agree with your sentiments, I'm finding it a bit hard to mellow out.
However, I disagree with you on one thing: Yes, I think it really is THAT unreasonable for someone to wonder if the problem is me.. One of the Wings TMobile sent me wouldn't even power on, right out of the box... how the HELL is that my fault, and how the HELL is it natural for someone to think that it is?? What, did I open the box the wrong way, sending a static charge through the foam and frying the circuitry of the phone??
Furthermore, to assume that I'm the problem, when I've shown no signs of incompetence or admittances of dropping, submersions, etc. is not only unethical, it's also pretty insulting.
I know perfectly well how to care for electronic devices, and if I did accidentally drop or submerse a phone, I would be embarassed to try to blame T-Mobile for it.
No, I'm sorry, but it is 100% NOT my fault, and without PROOF it IS unfair and unreasonable for someone on this board to assume so. Certainly if T-Mobile thought it was my fault they wouldn't keep sending me phones, now would they?? No, I'm sorry, but I think people here that are that ignorant are simply posting because they have nothing better to post... and perhaps they just get off on ripping into other people. Perhaps they had their lunch stepped on a few times too many in high school. Maybe they weren't hugged enough. I don't know. All I know is they have no right to make assumptions about me. I didn't do that to them, so they should show me the same respect.
ow my head
Hello all! I have a sad story and an opportunity.
Sad story: I forgot my Universal on top of my car today and when I came around a bend in the road, it was slung out into a highway. The first car dodged it, and the second car aimed for it. I have taken pics. I think ti would have survived the slinging, and I am testing to see if the mainboard survived being ran over.
Opportunity: I'd like to get a new one. I don't mind parts-ing one together either. I am comfortable buying on eBay, and I don't mind it if I have to pay for international shipping, but I'd prefer to buy from the US for quicker delivery time.
I was just about to start really customizing the ROMS and all that too....
Sigh.
I hafe attached pics of the carnage. The microSD card survived. I did pull all of my data off though. Luckily I had done a hard reset las week, so I had all my numbers backed up. The SIM card survived as well, and I am borrowing a phone I gave a firend for the time being.
Wow those are some scarey images! Sorry for your loss, but that needs to be a closed casket funeral...
I've been considering selling my Uni/JasJar, PM me if you're interested in buying a used device with a bit of wear.
Oh my god............
RIP Uni are you trying to disassemble it for some pics of motherboard?
It looks better than I would have thought after being run over. You may be lucky and Mobo may be ok. You can buy replacement screens and casings.
Was it a compact that ran it over ? Cause I really cant see the Uni being that strong?
There are quite a few Uni's going on the UK Ebay anywhere from $200 USD to $80 USD if you are patient enough.
Good luck with finding another!
2 minutes silence for the Uni please......
Status update
I have purchased a B stock unit from eXpansys (the last one they had) for a decent price. Only problem is with the new unit, all I can do is get into the boot loader to see that it is version 1.00, and give it the hard reboot command. The unit appears to respond to the command but does not initiate the hard reset.
Hard reboot command I used: two soft buttons and the reset button.
Bootloader command I used: power, brightness, and reset button.
The bootloader does recognize that the difference between a USB and !USB connection. However, Windows consistently reports that the USB device has malfunctioned.
At first I thought it was a battery issue because the unit looks like it is brand new. So I waited patiently until I got home and tried all of the batteries I have here at the house. Yes, I was wary sticking the battery that was in the unit that was ran over into it, but I did try it. I have tried 3 chargers and two computers, and NADA. The only response I get from the device is using one of the two commands above.
Other random observations:
I tried inserting an old (disconnected but good) SIM card into it. Nada.
The battery was shipped in the battery compartment.
The backlight does work, as does the screen to some degree.
When I first plugged it into the charger, the battery status LED was red, as I anticipated.
The battery status indicator no longer turns red when the unit is plugged in. It does turn red when the battery is removed and power is applied.
Postulations at this point:
I wonder if I could load a ROM image to it?
I wonder if the battery is really charged.
Any and all help will be much appreciated on the matter.
disection
Win_XP said:
RIP Uni are you trying to disassemble it for some pics of motherboard?
Click to expand...
Click to collapse
I have disassembled it already and done some preliminary testing. The power LED does illuminate RED. I have tried attaching a battery and holding it, but hats not producing anything. But then again the screen is cracked like its cool, so I don't know what to expect.
I'll post pics when I get a chance.
beast0898 said:
Was it a compact that ran it over ? Cause I really cant see the Uni being that strong?
There are quite a few Uni's going on the UK Ebay anywhere from $200 USD to $80 USD if you are patient enough.
Good luck with finding another!
Click to expand...
Click to collapse
It was one of those KIA/Mercades/lexus lifted CAR SUV things. They AIMED for it.
I looked on ebay, but I never though to check the UK side. Usually eBay does that for em for some reason....
Situation update
I have had a couple of offers and much sympathy. Thanks!
My unit from expansys is up and running. I was up till 3 am saturday morning playing around with it. I stumbled across a few posts that gave instructions on how to deal with a potentially bricked device. As far as I can figure. my phone was shipped to me without an OS. I knew that PCs could do that, but can you just blank the OS on a phone? I can theoretically see how that might be possible, but why would that happen? Do they not get shipped out with OS's? that baffles me.
The specific process of deduction I used:
read the manual (the service manual from HTC). It said to either reload the ROM or the mobo was defective. I started looking on this forum for the procedures and files neccessary.
It seemed that my phone was not booting, so I looked into the ROM upgradeing/reflashing pages.
Links to pages I found useful:
http://forum.xda-developers.com/announcement.php?f=357
http://forum.xda-developers.com/showthread.php?t=367448
http://wiki.xda-developers.com/
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Flashing Guide
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/inde...consumption measurements of the HTC Universal
http://wiki.xda-developers.com/inde...y car or USB charger! It just doesn't charge!
http://forum.xda-developers.com/showthread.php?t=298613
http://forum.xda-developers.com/showthread.php?t=285435
As you can see, the wiki was quite helpful for me. Thae list above is not inclusive. I thought I had bookmarked all the pages I found helpful, but it did not apepar to be so. I have done much reading on this forum, and I purchased my original Universal over a year ago. I say that to let any newbies know that this is not a simple process and should not be attempted until you have a clear picture of what's going on.
I also tried the set 0 14 procedure, but that sis NOT work in my case.
What finally got me was the imate ROM I have attached to this page. It was able to see my universal, but only when I was in the bootloader. I will say that again because it bears repeating. I put the phone into the bootloader and ONLY THEN could I update the ROM on the device. I found no instructions anywhere on this, I had to figure it out on my own. The way I discovered it though is kinda neat. When I just plugged the phone into my computer, windows would not recognize it and say that it malfunctioned. If I plugged it into my computer with it in the bootloader, I got that nice sound that windows makes when new hardware is found. Also, I tried the Universal RUU and it did not recognize that the phone was attached in either way. Lastly, I first tried the ROM update with the phone not int he bootloader, and the IMATE program didn't see the phone. I tried it with it in the bootloader, and it did its thing.
I have attached a few of the files I found useful. I found these on this site, in some posts.
This is not a formal writeup, so please forgive any grammatical errors or rambling. I just wanted to share what I found.
So I finally just switched the SIM card back into the new phone. I tried to get MMS going, and SAME FRAKKIN thing: small pics. ARGH!!
AllanonMage said:
I have had a couple of offers and much sympathy. Thanks!
My unit from expansys is up and running. I was up till 3 am saturday morning playing around with it. I stumbled across a few posts that gave instructions on how to deal with a potentially bricked device. As far as I can figure. my phone was shipped to me without an OS. I knew that PCs could do that, but can you just blank the OS on a phone? I can theoretically see how that might be possible, but why would that happen? Do they not get shipped out with OS's? that baffles me.
The specific process of deduction I used:
read the manual (the service manual from HTC). It said to either reload the ROM or the mobo was defective. I started looking on this forum for the procedures and files neccessary.
It seemed that my phone was not booting, so I looked into the ROM upgradeing/reflashing pages.
Links to pages I found useful:
http://forum.xda-developers.com/announcement.php?f=357
http://forum.xda-developers.com/showthread.php?t=367448
http://wiki.xda-developers.com/
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Flashing Guide
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/inde...consumption measurements of the HTC Universal
http://wiki.xda-developers.com/inde...y car or USB charger! It just doesn't charge!
http://forum.xda-developers.com/showthread.php?t=298613
http://forum.xda-developers.com/showthread.php?t=285435
As you can see, the wiki was quite helpful for me. Thae list above is not inclusive. I thought I had bookmarked all the pages I found helpful, but it did not apepar to be so. I have done much reading on this forum, and I purchased my original Universal over a year ago. I say that to let any newbies know that this is not a simple process and should not be attempted until you have a clear picture of what's going on.
I also tried the set 0 14 procedure, but that sis NOT work in my case.
What finally got me was the imate ROM I have attached to this page. It was able to see my universal, but only when I was in the bootloader. I will say that again because it bears repeating. I put the phone into the bootloader and ONLY THEN could I update the ROM on the device. I found no instructions anywhere on this, I had to figure it out on my own. The way I discovered it though is kinda neat. When I just plugged the phone into my computer, windows would not recognize it and say that it malfunctioned. If I plugged it into my computer with it in the bootloader, I got that nice sound that windows makes when new hardware is found. Also, I tried the Universal RUU and it did not recognize that the phone was attached in either way. Lastly, I first tried the ROM update with the phone not int he bootloader, and the IMATE program didn't see the phone. I tried it with it in the bootloader, and it did its thing.
I have attached a few of the files I found useful. I found these on this site, in some posts.
This is not a formal writeup, so please forgive any grammatical errors or rambling. I just wanted to share what I found.
So I finally just switched the SIM card back into the new phone. I tried to get MMS going, and SAME FRAKKIN thing: small pics. ARGH!!
Click to expand...
Click to collapse
Hi,
Some of the commands for MTTY are not in the standard bootloader command list, best advice is to supercid your device (this will help in recovery if things go wrong later too) then once supercid is complete, upgrade the Bootloader version and flash a complete Rom to the device, radio, extended and OS in one flash.
All info is in the Wiki mate, if you need any further help, post back to us or PM me.
Glad you got a device back up and running, ca'nt you sue the guy for intentionally hitting your old one................LoL!
Cheers,
Beasty
Ok, i spend alot of time on this forum and its the most informative one on the internet. But, i haven't been able to find a solution to the problem that i've had for a year and 2 phones later. When i receive an incoming call and i push either the green button or the answer soft key, the call gets rejected. My carrier is t-mobile and the 1st dash that i bought started doing it about a month after i got the phone. I kept dealing with the inconvenience, then it started to do it about 3 to 4 times a day. I sent the phone back under warranty and got a refurbed one. Didn't do it for about a month then back to same old same old. Thats when i started to read this forum and discovered there were other versions of windows to install. So, i installed Ricky's rom (which is great) and didn't have the problem for another 2 or 3 months. I thought the problem was fixed until yesterday, it happened again about 4 times with a full signal. I made sure that the "disable reject call registry edit" was turned off when i first in stalled Ricky's rom. I can't figure it out for the life of me what the issue is (carrier, radio, other people's phones lol), I rarely ask for help because everything on this forum is very helpful and easy to find solutions to, except this. Please help.
No offense at all, but is sounds like you are "hard" on phones. From what you describe it sounds like you have been pushing the keys hard, and now they are worn out. Maybe not, but you had a Dash, it worked fine, then it broke within a month, then you gotta new one, then IT broke within a month, the common denominator here is YOU. So, I would try to be more careful with my phone, other than that, just get T-Mo to send you a new one forever. They will, if your phone doesn't work. That's how they are.
I don't think its the button because it works fine when i call somebody. Its only on the incoming calls. Can't figure it out for the life of me. When I got the refurbed phone it did it until i installed Ricky's rom. then it went away for about a month. Could it be my sim? Or maybe even the network? It gets progressively worse over. Check out this web page about the same problem.
http://metroplexdirectory.com/blog/archives/113
This guy had the same problem as me except, I had the problem with both WM5 and WM6. Go figure, might be time for a blackberry.
Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.
You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app
LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!