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.
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
Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Rooted?
You mention in the title that the phone is rooted. To be able to discount hardware errors, have you tried flashing a factory image to set it back to stock? If the same problems continue, then I suggest that you return it to Google. I did this myself when the back of my N6 started to peel and the process was painless, since they send you the new phone before you return the old one, so you lose no airtime.
saraddictive said:
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Click to expand...
Click to collapse
Yes, as mentioned, flash a factory image to rule out any software issues. However, it is most likely hardware failure. Especially the camera fault. I've noticed this is becoming a rather common issue lately. So, you should probably RMA again.
Thanks guys. I was just concerned as I unlocked the bootloader and rooted the phone almost immediately after I got it. If I try to RMA it, they won't cry foul over a re-locked boot loader,will they?
Also,I have a feeling this might be an OTA that is acting up. It appears that loads of people have had issues after installing an ota (I did this before unlocking and rooting) so I'm going to try to flash a factory image. Thanks guys
Hello everyone,
as an update, I did exactly as dahawthorne and evolution_tech said, and re-flashed a factory image. However, i found it extremely strange that both my nexus 6s were experiencing the same issue so i did a little research.
Turns out, many users from 5.1 have been experiencing issues with changing their dpi in android 5.1 and above. Because I'm not all that familiar with build.prop and using adb shell (tried using it once, it wouldnt work properly so i just gave up), im not going to bother changing my dpi and it works all fine and good now.
To anyone else experiencing the same issue, check this page out: http://forum.xda-developers.com/nexus-6/general/dpi-conflicts-lmy47e-t3061261.
Cheers
Yep, well known issue.
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)