My Fiancee's G1 wont turn on at all,No T-mobile slpash screen or nothing.LED lights turn on and Call,Home,Back and Power buttons light up except for the screen itself her phone wasnt rooted,I have never experienced this before.
Can someone please help?
the phone is not turning on via the power(end) button???
try pressing the camera button and keeping it pressed, also press the power button to enter into hboot mode...if u succeed in entering that mode, the phone is fine, or else it could be bricked.
Try Home+Power see if you can get into recovery mode.
If you can wipe cache data.
Hi everyone, hope it's okay to post this here since this Question relates to mine.
I'm having a trouble like this except instead it's like my backlight went out, it was working fine until my alarm on my phone went off and when I went to turn it off I had to take the battery out of my phone because the screen wasn't pulling up. It flashed basically, so when I put the battery in the screen came on but no backlight. Could it be due to Cyanogen? I'm restoring my backup to see what else could I try?
could u be a bit more specific?phone is working??? calls etc???or are u stuck somewhere????
As I said, the screen came on but no backlight. The phone works fine except for the backlight I'm trying to figure out if it's a hardware issue or a software issue. I don't know how much more specific I can get really except that the only way to see the screen is to hold it at a certain angle so the light hits it just right.
Related
Tonight my G1 displayed some very odd behavior. It was running normally and I pressed the power button to make it sleep and I set it aside. About half an hour later I picked it up and tried to turn it on by pressing menu. The phone gave no response other than lighting up the five buttons on the bottom. I tried sliding the keyboard out and the keyboard lit up as well, but the display remained black. Plugging it in via USB to my computer did absolutely nothing (no sounds, no notification light, etc.), and I got the same result when I plugged it into the charger. I finally decided to take the battery out in order to turn the phone off, and then put it back in and pressed the power button. The phone booted up normally, and now everything seems to be working in proper order. I am slightly concerned, however, as I have never had this behavior in the year that I have owned my G1. I am running Cyanogen 4.1.999 with the Hard SPL boot loader. I am unsure whether this behavior has anything to do with the mod and I am wondering if anyone else has experienced anything similar. I do realize that if my phone is bricked it is my fault, and I want to determine if this was simply a freak accident or if I need to do something differently with the phone.
first of all if your phone was bricked you wouldn't be able to use it. as for your problem it doesnt sound too serious so if i were you i wouldn't worry about it. but if it does happen again reflash your phone and if it happens after that, pitch it to cyanogen to see if there is a problem with the rom.
I do realize that it isn't bricked now, but I am worried that this behavior could mean that I am pushing the phone too hard. I am mostly curious as to whether or not anyone else has experienced similar behavior from their G1.
Turn off compatibility mode in spare parts.
don't worry this is a common problen It happens to me all the time any hero I flash plays nice for about a day. and then boom no problems with cyan!
I had the same problem, but unfortunately my G1 is still not working properly.
In the morning, turning off the alarm I left the phone for 5 minutes. An attempt to turn it on did not work: there was no reaction on display, although the buttons were lighting up. I restarted phone taking the battery out and now I have following:
- keyboard fully closed: no reaction/black display, buttons are lighted up
- keyboard open: I can do everything: change ROM/make call/write messages/Internet/GPS/... - everything what is possible to do with rooted G1
- keyboard partially open (visible only lowest row with such buttons as ALT, SHIFT, SPACE): similar to 'open' but with changed orientation
Can anyone help/advise? Did almost everything: ROM changed, full wipe, recovery
Hey, I have been given a phone off a friend to fix but it wont turn on. Booting normally, I get a vibration and then the backlight comes on but i cannot see anything. When i try to boot into the bootloader by holding the camera button and powering it on, the backlight comes on but nothing else. I cannot see the bootloader. Under both circumstances, I cannot turn the phone off. I have to pull the battery to turn it off.
Does anyone have any suggestions about a possible fix? Thanks
Havie you tried send when trying to enter bootloader? If it resets then you can still get to bootloader. If not, your friend has soft bricked and only way is to JTAG which takes strong hardware knowledge and steady hands.
-------------------------------------
Sent via the XDA Tapatalk App
ok im having the exact same problem. actually i thought it was a battery problem so i spent 77$ on a 3700 mAh new batter i guess tripple life... and got it yesterday booted gave same problems. black screen where T-Mobile should be yet the rom loads with scribble screen meaning u see part but it looks like the pixels are messed up. so actually decided to resort to what someone told me a Factory Reset so Pressing Camera + Power i got a Black Backlight screen yet wont show... and I cant turn it off without Taking out the Battery this has become a issue after installing cyanogen 5.0.7 T5... since then i Re-rom'd to superbad 1.2.5 same problem screen scribbles and stops im thinking did I fry it i dont even know how to google my problem because its pretty unique it isnt a battery issue its something in the hardware ... or am I wrong please send us some feedback... ill keep this thread in mind
Sorry, what do you mean by 'send'. I am a complete noob when it comes to G1's. I have worked out i can shut off the phone by holding call + menu + end but thats it. I still cannot see anything at all on the screen. I still only get a vibration on boot. How would I know if the boot has been sucessful but i simply cannot see?
Could the flex ribbon cable be nackered?
Well today for some reason, my hero isn't working anymore. I had not changed any settings nor flashed anything or even charged it wrong. The symptoms are that everything appears to be working except the screen. A battery pull makes it so the phone vibrates when its turned on, and the buttons at the bottom even light up when used. I think its a screen problem because if not for that, the phone would work fine. What would cause this and is there any way I can get this fixed?
I can possibly help.
Are you rooted? Do you have a custom recovery and if so what version? Is your bootloader s-off?
If your answer is no to all the above
Try holding the volume down and press the power button. Does it boot into the bootloader?
Are you stock?
If so there should be an option for recovery. Press it.
Let me know any results. I'll post more info as needed.
Yeah sorry, I am rooted with the latest amon_ra (3.5 i think) however, even if i boot up with the volume button down, the screen doesnt show anything. I am fairly certtain this is a hardware issue... I might as well just break down and pay sprint the $35
Yea its bricked then. If you can get to the bootloader we couldve fixed it.
Hey guys, im having a bit of a problem. My phone is shuting off on itself.
Everytime i turn it on, it boots up no problem, but when i hit the power button to turn the screen off, when i want to turn the screen on again by pressing the power button, the screen just goes deep blue, and turns off.
I haven't change anything on it for quite a few months now, so i'm not sure why this is happening. Im on Viper 3.5 i think or 3.7, using faux123 kernel, dont remember which version, but an old one with which i never had any troubles... rooted, s-on
Any ideas?
Thanks!
Coldsun15
PD: Logcat in the .rar file...was too big for .txt
Really?? No one??
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Any ideas welcome
Edit: Attaching new logcats...
coldsun15 said:
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Click to expand...
Click to collapse
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
fenstre said:
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
Click to expand...
Click to collapse
Yeah, i thought about it being hardware but something is off... i mean, if it where the power button, then i shouldnt be able to turn it on easily, or it wouldnt turn off the screen properly, nor would it just start working alright for a couple of days... plus, it didnt recieve any hits or anything during, before or after the problem.
I also thought it could be the screen, but when its on, it works perfectly, as on the first day...
But yeah, I'm not taking hardware problem out of the table...just seems unlikely to me...
Thanks for your answer!
Coldsun15
Edit: also, I just found out it doesnt actually restart...screen just turns dark blue, then it powers the screen off and it wont turn on when pressing power... but i know its on, because i can still hear notification sounds of incoming messages...
Edit2: Just tried same but instead of using power button, i used logo2sleep and home2wake kernel options, and did the on/off with them, and same result...dark blue screen then off and not turning on... so it cant be power button
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!