I installed twrp and SU. Really the only reason I did it is because I use titanium backup to back up and restore apps and such. Otherwise I really don't need root.
I have two questions.
First Question: Can I re-lock the boot loader if I have TWRP and SuperSU installed? If not how can I use Android pay? Is there a work around? It's not allowing me to because it can't verify
Second Question: The OTA 6.0.1 won't stick. I'm pretty sure I've done one other over the air update (at least I thought I did, I may be remembering incorrectly) and it worked just fine. But for some reason 6.0.1 isn't taking. Any ideas?
If you don't need root what you can do is download the 6.0.1 imag direclty from google, put it in your adb/fastboo folder and use the flash-all command and it will erase root, twrp and it will be like you just got it from the factory. The only thing that would be still there is the unlocked bootloader. Once you've performed the flash-all command, you can simple lock the bootloader again. That's if you want to get rid of Root and Twrp.. If not, you can try a Rom like Chroma that has android pay working on it.. Here's the instructions. Hope this helps: http://forum.xda-developers.com/showpost.php?p=64269166&postcount=2338
Edit: Make sure you follow the systemless root instructions from that link to get android pay to work...
So I cannot lock the boot loader if I have root and twrp installed?
I really don't want to use a Rom. I'm happy with stock, just want to be able to use titanium backup.
And are ota updates not working if you have twrp installed?
OTA updates won't flash properly if you have TWRP installed, though I heard there is a way to extract the components of the update you want to apply so you can preserve root and custom recoveries while still updating. Sorry I don't know where the instructions are though.
No you can't lock the bootloader with TWRP installed, it can result in a brick.
I would not lock the bootloader unless you are 100% stock. You open yourself up to unrecoverable bricks. As for the update if you download the image from google you can just flash the individual partitions in fastboot. This way you can preserve your data. Heisenburg has a great guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 You will loose root but getting it back just involves reflashing the SuperSU-v2.62-3-20151211162651.zip from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125
Related
Hello,
I am looking for a smooth method to lock and unlock the bootloader on my Nexus Player. Although being it is not a phone I guess I could just leave it unlocked... I am also looking for the best current method to root the Nexus Player on 6.0. I have been searching but I keep coming across guides for lollipop.
Thank you in advance!
Unlock/root guides are similar. They are the same except for the files used.
For Android M - i use fugu-mra58k. Use Chainfire's beta-supersu-v2.51 and it requires custom boot img, can be found on his tread http://forum.xda-developers.com/apps...ellow-t3219344. There is supersu2.52 but im not sure if it will have issues. My NP was already unlocked so I just flashed factory,moved supersu2.51 zip, boot into bootloader and flash twrp and CF's custom boot.img. At this point DO NOT restart NP, just boot it into twrp and flash supersu (you'll need otg+mouse attached). reboot and you should be good to go.
My phone is prompting me to update to B29, but when it reboots, it brings me to the TWRP recovery, and I can't seem to find an update.zip or anything. Is it not there, or am I just looking in the wrong places? Will it even successfully update with the bootloader unlock (not the official unlock) and TWRP installed, or do I need to restore the stock recovery?
My phone was originally on B20_boot, but I've since restored using Draken's TWRP files to get to B27 (I'm assuming still B20_boot).
You won't be able to OTA update with your system modifications. DrakenFX has flashable zips posted in another thread, but beware there seems to be quite a few bugs in b29 (I have no in-call audio personally).
You can use my updated post to B29 (bootstack and boot/system) flashable files are there.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
So why am I getting the notification, then? Will it just keep popping up, or is there a way to block it (even though I'm not rooted)?
As for the bugs, I've seen plenty who have upgraded to B29 without issues. How did you update? Could it be something with updating via TWRP?
Have you personally heard of anyone having problems with your update file? Will it wipe my phone (ie: will I have to reinstall everything)?
Bootloader unlocked, normal twrp flash as per DrakenFX's instructions. And yeah but a lot of people are in both boats so your milage may vary.
Thanks. Do you think I'll be able to keep my data partition intact? I really don't want to set everything else up again. It's getting old... lol.
I wiped everything, so I'm not sure. Maybe that's why my stuff is broken lol
You can't do system updates with custom bootloader's. You are getting the message because you still have the update program on your phone. Look for some sort of update.apk and disable or uninstall it.
I didn't think you could do that without root.
Oh well, I plan on putting root back on soon anyway.
That would be interesting, if true. You would think a "dirty flash" would cause more problems than a clean one.
What about the whole "can't root B29" thing. I've seen a comment where someone said they could not root B29 since they didn't root before the upgrade. I'm not rooted now, but I am bootloader unlocked with the latest TWRP. Should I be ok to flash without rooting first? I was hoping to root afterwards, and try to figure out a way to make Magisk work.
You can't root locked bootloader B29 afaik at the moment. You'd either have to unlock your bootloader or stay on B27 to get root.
I am bootloader unlocked.
I'm not rooted now, but I am bootloader unlocked with the latest TWRP.
Click to expand...
Click to collapse
I'm about to provision my One Plus 5 for use I will be running it with TWRP a unencrypted data partition (makes restores easier) and root via Magisk day one.
I'm curious if I'm running it in this configuration when an OTA comes down the pipe will it do any of the following?
re apply fastboot oem lock?
flash the recovery to stock recovery?
remove magisk?
re-enable dm-verity?
Curious if the process after an OTA apply is to re-flash TWRP potentially re-apply magisk? Does applying ota mess with your data partition if you already decrypted it?
Also was thinking about leaving the data partition decrypted so I can push things to it via ADB or manipulate it when it's in a non-functional state can anyone here comment on if that's still possible while encrypted? And if so what dis-advantages of leaving it encrypted I hear one is you have to remove the lock screen password before you create a backup since the keys are not backed up and you might be locked out after a restore.
With some more research I've answered my own question I'll put them here in case anyone wants to refer to them in the future.
TWRP users will lose TWRP after a flash of the OTA.
Root will be lost regardless if you flash using TWRP or stock.
Data is not touched during flash so it should stay as is.
DM-verity requirement is unknown.
For rooted users it's better to do a full flash with TWRP OTA through TWRP will cause a problem.
Actually, you won't get the small incremental OTA, you will download the complete 1.5 - 2gb rom... This happens when you have root whether you have got TWRP or stock recovery.
Root will always be lost, yes but if you flash with TWRP you can flash magisk oe SuperSU immediately afterwards to gain root again. Not having TWRP you will need to either boot TWRP or install it to install root again.
DM-Verity, I have never had any problems with this after flashing and then rooting...
I dirty flash the 4.5.10 and i had to reflash the ROM + no_verity_op5.zip. My first and only issue was a sort of bootlop to the recovery.
So wait. If I flash the OTA, then flash Magisk, I will have root and lose TWRP, right?
Then could I use some app like Flashify or the TWRP app to install the recovery?
I don't own a PC right now and want to know if it's possible.
I brought a OnePlus 6t and immediately unlocked the bootloader. In hindsight, I wish I hadn't as I'm not really sure I need root.
But now I have, I need to root to use various apps now that I have unlocked the bootloader.
When I first rooted it, I didn't install twrp but can't remember what I did and cant find any guides.
Can anyone let me know what process I need to root without installing twrp please?
Duskfish said:
I brought a OnePlus 6t and immediately unlocked the bootloader. In hindsight, I wish I hadn't as I'm not really sure I need root.
But now I have, I need to root to use various apps now that I have unlocked the bootloader.
When I first rooted it, I didn't install twrp but can't remember what I did and cant find any guides.
Can anyone let me know what process I need to root without installing twrp please?
Click to expand...
Click to collapse
Boot in fastboot mode, then temporarily boot into TWRP (fastboot boot TWRPimage.img) and flash magisk zip and reboot system.
P.s. "boot" command does not permanently flash the image.
Duskfish said:
I brought a OnePlus 6t and immediately unlocked the bootloader. In hindsight, I wish I hadn't as I'm not really sure I need root.
But now I have, I need to root to use various apps now that I have unlocked the bootloader.
When I first rooted it, I didn't install twrp but can't remember what I did and cant find any guides.
Can anyone let me know what process I need to root without installing twrp please?
Click to expand...
Click to collapse
Here is the complete guide
If you need root without twrp you can patch the boot image for root access
So I've read a bunch of stuff and everything I've read tells me to do the same thing that I've already done. Also those thread seemed pretty old so....
Anyway I need a stock backup so I can perform OTA update but I don't have one. this is what I did
I used msmtool to start over
pushed through setup
unlocked bootloader switch in developer settings
unlocked bootloader in fastboot
updated android
fastboot boot twrp.img
wiped everything
flashed magisk.zip
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
installed magisk.apk
So what step am I missing to save the stock backup so I can uninstall magisk for OTAs?
I had a Pixel for 3 years that had a broken fastboot and so I couldn't unlock the bootloader and never got to learn about the new AB partitioning until now. so I'm a little behind
Thanks
GbizzleMcGrizzle said:
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
Click to expand...
Click to collapse
Unlocking the bootloader can make you fail safety net, much less Magisk if its not set up right. The recovery wont matter.
My guide here is for installing Lineage, however Step 5 will work for OOS too and make you pass safety net. So feel free to install TWRP.
I recommend Funk Wizards Guide on installing TWRP. Also note the section on EFS backups.
Look into TWRP backups, I dont use them, but I know its not straight forward unfortunately.
So when I'm flashing the magisk file in TWRP, does it save a copy of the image it's modifying? And where does it save that image? Also where should i put that image so I can uninstall-> Restore Images?