My moto droid's screen died. I have the common right 1/3 sreen dead problem. Because of this I can not open the lock screen. The phone has since been deactivated, so i can do what ever I want with it.
I want to root it so I can use screencast 0.4 to view it to make sure I got everything off it. I can't root it because I do not have USB debugging enabled. I can not enable debugging because I can not get past the unlock screen. But I can not use screencast because it is not rooted. So I am in a pickle. I have read a lot of XDA forums and others and still have not found a solution to remotely view my phone, at least that I can find.
I have Android Developer installed on my PC and I have played with it a little. I am trying to learn more everyday.
I also know that the adb needs to be running, and I have yet to figure out if it is running or not. I have also read that you need to stop and restart adb before screencast will operate properly.
So with all that info, does anyone have suggestions how I can view my phone and interact with it to make sure I know what all my programs were and save any data that are program related.
I have searched for keyboard unlock codes to no success. I also know that my android market library tells me most of what is installed.
So any suggestions??
Darshan
(Win 7 x64, HTC Thunderbolt, 2.2.1)
First of all what did u do to it? Spilled water, dropped it, installed something what?
Nothing!
Absolutely nothing.
I downloaded the lastest update, and about a week later the screen behaved very erratic. 2 weeks later I lost the right 3rd of the screen (touch only, not image) Could still get in by opening keyboard, then swiping the lock. 2 weeks later the swipe no longer works, keyboard open or closed.
This loss of touch response is very common. I have read about several other people with the same problem. It has nothing to do with any updates, as I have read about someone with this problem over a year ago. It has to be electrical. As an engineer, I have inferred that the touch screen has 3 circuits for 3 zones on the screen. 1 circuit must have gone belly up. So my right third does not respond.
Also most victums report erratic screen behavior just prior to loosing some of the screen.
So that is what I know.
D
Related
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy
IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.
The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S
well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.
just leave it off for a while and keep it someplace dry and warm so it can dry out.
You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup
Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.
I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.
Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x
I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??
This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...
same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!
Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol
I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.
I wonder if any of you have tried restoring your latest back up?
Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Hi All
New to the forum.
I did search this topic but didn't find anything finite.
I have had my Note for 3 weeks now.
In that time there has been 2 occasions in which my phone seems to have shut down while asleep.
There was a brief mention in another topic about it being the TWlauncher or an SD card problem.
I'm just really looking for any advice as to whether there is any settings i could change to stop this happening.
Thanks
Edit:
I am on Stock Rom 2.3.6
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
I have the same problem. But I do not remember what the phone was doing at the time. But I will be back if this happens again .
I had that kind of problem with an HTC Desire some time ago and HTC changed the motherboard , problem was solved.
I had this problem with my Galaxy Note but I was never able to locate the cause because it also happens on a stock firmware, There were a couple of similar posts before but they were never solved, same deal at a local forum a few people had the issue custom ROM or stock. When I started to use RevoNote HD with V3 I think these 'Sleep of deaths' stopped AFAIK.
Army92 said:
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
Click to expand...
Click to collapse
- I do have antivirus installed (AVG)
- I have many apps installed (the list would be too big to put here)
- It shut down whilst on the table
- Sorry but i am not aware how to view a logcat output
Well, I read in a german forum that anti virus programs can cause those shutdowns/reboots. I personally don't believe this but you can try to uninstall it.
You can find logcat here:
https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result&hl=en
Just install it and let it run. Wait for the problem to occur and then reopen this app, save the log and put it up here.
It also can be "just" a black screen.
So that the phone is awake but the screen is black, so it seems like it's down.
It can help to push the power button again.
(For example this problem sometimes occurs at CM9.)
Thanks for the help.
I have download CatLog. Fingers crossed that i wont have to use it
I had read about the black screen problem and that it could be linked to a lock screen issue so I have downloaded WidgetLocker as an alternative to see if that makes any difference (I don't hold too much hope for this as it is only ever running on top of the touchwiz lockscreen but i may aswell try)
i just got my note a few weeks ago and have been suffering this problem as well. it has happened twice now where the note has switched itself off, and my morning alarm has not gone off! which is quite tragic as i rely on it to get to work.
i wonder if this is a software or a hardware problem...
any other owners facing the same problem?
I've had my Note around three weeks and in the first week I had this happen to me twice. I cannot say what caused it (I'm on Stock Rom), as I went a bit app happy and downloaded all sorts of apps when I first got it. After the first week I cleaned up a lot of the apps (Which included AVG, GoLauncher) and I've only had it happen one time since.
I was using the app "My Country" or "Airport City" and I think it was being slow, so spammed it with commands - causing it to reboot. Which is probably unrelated to the previous problems, I have however looked into CatLog - so if it happens again, I will post some details up here :]
Ok so tonight on my way home from the movie theater while riding the Harley i run into a down pour, now the hero is in the saddle bag which i was hoping would keep it safe, dry and happy, unfortunately that wasn't to be.
i get home and after getting the phone i go to look to see if i have any missed messages and find that it seems to have turned off, upon attempting to boot it goes to fastboot mode.
i currently have it sitting in a bowl of rice to try to dry it out, but does the fact that it still attempts to boot at all mean there is hope for my little hero?! I <3 that phone it's been so loyal! Even though i'm currently considering upgrading i'd like to get a backup of some stuff i haven't backed up recently before changing phones.
ok so it boots up now, my only problem is that the screen won't unlock now, i've tried changing out the glass touch screen to one i know works and that's not doing it, so does this mean i'm SoL? that something on the motherboard has gone wrong?
even though i'm not getting any responses going to update, couldn't find a way to unlock the screen with the touch screen not working, now that being said, i did find a command to pull my mms/sms database through ADB, now when i get a new phone will i be able to paste this database file in and it compile automatically, once i get root access that is?
Yes. Transferring the messages shouldn't be a problem.
What phone did you get?
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk