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 just got a replacement G1 and I did the one touch root and every rom i loaded kept having freezing problems, even stable 1.6 roms which i ran on my old G1. I even tried unrooting then re rooting via one touch and it just keeps freezing up randomly. Does anyone have any idea why, and a way to fix this?
When exactly does it freeze, after setup or boot?
If one of the above it's just loading and background services are running while sd is being setup too.
Mostly when i am trying to run an app or something like that. If i am switching from screen to screen it is fine. But when i go to like use a message or something. It sometimes freezes, other times it doesnt.
Update: When my phone is plugged in to a power source it has no problems at all. But once i take it off it is a matter of minuets before it freezes. Mainly when I go to the message app and then hit end. I am running the SuperEclair_XxKOLOHExX_v2.3 rom.
Be sure that you are running the latest radio and engineering SPL.
radio:2.22.19.26I
and i am running the danger SPL(1.33.2005) is that the same as the Eng. one?
ttyrawa said:
radio:2.22.19.26I
and i am running the danger SPL(1.33.2005) is that the same as the Eng. one?
Click to expand...
Click to collapse
Yes, Death SPL is fine....you could update your radio to the newest one and not worry about bricking your phone. Though I don't think its going to fix your freezing when off charger problems....it sounds like you have a very messed up phone...I would have called Tmobile as soon as I found out it was doing that and sent it back to get another replacement.
But when i run the original g1 rom(non rooted) it works fine
Hey, I'm having some trouble with my ROM'd HTC Hero, running RegawMOD. She was running beautifully for a few weeks before today, where, after her battery dying, she refused to boot, entering an infinite loop cycle. I don't have a recent Nandroid so I'd like to avoid backing her up, but so far I can't get her to run properly.
Does anybody have suggestions? Could this be due to an application I was running? Her battery was dying unusually quickly, if that helps. And I recently installed AntPlayer.
Update: I've since attempted to restore my phone to her first available NANDroid backup, still got stuck at the boot screen, even after the boot screen I was using (the Nexus One boot) was replaced with the Hero's original boot. I feel this could be a hardware issue?
HZ.
Have you tried wiping/re-flashing?
If that doesn't work, it could be full memory, bad recovery(based on the nand fail), or bad hardware.
TL;DR: My phone is experiencing a very similar problem to the broken internal SD after Froyo update, except on eclair and is fixed (apparently temporarily) with a factory reset. I'm on Telus, bought the phone from somebody off craigslist and have a return receipt. What should I do?
So for the second time in a few days my Samsung Galaxy S (I9000M from bell, bought on craigslist running on telus) was having problems opening an app so I restarted it. (The first time Market would force close whenever I tried to open it, the second time it was Browser). After the app force closed a few times I did a restart. The first time I restarted it (when Market froze) it went to the lock screen, with the default background (it looked like my data was all wiped). After unlocking the screen, I got a perpetual series of force close messages. This happened each time. I had to do a factory reset and lost all my settings, photos, messages and everything (No backups, of course. Facepalm). Then today I pretty much had it back to the way it was before the reset, and Browser force closes repeatedly on opening. I restart the phone again and this time it only gets to the 'S' animation then goes black/restarts after the animation stops. The capacitive buttons sometimes light up. Similar to the issues from the Froyo update I think, except I didn't update to Froyo. I can get to the 3-button recovery screen and do system reset as well which seems to not help the froyo issue, I think. It's currently working but I'm not sure how long that will last. I'm not pleased about having a phone I have to re-setup every few days. (I'm actually pretty angry...)
Anyway, I have a "Mobile Device Repair and Return Receipt" from the seller from craigslist. It's still under warranty. Anybody else experience this? Can I take it to bell and have it fixed with the documentation I have? What would you suggest I do here?
Has anyone ever ran into a situation where the UI locks up after a boot? I keep searching through threads and can't find anything. I'm not sure if it's something I have installed or if there is actually something wrong with the device. I had a nook previously and never encountered this problem but on the new one I just got (ebay refurb) the problem just keeps coming back.
Basically, it boots just fine and starts to show the Launcher but then the screen goes black and leaves the soft buttons at the bottom. The only way to recover is to shut it down and start it back up.
The funny thing is it doesn't do it all the time... sometimes it boots just fine and never locks up while in the OS... it's only on boot it does this.
I've tried multiple different versions of cm7 and am getting the same thing on all versions. I've tried different kernels and stock speeds and it still happens.
Any help or advice would be appreciated!
Hmmm... well after hours of troubleshooting I think I pinpointed it to beautiful widgets