Database Info

Screen Alignment Problem..anybody having too?

HISTORY:
Recently back from screen replacement. Currently on TNT4.0 Professional.
PROBLEM:
It seems that the bottom half is alright. Just the upper half especially on right-hand at OK buttons. I've to click almost 5mm-10mm below to actually press OK or X. It becomes apparent while writing on Notes(I use PocketNote) with handwriting. Below appx. half line it writes where the pen is touching ie perfect. But above half line, it becomes very hard to write anything at all coz of problem in alignment. The alphabets don't appear as should be with some stopping short.
I suspect it's the hardware but also could be ROM(WM6) related. I briefly tested 1908 and it seems fine but due to the lack of time, I went back to current rom.
1)If others are also having same problem then possibly a ROM related.
2)Possibly some has already a solution if it's ROM related.
3)If hardware related, then time for wizard to retire as replacing again is not worth due to the price involved.
Just want to see whether anybody else having same kind of problem in WM6.
Thanks all.

I had similar problem with my previous ROM (but dunno from who was it, but OS said still 10.x.x.x), but this problem appeared and disappeared by itself, sometimes I had to re-align screen. It happened without any obvious reason - while playing solitaire, etc. Started to suspect hw, but reflashed to latest TNT and problem solved.

I have the same issue with my mda it in the same position, top right hand corner. I just haveto realign it, then reboot. And it fixs it for awhile, then I have to do it over again. Gets very annoying, I dont know whats the problem, since it happened when I was on the stock tmobile updated rom on wm5, and it still happens when I upgraded to the wm6. Currently running the black diamond rom, but since running black diamond it doesnt happen that often.
______________________________________________
Device: Tmobile MDA G3 Unlocked
Network: Tmobile US
IPL: 2.26 SPL 2.26 GSM: 02.25.11
OS: Black Diamond V3
SanDisk 2GB Mini SD

these devices are getting old
I've started noticing issues with screen alignment as well. Initially, I seriously thought it had to do with the "TouchFlo" fad and all the related WM6 ROMs, but I had since gone back to WM5 shipped and the problem persisted. So now I am facing the sad fact that my Wizard is probably just getting too damn old!!! I see the posts all the time.....ailing battery life....misaligned screens...flaky usb ports...miniSD cards not working...etc... I looked at various prices to replace parts ( http://www.pocketpctechs.com/main.asp?area=home )- but it just doesn't seem worth it!
Let's see how prices look for the Kaiser early next year... Or perhaps if I-mate gets their act together and produces hardware that lasts...

check this thread out, i tried the last suggestion, and it work awhile.

same ting here, but for me the problem occures on the bottum, at the softkeys. Most problem occures at the bottum left side. I also tried loading WM5 stock ROM (Qtek or T-Mobile) but without any improvement...
When aligning I also need to press the covering at the bottom left side, else I can't even align the screen....
In deed it seem to look for a new device will be the only good solution...

daishi17 said:
check this thread out, i tried the last suggestion, and it work awhile.
Click to expand...
Click to collapse
Which thread??

Screen Alignment Problem..anybody having too?
Click to expand...
Click to collapse
nope, i am using OLD mun.,..

my bad i forgot to paste the thread, but pretty much what the person did was use thier thumb and and wipe the screen with it. I did that and it worked quite well. I also installed the battary status app the beta version that is up on thier site, and have the cpu scaler enabled, and omap enabled with all options on.
omap overclock set at 247
CpuScaler
Min 143
Org 195
Max 247
Boost 260
Since i did this the screen alignment issue has disappeared, working great. Has been going good for a day and 8 hrs.
Try it and see, since this problem with the screen alignement is quite mysterious.

I think native12, is right. I have two Wizards (one OK one bad) and one Hermes. The bad Wizard was replaced by KPN, who told me that its a known problem, works fine now. The Hermes is even worse 1 cm out after half an hour.

YUP ! very true our ol'wizard are aged wearing out and goners
but certainly not a Rom upgrade malfunction,I must say only due to hardware malfunction or wearing out,

My story goes like this:
I've been having this realignment symptoms for over 6 months now but it got worse during the Summer. I used to have a protection film and read somewhere that the pressure it applied on the screen was responsible for the misalignment. By this time that was happening several times a day so i took the film off and it appeared to be the solution. It wasn't... after two weeks or so it came back and i started considering applying for warranty replacement or repair.
I have a friend that works at the official dealer repair center and offered to take my Wizard for observation regarding this matter. He saw i was running a WM6 customized ROM and was concerned that the repair guys would complain about void warranty so i decided to downgrade it to the original shipped ROM: 1.06 WWE
So he took it and in less than a week i had it back. You wanna know what they did? They upgraded it to WWE 2.17... HAHAHAHAHA After the large amount of ROMs flashed and countless times i read and flashed it to test WST they upgrade the device to solve a hardware issue.
Man, that almost makes me not want to send it back for the real repair/replacement...
"Grandfather: Well... that's it. Did you like the story?
Grandson: Yes, it was great!!
Grandfather: I'm glad, now off to bed." ('Manowar,Kings of Metal')

mestrini said:
My story goes like this:
I've been having this realignment symptoms for over 6 months now but it got worse during the Summer. I used to have a protection film and read somewhere that the pressure it applied on the screen was responsible for the misalignment. By this time that was happening several times a day so i took the film off and it appeared to be the solution. It wasn't... after two weeks or so it came back and i started considering applying for warranty replacement or repair.
I have a friend that works at the official dealer repair center and offered to take my Wizard for observation regarding this matter. He saw i was running a WM6 customized ROM and was concerned that the repair guys would complain about void warranty so i decided to downgrade it to the original shipped ROM: 1.06 WWE
So he took it and in less than a week i had it back. You wanna know what they did? They upgraded it to WWE 2.17... HAHAHAHAHA After the large amount of ROMs flashed and countless times i read and flashed it to test WST they upgrade the device to solve a hardware issue.
Man, that almost makes me not want to send it back for the real repair/replacement...
"Grandfather: Well... that's it. Did you like the story?
Grandson: Yes, it was great!!
Grandfather: I'm glad, now off to bed." ('Manowar,Kings of Metal')
Click to expand...
Click to collapse
"Grandfather: Well... that's it. Did you like the story?
Grandson: Yes, it was great!!
Grandfather: I'm glad, now off to bed." ('Manowar,Kings of Metal')
THAT"S IT

Asking "how" is like travelling through space in 3 seconds...(nice one )
It got worst from bad after using "search" function- with those cutting card method, screen protector off things. Now even the screen calibration never ends.
No....even can't sleep as "KAISER" is on my head.

Battery life and self powering on.

[Grrr lost message because of board login timeout]
Hi all,
I wonder if anyone else has had similar problems with their Rafael or has any suggestions...
I first got my Rafael (a stock O2 (UK) XDA Serra) back in February. At that time the battery was lasting about a day and a half between charges which was comparable with my previous Artemis (XDA Orbit). This is with my normal use.
About 6 weeks later the phone was needing recharged after about 5 hours of my normal use. The location I was using the phone hadn't changed, so this can't be put down to signal strength meaning the phone is using more power to compensate. My usage hadn't changed either, and I had not instaled any software that ran up the GPS in the background or anything that woudl cause extra drain.
One thing I did notice before I sent the phone back to O2 for repair was that occasionally I would take the phone from my pocket and the screen would be on, an app would have launched (like SMS or email or something) and the text entry area would be full of a repeated character. So the phone had obviously woken up from standby in my pocket.
The phone (and bettery) went back for repair and came back with a note saying that the fault had been found and repaired - unfortunately it didn't say what the fault was that had been found.
For a few weeks the phone seemed a bit better, but now about 3 weeks later it's doing it again.
Yesterday the phone was left in standby and not used at all. From full charge and just taken off the charger, the battery was dead within about 5 hours!
The waking up issue is a bit more than just inadvertantly touching the power button. I now have the phone in the supplied case/cover the other way around which protects the power button more meaning that I can't switch it on by accident. But sometimes I take the phone out and its on as before.
Even more odd is that sometimes if I pick the phone up of my desk by the sides (ie fingers nowhere near the power button) it switches on. And if I have used the phone and switch it back to standby and go to put the phone down, sometimes it wakes up again before I have managed to put it down...
A soft reset seesm to cure the waking up problem for a while, but after a few hours it seems to come back.
Obviously the phone waking up will cause extra battery drain, and that would mean the two are related or even the same problem. But does anyone have any idea what it could be and why a soft reset seems to sort the problem? Has anyone else seen this problem?
Obvisouly a battery life of just a few hours means this is not such a mobile device anymore!
Cheers,
FM

Update:
I sent the phone back for repair (to O2 UK) and they apparently found and fixed the fault.
When the phone came back it still seemed to have the same problem, but I tried it for about 6 weeks until I was absolutely convinced - it did!
So, back to o2 again, this time it was returned 'No Fault Found' - having done nothing to the phone.
So once again it was sent back, this time I was demanding a replacement handset as they were obviously unable to fix the fault.
A replacement handset turned up a week later. Note that this was not a new handset, but a refurb from the repair centre and it already had about 9 hours of calls on it and a dirty screen!
After putting all my apps and things back on the phone one at a time just in case it was a particular app causing the power on problem and the battery drain, the phone seemed absolutely fine - no switching itself on and battery life of a few days (estimated over two days). This was without the SIM card in though.
After 4 days when all my apps and things were back on I finally inserted the SIM and made my first call on the new handset...
...arrrggghhh....
This handset had a faulty speaker (earpiece, not handsfree loudspeaker)... sounding like a badly tuned analogue radio. Calls to a few numbers confirmed the handset at fault (the cracking started as soon as the speaker activated before the ringing tone started).
So after another heated call with o2 I eventually learned that they are no longer supplying the Serra (Raphael) and that my only option is repair again.
Oh no. Not going to happen. At this point I am 4 or 5 months into a new contract for which I paid for an upgrade to the Serra and have not yet had a new working handset. So I demand a replacement.
As they are no longer supplying the Serra, I have had to make do with an SE Xperia X1 (HTC made anyway, and just rebadged by Sony Ericsson), but in my opinion an inferior phone despite the widescreen.
The X1 has no accelerometer, no TV out, won't run Ton Tom Navigator 5 (of which I have a legit paid for copy), has a few supplied apps missing compared with the Raphael (RSS Hub, WorldCard Mobile - although they are available elsewhere incl links from these forums), and inferior remote control on the headphones (though better headphones, it must be said), and only a 3 row keyboard.
The loss of TF3D is no problem as I never used it anyway - I don't use the X1's 'Panels' either.
The X1 does seems to 'stick' a bit more often than the Serra did as well, but I'm managing to live with it so far - especially as I now have a battery which isn;t dead by 2pm each day!
-FM
P.S. O2 UK customer services were apalling. It was only after 3 months of grief that one day I eventually got to speak to decent people who genuinly seemed to want to help. One bloke (a supervisor!) I spoke to (called Nathan) was the most utterly rude and unhelpful tosspot I've had to deal with in a long time. Not only was he accusing me of 'trying it on' but he refused to even entertain the thought that I had received less than satisfactory service from O2. His superiors wil be receiving a letter very soon, when I eventually get this completely sorted - which it isn't quite yet.

The Touch Pro death thread - what are your experiences

I love my Touch Pro - really I do, its got all the features I want currently (except a digital compass would be good with some AR software, but that's not important roght now).
However, having got my first TP back in February I am about to send my handset back yet again as it has died again.
The first handset had a serious problem with battery drain and switching itself on (ie screen on) when not in use - I posted here about this at the time (clicky).
The o2 UK repair centre (Anovo) first of all said they'd fixed the fault, but after two weeks the phone was doing the same again - I did confirm this was not a software issue by running it ofr two weeks without any of my usuall applications on it.
So it went back again and was returned 'No Fault Found'.
At this point I demended a replacement handset. The replacement I received (a refurbished unit) had a speaker fault - crackling whenever the speaker activated, ie before a call connected and during.
That one went back as well and I ended up with an SE X1 for a while. OK but not a Touch Pro (and wouldn't run my legitimately purchased Tom Tom Nav 5 s/w). This was because o2 UK said they had no more stock of the Touch Pro and wouldn't be getting any more (why? too many problems with it?)
Eventually I got a call from o2 after numerous letters of complaint saying that they were going to exchange the SE X1 for a brand new boxed Touch Pro.
I have had this brand new replacement since August now.
About a month ago it died on me again. It just wouldn't switch on. Disconnecting and reconnecting the battery resulted in the flash on the back flashing, the handset vibrating (as though it was starting up) but nothing else.
Connecting the charger resulted in the flash on the back flashing bright about every second.
A hard reset would not work at this stage.
After a couple of days I heard the 'battery low' sound from the drawer that it was stashed in. SO tried a hard reset again - nothing. Tried a hard reset again with the charger plugged in and it reset and cam back to life.
... for two weeks...
then it died again.
This time is very similar to last with theflash falshing thing, except that if I try a hard reset it seems to go through the motions but without the screen coming on (ie the vibration. The beeping sound. Click the volume down and it pings again as though its starting the reset, then about a minute later the vibration again as though its restarting after the reset). But the screen doesn't come on at all. And the lights don't light up on the front buttons or the keypad.
Unfortunately I didn't have myMobiler installed on the handset so I couldn't try connecting to it from my PC (myMobiler did try installing but as I couldn't click the 'OK' button it didn't complete).
So. Are my four deaths of the TP unique or has anyone else had similar problems with this handset?
-FM

Not I.
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.

Anonymitee said:
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.
Click to expand...
Click to collapse
you need the 1.14.25.35 radio. and a different rom. maybe atts 5.11 rom if you want to still keep it stock. 1.14.25.35 is atts radio too so that stock and wont void your warranty as well.

Fuze Died Today, I Think
I've used this fuze since December of 2008 and have been quite pleased with the performance. (considering that it IS Windows) My signature radio works quite well in the mid west North America and travels well through different data protocols. Like H to Edge to GPRS and back to 3G again.
Today I flashed a new rom via usb and now it won't pass the splash screen. That flash appeared normal in all respects. Tried several hard resets (to the bootloader screen) and have tried to re-flash a different rom via micro sd card.
I've begun to think that this may be a hardware failure and would appreciate any advise for troubleshooting. Keep in mind that device will NOT connect via usb.

my screen went white a couple days ago. it would end up showing the windows logo for a while then a white screen. i hard reset a few times but nothing worked so i reloaded atts 5.11 rom and now it just stays at the "initial setup of the touchflo interface may take serveral minutes please wait" screen and wont get passed. i saw another thread about the white screen months back but i cant find it again. im just gonna wait till they have tilt2s and claim it under warranty. im gonna miss having flash, i use it to light up everything, but im sure a larger screen will make up for it.

Well I now have a bit more info on this since the phone cam eback from 'repair'on Saturday.
All they had done at the repair centre was to 'reload software' (their words, not mine). ie I guess they flashed the ROM again.
It worked for a day, though I guessed that was more coincidence than anything - after all, when this handset first did this a few weeks before it suddenly started working again a few days later.
Luckily in that time I'd remembere to install MyMobiler this time, and so when the screen died I connected to my laptop and fired up a remote view of the phone.
The screen itself was dead, but everything else seemed to be working on the phone - except that while the screen was dead I had an error displayed on screen. The error was "MicropERROR" as attached here.
So I Googled the error message, and what a shock a nice long thread on XDA-dev about it. Seems it s a fairly common problem with the Diamond, Touch Pro and Touch HD. Joy!
So the phone is now back with 'o2' again for another 'repair' this time with the attcahed screenshot enclosed. I have been warned again, though, that the Serra is out of stock and if they can't repir it I may have to select a substitute. As far as I am concerned there is no substitute - there is no other phone at the mo with the Touch Pro's features (hardware keyboard, VGA/WVGA screen, A-GPS, g-sensor, WinMo, runs TomTom Nav5).
I fear the worst again, and fear I'm back where I was in July with an impossible choice to make thanks to o2 UK discontinuing the Serra / Touch Pro after a few months of supplying it.
-FM

well i got my TP back in March.09 and last month i have to replace the mother board and the back speaker other than that all is good so far
but i was so frustrated with HTC support centre (which is the main one in Taiwan ) real unpleasant experience as you all may know
Cheers!

Time to send mine back
Just had an issue with my last one, it was only 5 months old and the screen started looking like it had a vertical hold issue. Just got my refurbished one in Wednesday and now it is doing the same thing after playing games on it for 5 minutes. The speaker phone is crackling too for some reason and when charging it at night it's like the screen will not fully black out. I am wondering if I even want to try another one of HTCs products or not. Nice phones but to many headaches it seems.

HTC build quality issues - am I alone?

Hey guys,
I've just receieved my third HTC handset with what I'd consider to be a major issue.
HTC Touch2 in 2009 - would often power off during calls (probably due to WinMo). Hardware buttons quickly became loose after about a month of use, and the backlighting stopped working.
HTC Legend in 2010 - this phone is two months old and the top speaker is so broken I can barely hear somebody on a call. Everything crackles and pops and, according to people on the other end, they can barely hear me either. It's annoying as when I bought it the call quality was great but gradually the speaker got buzzier and buzzier.
HTC 7 Trophy - the most serious of the bunch. Yesterday, whilst web browsing, the phone displayed a still multicoloured screen of static. None of the buttons would work. After taking the battery out and restarting, the static re-appeared. I've managed to power on the phone since - you have to wait an hour with the battery out - but you get the same static lock ups when web browsing or using search after about five minutes. Having had a similar experience on my laptop, it looks to me like a GPU failure.
Am I the only one who has experienced incredibly shoddy hardware quality control from HTC? I'm going to have to replace the HTC Trophy and, at the moment, I'm starting to seriously question going with an HTC. The touch2's button issues were forgiveable because that was relatively cheap, the Legend's speaker was incredibly annoying but the Trophy's GPU failures are completely unforgiveable IMO. They render the phone completely useless.
Am I just unlucky or have others experienced similar concerns?
Cheers

My Hero has been fine, along with my touch... Although that met a washing machine in the end

Finally ~ Someone With A Similar Issue
Finally, someone that doesn't purely worship HTC... Although I haven't experienced issues to the magnitude of your's, I haven't been 100% happy with my phone since the day I bought it. I have a HTC Desire, and I got this phone in confidence after reading many reviews about how good the phone was, these reviews were clearly written from people with 0% experience with the phone.
I will number the issues I have had with the build quality of this phone...
1) The case on the back of the phone, has only ever been took off about 4 times, I have never dropped my phone or anything, however it starting to come off, yes, I can take the back of my phone off, without using the finger slot.
2) The screen is so easy to scratch? It was in a pocket with an Asthma spray, and there was no vigorous shaking of my pocket, yet somehow the screen just completely f****d up man... wow.
3) This is probably the worst issue I have. Every time HTC releases an update for my phone, I run into some sort of issue. I got my phone in May/April 2010 (it's on Orange UK however de-branded and now due to update issues, running a custom ROM) and immidiatley I found that an update had been released. After downloading the update the phone started to install the update, however it restarted and nothing happened. Left it for about an hour, nothing... So yes, I did the worst, took the battery out and messed it up completely. The shop I got it from forced me to send it to HTC, it took them 5 weeks (VERY poor customer service) and when I got it back they had barely fixed it, as when I turned it on, it finished installing the update?
4) I have had some other software issues, such as the system occasionally locking up and having to remove the battery to get anything to work. Occasionally the screen will lock up, like I won't be able to click any icons, however I'll be able to swipe from screen to screen, and it really can be quite annoying. As far as battery goes, it will last me an entire day, but will require a charge at the end of the day.
However, I think me and you are in a minority. I'm 14 years old, and I talked my Dad into buying a HTC Desire HD. He hasn't had a single problem with his, it installs updates perfectly without and issue, and the software performs seaming-less (except for a problem with a process that took up 80.9% of the RAM, fixed by turning the USB Debugging on?) So I believe HTC are good, theres just a few really, really bad apples in there, and unfortunately HTC won't admit this, and don't want to do anything about it... I hope I helped, I'm fairly new on here...
Cheers, Michael.

Well guys,you are a minority indeed.This Tuesday I received my Desire HD,which is my fourth handset from HTC.I have had a Diamond,a Hero,a Desire and now the Desire HD.The only problem I ever had was with my Diamond which,after one year and a half took some water in it without getting exposed to any water,but it was because the climate here is very humid.Other than that I have never had an issue.And I am no fanboy,if I had problems I would change without second thought.
I'll just tell you that a friend of mine punched my Desire HD with his full strength(don't ask why) while it was in my pocket.I thought the phone was done for,scrap,but the phone is like nothing happened.My friend's hand wasn't so lucky however,it still needs ice!

[Q] "Retroactive Bricking" or "spontaneous" hardware fault?

PSA: *This will be crossposted in xda HTC One X 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.

*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!