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 been in this rooting game since it began, and I never had a major issue.
Unfortunately now I have come across one, and I believe it may be a Hardware problem, but I'm not entirely sure.
At any rate, the other day I'm on the computer the phone is charging through the usb cable, and while im using it, the back light goes out. I think this is weird.
I lock, and unlock it and everything is back to normal, but when I slid the screen back the back light went out again.
And the home button didn't work either, I doubt this was a problem with Cyan's ROM, or a theme. I do have the new lockscreen but I never had an issue.
So from Cyan's 4.0.4 I upgrade to the experimental version and the problem persists, the back light won't turn on unless the screen is slid up/open (Also, I have no lock screen!? wtf?).
Afterwards I decide to go back to 4.0.4 and even when my phone boots up the back light wont turn on unless the phone is open/screen is slid up. So obviously it seems like a hardware issue.
Anyone else have this problem? or any thoughts about it?
I'm on Cyan's 4.0.4 - no theme
26I Radio and H's SPL.
reset your phone. hit call,menu and power at the same time. then let us know how everything works.
Funny things happen when you don't wipe, make a nandroid backup of your current setup and than wipe and flash again and see if it persits
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
igloo77055 said:
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
Click to expand...
Click to collapse
This is a hardware problem. Happened to me too. Been trying to find a solution, but the fact that it still has the same backlight problems when the phone is booting (On the T-mobile G1 screen) shows that's it's way beyond the ROM.
Mine even has the same problems on the recovery screen. Time to find a new G1. If you find a solution, lemmie know. I've been looking for one.
Dear all DEV,
I dont know if you all facing same problem as me, I have tried many kind of Hero for G1 from tradition hero by Drizzy till now the rom was upgrade to use RAM hack, but now I found one issue with my G1 when I try new rom that build on new JAC kenel ( I can't remember all BFS xxx) and it was my phone will not wake up and alert me anything after he sleep for quite a long time, for example, some one call me, they still can ring me, but for me I know nothing from me phone and even I press to unlock the phone, nothing happen. The screen just stay back or sometime I can see some picture from the screen without backlight, but nothing work for me, unless I pulled out battery and reboot phone back. After new reboot, it will go back to same situation again after a long sleep.
This text is not a panic to any DEV, but I want to show it out to you guy all in the new thread just want you all hear about this issue, cause sometime I reply in other thread, it was obmitted.
MOD, you can say I start new thread for nothing important and you can close it anytime you want, cause My main purpose just need some DEV to see my issue and keep it in consideration.
As this issue happen to me currenly I can not use SenseHero or M-LING... cause it's all give me this bad experience, and now I just stay with a very tradition Hero from Drizzy.
Regards,
I did have the same problems when using BFS 300 and 302. But 202 was fine, but didn't have WIFI. Pretty much what you need to do is use one that doesn't use any BFS (MLIGN, myHero) and you'll be fine.
Not sure if this is the same problem or not?
I replaced the MB in my G1 and now it fails to wake the screen up - SOMETIMES. No real rhyme or reason to it that I have found. I suspect that it's related to the MB and not any specific ROM. On reboot, sometimes I get the G1 logo for a few seconds, and then it goes black until reaching the boot screen. Other times it will go white on reboot, or white with black stripes. Sometimes, I can get it to wake up by pressing power then home several times, but that hasn't worked in a few days.
I'm preventing it from going to sleep, seems to work but it killer on my battery. Posting here to see if anyone else has run into this, and if there are any known fixes.
This only happens to me when I had stericsons LS. This may be a thing of the past because now I just stick with cyans rom. Last night I tried the 10 mb hack and had the issue again. Developer was already aware and working on the kernels though.
I have had my G1 for about 6 months. I flashed a custom ROM few months ago, everything has worked fine. Few days ago something weird started happening. The screen will NOT light up when the phone is closed, doesn't matter what buttons I press or what I do, the screen will stay black. The only time the screen turns on is when I open the phone. When the screen is on and the phone is open and I close the phone, the screen will go dark and shut off...
I have tried hard reset that didnt help. Next think i would try is to format the phone and load up new OS.
Before I do that I would like to know if this happened to anyone else. Also I would like to know if this is hardware related or OS related.
Please help me!
Its still in warranty right? flash the stock rom and send it back, tell them you did a hard reset to try and fix it but it didn't work (explains away why your data isn't on the phone)
Sounds like a hardware issue. As Newbie said, reflash the stock ROM, if that doesn't fix it take it back to Tmo (assuming you're on a contract).
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.