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.
Well heres the story. I flashed cyanogen 6.0 and all was great,fast,smooth,perfect... Then it all went downhill. The backlight cut out. After wiping,reflashing,doing everything possible as far as that it was still the same.
I soon figured out that if i lock my phone while it was closed, then slid it open and hit menu the backlight would turn on, but it will not work when its not slid open at all.
Problem #2
As i have been dealing with the first problem and i dont have alot of time to fix it because of work and all, it grew even worse. Now when i do what i was doing to get the backlight to come on, The phone will randomly freeze/backlight wont come on at all/ Screen wont even come on.
When i turn on the phone sometimes the screen wont even come on but the backlight will and it wont get anywhere."blank lit black screen no tmobile g1 logo"
This also happens when i go to recovery using home+power. I remedy that by taking out the battery and starting the phone till it works.
Could someone please help me out here i dont really have to much to spend on a new phone and it would be great if i can get this one going like it should again.
you need to wipe before reinstall
if you have armonR, you wipe everything the wipe menu and flash the rom and the flash gapp-3
ive done that many times, hasnt solved anything. i dont know whats going on..getting to the point where i might just break down and get a htc hd2 and put android on it
Try flashing the Defanged Base (which you can find on the cyanogen wiki) then flash the Rom again.
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
tank65 said:
to be honest it was time for an upgrade anyways, now i have the samsung vibrant. Its awesome. Thank you for the help anyways though.
Click to expand...
Click to collapse
You lucky f***! How are you liking it? I was thinking about getting one soon but i havent talked to anyone with one. Is there anything you dont like about it?
i currently have a htc touch pro -mighty rom(sprint) and a while ago i once screwed the Touch Screen Digitizer so i bought another one. i just bought a used hero and the screen looks like it is in excellent condition, although i cannot swipe anything on the screen (had a user name and password lock when i got it and so i wiped it) after wiping at the very end i watched as it flashed a message really fast something about screen locked. when i see windows or whatever it is i push menu twice and it appears to unlock the phone as power save mode is all that i can see otherwise so now since i can see the icons but cannot touch anything only the buttons work, my question , is the screen broken? i click the talk button and i get a "sorry , the process android.process.acore has stopped unexpectedly.please try again." i was going to try and install Aloysius 1.0 v2 to see if the talk would work then although it seems alot more difficult to install a custom rom then the touch pro. i tried to find a Android Rooting in 1-click (limited time only… until it gets patched) to no avail
thank for any help
Try re-running the official RUU via your PC. See this thread to download it (scroll down to post #2 for the RUU): http://forum.xda-developers.com/showthread.php?t=694572
Don't worry about following all those rooting steps in the first long post #1. Just scroll down to post #2 and download the .5 RUU file, then run it from your PC with the phone plugged into USB.
It will completely wipe the phone and revert it back to factory stock settings. If your touch screen is still broken/messed up after this, then yes there's something wrong with the screen and you should take the phone back or replace it or whatever.
take it into sprint. hell you may even luck out and get an evo or epic out of it. i hear they are trying to push those phones on customers.
sorry i did not mention that i bought it at a swap meet for $30 and the phone seemed locked and said too many password attempts and the touch never worked , so i wiped it. i noticed on the side of the screen by the voulme controls , looks like some tweeker tried to maybe bull the battery out and did not know how to open the back.lol and tried to pry in that area a kinda bent the shiny piece slightly below the - vol button and cracked that chrome plated piece that seems to be inbetween the screen and the back case. i will still try the RUU and check it out, i never did try to replace the digitizer on the touch since the walkthrough seemed too detailed. i wounder about the hero.
trying to reset using RUU although says, error 170 usb i tried to install HTC sync can cant connect with it either. i dont understand how to properly install the drivers i suppose.
any advise
Does it just have the white HTC screen. And you can use all hard buttons but nothing else???
If so its because your phone was rooted and then someone did a factory reset. It happened to mine. Its a way of them locking you out of your phone after rooting.. I ran the ruu back to 2.1 and then rerooted it.
Try this RUU..
http://www.4shared.com/file/2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
Also you just download the htc sync here..
http://www.htc.com/us/support/hero-sprint/downloads/
Jus10o said:
Does it just have the white HTC screen. And you can use all hard buttons but nothing else???
http://www.htc.com/us/support/hero-sprint/downloads/
Click to expand...
Click to collapse
no the OS seems to be functioning fine , except for everytime i push send it get the "sorry! the process android.process.acore has stopped unexpectedly. please try again"
so i tried to power up holding on to vol + and doing the RUU as well as having the phone as normal as can be and running RUU and i get
error(170) usb connection error
rom update utility cannot connect to your phone.
i installed the file HTC_Sync_2.0.40.exe and ran RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe when told powered the phone and clicked next and always get the 170usb error. i still am guessing that the drivers are not installed properly as when i plug in the phone i dont hear the normal usb sound made by the pc. also i never noted that i dont have the offical usb sync cable i have 2 of them , one is shape the same as the area to insert it on the hero, it is the htc touch pro cable . and the other usb cable is the basic one that works for alot of stuff that it fits into, except for motorola`s cell phones to charge them.lol
heeeeeelp
Bringing back more old threads
I am having this exact problem with an HTC Hero. I started before it had ever been rooted. I have rooted, loaded custom roms, wiped everything, ran two diff RUUs, and replaced the digitizer.
If I boot the phone to the HBoot, at the top of the screen it says TOUCH PANEL-fail.
Wondering if it is hardware or software at this point. I had it working earlier today somehow after doing a full wipe, but when i reactivated the phone and started dialing a number to test it it froze up. Rebooted and it was back to the same problem.
I'm new to the forum as a member but have been reading for a while. Well, I successfully flashed my ROM to Serendipity 6.4. Really dig it...except for the fact that I couldn't overvolt it out of the box. It stated that my kernel wasn't compatible. I think I had 2.1 or something like that. So I tried to flash the kernel to 4.1 and everything seemed to be going good and it stated that it was successful until the reboot. It won't boot bast the AT&T splash screen, well it does, but after that there is a thin blue line and just stays there. I've gone through all of the key combinations and I can't get it to mount in any way whatsoever. Battery in, battery out, usb cable in, out. Volume in, up, down, etc...
Odin3 won't recognize it, Windows 7 does for a split sec, then the phone will reboot, over and over...
Did I completely brick it? I should have just left Serendipity just the way it was without trying to get to greedy. This is my replacement phone that I got a tad over a month ago. Think I may blame it on kies and tell them to send me a warranty replacement without paying the deductible, which is stupidly high.
Thanks for the feed back. Your tutorials have been great for the most part.
If the screen comes on your not bricked. Might take some maneuvering to get it in dl mode but when you do your golden. I had my win7 lappy stop recognizing my phone for sone reason, no mattrr what usb port i used, so I had to use a vista computer. A jig should work to get you in download. Once your there you just have to get Odin to recognize your phone which might take using different usb ports or a different cable. Do you know what bootloaders you had? Because i9000 uses a different button configuration for download mode then the i897
Sent from my I897 using XDA App
To be honest, no, I have no idea what boot loader I had/have. As far as using a different computer using anything different that 7, that may be a no go. Anything with Vista on it would have been reformatted or thrown out the window. I might have a PC that has XP on it but that may be a stretch. You make it sound somewhat comforting that it hits the ATT splash screen.
I've been overclocking PC's for the longest time and, believe it or not I work IT. Modding phones, which in this case shouldn't be much different, this one has me boggled. I've flashed ROM on a motherboard a million times...so how much different could this be?
I'll work on it a bit tomorrow and see what results I can come up with, with some help hopefully. If I can't get Windows to recognize, it seems a bit disparaging.
BTW, I have and I897.
i was wondering how check the bootloaders too. Because a friend want to change rom and he dosent know which bootloader he has.
Did I upgrade a kernel from one version to the other? I was on 2,XXX to 4.1?
What would you guys recommend so that I don't make the same mistake twice?
Of course I want the latest and greatest but I want to make sure it's stable.
Darkuso said:
i was wondering how check the bootloaders too. Because a friend want to change rom and he dosent know which bootloader he has.
Click to expand...
Click to collapse
White At&t screen is I897 boot loader. Black I9000 screen is I9000 boot loader.
Sent from my SGH-I897 using XDA App
If your PC recognizes it for a split second, use ADB to get into download mode, then use Odin to get back to stock.
could be the usb drivers are not up to per! Try installing kies mini
I indeed have kies mini installed and as a matter of fact I just updated it a few days ago.
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
rina__anir said:
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
Click to expand...
Click to collapse
If your warranty is still valid take it to service
donkeykong1 said:
If your warranty is still valid take it to service
Click to expand...
Click to collapse
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
rina__anir said:
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
Click to expand...
Click to collapse
Did you try factory reset from bootloader?
donkeykong1 said:
Did you try factory reset from bootloader?
Click to expand...
Click to collapse
Yes, I did. It flashed to the screen with 2 green arrows in a circle and 1 downward green arrow with a progress bar at the bottom but nothing happens during this period. I left the phone like that for about 30 mins just to see if anything would happen and nothing did.