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 tried to search but I haven't found anyone with this particular problem:
Today I had to swap the SIM card on my dad's N1. I must have touched something the wrong way since after doing so, it seems the trackball is constantly being pressed (even though it's not).
Here's some of the consequences of this, that are making me literally freak out:
1. I can't get into recovery (as soon as I do, a click is registered on "Reboot phone).
2. It only boots in safe mode
3. Navigating around the phone is almost impossible, opening up the app drawer immediately launches an app.
By hitting a text input field, I can observe how it's registering clicks really fast (by observing how the whole text field is selected/deselected)
I tried fiddling a bit with the trackball, long pressing it, clicking it, etc, but it's still a no go (long pressing it does register as a long press, but as soon as I let go, the constant clicking continues)
Seeing as how this happens whether or not after the ROM has booted, it looks like this is a hardware problem.
Has anyone run into something like this before? Any ideas on how to fix this myself?
I don't know if sending it to HTC is an option because of two reasons:
1. I live in Costa Rica, don't know if there's HTC support here, or if it'd be safe shipping the phone to the states for a repair.
2. My dad's N1 is rooted, but bootloader hasn't been unlocked. It's running a custom rom. Right now I'm not sure if I can't get it back to stock since I can't even get into recovery.
Please help! Thanks
I had this exact problem for about a day or so it turns out I had got the trackball wet try clicking it and rolling it also try giving it a day or two it might just come back good luck on your nexus
Sent from my Nexus One using XDA App
Turns out you were right!
I left it sitting for a day, turned it on and the problem was still there. I got a hair dryer and used it on the phone for like a minute, turned it on, and all is good now!
Thanks!
Problem has come back and won't go away now... definitely looks like a hardware issue, will call HTC support.
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
I updated my C6903 to Android 5.1.1 around... say a month ago? Or around there. It was giving me so much trouble, I couldn't stand to use my phone anymore.
Therefore, I read up on what I could, and attempted my first downgrade to 4.4 KitKat (Central European 01 version 108, unbranded). I didn't wipe the data and that turned into a bit of a mess, but I successfully flashed it and wiped the data properly during the second time around.
But I was still getting some problems, ones that had been occuring since my phone was upgraded to Lollipop. First, that my phone can not enter full screen at all, on any app. The home bar flickers on and off all the time, during Youtube, during any videos, during visualiser, or any app that will make use of fullscreen.
The second issue is that my home keys become unresponsive the vast majority of the time. Restarting does not fix this, and locking my screen then unlocking it again works for roughly 1 minute, then it's back to freezing and no response.
So, considering my main issues were persistent since the update of 5.1.1, I tried a factory reset. I wiped everything and flashed it properly again with Flashtool, to 4.4 KitKat.
It has not worked. Using the developer options/diagnostics I have tested my display and my entire screen has no dead pixels and reacts to the movement or touch of my finger with no issue. So if my screen is fine otherwise, why has 5.1.1 completely ****ed my phone over? It does not make any sense.
At this point I cannot even watch videos or do basic things on my phone as the above issues are preventing me from doing anything. I'm willing to provide as much information as I can, so I would appreciate some help and insight into this. Thank you!
EDIT: Additional information - Trying to view pictures in full screen (Album) ends up with it zooming in and out constantly, even when nothing on the screen is being touched.
When my phone is on landscape/full screen android keyboard, it will intermittently go crazy and start vibrating. I believe it is the symbol key being pressed on it's own, off/on constantly. Nothing on my phone is being touched or moved at this time, it just does this by itself.
it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!
masterofnocrack said:
it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!
Click to expand...
Click to collapse
The cover for the charger port is broken and just fell off one day a long time ago (it never closed properly, though) so unfortunately, I won't be able to go through with that suggestion.
Added new information. I hope I can get some insight into this soon.
Hey guys, I've been having some issues with my RP2 since fresh out of the box. Randomly, my phone screen will not turn on and will stay black. The phone itself isn't shutting down, as when I attempt to turn on the screen, I can feel the haptic feedback from an attempt to unlock via fingerprint.
It's really touch and go, sometimes its good for a day or two, sometimes it'll do this two or three times a day. A hard reset (Pwr+Vol Up) gets it back running again, but it's getting really annoying and interfering heavily with just everyday use.
Anyone else having the same issue? Anything I've read around the web hasn't helped or isn't pertinent. This happens on complete stock and running Arter97's kernel, so I'm left to believe it's a hardware issue (please no) or a ROM issue, i.e. Razer did a crap job.
Any thoughts? Thank you in advance!