Hello. I want to downgrade my Nexus from 7.0 to 5.0 so i can use xposed again. Can i just flash a 5.0 rom or do i have to flash to the images using a PC?
Sent from my Nexus 6 using XDA-Developers Legacy app
If you have TWRP installed, you can download the 5.0 image to the phone and restart in recovery.
If you don't have an alternative recovery on your Nexus 6, then you'll hav eto flash from a PC via USB with the adb/fastboot from Google.
AdriK said:
If you have TWRP installed, you can download the 5.0 image to the phone and restart in recovery.
If you don't have an alternative recovery on your Nexus 6, then you'll hav eto flash from a PC via USB with the adb/fastboot from Google.
Click to expand...
Click to collapse
Thanks I'll try that
Sent from my Nexus 6 using XDA-Developers Legacy app
AtrX said:
Thanks I'll try that
Click to expand...
Click to collapse
Hello just be careful with flashing 5.0 bootloader... Not 100% sure but it may brick your phone. Just search a bit more before you downgrade...
Good luck...
Just a link: https://forum.xda-developers.com/showpost.php?p=59506417&postcount=5
Cheers...
5.1 said:
Hello just be careful with flashing 5.0 bootloader... Not 100% sure but it may brick your phone. Just search a bit more before you downgrade...
Good luck...
Just a link: https://forum.xda-developers.com/showpost.php?p=59506417&postcount=5
Cheers...
Click to expand...
Click to collapse
Thanks!
Sent from my Nexus 6 using XDA-Developers Legacy app
You can downgrade... just download factory image 5.1.1 then flash it via adb.
i don't Recommend xposed, but if you want, just flash it.
If you want xposed, why don't you use Marshmallow? Xposed is available (heck, even systemless xposed with Magisk).
To clear up any confusion, you can keep your phone on the latest TWRP recovery, bootloader, and radio and just flash any older ROM no matter if it's based on N, M, or L. Doing an entire factory image is 100% not necessary. If you flash the whole factory image from Google you will wind up with outdated bootloader and radio, and also you will have to put TWRP on it again as it will replace the recovery with stock recovery.
Mr.Sugo said:
You can downgrade... just download factory image 5.1.1 then flash it via adb.
i don't Recommend xposed, but if you want, just flash it.
Click to expand...
Click to collapse
I don't know if it's the case, but if partition table changed with 6.x or 7.x and he downgrades, he could brick it... I remember I saw some reports in the past... Not sure if it was only 5.0 or also 5.1 bootloader...
Cheers...
Dopamin3 said:
If you want xposed, why don't you use Marshmallow? Xposed is available (heck, even systemless xposed with Magisk).
To clear up any confusion, you can keep your phone on the latest TWRP recovery, bootloader, and radio and just flash any older ROM no matter if it's based on N, M, or L. Doing an entire factory image is 100% not necessary. If you flash the whole factory image from Google you will wind up with outdated bootloader and radio, and also you will have to put TWRP on it again as it will replace the recovery with stock recovery.
Click to expand...
Click to collapse
I totally agree - downgrade to 6.0.1, not 5.1.1 - xposed is available for Marshmallow, no need to step back all the way to Lollipop.
Fvolfrine said:
I totally agree - downgrade to 6.0.1, not 5.1.1 - xposed is available for Marshmallow, no need to step back all the way to Lollipop.
Click to expand...
Click to collapse
Cool. Thanks for the great support.
Sent from my Nexus 6 using XDA-Developers Legacy app
I tried installing 6.0.1 yesterday but the installationwizard stopped repeatedly so i restored my backup. I extracted boot.img and system.img from the rom should i install those?
Sent from my Nexus 6 using XDA-Developers Legacy app
AtrX said:
I tried installing 6.0.1 yesterday but the installationwizard stopped repeatedly so i restored my backup. I extracted boot.img and system.img from the rom should i install those?
Click to expand...
Click to collapse
Should be enough... Do a factory reset afterward. 7.x.x datas may be incompatible...
Good luck...
AtrX said:
I tried installing 6.0.1 yesterday but the installationwizard stopped repeatedly so i restored my backup. I extracted boot.img and system.img from the rom should i install those?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Try the 6.0.1 from here https://forum.xda-developers.com/nexus-6/development/rom-leanrom-1-5mv-stock-rooted-t3452720
AtrX said:
I tried installing 6.0.1 yesterday but the installationwizard stopped repeatedly so i restored my backup. I extracted boot.img and system.img from the rom should i install those?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did you do a clean flash? Like wiping all paritions in TWRP except internal storage. If you don't you're gonna have a bad time.
5.1 said:
I don't know if it's the case, but if partition table changed with 6.x or 7.x and he downgrades, he could brick it... I remember I saw some reports in the past... Not sure if it was only 5.0 or also 5.1 bootloader...
Cheers...
Click to expand...
Click to collapse
I recently flashed on my Nexus 6 Pac-Rom 5.1, just for fun, and is working good.
Mr.Sugo said:
I recently flashed on my Nexus 6 Pac-Rom 5.1, just for fun, and is working good.
Click to expand...
Click to collapse
Hello... Have you flashed 5.0 bootloader? The rest of a 5.x is not the problem...
Cheers...
5.1 said:
Hello... Have you flashed 5.0 bootloader? The rest of a 5.x is not the problem...
Nope, i just flashed the rom via TWRP.
Click to expand...
Click to collapse
Latest bootloaders and radios are backward compatible with 5.0, 5.1, 6.0.1, 7.0, 7.1.1, 7.1.2, etc.
Related
Hi, I have an unlocked Nexus 6 bought direct from Google. Somehow it became the AT&T version of 5.1.1 (LMY48W). This means that there is currently no OTA upgrade to Android 6.0 Marshmallow for LMY48W.
However, as there is an upgrade to 6.0 from LMY48T, it is possible to either:
Edit the build.prop to trick the update –*and would this cause any problems?
Change my Nexus 6 to LMY48T some other official way?
1 - I wouldn't.
2 - Yes, by flashing a factory image, but in that case you might as well just move straight to Marshmallow. If you don't want to wipe your phone, just skip flashing the userdata image.
(There's a bunch of guides for this, search or check the stickies.)
1. Even if it did download an update, it wouldn't do anything but cause problems for you as the file verification would fail.
2. Why don't you just download the official factory image for Marshmallow and flash it via fastboot?
imnuts said:
1. Even if it did download an update, it wouldn't do anything but cause problems for you as the file verification would fail.
2. Why don't you just download the official factory image for Marshmallow and flash it via fastboot?
Click to expand...
Click to collapse
im on cm12.1 can i just flash the factory image using wugs toolkit?
Thanks, flashing all except userdata.img worked.
Thanks!
"Recordar es vivir"
reyscott1968 said:
im on cm12.1 can i just flash the factory image using wugs toolkit?
Click to expand...
Click to collapse
It doesn't take much to do it manually. Learn to do things without a toolkit and you'll be much better off.
Sent from my Nexus 6
imnuts said:
It doesn't take much to do it manually. Learn to do things without a toolkit and you'll be much better off.
Sent from my Nexus 6
Click to expand...
Click to collapse
adb and fastfoot will become your bestfriends:good:
This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?
Thanks My Brother ?
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.
krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).
This is a Safe Upgrade to the latest 6.0.1 firmware (N910VVRU2CPD1) for VZW Samsung Galaxy Note 4 (SM-N910V).
YOU NEED TO UPGRADE THE BOOTLOADER AND UNLOCK IT
★ Disclaimer:THIS SERVICE IS FREE OF CHARGE, USE IT AT YOUR OWN RISK, TAKE IT OR LEAVE IT !
★ Instructions:
Follow the instructions here to upgrade and unlock the bootloader
Extract the N910VVRU2CPD1_StockRestore.tar.md5 file using 7-Zip
Extract Odin v3.11.1 & open it
Reboot to Download Mode (press and hold Home + Power + Volume Down)
Connect phone and wait until you get a blue sign in Odin
Add the N910VVRU2CPD1_StockRestore.tar.md5 file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back & wait a few minutes
Reboot into recovery (press and hold Home + Power + Volume Up)
Wipe data (Factory Reset)
Reboot to system
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
N910VVRU2CPD1 Stock Restore: N910VVRU2CPD1_StockRestore.tar.md5.7z
md5: a9fa3e15729474955bee6e42a1cc86b8
Click to expand...
Click to collapse
Hi , I already unlocked my phone bootloader on the 5.1.1 firmware , do I now odin directly the N910VVRU2CPD1_StockRestore.tar.md5 and all set .
thanks
machhho said:
Hi , I already unlocked my phone bootloader on the 5.1.1 firmware , do I now odin directly the N910VVRU2CPD1_StockRestore.tar.md5 and all set .
thanks
Click to expand...
Click to collapse
No, you must upgrade to the marshmallow bootloader and unlock that one by following the directions in hsbadr's other thread. Then you flash the Stock Restore in Odin.
So i have a developer edition, can i just odin this and go? or do i have to install and unlock a bootloader as well? root/unlocking took so long i didnt keep up.
Is the safe upgrade PD1 rom is Pre-rooted.
buhohitr said:
Is the safe upgrade PD1 rom is Pre-rooted.
Click to expand...
Click to collapse
It probably isn't, since it's not a custom ROM but just a set of Stock firmware files.
Gravemoss42 said:
So i have a developer edition, can i just odin this and go? or do i have to install and unlock a bootloader as well? root/unlocking took so long i didnt keep up.
Click to expand...
Click to collapse
The only time you guys can flash directly any MM ROM is when you already on MM Unlocked bootloader and rooted. If you are on 5.1.1 Unlocked and rooted, you have to follow the OP instructions, doesn't matter if you have retails or Dev Edition.
And here we go.
Anyone have any recommendations on how to backup my Android install before I flash this?
FMXP said:
And here we go.
Anyone have any recommendations on how to backup my Android install before I flash this?
Click to expand...
Click to collapse
Are you rooted? You should be able to backup in recovery if you are.
This won't replace Recovery, right?
---------- Post added at 02:54 AM ---------- Previous post was at 02:19 AM ----------
The first link goes to the BPA1 download. I didn't notice, and ended up waiting about 30 minutes for it to download before I saw it .
This method is exclusively for Developer Editions, right? Retail users have to follow the steps listed in this thread? Otherwise both methods get users to CPD1?
Never mind, I see it says Retail/Dev in the thread title...
Missing Applications Manager?
So I went through this process twice, the first time because wifi wasn't working and the application manager (Settings -> Application) was missing.
On the second shot, wifi was working again, but I'm still missing the app manager.
Where I expect Applications, I see Application Settings (the part where you can set the default program, etc.)
Did this happened to anyone else?
Anyone have a fix for this?
I have a developer edition Note 4 and am currently on 4.4.4 ANJ5. If I upgrade to CPD1, can I safely downgrade to any prior release (4.4, 5.0, 5.1, etc.)?
Would I follow the same process as going from 4.4 to 5.1 and vice versa?
I've found that I like 4.4 better than any of the 5.0 ROM's, but I want to try 6.0 now that it is out.
Thank in advance for your help!
I'm curious as anyone been able to root this.
Sent from my SM-N910V using Tapatalk
dkahs23 said:
I'm curious as anyone been able to root this.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
If you unlock it and install twrp, you can try flashing SuperSu then. But if you root the stock rom it might not boot, that was the case with LL. Had to flash custom kernel.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
tolymatev said:
If you unlock it and install twrp, you can try flashing SuperSu then. But if you root the stock rom it might not boot, that was the case with LL. Had to flash custom kernel.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm on stock LL now unlocked BL and rooted retail edition. I didn't know if king root would work
Sent from my SM-N910V using Tapatalk
dkahs23 said:
I'm on stock LL now unlocked BL and rooted retail edition. I didn't know if king root would work
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Kingoroot will work but you have to follow this guide http://forum.xda-developers.com/showthread.php?t=3398144
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Well I am on MM via this way and have Retail version w/developer mode with boot loader unlock and twrp installed but cannot get root via kingroot. So I flashed SuperSu. And still no root
dkahs23 said:
Well I am on MM via this way and have Retail version w/developer mode with boot loader unlock and twrp installed but cannot get root via kingroot. So I flashed SuperSu. And still no root
Click to expand...
Click to collapse
If you use the Jasmine ROM v6.0.1 by hsbadr - which is almost like stock MM - you can get root. Jasmine ROM has the custom Multisystem kernel for MM to root.
---------- Post added at 02:01 AM ---------- Previous post was at 01:53 AM ----------
gowronshammer said:
So I went through this process twice, the first time because wifi wasn't working and the application manager (Settings -> Application) was missing.
On the second shot, wifi was working again, but I'm still missing the app manager.
Where I expect Applications, I see Application Settings (the part where you can set the default program, etc.)
Did this happened to anyone else?
Anyone have a fix for this?
Click to expand...
Click to collapse
Did you get Wifi back?
chappatti said:
If you use the Jasmine ROM v6.0.1 by hsbadr - which is almost like stock MM - you can get root. Jasmine ROM has the custom Multisystem kernel for MM to root.
---------- Post added at 02:01 AM ---------- Previous post was at 01:53 AM ----------
Did you get Wifi back?
Click to expand...
Click to collapse
I did, but not with the Applications manager. After going ODIN back to 5.1.1, unlocking and upgrading the bootloader and then applying the MM Safe upgrade, twice, I got wifi, but not Applications manager.
I ended up using the full firmware found here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 and just flashing straight to 6.0.1.
I don't have root, a locked boot loader, complaints about dm-verity and DRK in recovery mode, but I have a working MM with Wifi and Applications manager and Android Pay.
I'm happy at the moment, thanks for the help.
I tried to root my huawei p8 lite which runs on marshmallow but it got stuck at boot. Even after formatting it through custom recovery didnt fix it . I was force to do update through my sd card and lost all data . Now the phone works fine. But doesnt have root access. I was able to root the lollipop veraion of the device thru adb. But when it come to marshmallow am unable to root.
Sent from my ALE-L21 using XDA-Developers mobile app
nayeemudheen said:
I tried to root my huawei p8 lite which runs on marshmallow but it got stuck at boot. Even after formatting it through custom recovery didnt fix it . I was force to do update through my sd card and lost all data . Now the phone works fine. But doesnt have root access. I was able to root the lollipop veraion of the device thru adb. But when it come to marshmallow am unable to root.
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Here you go just follow the instructions.
also wrong section must be in Q&A
Lordbannakaffalatta said:
Here you go just follow the instructions.
also wrong section must be in Q&A
Click to expand...
Click to collapse
i tried the method you said but my device got bootloop.
Sent from my ALE-L21 using XDA-Developers mobile app
nayeemudheen said:
i tried the method you said but my device got bootloop.
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
ok then, some questions...
what model do you have? (ALE-L21, Ale-L02 oe ALE-L23)
what build number do you have?
and wich version did you use also did you got your bootloader unlocked and twrp installed?
Hi!
I've tried to root my P8 lite (ALE-L21 B564, MM ) and I stuck at bootloop. I reflashed my boot img, system img, recovery img, and now the phone is working fine. I tried also every oneclick root solution, no one works so far.
Lordbannakaffalatta said:
ok then, some questions...
what model do you have? (ALE-L21, Ale-L02 oe ALE-L23)
what build number do you have?
and wich version did you use also did you got your bootloader unlocked and twrp installed?
Click to expand...
Click to collapse
ALE-L21 BUILD NO. C185B525 marshmallow 6.0
Sent from my ALE-L21 using XDA-Developers mobile app
Szabi01 said:
Hi!
I've tried to root my P8 lite (ALE-L21 B564, MM ) and I stuck at bootloop. I reflashed my boot img, system img, recovery img, and now the phone is working fine. I tried also every oneclick root solution, no one works so far.
Click to expand...
Click to collapse
see the link that is gave a few posts back
nayeemudheen said:
ALE-L21 BUILD NO. C185B525 marshmallow 6.0
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
there's your problem... your still on beta version. we're on B564 already (single b565)
try doing an ota
if that doesn't work try doing a local update or go into the thread and follow the unbricking chapter or the converting chapter
Lordbannakaffalatta said:
see the link that is gave a few posts back
there's your problem... your still on beta version. we're on B564 already (single b565)
try doing an ota
if that doesn't work try doing a local update or go into the thread and follow the unbricking chapter or the converting chapter
Click to expand...
Click to collapse
So, this won't **** up my device completely, I guess. I'm gonna try it later, THX.
Edit: I've did it succesfully, many thanks to you!
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Yep I rooted just fine. works ok.
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
yudumcan said:
Yep I rooted just fine. works ok.
Click to expand...
Click to collapse
pkgnex said:
I had no problems with the latest version, which I installed last night (downloaded factory image, extracted to PC and fastboot flashed through bootloader, rebooted to recovery and flashed SuperSU 2.78-SR1).
Click to expand...
Click to collapse
Perfect. Flashed and working great. Thank you! :good:
If you enjoy having an unknown organization having absolute godlike control over your phone, then sure, use stupidsu.
But if you like to have auditable and sane control over your own device, I would very VERY much suggest that you instead use https://github.com/seSuperuser/AOSP-SU-PATCH
Nucleotide said:
I can't seem to find the answer to this.
I've just flashed the Nougat Factory image for Nexus 6 and want root. Can anyone confirm is the latest SuperSU is compatible? I've flashed TWRP and downloaded the latest SuperSU but just a little hesitant to flash it in case of issues.
Thanks a lot.
Click to expand...
Click to collapse
I flashed factory image today and went to Nexus Root Toolkit to root and flash recovery. It went well.
new to Nexus 6, just got Nougat OTA, whats the best way to root and have double tap to wake (will it drain battery big time?) and notification led? pls help, tia
btw I use Mac
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Isn't the nexus 6 supposed to be 100% stock Android and with that being able to be rooted by any root method? I know I've read many times that if you want to get into root and hacking to pick up a nexus device as they were easily recoverable and weren't root blocked by any means
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
Not sure what exactly you're asking but the Nexus 6 is easily rooted when using the proper methods. Unlock the bootloader, fastboot flash TWRP recovery and then flash SuperSU or Magisk in TWRP.