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.
I've checked and some says that I need to replace it but as I dont have much cash I wanna make sure that my screen needs replacing.
My bro got me an old G1. And its screen starts to behave quite odd recently. Sometimes I cant touch anything, or it just keeps pressing itself. (In cases like when I'm typing it will types it self bunch of letters in the mid and bottom lines (the asd-zxc lines) And when things happen I have to turn off the screen and wake it again. Problem resolved temporarily.
And it happens daily, if not nearly all day
So please anyone that got experiences or advices please tell me is it the screen's fault? And should I replace it?
Thank you for your attention!
P.S: I know that nothing can live forever...
I had similar problems. It happened when my battery was low... Im pretty sure it was just my ROM being buggy.
Thank you for responding
But I dont think so. I changed to dwang's rom (donut as I remember) and it still were "lagged" like that so I flash back to CM 6.1.2. So I dont think that's the roms' fault.
And about the battery... Im not sure. Sometimes when the batts gets lower I got better responds .. quite unpredictable
And what did you do?
I attempted to install a new ROM, failed. Tried to recover my back up, and now I'm learning to fastboot. :/
After the install failed, and I had a fresh instal of my ROM running, it seemed to stop.
I also noticed that it only did it when I had the keyboard opened.
Aww I'm not lucky as you are.
Since I've installed 4 roms but none of them fixes it. I'm thinking of changing the radio Im not sure though...
Just see what other people have to say
Still no clue...
Good evening everyone!
Little did I know, my father had his OG Droid just sitting in a drawer when he upgraded to the Inc2. I had him ship it out to me this past day so I can use it as my play thing!
Upon first boot up, before root or anything at all, I noticed the left side of the screen wasn't responding. Say, the back button and all the way up. Everything beyond the back button seemed ok.
I felt that maybe it was just a quirk with how old and how much he had used his phone, and was hoping for a software fix (read - flashing) and not a broken screen or any hardware problem.
As I began wiping data and resetting everything that could / should be, it started to get worse. Random "touches" on the screen, menu keys moving, total unresponsiveness. Just general whacked out problems that make you want to throw any device across the room.
I did manage to get Clockwork on, flash into recovery and install (successfully!) a plain 2.3.5 ROM I like. It was annoying with all the menus and key presses going all over the place, but they weren't happening while in recovery, so I was hopeful.
Upon the successful bootup of 2.3.5 though, the screen was even worse - more bouncing around, less responsive, etc etc.
So, my long winded question: anyone have any idea if this could be any problem but some sort of screen mishap or other hardware problem? I kind of hope it's not, just so I can have a device to constantly play with.
Thanks in advance!
broken digitizer, a common issues with droids/milestones.
Hey guys,
I don't know if anyone else has experienced this, but the back and menu buttons stop working suddenly. This has happened to me twice. A simple On and Off fixes this, but I wanna know if theres a proper fix for it? My phone is rooted with the stock ROM "KKA". Anyone else experienced this?
My phone is NOT rooted with the stock ROM "KKA" and suffers the same problem.
Mone rom is rocket v17 , i got the same problem 2nd time.AND screen didn't wake up.
I have had this issue once so far, rooted with official Arabic Rom. does anyone have a solution?
had to restart the phone to bring it back to normal.
Read on Androidnz blog that this happens sometimes using spen with button press for using menu features like pulling up menu or back button etc.
I'm rooted, standard ROM, rarely use the SPen (haven't got around to understanding what I can do with it). I've had the unresponsive Back and Menu button problems a few times - only solution I can find is to switch off and back on again.
Good to know that it's not just me, but it would be nice to find a solution.
Same issue. Stock rom. Happened to me just now and the stylus was not being used at all.
well i also have that problem. i also know others with this problem.in my case restarting the launcher helps.ofcourse if u have both home and back button not responding at the same time then its not possible.i get both of them not responding at the same time very very rare.at that time all i do is turn of the screen and wait a few minutes.thats all,every thing is normal again.oh one more thing i think its a good idea to keep more than one launcher installed and not making any of the default.it helps switch between them easier.switching between launcher always helps in these not respondig issues.
Heya all,
So my Galaxy Mini started rebooting itself today.. Anybody knows what to do? I can't give much details only that I thought the problem could be the custom rom (CM7, New Experience). I flashed it back to stock, but it's still doing the same thing, sometimes it'll hold out for 30 minutes but sometimes it restarts and I can't even open Whatsapp before it reboots again.
All I can tell the on/off button for locking isn't always working as fast as it should. Could this button be stuck or something like that?
Also warranty is gone, got water damage from like 1.5 year ago.. Maybe that could still have something to do with it.
Thanks in advance,
Sanderth.
Update: I was just viewing a WhatsApp message and it rebooted itself again, please does somebody have any advice on how to fix this?
Bump: Please does anybody know what the problem could be? Today at school I wasn't even able to send a message via WhatsApp
Edit: I'm pretty sure it always happens a few seconds after I pressed the on/off button to lock. I just tried to lock it, got the prompt where you can enable airplane mode and turn the phone off and I clicked the back arrow, after ~5 secs it rebooted, could something be stuck behind this button or could my ROM be bugged?
Edit2: Well I disassembled my phone, probably something was stuck behind my button and fell out or something else was wrong with it.. But the most important thing is: It works like it should again, locking is going smooth now and it really feels as if my phone was better than before XD
Next time I'll open it first before opening a topic on xda, but well.. Hopefully somebody who will ever have the same problem will find this thread and fix it the same way I did
:thumbup:
Sent from my GT-I9300 using xda premium
Well to be honest, it'll stick to randomly rebooting itself once in a while, less than it was before disassembling and putting it back together again though (From 5 times in one hour to max. 3 on a day). But trying this could never mess something up (as long as you know what you are doing.) At least it's possible to use my phone normally again.
For the people that don't know how to disassemble, use this: http://www.formymobile.co.uk/s5570disassembly.php
Disassemble until you've got the battery compartment of, then just assemble again.