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.
Any help would be greatly appreciated.
I have a launch day Nexus One running CM5.0.5.3, the OC/UV kernel, and the EPE54B radio.
It has all been running great until today. I took it out of my pocket and it was warm (not hot) to the touch. I noticed the screen was blank but the buttons along the bottom were illuminated. I tried resetting it (power+volume down+trackball) and that didn't do anything, so I pulled the battery. When I rebooted it, it seemed to take a longer than usual time at the initial boot screen, and then went to the animated screen. It stayed on the animated screen for quite a while and then froze. It's stuck on the X mid-formation.
I then booted into the bootloader (which reacts like normal) and went into recovery. I re-flashed CM5.0.5.3, no effect. I wiped cache and system and re-flashed. Nothing. I did it again, and it finally booted up but I could only select things with the scrollball. The volume rocker worked fine, but the touchscreen is completely non responsive.
If I let it sit at the boot screen for a while it will go black eventually and time out.
I'm at a loss. I'm in the process of downloading a stock ROM and am going to flash it next. Anyone have any suggestions? My bootloader is (obviously) unlocked, so I'm worried about warranty work
Update: Just got it to boot (with the stock ROM) and I've got a warning screen saying:
Sorry!
Process system is not
responding.
[Force close] [Wait]
Any ideas?
Reflash CM 5.0.5.3 and then post back
Ok, re-downloading now.
Just flash in recovery?
Flashed in recovery (after wiping)
The phone stays on the stationary initial boot screen (four bars) for about a minute and a half and then goes to the animated cyan X. It stays there booting for probably two minutes before stopping mid-animation. If you let it sit there for a while the screen will time-out, which you can bring back with the power button. Sometimes when you hit the volume rocker you can hear the beep beep but nothing shows on the screen.
What the hell is wrong with my phone?
After an obscenely long time I got it to boot up.
Touchscreen is not responding, trackball is not responding, I have a question mark on the battery indicator, and no service.
I can't unlock the screen because of the non-functioning touchscreen. Live wallpaper is running great, it makes the sound when USB debugging is connected, it just won't react to any input.
I can, however, establish an ADB connection. It shows up on the device list and a remount succeeded.
Would reflashing the radio be of any benefit?
Dang the touch screen is unresponsive? I'm not an expert, but i'll try to give you some ideas.
I had some trouble once and I used settings-privacy then erased everything from within the OS. Then I reported to the screen just before going into recover and hit clear storage. Then went into recovery and wiped everything that I could. After that, flash the Rom that you want.
I've done a full wipe to no avail.
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Scaaaary!! But hey, it happens. I would also try wiping for EXT on the SD card if you have been using apps2sd.....May not hurt, mights well try everything.....
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
liam.lah said:
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Click to expand...
Click to collapse
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
mortzz said:
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
Click to expand...
Click to collapse
Many people have posted that they got a replacement even with an unlocked bootloader. One guy I heard said they charged him $55.
Either way, you can probably get a replacement.
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
Hi, I have an AT&T Nexus One, running FRF85B currently. As of lately, even before update I noticed my home and search button stopped working. The haptic feedback responds when I touch them but they don't do anything. I searched the forums so please don't flame me if I missed a thread. Much thanks to anyone that can help!
P.S. I soft reset the phone a few times and also have reflashed
can you post a logcat of what happens when you press the buttons? and also try wiping cache and dalvik cache
Try to wipe and reflash and post logcat
Gfs stock phone just started doing this. Will try to get some kind of logs... A reset wouldn't make her very happy, fffuuuu
http://www.google.com/support/forum/p/android/thread?tid=3c3ae39887a83bbc&hl=en
&
http://code.google.com/p/android/issues/detail?id=8503
according to this we arent the only ones. it looks like a factory reset can fix the problem, but some on the link above re-encountered the problem weeks later.
surprised XDA hasnt run into this before...
in addition to home/search buttons haptic'in but not doing anything, slide lock screen goes away and the phones cannot receive calls.
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
'Programmable'? How can I set Search to ixquick?
Quantumstate said:
'Programmable'? How can I set Search to ixquick?
Click to expand...
Click to collapse
The app's manifest needs to mention that it can handle that event
britoso said:
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
Click to expand...
Click to collapse
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
turbosix said:
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
Click to expand...
Click to collapse
This is exactly what is happening to me. I'm going to wipe now.
god damn it. this **** just started happening again... n1 has been running the OTA stock GB 2.3.3...
we ended up getting HTC to warranty the phone and everything was fine until this morning..
any help?
same
So i started having this problem about 3 weeks ago as well right after i flashed CM7's newest experimental build. first thing I witnessed was not being able to receive calls. I figured that this was a problem with CM7 and flashed modaco's r26, after a full wipe, when it just came out a few days ago. After a day, i got the problem with the lock screen and the home and search buttons not working. I again thought this was a problem with gingerbread for some reason and flashed MIUI Mod Rodriguez style rom, again full wipe. I had restored everything through titanium backup and other forms of recovery and within about 60 minutes my home button and search keys stopped working.
So I finally figured that it was some settings that I must have adjusted and carried through numerous different ROMs that caused the problems. So next time around I didn't restore anything, running on MIUI mod, and didn't restore anything for the remainder of the day to see what happened. Low and behold, after a reset the problem came back. One other complication is that the phone will always forget my google account and i'll have to re-connect it. Then I realize that the home key doesn't work. So even not importing anything from my old Rom's with a clean wipe didn't get rid of it.
I still get haptic feedback, but the buttons just don't do anything. I changed the setting for how home and search respond in both scenarios and can't get any response either. I flashed back to an old version now and so far i'm alright. But if someone can figure out why this is happening that would be awesome.
For the other people who are having this problem, when you're doing a clean wipe are you then restoring things back via titanium back up or otherwise? and when did you first start to experience these problems?
Istarted having this same problem today. I recently flashed over to cm7 rc2 and then the same thing happened. It seems like after I do a titanium backup and then change a setting it will reset to the cm boot screen and when it comes back there's no home screen or search buttons. All the same issues. Haptic feedback works but nothing happens. I'm on an evo btw.
Same thing occuring for me after flashing CM7. Reverted back to Miui, but so far no luck in fixing this. Numerous factory resets have yet to resolve as well. This is pretty frustrating...
Having this issue as well on CM7. DEFINITELY Titanium related.
I had this problem too. I just had to shut down the phone then leave it for about 10-15 minutes then turn it on again. Everything should be fine again. ^^
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.