Hi all. I got my Kaiser on Monday and am VERY pleased with it. Like pretty much all of the folks on this forum, I wanted to "upgrade" it a bit.
My problem is:
I installed the BBC file onto the mem card (2 gig). It said click OK to restart device. I did, but now it gives me the Windows Mobile screen and NOTHING else. The (left) indicator light is flashing green but nothing else is happening. When I press any of the buttons, they light up, but the screen does not change.
Mine is the HTC original rom, unlocked. The only thing I have installed on it is Skype.
When I call it, the incoming screen comes in over the WM startup screen but that's it. The phone works but the "Phone - Incoming" notification stays visible even after I have hung up.
I can connect and sync with ActiveSync, but the screen does not change.
Even after I take out the battery (because that's the only way to turn it off) and take out the mem card and restart, same thing happens.
I am in DESPARATE need of help!!!!!
Any suggestions as to how to "unbrick" my baby?
If there is any other info you wold need in order to shed some light on the issue, just let me know.
Thanks in advance.
Dominic
Hi all.
I found a way around the problem.
Apparently the file I got was a VERY old version. I did a hard reset (luckily I didn't lose anything as I only had it a few days) and installed the file from the link on this forum: http://forum.xda-developers.com/showthread.php?t=327695 and it works fine now.
Thanks to all of you guys who already did the hard work in getting links, etc.
Later.
Dominic
Hi,
Everything is working great on the new WP7 rom with the exception of the Messenger app by Miyowa.
It starts about 50% of the time.
When I do get the login screen, and sign in, it shows the loading line, and as soon as its full it switches back to the application list.
I have uninstalled, rebooted, reinstalled many times, but cant seem to get it to work.
I know it does have lots of problems and issues (going by the reviews), but does anyone have it working on the HD2?
Thanks
Chris
Just recently I was trying to install but I get the error that Zune is not open and the phone is not unlocked.
it works.... but as you said its very unstable... havent tryed to have a normal conversation on it yet....
redman99 said:
Hi,
Everything is working great on the new WP7 rom with the exception of the Messenger app by Miyowa.
It starts about 50% of the time.
When I do get the login screen, and sign in, it shows the loading line, and as soon as its full it switches back to the application list.
I have uninstalled, rebooted, reinstalled many times, but cant seem to get it to work.
I know it does have lots of problems and issues (going by the reviews), but does anyone have it working on the HD2?
Thanks
Chris
Click to expand...
Click to collapse
the login screen and the screen after login look kinda similar (was also confused the first time)
try it again, and after logging in swype to the left (to reveal the page on the right which is the contact list)
chevron unlocked my phone yesterday and had used this messenger about three times since..
Yeah, it wont log in. I don't get any screen after the spinning dude finishes, just jumps back to app list.
But it sounds like it works on your hd2.
I have samsung galaxy tab p1000, india.
I am experiencing a problem with touch screen.
Once it starts working, it works perfectly fine with no glitches or any problem but once it goes to sleep mode, it may or may not recover from the sleep mode. When I press the power button, the screen comes but i m not able to unlock it or used.
Initially this problem used to occur rarely but now it is very rare to get my touch working.
I have tried hard reset / soft reset / changing the firmware (approx 20 times) but m not able to make the touchscreen working reliably.
Have also flashed miui ICS, aokp , firmware from samfirmware , tsar300, but no use.
As far as i appreciate this is a software glitch as the touch screen are not able to load everytime the tab wakes up. So, if some body could correct this problem or suggest a solution.... it would mean a lot ..
continue
I was just working out things. When i flashed stock firmware ddjm2, i had a comparatively stable system and improved touch response, although the frequency has reduced but the problem still exists. Any help would be apperciated, i am really frustrated,
thanx in advance
It may be a kernel issue. Have you tried Overcome's kernel/ROM?
tried overcome kernel also, no use.....
It sounds like a software/firmware problem, but if you're still having issues on stock kernel & ROM, it may be a hardware issue...I've never had any issues with touch on my tab...
bigz1981 said:
It sounds like a software/firmware problem, but if you're still having issues on stock kernel & ROM, it may be a hardware issue...I've never had any issues with touch on my tab...
Click to expand...
Click to collapse
thanx bigz1981, one more thing discovered today.
once i flashed fresh froyo 2.2, it works fine but when i connect it to internet, something is updated which results in touchscreen showing above abnormal behaviour. This time after installing the firmware, I switched off the network, lets see if this solves the problem. Nyways thanx for the advice.
Also, i now remember that previously I updated my "tsp update" by dialing that *#____#* number, Which had failed. All this may be result of that. Can you throw some light on TSP,
1. is it touch screen ******,
2. whats wrong in updating it.
3. Was it trying to update through internet, since I was not flashing anything at that time.
4. Is there anything known as touch screen firmware , from where can i update it.
Thanx dear, for all the effort putin by you.....
I also request some senior administrator of the forum to show some way in this darkness...
from the developers, i wanna know,like we have device drivers in case of computers ,
1. we must be having some drivers for thetouch screen ,???.
2. Can this driver be loaded everytime the tab wakes up from sleep.
3. Can we shift loading of this touch screen driver higher in the booting sequence.
I am not a android nerd, but i know some basics of windows. Please guide the correct way. Thanxxxx
Just another input for processing, around 8hrs earlier i had again flashed my tab with ddjm2 foryo2.2, and disconnected from internet. The tab worked fine. I operated it for around 40 times waking up from sleep. It worked perfectly except 4-5 times. I am not able to understand,, what is there that is spoiling the firmware, once it starts updating through internet.
Hello .....
i came up to the forum ....with some expectations .... . ....
moderators , administrators pl listen,....
I saw a similar thread, but try to download ILITEK Touch Utility from the Play Store & see if this helps with your issue.
Dear,
I have the same issue!! very odd. I was a long time without using my tab and then I found out this issue few weeks ago. I've installed 2 applications (angry birds space and juice defender) right before the issue, no new rom updates (I'm still using the euro rom update on my t-mobile tab done 2y ago), however not sure if any automatic update has been performed on the apps. After deleting these 2 apps, issue still persists.
Let me know if someone found a solution.
B. Regards,
Marcel
happened to me when google market is updated to google play
This is my first post around here, so first of all I guess I must say hi to everybody
Two weeks ago I bought a brand new KFHD 7''. I rooted it and followed the steps in order to get all the gapps correctly running. Everything worked out and the tablet performs great. But there's something that is starting to annoy me.
Initially I didn't care about it but now it keeps catching my attention and gradually bothering me more and more.
When I'm running an application and press the home button to go back to the Desktop the whole screen blinks twice. Moreover, when I recieve an email, the notification bar starts blinking as well and also hides, which turns out to be impossible to scroll it down in order to check the notification. It's getting desperating.
At a very first moment I figured it was an issue with the launcher (EX launcher HD), but afterwards, once I'd changed it to ADW launcher the problem persisted.
So what do you suggest me to do? Any tips or advice? Should I try to install kinology?
Thanks in advance and thanks for having this great phorum.
First of all it's working again so I'm not really looking for any help to get it running but still I thought this is worth mentioning
I wanted to import a .mobi book to Nexus 7. This book was sent to me by a friend and I wasn't completely sure what it was. Not even sure if a .mobi file could cause this. But here it goes:
I tried to import this ebook to Aldiko, turned out, it does not even find the file - so I've downloaded Moon Reader from Play Store which found the book and offered me to import it. While importing it the app froze and superuser showed me that "Shell" asked root permissions but was denied. Eventually the tablet itself froze. After a few minutes the message occured that Moon reader does not response and I chose to kill the app. Then the display turned black and the tablet seemed to have turned off.
After that point the tablet was not responsive anymore. No matter what I tried, it would not respond to anything. Battery was at 40% before but I connected it to the charger anyways. I've tried to boot up again and this time I got some disfigured weird glitches but nothing like a bootscreen. After some time it actually booted into Android (at that point it was an older PACman ROM). As soon as I've tried to unlock the screen the tablet made some weird noises (sounded like R2D2 ) and turned black again.
Again the only reaction to pressing the power button were some glitches...I left the device untouched for a few minutes and tried booting again, this time holding volume down button and it got me into download mode where I was able to choose recovery mode which then gave me the chance to restore a backup. After that it worked as if all the above never occured
However I've decided to flash cm10.2 nightly build then since I had my little issues with PACman on Nexus 4. Though I don't blame the ROM. But quite frankly I don't have the slightest idea why this happened, what caused it and what exactly this issue was.
So I just thought maybe someone encountered similar before and might be able to tell me, what all this was about.
Besides I've checked this .mobi file with virustotal.com and not one antivirus raised alarm. Still don't know what was inside that .mobi, but I don't really wanna try it on any other device
Anyone ever had this?