Database Users

New N release 4/7/16

Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.

pospower said:
Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.
Click to expand...
Click to collapse
Hello pospower,
I hope you are new to the community, so first of all, welcome to the Nexus 6P section.
I advise you to read the sticky threads here at the section. First in the list would be: http://forum.xda-developers.com/nexus-6p/general/questions-section-t3214020
Over to your query now. Bootloader has no relation to rooting, except one, that it should be unlocked. Unlocking the bootloader will enable you to flash TWRP recovery, which in turn would be used to flash SuperSU v2.71 flash-able zip.
For detailed instructions, please refer to section #1, #2, and #6 in the following thread: [GUIDE] Unlock/Root/Flash for Nexus 6P
I hope this helps. Best regards.
DJBhardwaj

boot.img my bad i was refering to this below
Download the latest TWRP Recovery. Please note: if you're on MHC19I or above you must use TWRP 3.0.0-1 or above, otherwise TWRP won't be able to decrypt. Also, if you want to use TWRP with the Android N Developer Preview you must use TWRP 3.0.0-1 or above, and you must also flash the modified boot.img found here.

ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen

pospower said:
ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen
Click to expand...
Click to collapse
TWRP is having issues with encrypted filesystems right now. You can either flash TWRP v3.0.0 or decrypt your 6P.
The decryption process should be carried out just after you flash the modified boot.img.
To decrypt, you will need to connect your device in bootloader mode and enter the following command:
Code:
fastboot format userdata
(Please note that this will wipe your complete internal storage).

OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?

pospower said:
OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?
Click to expand...
Click to collapse
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?

DJBhardwaj said:
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?
Click to expand...
Click to collapse
I must have

pospower said:
I must have
Click to expand...
Click to collapse
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.

DJBhardwaj said:
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.
Click to expand...
Click to collapse
Yes this is what I did. Followed the steps exactly.

pospower said:
Yes this is what I did. Followed the steps exactly.
Click to expand...
Click to collapse
Give a try to v3.0.0-1, and let me know.

DJBhardwaj said:
Give a try to v3.0.0-1, and let me know.
Click to expand...
Click to collapse
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?

pospower said:
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?
Click to expand...
Click to collapse
If you don't mind doing it, I would say Yes!

reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg

pospower said:
reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg
Click to expand...
Click to collapse
That is weird. I have done the same thing like twice or thrice since the last two days, and it has worked like a charm.
If you're decrypted, TWRP v3.0.0-1 should work fine.
Are you sure you wiped complete storage using fastboot format userdata command?

Yes

pospower said:
Yes
Click to expand...
Click to collapse
Try switching to a different version of TWRP, and see if any one of them works for you.
v3.0.0-1, v3.0.1-0, or v3.0.2-0.

broke root?

So i just flashed android N and i think i broke root. Whne i try to boot into recovery it just hangs at the TWRP logo and i flashed su before and it doesnt appear to be on my page. Do i just revert stock or what do i do thanks. I was on pure rom and just flashed N over . Bootloader system and radio.

You have to decrypt the phone for Twrp to work on N Preview, it was like that since the first preview released.

Techno Peter said:
You have to decrypt the phone for Twrp to work on N Preview, it was like that since the first preview released.
Click to expand...
Click to collapse
how would i be able to do that

havy15 said:
how would i be able to do that
Click to expand...
Click to collapse
You need to fastboot modified boot img

Easy way out: Use TWRP 3.0.0.0 and adb sideload the SuperSU zipfile.

Bricked, bootloop tried all I can think of

I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P

maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t

Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...

maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?

v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image

maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?

v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image

I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.

maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.

same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?

mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"

maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...

5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.

DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...

We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.

5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful

so i'm going thru the same thing as OP.
I need help.

twrp gets erased

Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you

Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.

As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.

Or you can just root it and twrp won't erase with stock recover.

naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine

[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.

ahhh, ok I see. Thanks for the explanation.

Device boots only into fastboot after Magisk 22.0 update

I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?

Nikos2k said:
I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?
Click to expand...
Click to collapse
Try to re flash 21.4

Nameless Foe said:
Try to re flash 21.4
Click to expand...
Click to collapse
yes, but how?

Nikos2k said:
yes, but how?
Click to expand...
Click to collapse
Are you able to boot into fastboot mode?

Nameless Foe said:
Are you able to boot into fastboot mode?
Click to expand...
Click to collapse
Yes

Nikos2k said:
Yes
Click to expand...
Click to collapse
Are you able to flash the older version magisk through fast boot?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
Don't know how
Magisk 21.4 is a .zip file: Magisk 21.4
Is it possible to flash it through fastboot ?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
You might have to reset your phone via fastboot then flash the stock firmware

Nameless Foe said:
You might have to reset your phone via fastboot then flash the stock firmware
Click to expand...
Click to collapse
How can i reset it from fastboot?
And will I lose all my data?

Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.

Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.

Nikos2k said:
How can i reset it from fastboot?
And will I lose all my data?
Click to expand...
Click to collapse
Just use the MSM tool,, easier and risk free

wgs1028 said:
Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.
Click to expand...
Click to collapse
I didn't manage to restore it by just flashing boot.img
I then flashed all the image files from the output of payload dumper, but it didn't work either
Then wiped userdata (by using -w switch of fastboot), still no luck
Then changed active slot and flashed all the image files to that slot, and it booted successfully

dladz said:
Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.
Click to expand...
Click to collapse
i didn't manage to successfully boot it with the stock boot.img ...

Nikos2k said:
i didn't manage to successfully boot it with the stock boot.img ...
Click to expand...
Click to collapse
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required

dladz said:
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required
Click to expand...
Click to collapse
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Then did you try safe mode

Add bookmark
#45
For the Oneplus 8 pro with 11.0.4.4.IN11AA I had to get a boot.img (for 11.0.4.4IN11AA) and flashed it with adb via fastboot (from PC), then my phone started up without root but still unlocked (and none of my data was lost). I reinstalled Magisk 22.0 (apk) and then put the boot.img on my sdcard and used Magisk to patch my boot.img and then i booted into fastboot and and flashed the patched boot.img via adb fastboot(from my PC). I never orginally had Magisk hidden so not sure why my phone lost root after the Magisk 22.0 update. Hopefully this helps someone onto the right path.

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK

dladz said:
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK
Click to expand...
Click to collapse
No no, i installed them to their respective partitions
Like a total firmware reset