I've been in this rooting game since it began, and I never had a major issue.
Unfortunately now I have come across one, and I believe it may be a Hardware problem, but I'm not entirely sure.
At any rate, the other day I'm on the computer the phone is charging through the usb cable, and while im using it, the back light goes out. I think this is weird.
I lock, and unlock it and everything is back to normal, but when I slid the screen back the back light went out again.
And the home button didn't work either, I doubt this was a problem with Cyan's ROM, or a theme. I do have the new lockscreen but I never had an issue.
So from Cyan's 4.0.4 I upgrade to the experimental version and the problem persists, the back light won't turn on unless the screen is slid up/open (Also, I have no lock screen!? wtf?).
Afterwards I decide to go back to 4.0.4 and even when my phone boots up the back light wont turn on unless the phone is open/screen is slid up. So obviously it seems like a hardware issue.
Anyone else have this problem? or any thoughts about it?
I'm on Cyan's 4.0.4 - no theme
26I Radio and H's SPL.
reset your phone. hit call,menu and power at the same time. then let us know how everything works.
Funny things happen when you don't wipe, make a nandroid backup of your current setup and than wipe and flash again and see if it persits
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
igloo77055 said:
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
Click to expand...
Click to collapse
This is a hardware problem. Happened to me too. Been trying to find a solution, but the fact that it still has the same backlight problems when the phone is booting (On the T-mobile G1 screen) shows that's it's way beyond the ROM.
Mine even has the same problems on the recovery screen. Time to find a new G1. If you find a solution, lemmie know. I've been looking for one.
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 have had my G1 for about 6 months. I flashed a custom ROM few months ago, everything has worked fine. Few days ago something weird started happening. The screen will NOT light up when the phone is closed, doesn't matter what buttons I press or what I do, the screen will stay black. The only time the screen turns on is when I open the phone. When the screen is on and the phone is open and I close the phone, the screen will go dark and shut off...
I have tried hard reset that didnt help. Next think i would try is to format the phone and load up new OS.
Before I do that I would like to know if this happened to anyone else. Also I would like to know if this is hardware related or OS related.
Please help me!
Its still in warranty right? flash the stock rom and send it back, tell them you did a hard reset to try and fix it but it didn't work (explains away why your data isn't on the phone)
Sounds like a hardware issue. As Newbie said, reflash the stock ROM, if that doesn't fix it take it back to Tmo (assuming you're on a contract).
Does anyone else have a problem with holding down the power button?
When I hold down the button my Nexus only registers it as pressing it and letting go and usually just turns off the screen. It's quite frustrating when I need to turn off my N1 or set airplane mode, and usually takes half a dozen tries before it actually registers as holding down the button and not just pressing it.
I fear it may be a hardware issue and I will have to return it.
I got the same issue. Not sure if it is soft- or hardware related. Also having problem with waking up. Works well with the track ball so I guess it's the hardware.
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
andythefan said:
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
Click to expand...
Click to collapse
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
I will say that I've been using a Desire2Nexus port ROM and it definitely happens more with this ROM than the CM-based ROMs, but that could also be due to the laggy/sluggishness of SenseUI.
I was seeing the same problem in both ROMs of recent generation though. So my gut tells me it's a hardware issue. Flashing to stock and testing it out will be a dead giveaway, though.
HTC has historically been pretty good about replacing known hardware malfunctions. I also bought SquareTrade coverage just in case, though, so I will be getting my money back one way or another.
maxawesome said:
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
Click to expand...
Click to collapse
I've wiped and flashed the last stable CM version. The issue persists. Also, it happens when I'm in recovery as well, so I'm afraid it may be a hardware related issue.
Can I still send this in for replacement if the bootloader is unlocked? When I be charged repairs in that regard?
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?
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...