Hello, unfortunately I also have the problem with the recovery mode. I can not find any way in this. I have already tried the power button for 10 seconds. Then the lights of the radio flash several times but it does not happen. Even if I briefly press the power button again briefly (even several times) nothing happens.
Does anyone know advice?
Related
I upgraded from 2.51.1 to 3.4.2-117, and the phone lags, seems to me that it is because of the google sync. Someone posted the very same problem and said that factory reset solved his problem.
My problem is that the phone does not do factory reset, in Privacy I press the erase button and nothing happens.
I tried to boot into recovery, but I can't get into it. The droid comes up but upon touching the lower right corner nothing happens.
When i try to boot with vol up and down same time, the phone boots into safe mode.
How shall I get into recovery so I could do a wipe? The phone is basically unuseable now because of the lags and freezes
Hey mate! Don't give up. When you see the droid in the center of the lcd just push vol+ and vol- at once. You'll get into recovery mode. )))
thx dude, i figured it out "accidentaly"
Everyone was writing on the net that the recovery boot is up and down the same time instead of the old method of power & volume -.
So, when I got to the droid, started to push every possible button in every possible variation and I got in.
since then I learned that the vol up and down is after power & vol -, not instead.
I am not a total noob. I have always done my research and I am well versed with the procedures but this has me stumped. About six months before I had installed Omega ROM (told you i wasn't a noob) and things were fine and dandy. I was running today and bam! my phone just enters into a bootloop (lost my data on endomondo too). But hey! I am an expert right? or so i think to myself and I try getting into the recovery mode / download mode. I press the volume down, power and home button. The warning comes up and all that i have to do now is to press the volume up key right? wrong!! Inspite of pressing the volume up key the bootloop continues. I dont know what i am doing wrong. I am sure it is a really silly thing but i am not able to figure it out myself. I read the posts and all of them deal with other issues. Can someone help me?
Can someone check this up for me? Switch off your phone and try going into the recovery mode by pressing only the vol. down button and the home button pressed together. If it does not show the warning screen prior to the recovery mode then it would mean that my power button is malfunctioning. It would take just two minutes of your time. Please post your results here. Please.
If you press just the volume down and home button not a lot happens not the warning screen anyway. When I boot into recovery I have to wait for the Samsung logo to appear twice or it just reboots. Might be worth pressing all 3 buttons and wait for the 3rd restart before letting go
Edit
It's volume up home and power for recovery if you get download mode and volume up the phone just reboots hence why you go back to bootloop
Sent from my GT-N7105 using Tapatalk
The problem is solved. It turned out that it was not a boot loop after all. The power button got pressed and was stuck in that state thus causing repeated reboots. It was by pressing the volume down and home button without pressing the power button that i figured out that the power button was stuck. So i took out the screws and adjusted the band slightly and now alls well.
I am having a problem with my phone. I installed CM 11 on it via TWRP 2.6.3 but for some reason the flash didn't workout well and the phone was stuck in the boot animation. The problem is now I am not able to access bootloader because of a faulty vol down button. Before it would work some time, but now have tried it several times but can't do any thing. It just recognizes the power button press and turns the phone on and it gets stuck in bootloader. How do I get in recover to solve this problem.
Any advice?
Kabir999 said:
I am having a problem with my phone. I installed CM 11 on it via TWRP 2.6.3 but for some reason the flash didn't workout well and the phone was stuck in the boot animation. The problem is now I am not able to access bootloader because of a faulty vol down button. Before it would work some time, but now have tried it several times but can't do any thing. It just recognizes the power button press and turns the phone on and it gets stuck in bootloader. How do I get in recover to solve this problem.
Any advice?
Click to expand...
Click to collapse
Press and hold back button + power. That will boot into fastboot then use volume up to navigate
try to keep volume down button
try to keep volume down button harder from the start and after the power button, i have the same prolem and it work after 1-2 tryes
VallNAr said:
try to keep volume down button harder from the start and after the power button, i have the same prolem and it work after 1-2 tryes
Click to expand...
Click to collapse
Or u could use back button + power aswell and get there first try, no point killing the button even more.
i recently updated the mcu to kld2 2.81. Now i can not get in to my recovery manual to fix my rom problem. i can only get into from the rom power options. everything i hold the power buttons it gives me 3 shorts beeps like normal. then one long beep then nothing happens. no recovery anything. i have tried holding reset button all i get is a long beep. Someone please help me?
My Pixel C is fully changed but the screen is black and won't display anything at all. I know it is on because I can take screenshots with the hardware button and hear the noise. I can also see it on Android Device Manager. I have long pressed with all the different button combinations. It reboots but the screen shows NOTHING (not even the Google boot logo).
Any ideas would be greatly appreciated!
It is stock and not rooted but subscribed to the Beta channel.
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
mightywhites29111971 said:
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
Click to expand...
Click to collapse
I didn't elect to install O. I didn't see the update notification in the last couple weeks before it had this problem.
I can't get to recovery because the screen is off. How did you do it? Or were you able to see the screen after holding the volume down button as well as the power button to get into recovery mode?
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
mightywhites29111971 said:
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
Click to expand...
Click to collapse
Thank you for your reply. Unfortunately, that is not working. I have tried holding for 60 seconds just to be sure. It is so strange!
Not sure what it is in that case. Have you tried the volume up button to get fast boot mode?
I am having this problem aswel, on the android O beta. I can not use it and I can not see the bootloader when holding down power + volume down
edit: resolved the issue by trying button combinations until it booted (took around 2 hours total with time of disappointment in between)
edit2: oh my ****ing god it booted correctly (showed bootloader warning + bootlogo + lockscreen) but it locked and now it's black again!
edit3: was able to get into fastboot after 3 tries so i'm flashing the factory image right now (7.1.2)
edit4: flashed 7.1.2 factory image and was able to fastboot boot into twrp but still no display.
edit5: i am now troubleshooting i checked all the files in /sys/devices/50000000.host1x/54400000.dsi/54400000.dsi.0/backlight/lpm102a188a-backlight/ they all indicate 255 which is 100% anyone have any ideas?
final edit: i fixed it by trying a **** ton of times
Hello,
Can you tell what have you do to repair the pixel? Have the same issues after Oreo update :/
Anyone found a way to fix permanently? Mine started doing it around Christmas 2018, and it takes more and more tries every time (to ctrl-down power) and at some point it works... Then all stays fine until I close the lid or put it to seep.
Did someone reinstalled completly the os and got a success? I am not rooted, this started when It tried (and failed) to install 8.1 (update of oreo).