Nandroid Backup - Nexus 6P Q&A, Help & Troubleshooting

Hello people I have returned back to this faithful site and I am rocking a Nexus 6p since November but after sticking with stock which I partially don't mind I'm just butthurt about one thing and one thing only. There is no specific app out there or even adb backup that does the job like nandroid does.
No my questions are...
Before you could boot into custom recovery without actually flashing the .IMG file is it the same with 6.0 with the locked bootloader?
Second is does unlocking the bootloader wipe the device?
Thanks in advance guys
Sent from my Nexus 6P using XDA-Developers mobile app

Aamir.Badat said:
Hello people I have returned back to this faithful site and I am rocking a Nexus 6p since November but after sticking with stock which I partially don't mind I'm just butthurt about one thing and one thing only. There is no specific app out there or even adb backup that does the job like nandroid does.
No my questions are...
Before you could boot into custom recovery without actually flashing the .IMG file is it the same with 6.0 with the locked bootloader?
Second is does unlocking the bootloader wipe the device?
Thanks in advance guys
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
You need to unlock the bootloader for custom recovery and it will erase the device.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Related

[Q] Unroot back to stock for warranty

In searching through the Development threads about rooting, I didn't really see a concise answer to this.
If I root using a method from Development - say SuperRoot from paulobrien, can I unroot back to stock say for warranty purposes? I'm all for rooting and trying the ROMs already out for us (thank you to those that have gotten this ball rolling fast already!!), but I've seen some low build quality issues from friends and want the ability to return this if necessary.
Google already has the factory images posted. Been up for a while. Flash em and relock bootloader
Download the stock Nexus 7 image and go into the recovery mode on your Nexus 7. Then extract the stock image file and the scripts inside the same archive. Use these scripts to restore back to stock, and use fastboot oem lock to lock it up when you're done.
Now it'll be exactly as it was from Google.
Even if you return to root, google can still detect that the device has been rooted.
Sent from my Nexus S 4G using Tapatalk 2
elias0441 said:
Even if you return to root, google can still detect that the device has been rooted.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
When you stock and lock, there won't won't be warranty issues.
Sent from my Nexus 7 using xda app-developers app

Flash Stock ROM on Rooted Nexus 7

I have rooted and unlocked the bootloader of my N7 and installed cm10. Now I want to go back and reflash the Stock ROM. Can someone outline me the exact steps?
I've used the Nexus 7 Toolkit and selected option 9 to flash the Stock ROM but it didnt work..
binarydrummer said:
I have rooted and unlocked the bootloader of my N7 and installed cm10. Now I want to go back and reflash the Stock ROM. Can someone outline me the exact steps?
I've used the Nexus 7 Toolkit and selected option 9 to flash the Stock ROM but it didnt work..
Click to expand...
Click to collapse
Use the Toolkit, option 9
http://forum.xda-developers.com/showthread.php?p=29637670
Sent from my Nexus 7 using Tapatalk 2
heyodee said:
Use the Toolkit, option 9
http://forum.xda-developers.com/showthread.php?p=29637670
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I just used Nexus Root Toolkit instead and it worked. I selected the option: "flash stock and unroot". So I am guessing that I went back to stock JB 4.1.1 and the only thing needed is to root using the same tool?
I'm in a similar situation, but I rooted/unlocked manually on a MAC.
Flashed to a ROM but would prefer to flash back to the original one.
pmgreen said:
I'm in a similar situation, but I rooted/unlocked manually on a MAC.
Flashed to a ROM but would prefer to flash back to the original one.
Click to expand...
Click to collapse
+1
Guys. Take 5 minutes and learn some basic fast boot and adb commands. Then this kind of stuff will seem trivial.... Stop acting helpless and learn something here
Sent from my Galaxy Nexus
Pirateghost said:
Guys. Take 5 minutes and learn some basic fast boot and adb commands. Then this kind of stuff will seem trivial.... Stop acting helpless and learn something here
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Your point is right, but the delivery is wrong. All of us were noobs at some point and asked questions that seemed trivial to the more experienced HUMANS in the community.
True, we should all look around the forums and read, but, that's not the way to answer to people looking to incur into the flashng, dev, modding community.
Just saying, no offense meant.

Any reason to unlock the bootloader?

My Nexus 7 (2013) will be arriving today. I unlocked the bootloader on my Galaxy Nexus to flash TAKJU, since the Canadian version of Android was updated by Samsung (a dumb situation that delayed updates), so it made sense to unlock.
I don't flash ROMs or tinker in any way - I only want the device to have the latest version of stock Android. Is there any compelling reason to unlock the bootloader of the Nexus 7, before I start loading my apps and configure my Google accounts?
I suppose if I leave it locked the device will have greater security.
I think the best reason is so you can flash custom recovery and make backups. You could also root and do all the good things that come with that.
Sent from my SCH-I535 using Tapatalk 4
Reasons for me:
+ Titanium Backup
+ Browser replacement (to stock browser, not chrome)
+ Custom Recovery (for backup and restoring)
I have the LTE version, so therefore there is no custom rom yet.
I just unlocked the bootloader to temporary boot TWRP and create a Nandroid backup.
nex86 said:
Reasons for me:
+ Titanium Backup
+ Browser replacement (to stock browser, not chrome)
+ Custom Recovery (for backup and restoring)
I have the LTE version, so therefore there is no custom rom yet.
I just unlocked the bootloader to temporary boot TWRP and create a Nandroid backup.
Click to expand...
Click to collapse
How can you have a LTE version its not sold yet?
Sent from my Nexus 7 using Tapatalk 4
Andrew149 said:
How can you have a LTE version its not sold yet?
Click to expand...
Click to collapse
Available in Europe.
Most unlock to install/try different ROMs. Also, recall that when you do unlock at a later time, it does wipe your device; so may be worthwhile to unlock right now while you're still setting it up so you don't have to go through that again.
ChrisAG said:
My Nexus 7 (2013) will be arriving today. I unlocked the bootloader on my Galaxy Nexus to flash TAKJU, since the Canadian version of Android was updated by Samsung (a dumb situation that delayed updates), so it made sense to unlock.
I don't flash ROMs or tinker in any way - I only want the device to have the latest version of stock Android. Is there any compelling reason to unlock the bootloader of the Nexus 7, before I start loading my apps and configure my Google accounts?
I suppose if I leave it locked the device will have greater security.
Click to expand...
Click to collapse
1) unlocking process will trigger factory reset for security, so best to do it before you install everything, if you will ever need it in the future
2) even if you never root or make any changes, one day you will probably need to restore factory images, in which case you'll need to be unlocked
I think the main reason is the erase that unlocking causes. If you unlock right away, you don't lose anything or need to back and restore sdcard, etc.
Good answers so far, plus I also unlock in order to flash OTA updates as soon as they are linked to in this forum.
Sent from my Nexus 10 using Tapatalk 4
Well there aren't any reasons on not to do it?
Sent from my Nexus 7 using Tapatalk 4
Someone can bypass your lockscreen.
sfhub said:
Someone can bypass your lockscreen.
Click to expand...
Click to collapse
Not a problem: I have the lock screen turned off too .
Best reason to unlock your bootloader asap:
So you don't have to lose all your data later if you decide to root.
Unlocking your bootloader will wipe all your data but effectively doesn't do anything so you still get OTA updates and 100% stock.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Enables you to use apps such as adaway and LMT...
Sent from my Nexus 7 using Tapatalk 4
nex86 said:
Reasons for me:
+ Titanium Backup
+ Browser replacement (to stock browser, not chrome)
+ Custom Recovery (for backup and restoring)
I have the LTE version, so therefore there is no custom rom yet.
I just unlocked the bootloader to temporary boot TWRP and create a Nandroid backup.
Click to expand...
Click to collapse
Done need to unlock to get the stock browser anymore heres the thread about http://forum.xda-developers.com/showthread.php?t=2385928
Sent from my Nexus 7 using xda premium
nex86 said:
Reasons for me:
+ Titanium Backup
+ Browser replacement (to stock browser, not chrome)
+ Custom Recovery (for backup and restoring)
I have the LTE version, so therefore there is no custom rom yet.
I just unlocked the bootloader to temporary boot TWRP and create a Nandroid backup.
Click to expand...
Click to collapse
Is unlocking bootloader necessary to root Nexus 7? Can I just root the N7 without unlock?
Sent from my ST25i using xda app-developers app
Kumczak said:
Is unlocking bootloader necessary to root Nexus 7? Can I just root the N7 without unlock?
Click to expand...
Click to collapse
Yes, must unlock bootloader or the system partition is write protected and any root you tried to install would be lost at next reboot.

Pure AOSP for Locked Bootloader?

I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?

Does this mean root on Marshallow will not be as easy as ADB?

http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
I just read this and the part that stuck out the most to me was this.
"If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image."
Does this have anyone else concerned? I was excited to get back into the Nexus game so I could power on my new 6P and be rooted 10 minutes later.
It will not. You need a custom kernel. It's fine, someone made a modified boot which is stock and just permissive, easy sauce
Sent from my Nexus 6 using Tapatalk
No worries! I just flashed the modified boot image and then Super SU 2.50 and after that the kernel I wanted to use on my Nexus 9! Everything went fast with TWRP
Big Cam said:
http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
I just read this and the part that stuck out the most to me was this.
"If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image."
Does this have anyone else concerned? I was excited to get back into the Nexus game so I could power on my new 6P and be rooted 10 minutes later.
Click to expand...
Click to collapse
Nexus 5X/6P allow the unlocking of the bootloader.
The article has no effect on rooting a Nexus device. It may have ramifications for locked down devices.
tech_head said:
Nexus 5X/6P allow the unlocking of the bootloader.
The article has no effect on rooting a Nexus device. It may have ramifications for locked down devices.
Click to expand...
Click to collapse
That's not quite true I'm afraid, even nexus devices will need a modified boot image too now
Sent from my Nexus 6 using Tapatalk
It's a nexus. Nuff said.
I got root on stock Marshmallow. Flashed hells-Core and SuperSU 2.49 using TWRP. As soon as I hit "reboot system" TWRP said it noticed I had an unmodified boot image and offered to modify it for me. I allowed it to and it's been working fine for 36 hours now.
Sent from my Nexus 6 using XDA Free mobile app
dadsterflip said:
It's a nexus. Nuff said.
Click to expand...
Click to collapse
^^This.^^
Info
Big Cam said:
http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
I just read this and the part that stuck out the most to me was this.
"If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image."
Does this have anyone else concerned? I was excited to get back into the Nexus game so I could power on my new 6P and be rooted 10 minutes later.
Click to expand...
Click to collapse
Yes you can root it but one more step u need to do for complete root access
they won't do anything to completely disable root and unlocking bootloader cause it s Open Source
u should do adb unlock for bootloader and then install boot img in fastboot and u good to do more...
:good:
As others have said - no need to worry.
I'm running Marshmallow rooted, works perfect.
This is only an issue with devices that have bootloaders that can't be unlocked. For now.

Categories

Resources