For the last week I've been forced to a life without my G1. This is the situation:
My phone wont boot. Not normally, not into safe mode (Menu+Power), not into Recovery Mode (Home+Power), not into the bootloader (Camera+Power). Whichever I try it just gives me a buzz and a black screen with backlight on. To power off I have to remove the battery.
Is there a way to bring this device back to life? Any hints are welcome!
Background:
My phone is bought from the US on Ebay (I live in Sweden, Europe) in November. It is not rooted (even if I have thought about rooting it for quite a while), but unlocked and set free from T-mo.
Trouble started when I inserted a new 8GB SD and the phone rang at the exact same time. After that, Android became extremely slow and a touch on the display took several seconds to process. Reboot didn't help, neither did safe mode. Tried with and without SD and/or SIM.
I managed to boot into recovery mode (Home+Power), but couldn't bring up any menu. I had to take out the battery to power off and after that I couldn't boot at all any more (yes, I did put the battery back...). What troubles me most is that I can't even start the bootloader.
Sounds like there is hardware failure, but I could be wrong. Also, can you check to see if the ribbon came lose for the screen? When you have the phone opened look from the bottom of the phone (where you charge) up towards the top and you will see a hole in the screen portion. There should be a ribbon connecting the screen inside this, see if you can make sure it is securely connected.
I'm with Neoobs... Sounds like the screen isn't turning on (you can't power it off without it plugged in).
If the ribbon cable is connected, somehow the screen has been trashed. How or why this occurred when swapping the cards is beyond me. Have you tried to ADB into the phone from your computer?
Related
Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish
Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.
OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish
My S4 has finally kicked the bucket. It turns on long enough to display the "Samsung" splash screen with the padlock icon that says "Custom." After about two seconds it instantly shuts off, and can't be turned back on.
Pull the battery, the phone automatically turns on, shuts off again, rinse and repeat.
At this point I just want to salvage my pictures and music from the phone; is there any way I can mount the internal SD in the state that it's in? I'm sure this power issue is hardware-based; I can't get into recovery or download mode before it shuts off on me.
I was having this same problem recently as well. It happened on two separate occasions with about a week in between. The first time it came back after a few battery pulls and attempts to boot to recovery as well as download mode. The second time I fiddled with it for about an hour with numerous battery pulls and attempts to boot to recovery and download mode. I even swapped batteries to no avail. I don't know why exactly it finally decided to boot, but I haven't had an issue with it since. Maybe keep trying and hope for the best?
Can you boot and stay into recovery or download mode?
If not, then it very well might be a button issue. Have the phone checked out or you can do it yourself with a voltmeter if you have the knowledge and tech. Otherwise take it to a professional. I paid around 15$ to a button replaced. Which kinda seems a lot, considering a set of 4 buttons costs about 5$ and then you can do it yourself since it doesn't appear to be that hard, especially if you've done soldering before.
Hello everyone im really hoping you guys can save me here.
Ok so The phone is a LG G2 D802 16gb
because the phone was dropped i had to get a new screen. i also got a new battery as well as when trying to remove it i broke the seal.
the phones been without a battery connected for 3 days. now with everything reconnected i cannot get it to power on when holding the power button
also plugging it in to charge appears to do nothing. (however i can feel a chip getting warm so it must be charging.)
When i try to power on i literally get nothing, no sound, vibration or screen.
so i tried the solution in https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Now when i jumped the pins it did show signs of life. i can see the screen is lighting up, but is black. (which apparently it should be)
when i connect it to the computer its recognised and maps about 12 partitions. but they are unreadable by my windows 10 (i assume is normal)
I then used the tool in https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
i used this to unbrick the phone, i can see in the tool it was copying data successfully into them partitions on my phone. but its made no difference at all to its original state.
Does anyone have any suggestions?
Hi people.
So i'm having a problem with my S7 Edge and i don't think it is common. A few weeks back I was using my phone and it would suddenly turn off and the battery would be drained too. After this first incident with the problem it happened more often, and the phone would start doing boot loops to the point where the phone just froze and turned off. When these problems occured it will usually need to be a problem where I do a safe boot (Volume up, Home button and power key), and everything will be fine (or to charge it if the battery drained), but recently, the phone just didn't work at all, to the point I waited for the battery to drain (10 hours), and try charging it, nothing happens.
So firstly I was watching a video and checking my CPU/Battery tempretures to see if that was the problem (the tempretures at the time were around 31 degrees), and mid way through the video it bugged out through the audio in a high screech and turned itself off.
I tried turning it on again but no response to the screen, i tried safe booting it, or every alternative booting option, it did not work at all.
Here is all the diagnostics and repairs I did, but no luck:
- Tried turning it on
- Different boot options (Volume up/down, Home button & power key)
- Cleaning the port for moisture detection
- Replacing the battery for a new one (Genuine one)
- Doing all of the above, with it on charge
- Connecting to a PC, but no detection
One positive I found was that when i put the phone on a wireless station, it would change colour to show that the phone is charging. I have however took the wireless out of the phone as it was in the way of the battery, and safely in my draw.
Before this final fault happened, I did do a recovery to a previous Android version, just incase if it was a software fault, but it wasn't. The phone is not rooted and I had it since September of 2016.
Is there any alternative options to do? As i'm running out of ideas to do as every solution on the internet is to turn it on, which i can't whatsoever.
The warranty is voided also as there is a crack on the screen lens, and it's way too much to pay for a repair.
I need some explination of why this is happening, so I can go in the right direction and not to waste money if i was going to a repair service, or purchasing the parts for myself.
Any help would be highly appericiated.
Check your installed apps to see if there any viruses on your phone. All you said are signs that your phone might have a virus (check how to remove it here: https://www.unlockunit.com/blog/how-to-tell-if-your-phone-has-a-virus/
However, there is a chance that you do not have any viruses on your phone, but at least you have to isolate this possibility.
Did you recall installing any app prior to this behavior?
This may be the case, however i can't turn on the phone at all. I tried every possible reboot possible, download mode, bios mode, safe boot, reboot, but nothing happens unfortunately. Unless i can do it whilst it is turned off, i can do something. I have a PC if i can do anything else with it.
I don't think I have installed any weird apps on the phone.
sounds like a brick to me. Not a lot I can thing of you can do.
If you place the wireless card back in does it boot?
IT sounds like you've messed with the internals, so possible you damaged something?
I don't particularly think that I broke it from the inside as it was behaving the same before i opened it. And when i used the wireless charging, it will only indicate it was charging or getting detected on that charging pad and not on the phone regarding a red led, or the charging icon
Have you tried holding volume down + home + power for 15 seconds and try turning on the phone again?
As mentioned in the description, I have unfortunately
MOweenSalah said:
As mentioned in the description, I have unfortunately
Click to expand...
Click to collapse
Have you had any luck? Am in the same boat.
Essential PH-1 has continued to be my daily driver for almost 5 years now.
I haven't backed up the data, not even to GDrive. Yes, quite dumb. I finally found time to start to look into backing up recently, with the ADB route.
For the past 2 or 3 years, rebooting was problematic where it'd take 5+ minutes or required pressing the Power button down for a second buzz from off state, releasing it only when the animation with small circles would start. It'd then boot up to completion.
Recently, after fully charging and booting up from off state, it started showing new symptom where it'd be stuck indefinitely the Essential logo splash screen. At that time, I was still able to go into bootloader/recovery menu.
I rebooted and let it continue stuck on the Essential logo, hoping maybe it'd just take longer. After an hour, I forced it to shut down and rebooted again and put it aside to wait for it.
Within less than 2 hours, I noticed the display went blank/black.
After that, regardless of how long I press the Power button, the phone would never wake up anymore.
Plugging in the Essential OEM power adapter also does not even show the LED turning on. Can't tell if the USB port was busted or not but would be surprised if it did as charging and data transfer had always gone through a magnetic plug that's permanently plugged-in to the USB port.
Bootloader was never unlocked and, as such, also never attempted to gain root access to Android.
It was running the official Android 10 ROM from February 2020 (?).
There was no smoke or any unusual smell.
1. Is this a known/previously reported problem? I'd like to read on what others who experienced the same may have tried to resurrect.
2. If, let us say, the problem is actually with the battery, would the phone not show any signs of life when plugged-in to power adapter?
3. What are the chances some other electronics may either have slowly deteriorated or have gotten fried inside that casing?
4. If it's never powering back on, are there instructions on how to de-solder the internal storage component to try to recover the data?
5. What other possibilities can cause an Android device to not even show any signs of life?
6. Any other ideas?
Appreciate help from the community, including any pointers even if referring to a different Android device.