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.
I've checked and some says that I need to replace it but as I dont have much cash I wanna make sure that my screen needs replacing.
My bro got me an old G1. And its screen starts to behave quite odd recently. Sometimes I cant touch anything, or it just keeps pressing itself. (In cases like when I'm typing it will types it self bunch of letters in the mid and bottom lines (the asd-zxc lines) And when things happen I have to turn off the screen and wake it again. Problem resolved temporarily.
And it happens daily, if not nearly all day
So please anyone that got experiences or advices please tell me is it the screen's fault? And should I replace it?
Thank you for your attention!
P.S: I know that nothing can live forever...
I had similar problems. It happened when my battery was low... Im pretty sure it was just my ROM being buggy.
Thank you for responding
But I dont think so. I changed to dwang's rom (donut as I remember) and it still were "lagged" like that so I flash back to CM 6.1.2. So I dont think that's the roms' fault.
And about the battery... Im not sure. Sometimes when the batts gets lower I got better responds .. quite unpredictable
And what did you do?
I attempted to install a new ROM, failed. Tried to recover my back up, and now I'm learning to fastboot. :/
After the install failed, and I had a fresh instal of my ROM running, it seemed to stop.
I also noticed that it only did it when I had the keyboard opened.
Aww I'm not lucky as you are.
Since I've installed 4 roms but none of them fixes it. I'm thinking of changing the radio Im not sure though...
Just see what other people have to say
Still no clue...
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.
I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.
can you take a picture from the location of the 2 capasitors and the types of it
Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.