Hi everyone ...
I recently disassembled my G1 to fix the touch screen. I acknowledge that I took the phone's fate into my hands when I decided to open it up, but I had done this twice before with no problems whatsoever. If these symptoms sound familiar to you, please let me know if you were able to fix your phone.
I put it back together, and now when I power it on, I get the short vibration that confirms the power-on ... but I get no screen image, no keyboard lights. So when this first happened I pulled the whole thing apart again to be absolutely sure I hooked up all the flex cables and ribbon cables. Yes, everything is connected. Everything. I've triple-checked it now.
What I did next was a couple of tests to see how "awake" or functional the phone actually is behind that blank screen. When I power it on and let it sit a couple minutes, so that I know it has finished booting ....
I CAN:
- boot the phone in normal or recovery mode. both modes produce the blank screen and no key lights.
- view the phone in ADB. (ADB tells me "device" or "recovery" mode)
- execute commands and view files on the phone with ADB shell.
- pull files off the phone with ADB.
- make the LED light up by plugging in the wall charger or USB cable when the phone is off.
I CANNOT:
- make any of the backlit keys turn on by pressing them.
- make the phone receive a call or a text.
- make the LED light up by a missed call, text, or plugging in the charger/USB when the phone is on.
My first impression is that I've done something terrible to the mainboard so the phone is somehow in this "semi-booted" state, where it won't run the screen. Is it possible that a bad cable to the screen could cause this? Thanks so much for your help.
Come on, no one can help me with this? I know I'm not the only one who has taken a G1 apart and met with disappointment.
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 all,
I just installed a new digitzer on my Vivid. Everything went fine, and nothing broke as I was taking apart the phone, or putting it back together.
Now that the phone is back together, however, it is having some problems.
First off, When I try to power the phone on, it vibrates like usual, but then doesn't display anything. The phone then proceeds to enter in to a bootloop and keeps vibrating every couple moments. When plugged in to the computer, the orange light comes on for a few seconds, then turns off. Windows will not recognize the phone. All the while, the screen is completely black, and none of the lights come on for the buttons either.
The phone was working fine before replacing broken digitizer.
The phone is NOT rooted, nor has it ever been. I am running stock ICS.
have tried entering Hboot with no avail.
Any advice?
Thank you!
Can you get into any other modes? Try to get to hboot(hold down power button and volume down) while plugged into computer. Should take it to fastboot.
how long for? I tried holding down for a good 30 seconds...nothing happened other than my orange light turning off
I noticed with mine I had to go with:
Remove battery.
Replace battery
hold vol down + power
few seconds later release power
few seconds later in hboot
YMMV due to repair.
You can also try a knoppix boot disc and some tutorial to see if you can find any sign of life off the phone in dmesg.
hope this helps some.
Sounds like a loose connection. Make sure that you've correctly reconnected all internal connections. Especially the connection under the little door with the void sticker on the screw in the battery compartment. If after verifying all connections are made and proper, the problem persists, I'm sorry to say you may have physically damaged the connectors during disassembly. Please visually inspect all connections for damage. A powerful magnifying glass is recommended.
(I have successfully replaced my digitizer twice, and my LCD panel once on this phone...)
Sent from my HTC Dark Raider using XDA.
I have taken it apart twice, checked all connections, and everything is good. Phone cannot enter any boot mode, and computer still doesn't recognize it. The orange light still only stays on for a few seconds when plugged in, then turns off. The phone then proceeds to keep trying to restart itself, but the screen remains pitch black blank
idk.. get a replacement.?
Hello
Recently i've bought an broken screen Xperia Z, for repair it (i got it like $300 bucks cheaper) and i was ready to buy the screen, but i battery was drained and i could not test it right, when i connected to the charger, it started red light, vibrate, then 3 continuous vibes, read on the internet, OK BATTERY DRAINED, i left it charge THE WHOLE NIGHT, and when i woke up in the morning it was orange (charging), later in the day it was green (charged) but when i disconnect it, it wont turn on anyways, when i connect it to a pc, it goes blue light (wich later i read it was fastboot mode). i read for making a repair with PCC, but it didnt fixed it, then i flashed it with Flashtool, with the latest software (wich had the Sudden death issue fixed) no luck. it wont boot. for it to boot, i have to connect it to PC and with fastboot run "fastboot continue", but most of the time, it reboots and goes redlight and vibrate 3 times then reboot, so i press the power button and it enters fastboot mode (if connected to PC) or loads charging if connected to wall charger, but it reboots again and goes to redlight vibrate reboot, sometimes it stay charging or in fastboot mode, but only "works" if connected in the USB.
when it stays in fastboot, i do "fastboot continue" and it loads the OS, and it works (well, the things i can do with a broken LCD/Touchscreen, i put my sim card and could call it, and it works, but i cant pick up the call). i can explore the phone memory etc. but if it reboots or if i disconnect the USB, it will almost always turn off. i havn't found a solution (or idea) of what can happen, i dont know if its normal since it has broken lcd/touchscreen or it definitely have a huge problem,
any ideas?
thanks in advance!
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Click to expand...
Click to collapse
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
blackknigt said:
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
Click to expand...
Click to collapse
Correct me if i am wrong but does the xperia z not support usg-otg and mhl? You could rig the phone up to the tv with a mhl-hdmi cable and maybe use a usb mouse to select things, and enable usb debugging?
Sent from my Nexus 7 using Tapatalk 4
Nice idea, now i need to find who in this country (DR) have that adapter
i ordered the LCD screen assembly for repair it myself, but im still concerned about this, as i dont know if it will boot up anyways
my phone right now isnt booting. but as i cant see images i dont know what is it showing.
i noticed the touch screen is working indeed. (when booted, it plays sounds when tapping)
i will wait till the lcd assembly arrives. any ways, any other ideas on what may happen?
the ex-owner of the phone said it started like that when it fell and broke the lcd.
OK now, i've installed the LCD, the phone works, its ON, BUT the Volume Up button and the Power Button does not work when the phone is ON,
the Vol UP button seems always be pressed cause when i press the power button for some seconds, the Phone restarts and not power off or lock/unlock
Service tests: None of these buttons where recognized.
any ideas on any hardware fixes i could try?
I FIXED IT!!
dissasembled the phone, took out the side button flex cable and the volume up button on the flex was dirty, so it was having a false contact. (wich made the button always be pressed)
I took out the yellow tape and cleaned with alcohol and a needle (its so freakin small) and put the tape again and assembled the phone and voila! IT WORKS OK!!
Yes the vol up button pressed means u get fastboot. Now that you fixed the problem and repaired the phone enjoy. Btw nice job getting it up and running.
[email protected] Z
So my HTC ran out of battery last night, and I left it overnight to charge (red light was showing up).
So I turn it on this morning, and nothing happens. I unplug it from charger and red light is still on, and when I held down powerbutton the home and back buttons would blink, but phone would not come on.
So I read online and tried the home+vol button trick under a bright light and the red light did go away, but nothing else happened.
Now when I press power button nothing happens, not even the home/back button come up.
When I plug it in to the computer I see a driver for QHUSB_DLOAD failing to load. And if I hold down power button and volume while connected to PC, I can hear it "unplugging and replugging" noise from pc.
So is my phone bricked? This was NOT rooted, it was simply the stock device.
I really just want the pictures I have on there, is there any way to get that data back?
QHUSB_DLOAD is related to the boot partition of your phone and is an extremely tricky driver to find. If, for whatever reason, that driver is buggered, your phone may be bricked. As you haven't rooted there really isn't much you can do past try a USB jig or shine a light at the light sensor (two black circles on the front) whilst you try and turn it on. On the bright side though, you should be able to get a relatively easy replacement.
postfatal said:
QHUSB_DLOAD is related to the boot partition of your phone and is an extremely tricky driver to find. If, for whatever reason, that driver is buggered, your phone may be bricked. As you haven't rooted there really isn't much you can do past try a USB jig or shine a light at the light sensor (two black circles on the front) whilst you try and turn it on. On the bright side though, you should be able to get a relatively easy replacement.
Click to expand...
Click to collapse
Where can I get a USB jig for a tmobile htc one?
My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.
One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.
Maybe you have destroyed a lil cable or something.