Hi there,
so here is the situation. We have GG EE glasses which are not booting up. They show bright Glass logo which then goes darker.
The glasses appear only for very short time in device manager - fastboot and ADB does not pick them up. It seems they are not replying (tried USBlyzer to sniff the communication).
I tried also the fastboot cable, still no luck.
Is there any trick to save them?
Thanks!
Hey, I'm in the same situation. We're you able find a fix?
Related
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.
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
vessk0 said:
Hello, I have Z3 Compact D5803. The back (glass cover that is bonded factory) was beginning to lift off in the middle and I put a (micro) droplet of glue. The phone was turned off and the procedure was carried out carefully and without any spill. After a few days, I decided to turn it on, however, did not see anything, tried all possible combinations, but it is not working. When I plug it into the wall charger the display lights up momentarily with the Sony logo, lit red LED and then immediately restarts. This thing is going indefinitely, I have even left it plugged for 24 hours, but it keeps boot looping. Detached rear cover to look inside, everything looks fine, not even a trace of my gluing work.
Any ideas?
Click to expand...
Click to collapse
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Didgesteve said:
Have you tried the hard reset button ?
Look under the flap where you put the sim, next to it is a tiny button hole, press this.
Click to expand...
Click to collapse
Yes, nothing happens...
I can only put it in fastboot mode (blue LED on black screen), while it's connected to the PC.
Well If fastboot works then this shouldn't really be much of a problem , simply fastboot flash any kernel with a custom recovery and flash a ROM. If that doesn't work then you might be facing a hardware issue and the best course of action would be to send it in for repair
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
Can you detect it via ADB? Go to adb ( found in Android SDK ), open command window there and type fastboot devices, something should come up ( Assuming you have the fastboot drivers installed ) You can also use flashtool if you don't have the SDK Installed but install drivers first
vessk0 said:
But there is no way to correctly see it in Windows. Tried to install drivers, but it keeps stay as a "S1Boot Fastboot" device in Windows 10.
Click to expand...
Click to collapse
I think your drivers have not been installed correctly. It is a bit of a hassle in Windows 10 since you need to disable driver signature verification. I successfully installed the drivers from Flashtool after doing this.
i have the same problem but....
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
williamzerner said:
but i cannot start recovery nor fastboot not even download mode ( i think fastboot and download mode are the same) please help me
Click to expand...
Click to collapse
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
M1chiel said:
Either your battery is completely dead or you have a hardware problem. What happens if you try to charge your phone?
Click to expand...
Click to collapse
When i try to charge my phone the phone does the same thing.... means the phone boots upto the sony logo red led glows up and the the phone restats ... this repeats forever unless battery runs out...
Hi folks,
I recently ordered what appeared to be original huawei p9 replacement screen together with metal frame and replaced broken screen. Phone now boots normally, I can also boot to fastboot and recovery, but unfortunately phone doesn't have ADB debugging and OEM unlock turned on.
When phone boots normally, I can get only to the lock screen of "Smart view" or "cover view", so I cant unlock phone or anything else. I tried also with mouse via OTG, no luck...
Anyone have some other idea that I can try? If i could enter settings to turn off cover screen all would be good
Edit: Sry for duplicate thread, please delete this one.
hmmm, i think that u might covered the poximity sensor. a factory reset would solve the problem
Demsar said:
Hi folks,
I recently ordered what appeared to be original huawei p9 replacement screen together with metal frame and replaced broken screen. Phone now boots normally, I can also boot to fastboot and recovery, but unfortunately phone doesn't have ADB debugging and OEM unlock turned on.
When phone boots normally, I can get only to the lock screen of "Smart view" or "cover view", so I cant unlock phone or anything else. I tried also with mouse via OTG, no luck...
Anyone have some other idea that I can try? If i could enter settings to turn off cover screen all would be good
Edit: Sry for duplicate thread, please delete this one.
Click to expand...
Click to collapse
Check your sub board or the flat cable connecting it to main board. Its easy to test it, just turn on your phone without sub board connected and see if you are still stuck in cover mode.
My google glass was not updating on wifi so I tried to use adb and fastboot to force the update. I followed some steps I found online and now my glass is stuck at the "Glass" loading screen. Upon startup it shows the "Glass" screen in blue and/or red then changes back to the regular color. My computer can recognize the device is plugged in but I cant find it in either adb devices or fastboot devices. Any suggestions? I am worried I bricked my device.
Issue Solved by going into fastboot directly by holding camera button when powering device on.
I'm having a similar issue, stuck at the Glass boot screen and unable to get ADB to recognize it (although Windows "sees" it).
Every once in a while I can see the screen that says to swipe forward to start the setup, but then it switches to the Glass screen again.
Anyone have some ideas?
Thanks in advance!
I have a Pixel 4a that I dropped from coffee-table height onto a wooden floor. The phone landed on an edge and broke the internal screen. The outer glass is undamaged.
Initially there were rainbow lines all over the screen, but after abandoning it for a few days, now nothing shows up on the screen at all. Charged it overnight. Nothing. It does make the device a little warm, though. Powering it on produces no signs of life.
When I took it to uBreakiFix they checked for a minute and said since it doesn't respond to charging (no vibration) and doesn't seem to "power on", it probably has a dead motherboard as well.
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
I also put another SIM into the phone and tried calling it, but it goes to voicemail.
Is this phone dead and ready for recycle-grave? Or is there any hope? Help is much appreciated!
Pull it apart. May have loose connectors.
See what visible damage is there.
No visible damage doesn't mean your in the clear but it's a start. Inspect the battery for swelling, a failed Li.
If it starts responding when you use a pencil eraser to gently push and flex the mobo different ways, push on the BGA chipsets, that's clear sign of a mobo solder fracture or broken trace. You can also try this with the phone together by putting pressure on the case at various points... don't go too nuts with it though.
urover said:
However, when connecting it to a Windows laptop, it is reported as "Pixel 4a(5g)" in Settings>Devices, and an "MTP device" shows up in Device Manager.
Since I did not have File-Transfer as the default option for USB, and because ADB was not enabled prior to it breaking, I am left with no real way to test this device.
Click to expand...
Click to collapse
you can do some things booting twrp (fastboot boot twrp.img) for your pixle 4a provided your phone bootloader is unlocked (fastboot flashing unlock vol down once then power to unlock without screen is the command). i can't remember if it wipes the phone or not. adb devices should see the phone once you boot up twrp. you should also be able to access the phone like a usb drive as well. if you are trying to pull data off it. make sure you have the latest google usb drivers installed from their website https://developer.android.com/studio/run/win-usb
this should give you some sort of start. to see if it even is responsive.