OK so 15min ago my phone was working fine.
I plugged it into my computer via USB to I could copy some videos and my PC didn't detect it so I rebooted the phone to see if that would help....
From that point on, it doesn't go past the initial "Samsung" screen. Well, it sort of does... regardless of any button combinations I press while booting up it always goes into a bright write and green screen that isn't normal. It is some sort of ghosted or washed out image.
From there the only thing it responds to is a forced reboot and it loops back to this again.
I've tried every button combo available and they don't respond. I cannot get to the download menu or the recovery menu so I can't reload the ROM or the TWRP recovery.
I've never seen anything like this in over 10 years of rooting phones... and the worst part is that I wasn't making any changes, just doing a reboot.
Any ideas of the problem?
Related
Well I was screwing around with my gtab, trying to put honeycomb on it, (I was on cyanogenmod) and I knew that I needed to put build 4349 on it. Unfortunately, I put that build on it, and installed my rom, but it didn't work. I decided to do the exact same thing over again, to see if it worked the second time. Halfway through the process, while restarting my gtablet, I had a serious problem. My gtablet will turn on after holding down the power button for about 30 seconds, but the screen is completely black and blank. Also, if I hit the (+) button, it says it will boot a recovery image, but it never does. If I hit the (-) to put it in APX mode for a NVflash, it simply turns off.
PLEASE, I have no idea what to do, because I really don't know what is going on with my tablet. I am just trying to put a honeycomb rom on it, but it seems I have completely screwed it up.
To put it straight: It won't go into APX mode
The screen is supposed to go black and blank when you start up in APX mode. Plug it into your computer and check to see if it is or not.
yea but supposedly it shows the viewsonic logo for a second. Mine when I hit the power button and hold the minus and just hit the power button are both the same. Also, I plug it in and nothing happens.
I tried holding the power for 15 seconds, nothing, if I hit the power for about 5 seconds it turns on that blank screen, if I hit + it says recovery key detected and booting recovery, but nothing happens after that
the black screen is the APX screen, it is blank and black.
You don't see an android symbol first.
my computer never says anything about a tablet without drivers or anything as stated in all guides
It's not unusual for the VS Birds splash screen to get lost during flashing operations that go bad. You also might not get a missing driver message for a number of reasons (especially if the driver isn't missing). So...
If the splash screen is missing, when you turn the tablet on while holding the volume down key the backlight should come on momentarily then the screen will go black. If that happens then you are in APX mode. If you have a linux box handy you can plug it into that and issue an "lsusb" command in a terminal window to verify that. There might be an equivalent for windows but I don't use it so I can't tell you what it would be.
If you are really having that much trouble with it I'd be happy to look at it for you if you cover shipping.
Hi.
My HS-U939 became very slow and unresponsive so I decided to re flash it. I used SP flashing tool. After it were done my phone only shown a white fuzzy screen with lines and faint dots and keep rebooting to the same white screen. I have tried everything but nothing works. My PC wont detect my phone so I can re flash it. The only time my I can see on my screen is when I hold power - & power button. I then get Select boot mode. When I choose recovery the phone restarts to white screen but still don't detect on PC. If chosen fast boot it detects for about 3 seconds and then disappears. When I try booting without battery the device detect and undetected every second. Is it possible to fix this or can I throw the phone away?? Thanks.
My wife's phone was rebooting constantly, so I thought I'd go into recovery and factory reset it. Well, as it turns out, I'm a moron...I did from the "maintenance recovery" screen and now it's stuck in a loop. If I try booting like normal it'll say "recovery booting....." A few times, I've been able to hold power, vol. up, and home and get it to a blue screen that says "installing system update", then into the no command screen. Then when I do vol. up and power, I get a message that says "Failed to open recovery_cause" I'm trying to replicate that screen now to get all of the details off, but can't currently seem to get to the no command screen.
Any advice? Thanks in advance.
Oh, the blue light is constantly pulsing regardless of the state of the phone.
Edit: Tried it again and this time got a "Secure check fail" screen
Edit (2): Got in this time, got the error, somehow got back to the no command screen, got a longer failed to open error, see pics. Let the phone sit long enough and recovery eventually loaded. Did the factory reset from there and I'm back to the same point as when I first posted.
Text me on telegram and I'll help you fix it @vishanMK
VooDooCC said:
My wife's phone was rebooting constantly, so I thought I'd go into recovery and factory reset it. Well, as it turns out, I'm a moron...I did from the "maintenance recovery" screen and now it's stuck in a loop. If I try booting like normal it'll say "recovery booting....." A few times, I've been able to hold power, vol. up, and home and get it to a blue screen that says "installing system update", then into the no command screen. Then when I do vol. up and power, I get a message that says "Failed to open recovery_cause" I'm trying to replicate that screen now to get all of the details off, but can't currently seem to get to the no command screen.
Any advice? Thanks in advance.
Oh, the blue light is constantly pulsing regardless of the state of the phone.
Edit: Tried it again and this time got a "Secure check fail" screen
Edit (2): Got in this time, got the error, somehow got back to the no command screen, got a longer failed to open error, see pics. Let the phone sit long enough and recovery eventually loaded. Did the factory reset from there and I'm back to the same point as when I first posted.
Click to expand...
Click to collapse
Have you been able to fix this?
Was able to boot into maintenance mode, then into recovery mode and reset. The power cycling was still happening, so I tried a shot of canned air in the usb port since I saw that suggested on other stores. After that it decided to not charge anymore. Ended up upgrading her to a galaxy s20.
Today it charges, started to go through the new phone setup process, but then the bootlooping started again. After a few rounds of that, it seems like it's powered off, but has a pulsing blue light.
Got it to boot into safe mode, still turned off, but it didn't loop this time and no pulsing light now.
Power it in again normally and it works for about a minute, reboots 3 times, works for a minute and repeats that process a few times. Then goes back to seeming powered off but a pulsing blue light
VooDooCC said:
Today it charges, started to go through the new phone setup process, but then the bootlooping started again. After a few rounds of that, it seems like it's powered off, but has a pulsing blue light.
Got it to boot into safe mode, still turned off, but it didn't loop this time and no pulsing light now.
Power it in again normally and it works for about a minute, reboots 3 times, works for a minute and repeats that process a few times. Then goes back to seeming powered off but a pulsing blue light
Click to expand...
Click to collapse
Boot into recovery and clear cache then reboot.
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
yellownese said:
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
Click to expand...
Click to collapse
Which OOS build are you on? And your device is unlocked or not?
Getting into EDL mode is tricky. Power off device completely. With the device powered off, hold down volume up and volume up at the same time, keep them pressed all the time, and during that time plug into PC (phone all the time powered off). Still hold both of the buttons. By the time you plug into PC, you should be in EDL mode, BUT it only lasts about 10 seconds. I mean you have to click start in this 10 seconds time bracket, other way phone exits EDL itself. After you click start, you can release button, obviously
A few weeks after switching from my old S7 Edge to my old S8 (which I did about a month ago), I tried turning on my S7 Edge only for it to enter recovery mode. Since the power button is broken, I figured I would have to reboot it out of recovery mode using ADB on my PC. When I switched my S7 on again the next day to enter recovery mode and connect it to my PC, I got to the "installing updates" screen that precedes recovery mode. This screen showed up for about three seconds before my screen went black. After 10 seconds my phone rebooted and went back to the "installing updates" screen, went black, rebooted, and so on.
I think my phone might be out of battery so when it charges a little bit, it automatically tries to enter recovery mode, which uses up all the power in the battery and causes it to die, restarting the cycle. Is there any way I can stop my phone from automatically turning on when it is plugged in so that it can charge enough to actually make it to recovery mode?
Thanks!
For some reason, the bootloader on this device remembers if you were last booted into recovery, and will return to it on the next poweron, so - without a working power button - there aren't very many options.
The power button could be an easy fix - depending on if it's stuck or damaged. The outer parts of the volume and power buttons on this device are interchangable, so that could make all boot modes possible again. Opening your device may sound scary, but - with good research and some patience - you will find it is certainly doable using basic tools. And if you don't want to do it yourself, a local repair shop would probably do it for cheap as well.
As far is I know, there isn't any usable software fix without a working power button.