I discontinued using my X Compact in mid-2020 when I got a new Pixel 4a. It's been sitting in a drawer since. It was rooted but working fine.
Recently I pulled it out to try charging it up to use as a spare. What I found was, upon plugging it in to charge, I'd get the "Your devices has been unlocked and can't be trusted" splash screen, then after the 5 seconds it would vibrate and bootloop back into the same screen, etc. I tried booting into recovery with power button / volume down and got only a blank screen. I booted it into fastboot with power button / volume up and left it to charge in that state.
Today I got all the drivers set up on my laptop and was able to access fastboot. I tried installing two different versions of TWRP for kugo (twrp-3.3.1-0-kugo and twrp-3.6.2_9-0-kugo). In both cases, subsequently attempting to boot into recovery, I got the SONY screen followed by the TWRP splash screen and then... hang.
Certainly seems like something got corrupted in there. Should I just call it a brick and leave it alone, or are there any further bright ideas on what to try?
Is the battery good? It may not be able to sink enough current otherwise.
blackhawk said:
Is the battery good? It may not be able to sink enough current otherwise.
Click to expand...
Click to collapse
Hard to judge in this state, but if I immediately plug it into charge after launching recovery mode, it still hangs.
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.
I've looked online, especially on here, for solutions to my problem but they all seem to assume that I can access fastboot. Here is my specific problem:
I was using my phone and suddenly the screen went black. It rebooted once into the OS but immediately restarted and has been stuck in bootloop for 4.5hrs thus far. I have tried to wipe cache, enter fastboot, power down the phone but nothing worked and it kept looping. Even when I powered off. It's like the power button signal is malfunctioning because it doesn't always reboot at the same exact point in the boot cycle.
My phone is stock, no custom anything, and is encrypted. My only thought right now is to let the battery drain fully and try to boot again after that. I have not tried to enter fastboot while connected to a PC, but I have tried to do it just on the phone.
I have not been home yet so I do not have access to a PC I can actually do things with at the moment. Any help is much appreciated. Thanks!
EDIT: I am home now. Going on 6hrs of looping and nothing has changed.
EDIT 2: The battery was drained. It starts to charge but instantly tries to enter the boot loop again so the battery never gets enough charge to do anything; thus, I can do nothing to save the phone, I don't think.
If its some malfunction with power button, try to abuse the button gently. I used to do that with my Nexus 5 when its power button gets stuck inside causing bootloops.
nirmalkurienmathews said:
If its some malfunction with power button, try to abuse the button gently. I used to do that with my Nexus 5 when its power button gets stuck inside causing bootloops.
Click to expand...
Click to collapse
The button itself is fine, it works as it should and is not pressed down; however, there might be some sort of internal problem causing the phone to think that it's being pressed.
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Omnipotus said:
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Click to expand...
Click to collapse
If the power button doesn't work and you can't get into fastboot mode then you really can't do much
Sent from my Pixel 3a using Tapatalk
Did you try adb rather than fastboot? Or does the computer just not recognize the device is connected at all? In that case, try different cables, computer and make sure to use a USB-A to C cable, not C to C. Use a USB 2 port, not USB 3.
A last resort before it hits the trash can, open it and disconnect the battery for a bit.
Omnipotus said:
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Click to expand...
Click to collapse
Done the same thing, luckily I noticed a minute or two after I put phone in mount & it rebooted normally, bring back the old Nokia power buttons on the top ?
Recharge your battery to make sure you have enough power to boot properly. Then try a forced reboot by holding both the power button + vol down buttons at the same time for 10s (think this does a simulated battery pull)
(Though obviously if you have a power button stuck on this won't help, some old Samsungs got this & people reported banging phone on hard surface sometimes fixed but with newer screens being so close to the edge & our ceramic body you run the risk of cracking screen/ceramic!)
I'm going to add to @IronRoo's advice by reminding that when plugged in, the device tries to boot. It's helps to unplug when doing button commands.
So since the bootloader is unlocked, when I plug up my tablet, it keeps flashing the battery icon., with the orange state message. I was trying to install an os but when I try to install something via TWRP or Fastboot, the device just shuts off. and it keeps showing the battery icon for every 5 seconds. Help!!!!!
antoinejr1111 said:
So since the bootloader is unlocked, when I plug up my tablet, it keeps flashing the battery icon., with the orange state message. I was trying to install an os but when I try to install something via TWRP or Fastboot, the device just shuts off. and it keeps showing the battery icon for every 5 seconds. Help!!!!!
Click to expand...
Click to collapse
Mine did that when i had a bad battery (i had it less that a week). I bought another battery from ebay and replaced it and it is working again... it gave me all the options to fastboot, recovery, or boot normally when i held the vol up. Whenever i selected anything it would shut off. When plugged in, it would just keep popping up the battery icon. You can try the sp flash tool and try flashing the factory image, if you are sure the battery is working...
It sounds like your battery is too low. At least that was my problem, same symptoms. I had to open mine up and unplug the screen so it would charge the battery enough.
I threw mine in the garbage! It did it again with the ****ty battery... Onn has found a way to make Amazon fires looks like high tech.... I have a 10.1 that hasn't given me issues yet...
Michajin said:
I threw mine in the garbage! It did it again with the ****ty battery... Onn has found a way to make Amazon fires looks like high tech.... I have a 10.1 that hasn't given me issues yet...
Click to expand...
Click to collapse
Nevermind I used the SP Flash Tool.