Database Users

Nexus 6P stuck in bootloop

128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, I have no idea how to get it out of this. Any suggestions?

dandpw said:
128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, I have no idea how to get it out of this. Any suggestions?
Click to expand...
Click to collapse
Same issue here. I booted and setup device just fine over WiFi. I powered down to install SIM. On reboot I get to PIN lock, and then phone is stuck in boot screen.
{Edit} Reset handset and starting over.
{Edit 2} After factory reset, I've restarted handset three times with no problems.
{Edit 3} Factory reset seems to have fixed the problem.

PhiPsi32 said:
Same issue here. I booted and setup device just fine over WiFi. I powered down to install SIM. On reboot I get to PIN lock, and then phone is stuck in boot screen.
{Edit} Reset handset and starting over.
{Edit 2} After factory reset, I've restarted handset three times with no problems.
{Edit 3} Factory reset seems to have fixed the problem.
Click to expand...
Click to collapse
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4

sabesh said:
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
You are going to need to boot into fastboot, unlock the bootloader and flash the stock img file from Google.

sabesh said:
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
I would think that holding power and volume up will get you to the factory reset screen, even if bootlooping. I don't think you need to unlock the bootloader.

Shockz said:
You are going to need to boot into fastboot, unlock the bootloader and flash the stock img file from Google.
Click to expand...
Click to collapse
You can't unlock the bootloader anyway unless you flip the switch in developer options while the phone is booted. You'd have to go into stock recovery and do a factory reset from there.
Sent from my Nexus 6P using Tapatalk

sabbotage said:
You can't unlock the bootloader anyway unless you flip the switch in developer options while the phone is booted. You'd have to go into stock recovery and do a factory reset from there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.

Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?

Shockz said:
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.
Click to expand...
Click to collapse
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4

sabesh said:
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
There is no clear answer here, but I would say the general answer is that no it will not void your warranty. I have never heard of people being rejected by google support if their bootloader was unlocked.

Won't be druv said:
I would think that holding power and volume up will get you to the factory reset screen, even if bootlooping. I don't think you need to unlock the bootloader.
Click to expand...
Click to collapse
I held volume down and power.

diceman725 said:
Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?
Click to expand...
Click to collapse
try: fastboot flashing unlock

diceman725 said:
Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?
Click to expand...
Click to collapse
Found a solution. I just wasn't familiar with how to get into the stock recovery menu... Too used to TWRP. Factory reset cleared it up - though who knows for how long.

I have the MDB08L variant and I used the boot image from the stock Google MDB08L and thatvworked and I was able to flash TWRP from CMD but it was when I tried installing SuperSU that I got stuck in the bootnloop. I wiped the whole system from TWRP and I'm wondering what steps I should take next? Should I try flashing Chainfire's modified K variant boot image? Or try again with the L boot image?

PhiPsi32 said:
I held volume down and power.
Click to expand...
Click to collapse
Yes, sorry, my mistake.

This is happening to me. First time restarting since putting the sim card in. I hold the power button and volume down, select "factory" but then it still gets stuck in the boot loop. How do I factory reset with this issue?
Thanks for any help this really sucks.
Edit: I figured out how to factory reset from this site's instructions:
http://www.androidexplained.com/nexus-6p-recovery-mode/
Looks like half of my initial setup was saved with google syncing my settings but I now need to spend a couple hours to get back to where I was today. WHY DO I HAVE TO CUSTOMIZE SO MUCH?!?....OH YEAH BECAUSE IT IS FUN

Shockz said:
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.
Click to expand...
Click to collapse
quick question, if i unlock the bootloader and decdie to root the phone later.. does rooting wipe data on the phone?

No, rooting does not wipe the device.

sabesh said:
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
Shockz said:
There is no clear answer here, but I would say the general answer is that no it will not void your warranty. I have never heard of people being rejected by google support if their bootloader was unlocked.
Click to expand...
Click to collapse
The US, the Magnuson-Moss Warranty Act prevents companies from voiding it if the bootloader is unlocked, provided they explain a way to unlock it. Making it a feature of the device itself. Since Google puts out all of their factory images, and even gives instructions on how to unlock the bootloader , it's very likely that it falls under the terms of this law. I've also never heard of them denying warranty service on a device provided there was no accidental damage. Their support is actually pleasant to speak with (unlike HTC in my experince).

I unlocked my bootloader then install the updated factory image.. which reset everything installed twrp then I rebooted in to android I guess for the last time cause now I'm in the bootloop at the colorful android screen any help would be greatly appreciated if I comeback from this I honestly think ill never root my nexus again please help !!!

Any possible way to recover from "System software not authorized by AT&T?"

Any possible way to recover from "System software not authorized by AT&T?"
I have an S7 Edge SM-G935A on Nougat 7.0.0 and rooted, and I was having trouble with connections in apps detecting root. I searched for solutions online, and found Magisk could help mask root from apps. I foolishly tried installing it on my phone without reading about the prerequisites and after turning off my phone, I get the message "System software not authorized by AT&T has been found on your phone." The only way I know right now to fix it is to do a complete stock flash, but I didn't want to resort to that just yet, wondering if there was some other way to remove Magisk, bypass the message, or recover my data (photos & contacts) before I did so?

Mufasa2.0 said:
I have an S7 Edge SM-G935A on Nougat 7.0.0 and rooted, and I was having trouble with connections in apps detecting root. I searched for solutions online, and found Magisk could help mask root from apps. I foolishly tried installing it on my phone without reading about the prerequisites and after turning off my phone, I get the message "System software not authorized by AT&T has been found on your phone." The only way I know right now to fix it is to do a complete stock flash, but I didn't want to resort to that just yet, wondering if there was some other way to remove Magisk, bypass the message, or recover my data (photos & contacts) before I did so?
Click to expand...
Click to collapse
Flash the engineer boot again

billdauterive23 said:
Flash the engineer boot again
Click to expand...
Click to collapse
Does doing so wipe any data? There's a few important files I need to keep from my Galaxy

Mufasa2.0 said:
Does doing so wipe any data? There's a few important files I need to keep from my Galaxy
Click to expand...
Click to collapse
No, i ran into the exact same issue but you still wont get magisk working

billdauterive23 said:
No, i ran into the exact same issue but you still wont get magisk working
Click to expand...
Click to collapse
Magisk isn't an issue, as long as I can get my phone to by pass that message. I found another solution to my connection problem. Thanks for the help

billdauterive23 said:
No, i ran into the exact same issue but you still wont get magisk working
Click to expand...
Click to collapse
I flashed the engineering bootlaoder, but now the start up screen keeps looping and flashing. The message is gone, however. Any ideas what might have happened?

Mufasa2.0 said:
I flashed the engineering bootlaoder, but now the start up screen keeps looping and flashing. The message is gone, however. Any ideas what might have happened?
Click to expand...
Click to collapse
I really dont know, i was just able to boot back into android im afraid your data is gone my friend.

billdauterive23 said:
I really dont know, i was just able to boot back into android im afraid your data is gone my friend.
Click to expand...
Click to collapse
Oh well, that's alright, I won't be giving up on it anytime soon, will keep searching for some solution. But thanks for the help anyway

Mufasa2.0 said:
Magisk isn't an issue, as long as I can get my phone to by pass that message. I found another solution to my connection problem. Thanks for the help
Click to expand...
Click to collapse
How did you by pass the connection error due to root? I am running into the same thing and Magisk just causes the same unauthorized message from AT&T (I reflash with boot img and fix it but I need to hide my root to access to app)

[HELP]Custom binary blocked by FRP.

Please help me, I accidentally turned off the OEM Unlock on the Developer options. Is there a way to bypass or to unblocked this. My phone is Samsung Galaxy j510GN/DS 7.1.1

jiggey025 said:
Please help me, I accidentally turned off the OEM Unlock on the Developer options. Is there a way to bypass or to unblocked this. My phone is Samsung Galaxy j510GN/DS 7.1.1
Click to expand...
Click to collapse
Can you give more details?
Why cant you just turn it back on?

garylawwd said:
Can you give more details?
Why cant you just turn it back on?
Click to expand...
Click to collapse
Well, I tried to root my phone and It was success but I accidentally turned of OEM Unlock which is the thing that is needed in order to keep the phone to be rooted and right after turning off OEM Unlock, everytime I turn on my phone, it stucks on "Custom Binary Blocked by FRP".
But anyways, I've followed the step of #Henkate which helps me a lot on retrieving my phone back without erasing my files. Thanks to you man. I just followed the steps then voila! it works like a charm <3

jiggey025 said:
Well, I tried to root my phone and It was success but I accidentally turned of OEM Unlock which is the thing that is needed in order to keep the phone to be rooted and right after turning off OEM Unlock, everytime I turn on my phone, it stucks on "Custom Binary Blocked by FRP".
But anyways, I've followed the step of #Henkate which helps me a lot on retrieving my phone back without erasing my files. Thanks to you man. I just followed the steps then voila! it works like a charm <3
Click to expand...
Click to collapse
Lesson learned.
Well done on fixing it

Had the same issue. Just flashed a stock firmware and started over.

Impossible root in Samsung A20e sm-202f

Hello everyone. I open this post because I have fought hard enough to root my samsung A20e model: sm-202f. Any solution? I’ve tried everything from parking the AP boot. Modify BL. Everything, everything, everything. All I get is an eternal boot loop. I have to point out that the Bootloader is already unlocked but nothing. A greeting and thank you to help me.

LGK10420 said:
Hello everyone. I open this post because I have fought hard enough to root my samsung A20e model: sm-202f. Any solution? I’ve tried everything from parking the AP boot. Modify BL. Everything, everything, everything. All I get is an eternal boot loop. I have to point out that the Bootloader is already unlocked but nothing. A greeting and thank you to help me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767

physwizz said:
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
Click to expand...
Click to collapse
I have tried that method, followed all the steps and nothing.

LGK10420 said:
I have tried that method, followed all the steps and nothing.
Click to expand...
Click to collapse
Try this
[Root] [guide] Samsung Galaxy A20 rooting guide (Android 9 & 10)
https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872

physwizz said:
Try this
[Root] [guide] Samsung Galaxy A20 rooting guide (Android 9 & 10)
https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
Click to expand...
Click to collapse
The first one I tried was that and nothing. Eternal loop at startup.

LGK10420 said:
The first one I tried was that and nothing. Eternal loop at startup.
Click to expand...
Click to collapse
It takes quite a while to reboot after factory reset

physwizz said:
It takes quite a while to reboot after factory reset
Click to expand...
Click to collapse
How long is a while?
I've left mine on boot loop for 5-6 hours overnight and never gotten out of the boot loop.

LGK10420 said:
Hello everyone. I open this post because I have fought hard enough to root my samsung A20e model: sm-202f. Any solution? I’ve tried everything from parking the AP boot. Modify BL. Everything, everything, everything. All I get is an eternal boot loop. I have to point out that the Bootloader is already unlocked but nothing. A greeting and thank you to help me.
Click to expand...
Click to collapse
-------
Hi, I fought a lot too but in the end I managed to... Hi, I fought a lot too but in the end I managed to... without TWPR and with Odin and Magisk.... but the reason I wanted ROOT was to change some phone identifiers but apparently with the new Androids this is impossible due to the new phone security and agreements with Google.... since I don't need this phone to play with it or to do things that are too heavy but only for work tests and trials,,,I'm thinking about doing root after having re-released Android 4.4 which for me was the best (the easiest to make "anonymous")

Sandro111 said:
-------
Hi, I fought a lot too but in the end I managed to... Hi, I fought a lot too but in the end I managed to... without TWPR and with Odin and Magisk.... but the reason I wanted ROOT was to change some phone identifiers but apparently with the new Androids this is impossible due to the new phone security and agreements with Google.... since I don't need this phone to play with it or to do things that are too heavy but only for work tests and trials,,,I'm thinking about doing root after having re-released Android 4.4 which for me was the best (the easiest to make "anonymous")
Click to expand...
Click to collapse
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com

Device corrupt and will not reboot

Hi, I have searched but couldn't find a solution, so here's my question.
I had unlocked the bootloader before and worked fine.
Wanted to go back to stock and lock the bootloader again but made a mistake I guess.
I locked the bootloader and now it gives me the 'corrupt' message. Is there anyway I can get it running again?
Unable to re-install the stock atm because flash-all.bat doesn't see a device.
Who is able to help me please?

dennisb71 said:
Hi, I have searched but couldn't find a solution, so here's my question.
I had unlocked the bootloader before and worked fine.
Wanted to go back to stock and lock the bootloader again but made a mistake I guess.
I locked the bootloader and now it gives me the 'corrupt' message. Is there anyway I can get it running again?
Unable to re-install the stock atm because flash-all.bat doesn't see a device.
Who is able to help me please?
Click to expand...
Click to collapse
You need to recover your phone with msm tool

Lycidias said:
You need to recover your phone with msm tool
Click to expand...
Click to collapse
Thanks for the reply. Can you help me to a correct link?
I managed to get it into fastboot and then I got it to unlock bootloader again.
Then I tried the Maronofrio install tool. That gave me a lot of "failed" messages on the prompt.
Now the phone keeps restarting with the OnePlus logo, but that's it.

Managed! Resolved.
Thanks again Lycidias