Related
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
I mistakenly deleted my Nexus 6P internal memory with TWRP. Now my phone turns on and gets stuck at Google logo.
I am able to go to recovery mode but it reboots again and gets stuck at Google.
When I try to reboot it, it asks me "There is not OS, do you still want to reboot?"
I am able to go to CMD in Windows and when I try to unlock the bootloader, it gives my error "Remote: boot loader can't be unlocked".
Is there any way to install the OS from scratch even the bootloader is locked.
I am not able to access the internal memory of my phone on Windows computer and there is no TWRP on my phone anymore.
Any suggestions are greatly appreciated.
Thanks
I would recommend looking at this guide, section 10 or 11. It will get you back to stock and from there you can start over with the TWRP, rooting, etc... Hopefully it'll at least get you back to a bootable OS and you'll have something to work with...
Thanks
Thanks buddy. I will try it
You won't be able to use those sections of my guide with a locked bootloader so don't bother. Check out section 13 though, that involves using adb sideload and the stock recovery to flash one of the full OTA zips.
Heisenberg said:
You won't be able to use those sections of my guide with a locked bootloader so don't bother. Check out section 13 though, that involves using adb sideload and the stock recovery to flash one of the full OTA zips.
Click to expand...
Click to collapse
Yeah I figured out that with locked boot loader, it doesn't work. I will try to see section 13.
Thanks for the tip.
umer221 said:
Yeah I figured out that with locked boot loader, it doesn't work. I will try to see section 13.
Thanks for the tip.
Click to expand...
Click to collapse
No worries, let me know how you go.
Heisenberg said:
You won't be able to use those sections of my guide with a locked bootloader so don't bother. Check out section 13 though, that involves using adb sideload and the stock recovery to flash one of the full OTA zips.
Click to expand...
Click to collapse
I am in a similar situation. My bootloader is unlocked however i cant get abd or fastboot to see the phone. tried on windows and linux. any suggestions?
ppbatman said:
I am in a similar situation. My bootloader is unlocked however i cant get abd or fastboot to see the phone. tried on windows and linux. any suggestions?
Click to expand...
Click to collapse
What Linux distro are you using? And how did you install adb/fastboot on it?
Heisenberg said:
What Linux distro are you using? And how did you install adb/fastboot on it?
Click to expand...
Click to collapse
I used a mac, sorry about that had a brain fart when typing that post. Installed using a guide on xda. tested it with a nexus 5x and worked fine.
Hi all,
let me first start by thanking the good people of xda community for your kind help and contribution. It would not be possible for people like me with extremely limited rooting knowledge to even have the courage to attempt a root if it wasn't for the good people like you here.
I just got my Axon 7 and is trying to work up the courage to attempt a root following tenfar's instruction (I'm extremely scared of bricking my new phone) I also hope that I can continue to play Pokemon Go after I root it, but unfortunately with the latest update, it seems impossible until I discovered Magisk. My question may seem fairly simple but it is extremely confusing to me. In Magisk's instruction it says that in order to install Magisk, one must remove any kind of root and systemless Xposed. Since my phone is not rooted, I do not have to go through the step of removing root and xposed? However, it says that I have to download Magisk and flash it. My confusion rests on the concept on how I can flash Magisk if my phone is not rooted? I thought one can only flash a rom etc after the phone is rooted? So should I follow tenfar's root first and root my axon 7 then try to flash Magisk? or the other way around? Any advice /tips/precautions/high level guides regarding both rooting using the tenfar method and flashing Magisk is greatly appreciate! I may suck at rooting and etc, but what I can do is follow all instructions carefully. Thank you everyone, you are the best!
To flash something (a ROM or an app, like Magisk) you need to have a custom recovery installed (such as TWRP, you boot into the custom recovery to flash the .zip file that contains whatever you want to flash) which generally means having an unlocked boot-loader, neither of those has anything to do with root (other than that they make rooting the phone considerably easier) they don't require it and they don't do it by themselves.
@Nameless One is right, you need a custom recovery (TWRP) to be able to flash Magisk. There is a thread about this in the forums.
However I would advise you to wait until next week when a new update is expected and perhaps some changes to the bootloader unlock policy and hopefully stock ROMs, which will make it much easier to solve any problems.
If you insist on going through with this now, you should take backup images of various partitions so that you can restore your phone to stock to receive the OTA.
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
KyJelly69 said:
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
Click to expand...
Click to collapse
It right on the top of their post
"This mod requires boot image modification, so unlocked bootloaders are required!"
What it does is implement it's own system-less root management module that will not be detected like other root methods. But will conflict with other root methods hence you have to be unrooted
Unlocked bootloader let's you flash custom recovery. That in turn let's you flash anything else including root modifications. In essence tenfar's boot image is modified to allow root. This will do something similar but you have to have the BL unlocked since patching boot image will change the signature.
iirc magisk alters the bootimage, so you need a unlocked Bootloader go get it to work.
And no, root is not a preq, you can use magisk to /aquire/ root though.
What u need:
- unlocked bootloader
- custom recovery
- a somewhat clean and not already modified system
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
projectseahorse said:
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
Click to expand...
Click to collapse
If you have copies of the stock images you will probably be able to fix your phone if something goes wrong and you want to go back to stock.
Not having these copies is like jumping out of a plane without a parachute and hoping you'll hit a haystack, without the pitchfork in it...
There are never any guarantees, every phone is different and as you are playing with important partitions there is a chance, generally through users fault, to brick your device...
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
projectseahorse said:
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
Click to expand...
Click to collapse
Well, the stock images have not been released for the B27 update, which would make it much easier to recover if something goes wrong. However, unofficial images are available (look around the forums). So at this point it is your call, just be careful.
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
roelmmata said:
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
Click to expand...
Click to collapse
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
roelmmata said:
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
Click to expand...
Click to collapse
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Click to expand...
Click to collapse
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
roelmmata said:
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
Click to expand...
Click to collapse
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
Thanks I try it out!
ultyrunner said:
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Click to expand...
Click to collapse
Hey again
I used guide specifically to go back to stock, combined with a couple times of wiping in stock recovery I finally got the phone to boot up! However I've learned something new, the phone will only stay on if I'm plugged into charger, and as soon as it's unplugged it turns off. Any other suggestions?
Like the title say, I'm getting ready to buy the T-Mobile version. I have read the conversion thread, but see others who say don't do that. I have a oneplus 3t but not a/b so I am confused lol
jamescable said:
Like the title say, I'm getting ready to buy the T-Mobile version. I have read the conversion thread, but see others who say don't do that. I have a oneplus 3t but not a/b so I am confused lol
Click to expand...
Click to collapse
I converted my 6t to the international version and have not had any issues in doing so. Don't quite understand why other users would advise not to do so. A plus to converting to the international rom allows you to easily unlock the bootloader and root the device of that's what you are looking to do.
elrey420 said:
I converted my 6t to the international version and have not had any issues in doing so. Don't quite understand why other users would advise not to do so. A plus to converting to the international rom allows you to easily unlock the bootloader and root the device of that's what you are looking to do.
Click to expand...
Click to collapse
Well, I have never used a a/b device before.....so I am very worried about the whole no permanent twrp
Don't worry about it you don't have to do anything with a or b slots just follow the instructions and you'll be fine
The a/b slots are nothing to worry about, as long as you follow the directions in the thread you'll be fine. There's an msm tool than can recover from any software failure if things go south. And for twrp, someone can correct me if I'm wrong but we have permanent twrp, at least I do
So, using the conversion tool is all I have to do to unlock bootloader and install ROMs like normal?
jamescable said:
So, using the conversion tool is all I have to do to unlock bootloader and install ROMs like normal?
Click to expand...
Click to collapse
Basically, yeah. Use this to do so. And for unlocking the bootloader extract the attached .rar file and run the .exe as administrator (you need ADB installed on your PC, OEM Unlocking enabled and USB Debugging Enabled for it to work) or use the command
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
For installing TWRP use this TWRP Installer (It also flashes Magisk), for installing custom ROMs use this guide.
_Masked_ said:
Basically, yeah. Use this to do so. And for unlocking the bootloader extract the attached .rar file and run the .exe as administrator (you need ADB installed on your PC, OEM Unlocking enabled and USB Debugging Enabled for it to work) or use the command
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
For installing TWRP use this TWRP Installer (It also flashes Magisk), for installing custom ROMs use this guide.
Click to expand...
Click to collapse
OK, and what about firmware? For the 3t, I have to have the updated firmware, is it the same for the 6t? And also, as I see, we have to use a computer for adb sideload everyyime we install a ROM?
jamescable said:
OK, and what about firmware? For the 3t, I have to have the updated firmware, is it the same for the 6t? And also, as I see, we have to use a computer for adb sideload everyyime we install a ROM?
Click to expand...
Click to collapse
No, the adb sideload was to bypass decryption issues, thanks (I forgot to update the guide). You don't need updated firmware.