Related
I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
341464 said:
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Heisenberg said:
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Click to expand...
Click to collapse
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
341464 said:
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
There are two versions, the traditional version, and the systemless version.
Heisenberg said:
There are two versions, the traditional version, and the systemless version.
Click to expand...
Click to collapse
Speaking of OTA and systemless. I have opted for the systemless root method. If I want to install an OTA, all I have to do is flash the stock boot image, install update, then re root correct? Assuming there are no changes to system?
Sent from my Nexus 6P using Tapatalk
Came across this article. Did not see it mentioned in the general forum. Thought I would share. This allows users to flash otas on both locked and unlocked bootloader.
http://www.androidpolice.com/2016/0...s-for-nexus-devices-alongside-factory-images/
Sent from my Nexus 6 using XDA-Developers mobile app
this now is everywhere, my question is... can I flash ota with stock recovery? there is a option on stock recovery that says: "apply update from sdcard"
my n6 is bootloader unlocked but the rest is stock.
I am forced to do this because all I have is chromebook/box and no pc. So I can install adb. as everyone here knows chromebooks are made by the very same Google, but I guess adb department hates chromeos department
hormosapiens said:
this now is everywhere, my question is... can I flash ota with stock recovery? there is a option on stock recovery that says: "apply update from sdcard"
my n6 is bootloader unlocked but the rest is stock.
I am forced to do this because all I have is chromebook/box and no pc. So I can install adb. as everyone here knows chromebooks are made by the very same Google, but I guess adb department hates chromeos department
Click to expand...
Click to collapse
You can flash a newer build OTA using adb with stock recovery.
You cannot flash an older build OTA than you are currently running (it checks the build date, even in these new full OTAs).
You cannot sideload from SD card due to storage encryption.
xdatastic said:
You can flash a newer build OTA using adb with stock recovery.
You cannot flash an older build OTA than you are currently running (it checks the build date, even in these new full OTAs).
You cannot sideload from SD card due to storage encryption.
Click to expand...
Click to collapse
I thought maybe I can put the new ota one my sdcard/download folder and flash it from stock recovery using the option "apply update from sdcard".
you say because my n6 is encrypted it wouldn't work. right?
I hate to crouton just for flashing android images...
thanks
hormosapiens said:
I thought maybe I can put the new ota one my sdcard/download folder and flash it from stock recovery using the option "apply update from sdcard".
you say because my n6 is encrypted it wouldn't work. right?
I hate to crouton just for flashing android images...
thanks
Click to expand...
Click to collapse
Yeah, the option is there for sideload from sdcard, but it wont work on the N6. You need to use ADB from a computer.
Wonder if people can flash this that managed to lock their bootloader with a non booting device and can't get into Android to tick the box to allow unlocks?
Could be a fix to the permanent soft brick with no recovery.
Since it's signed the stock recovery should flash it with a sideload.
Sent from my Nexus 7 using Tapatalk
These are full system images, thus they can be used to recover from soft bricks with a locked bootloader. Just like the N Preview could be used for that purpose.
Anyone decipher the preferred radio for each carrier out of the May releases?
So... a couple of questions:
If I have a rooted nexus 6 with TWRP and use adb to sideload this ota:
Do I still have TWRP after the sideload?
Do I still have all my phone "data" - sms, mms, call logs, pictures, apps, etc?
Then do I re-root the phone with TWRP and supersu file?
Thanks
Johnnyrocket said:
So... a couple of questions:
If I have a rooted nexus 6 with TWRP and use adb to sideload this ota:
Do I still have TWRP after the sideload?
Do I still have all my phone "data" - sms, mms, call logs, pictures, apps, etc?
Then do I re-root the phone with TWRP and supersu file?
Thanks
Click to expand...
Click to collapse
I'm guessing you're out of luck... Normally an OTA verifies the system before flashing. If you're not stock, it won't flash. Might be different with these new OTAs, you never know until you've tried.
Johnnyrocket said:
So... a couple of questions:
If I have a rooted nexus 6 with TWRP and use adb to sideload this ota:
Do I still have TWRP after the sideload?
Do I still have all my phone "data" - sms, mms, call logs, pictures, apps, etc?
Then do I re-root the phone with TWRP and supersu file?
Thanks
Click to expand...
Click to collapse
Didgeridoohan said:
I'm guessing you're out of luck... Normally an OTA verifies the system before flashing. If you're not stock, it won't flash. Might be different with these new OTAs, you never know until you've tried.
Click to expand...
Click to collapse
Let's see what files are inside the OTA, if you have userdata.img you can bet your android-a** it will delete your data. If it has recovery.img, apply the same to TWRP.
Don't know if I'm 100% right on this so please don't quote me haha
benleonheart said:
Let's see what files are inside the OTA, if you have userdata.img you can bet your android-a** it will delete your data. If it has recovery.img, apply the same to TWRP.
Don't know if I'm 100% right on this so please don't quote me haha
Click to expand...
Click to collapse
Just extract the ota and flash image files with twrp
Sent from my Nexus 6 using XDA Free mobile app
Unlike normal incremental OTAs that verify current partition contents, these full block mode OTAs unconditionally over write all partitions except userdata and possibly cache. Probably a good idea to wipe cache prior to sideloading one.
I don't think TWRP has the ability to sideload a stock Google OTA, but if it does, TWRP will be gone afterwards as the full block mode OTA will over write the recovery partition with stock android recovery.
Every device I've ever had has been bootloader-unlocked and rooted within hours of receiving it.
However, with the Nexus 6P, I didn't think the hassle of losing android pay and OTA updates was worth it since the device works so well as stock.
I've seen the posts about porting the Pixel-exclusive features to the 6P via build.prop edits. However, as far as I'm aware, changes to the system partition break both of the above.
Is there a way to modify system files like build.prop without breaking OTA updates and Android Pay?
chrispy_212 said:
Every device I've ever had has been bootloader-unlocked and rooted within hours of receiving it.
However, with the Nexus 6P, I didn't think the hassle of losing android pay and OTA updates was worth it since the device works so well as stock.
I've seen the posts about porting the Pixel-exclusive features to the 6P via build.prop edits. However, as far as I'm aware, changes to the system partition break both of the above.
Is there a way to modify system files like build.prop without breaking OTA updates and Android Pay?
Click to expand...
Click to collapse
It's not just modification to the system partition alone. It has to be specific modifications.
build.prop may be one of those but, I have modified multiple files and that didn't kill safetynet checks.
I'm on the latest version, not rooted, custom recovery and kernel. I used the 2 zips and my AP worked with no issue. I bought something using a vending machine with no issue and have assistant working also.
Ok but, the question is: is there a way to edit build.prop without a custom recovery and flashing a zip?
Maybe through adb?
thegios said:
Ok but, the question is: is there a way to edit build.prop without a custom recovery and flashing a zip?
Maybe through adb?
Click to expand...
Click to collapse
No. If you're stock, no root or custom recovery, then no. dm-verity will overwrite your changes on boot and your build.prop will be stock again.
Enabling Assistant via build.prop tweak won't break Android Pay (shouldn't, at least), but it will cause the OTA to fail, even with systemless root / mods.
My g 4 play is rooted and unlocked, and I received a security update via OTA today, my recovery is TWRP 3.2.0, I already saw that it has support for OTA update, but I did not find it to install. How do I do? the update is MPIS241-15.3-16
Fabiano Monticeli said:
My g 4 play is rooted and unlocked, and I received a security update via OTA today, my recovery is TWRP 3.2.0, I already saw that it has support for OTA update, but I did not find it to install. How do I do? the update is MPIS241-15.3-16
Click to expand...
Click to collapse
I'm not an expert, but I think it depends on how you use twrp. Do you boot twrp each time you go in, or did you flash? More importantly, did you choose the option to keep system read only? If you kept it read only, ota should be same as always. Settings--about phone--software update. If not allowed modifications to system, I think you'd need to use a backup from before the change was made to system partition, or dl a factory image from somewhere there's good instructions on XDA