Related
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 !!!
just as the title asks, have any of you guys had success rooting tbe Droid Turbo 2 with the updated Kingroot app? thanks.
Doesn't work
Sent from my XT1585 using XDA Premium 4 mobile app
cool. their new,update claims it roots 5.1. didnt know if 5.1.1 was a stretch. thank you!!
Yeah but it checks your device and says it doesn't work on turbo 2. Maybe someday.
Sent from my XT1585 using XDA Premium 4 mobile app
have anyone tried SRSroot? I gave it a shot because it supposedly supports the turbo 2, it did show root complete and rebooted the phone but the phone still don't have root, wondering if the tool is a fake or maybe I did something wrong :-/
Jimmy8881 said:
have anyone tried SRSroot? I gave it a shot because it supposedly supports the turbo 2, it did show root complete and rebooted the phone but the phone still don't have root, wondering if the tool is a fake or maybe I did something wrong :-/
Click to expand...
Click to collapse
where did you see it works w DT2?
asuhoops8628 said:
where did you see it works w DT2?
Click to expand...
Click to collapse
I tried it myself, it connected through adb, detected the phone successfully, started the exploit, said root complete and rebooted my phone, but after the reboot my phone still don't have root, was wondering if anyone else tried it or knew if the software might be fake or faulty.
Jimmy8881 said:
I tried it myself, it connected through adb, detected the phone successfully, started the exploit, said root complete and rebooted my phone, but after the reboot my phone still don't have root, was wondering if anyone else tried it or knew if the software might be fake or faulty.
Click to expand...
Click to collapse
I think the SW is faulty... tried a bunch of times, even going as far as to pull the usb connection before the reboot hoping that the root would stick.... nothing.
i believe SRSroot auto reports as working & supported anytime the software doesn't fail!
New kingroot
I used to have a T2 and sold it because of inability to root or bootloader unlock. There may be a way to free it now, CVE2019-2215 use after free exploit.
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)
Hi,
I have the OnePlus 5 8GB.
I unlocked my bootload, rooted my phone, all good.
But then I realized android pay is not working with rooted phones, so i wanted to undo it.
for some reason i ran this because i found it in a guide to lock the bootloader again (yes, it was was stupid):
./fastboot flashing lock
After that i got the message that my device is corrupt and cant boot. So i ran ./fastboot oem unlock and that message disappeard.
I tried booting, but nothing happend for 10 minutes, still boot animation. so i went into fastboot, flashed twrp and tried doing a factory reset, but whatever i do, I get tons of these error messages:
Updating partition details...
Error opening: '/data/misc/[...]
Error opening: '/data/user_de/0/[...['
(No such file or directory)
What can I do?
I can even ADB sideload because of those errors.
edit:
also it shows nothing for bootloader version or baseband version in the fastboot screen.
https://imgur.com/a/z2KN3
doesnt look good. cant copy anything to device or from device
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Eric214 said:
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Click to expand...
Click to collapse
Anything I should do to have them not reject the RMA?
thx for the Magisk advice, using it now.
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
TheCorax said:
Anything I should do to have them not reject the RMA?
Click to expand...
Click to collapse
Since it's obvious someone tampered with the software, they may reject it.
You don't lose warranty if you root, but they won't cover the cost if anything happens to it due to the user's intervention.
If you manage to get the stock ROM onto the phone, you may be able to flash it from TWRP.
TheCorax said:
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
Click to expand...
Click to collapse
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
elbuenzurdo said:
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Yes it works again. That what I meant by android is launching.
TheCorax said:
Yes it works again. That what I meant by android is launching.
Click to expand...
Click to collapse
How do you do to get your device recognized? I have a similar problem for that command. But muy device just turned off and doesnt do nothing, Im trying flash it but nothing atm.
I have a leeco le s3 x626
I may be buying a nexus 6p for 70 bucks. The buyer said this
"powered off during a software update and it is in a "bricked" status. Screen turns on and you can access bootloader etc."
Is it fixable to get back to working condition? I wanna make for sure be for I buy it.
germanguy45 said:
I may be buying a nexus 6p for 70 bucks. The buyer said this
"powered off during a software update and it is in a "bricked" status. Screen turns on and you can access bootloader etc."
Is it fixable to get back to working condition? I wanna make for sure be for I buy it.
Click to expand...
Click to collapse
Doesn't sound bricked to me. I'd buy it for 70 and take your time figuring out how to get it working again.
tropical cactus said:
Doesn't sound bricked to me. I'd buy it for 70 and take your time figuring out how to get it working again.
Click to expand...
Click to collapse
Will do then was just curious 70 bucks isnt a bad deal at all.
germanguy45 said:
Will do then was just curious 70 bucks isnt a bad deal at all.
Click to expand...
Click to collapse
My opinion I would ask the owner if the bootloader is unlocked. If the owner is smart enough to know that the bootloader can be accessed then he or she can also tell you if it's unlocked and whether you will have the capability to flash anything to it or not. If the phone is in the boot loop of death you will at least need an unlocked bootloader to flash a fix.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
My opinion I would ask the owner if the bootloader is unlocked. If the owner is smart enough to know that the bootloader can be accessed then he or she can also tell you if it's unlocked and whether you will have the capability to flash anything to it or not. If the phone is in the boot loop of death you will at least need an unlocked bootloader to flash a fix.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok will do thank you for the good tip.
germanguy45 said:
Ok will do thank you for the good tip.
Click to expand...
Click to collapse
Also being able to access Recovery would be a good sign. If you you cannot access Recovery mode you cannot use ADB and is a tell tale sign of the BLOD.
The phone doesn't sound bricked. Even if the bootloader is locked as long as you can access it you should be able to sideload an OTA update which might get the phone working again. I think if your adb and fastboot binaries are up to date you can even sideload the entire factory image instead of just an OTA.