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.
Related
I was running Slim 4.3, and over the weekend my phone started to reset during the boot splash phase. I used Odin to go back to stock 4.1.2, same thing. I tried using Odin again last night and the phone reset during the process, now it keeps resetting at the "firmware update encountered an error" screen.
After searching, it seems it's the "stuck power button" issue, so I took the whole thing apart, cleaned each contact, and still, even without the piece that has the power/volume buttons attached, it's still doing this. How could it be a stuck power button if there's not power button attached?
It restarted in the middle of flashing with odin? Your probably hosed if it did.
mikewhy said:
I was running Slim 4.3, and over the weekend my phone started to reset during the boot splash phase. I used Odin to go back to stock 4.1.2, same thing. I tried using Odin again last night and the phone reset during the process, now it keeps resetting at the "firmware update encountered an error" screen.
After searching, it seems it's the "stuck power button" issue, so I took the whole thing apart, cleaned each contact, and still, even without the piece that has the power/volume buttons attached, it's still doing this. How could it be a stuck power button if there's not power button attached?
Click to expand...
Click to collapse
if removing battery then reinserting it starts the phone then its the power button, the button(white) is attached to the mobo its not the the black button on the case
heres a pic
yeah, that little white button is the one I cleaned. literally detached the mobo to clean it all.
even keeping that button depressed with a screwdriver would still let me "hijack" and take control of the constant rebooting, but upon letting go the phone will enter the "firmware update encountered an error" screen and constantly restart from there. so, I can still get into download mode, just not for any length of time.
mikewhy said:
yeah, that little white button is the one I cleaned. literally detached the mobo to clean it all.
even keeping that button depressed with a screwdriver would still let me "hijack" and take control of the constant rebooting, but upon letting go the phone will enter the "firmware update encountered an error" screen and constantly restart from there. so, I can still get into download mode, just not for any length of time.
Click to expand...
Click to collapse
button needs to be replaced, its cheap to buy $0.99 http://www.etradesupply.com/oem-samsung-galaxy-s-ii-skyrocket-sgh-i727-power-button.html
So my sister-in-law has an Acer Iconia A1-810 tablet, somehow it crashed and she used "Power+volume up" to enter the bootloader and start a recovery, or maybe erase, I really don't know what she selected, but now all the tablet will do is turn on and go strait to a screen with the android with the spinning stomach and says "Erasing..." but it stays on this screen for hours and hours and does nothing.
I have a bit of experience with androids and lots of experience in software/hardware development but I can not get this thing to do anything. I have used the little paperclip shutdown hole to turn it off and then tried to get back in to the bootloader with "power + volume up" (tried volume down too, along with both volume buttons) and that wont work, still goes strait in to the "Erasing..." screen. I have tried with adb and fastboot to interupt the boot process and get it to do anything, it won't. When you do something with fastboot, it will say "waiting for device" so I restart the tablet, and when the tablet first starts to boot, during the Acer logo screen, fastboots cursur stops blinking but won't go any further.
As far as I can tell, nothing I do will get me to the bootloader again, now it just goes to the "Erasing..." screen everytime and ignores everything else you try to do. Is there anything that can be done? Or is this thing just a paperweight now? I'm about ready to start pulling this thing apart and seeing if I can do anything at the hardware level....
Just some minutes ago my S7 froze because of Focus Gallery App. I don't exactly know what it did but the phone did not respond any more.
So pressing the power button did not bring back the phone either. After searching for a bit I found a way to simulate a bettery disconnect by pressing Volume Down + Power Button.
The Phone came back up and displayed the initial boot logo. Also the blue LED is on. But nothing happens from here on. I do not come to the "Samsung" boot animation and the phone simply
does nothing. Retriying Volume Down + Power Button doesn't seem to help too. I tryed all button combinations but nothing brings the phone back.
I also cannot enter the recovery menu. So no chance to reset to default settings.
I am running a stock Android on the phone. Nothing was done by me. No custom ROM, no root, just plain Samsung Android.
Is there sill something I can do?
Edit: I just got into whats seems to be ODIN Mode??? Can I do something from here?
Oddly this happened to me last night although I may have inadvertently done it. But the only way I was able to get my phone functioning again was reflashing the OS to the phone.
How did you manage to get the phone into Odin mode? I'm having the same issue with the phone being totally unresponsive but the blue LED on.
if you can reboot your phone with the VOL Down/Power, when the screen goes black, quickly press and hold VOL Up, Home and Power. it should enter recovery. or hold Vol down, Home and Power to enter the download screen.
I have the S7 Edge (rooted, custom ROM) and it's running fine. My girlfriend's regular S7 is having the same issue though.
When she plugged it in to charge last night, she checked it a few minutes later at which point the phone had (started to) reboot. The blue notification LED was on and the screen had frozen at the 'SA' from the 'SAMSUNG' startup logo. Forced a reboot with down+power, resulting in just the blue LED (no logo this time). Phone was unresponsive (couldn't force a reboot again) so left the battery to drain overnight. The phone is completely dead today even after charging - no LED, no boot, no anything.
I'm not sure if she had the phone scheduled to perform an update overnight and it froze halfway through, but that would be my first guess. So far, no fix.
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?
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