Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
If you had TWRP touch your /system in R/W mode even if it made no changes, the system partition is tainted (there is meta-data that changed)
The only practical way to get back to untainted /system is to flash the stock system.img. The flashing is simple, but it might take a little time to download the factory image and extract the system.img.
I usually keep twrp in the recovery partition, probably chainfire has something to boot twrp directly. I do know that if you boot twrp over usb there is a problem where it doesn't accept your pin/pattern/pass to decrypt the user partition. I don't know if it suffers the same problem through other booting methods.
BTW even with systemless root, you cannot flash the differential OTA you receive over the air directly. You need to restore the stock boot.img before flashing the OTA.
The FULL OTA you get from the factory image website, on the other hand, can flash over anything, regardless of whether you have boot, system, or vendor modified.
Thank you for the clear answer
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
The command
Code:
[I]fastboot boot <img file name>[/I]
will boot twrp from your computer with out having to install it.
Related
Hi guys, the last time I rooted my 5X was a very long time ago when I did a "traditional" root by using a modified boot.img. I checked out Heisenberg's guide to rooting thread and I no longer see references to systemless root or modified boot.img files. Is the current rooting method no longer requiring these things? Is the only root now systemless? I would like to update to the most recent stock rom and then re-root. Thanks.
When you install SuperSU (through TWRP) it will detect your nexus 5x needs systemless root and on the fly it will patch your boot.img (and backup your original boot.img to /data).
It will also install /data/su.img which is a mountable image containing SuperSUs main files.
If you do a factory reset, it will wipe out /data (and thus su.img) so you'll lose root, but you will still have the patched boot.img (meaning dm-verity verifying of /system and /vendor is disabled, /data is not forceencrypt, and some se contexts were adjusted)
To reinstall root in the case of factory reset, just reinstall SuperSU-*.zip. It will complain that it can't restore your boot.img (because it was also wiped out by the factory reset) but by that time everything has been installed to get root back so it'll just work.
Also, one other thing, you need to actually install twrp.img into the recovery partition (fastboot flash recovery twrp.img) rather than just taking the shortcut of doing fastboot boot twrp.img or twrp won't be able to decrypt your /data partition.
Thanks @sfhub. So sounds like the answer is yes SuperSU will only install the systemless root if you're on the 5x.
Is there anything else I would need to do in order to finalize the "systemless" portion of the root?
I.e. delete the /data/SU.img or something?
also - is there a way to know if my root is "systemless" or not? does the systemless route not have a supersu application installed?
Since I have the traditional root, ie using an old modified boot.img, should I just wipe my device and flash the newest firmware from adb? I'd like to keep everything in tact a go stock rooted on newest software but I'm worried I will brick my phone going from the traditional root to systemless method. Thoughts?
SeriesOfTubes said:
Since I have the traditional root, ie using an old modified boot.img, should I just wipe my device and flash the newest firmware from adb? I'd like to keep everything in tact a go stock rooted on newest software but I'm worried I will brick my phone going from the traditional root to systemless method. Thoughts?
Click to expand...
Click to collapse
You probably have systemless root already. The modified boot image was required until CF make it so SuperSU patched the boot on install. Anyway, thats kind of irrelevant now that you plan on updating.
The quickest way to update is to to flash the latest factory images. This is done in fastboot mode and with the tool called, you guessed it, fastboot. ADB and fastboot are not the same thing. ADB only works when booted up or in recovery. Fastboot only works in... fastboot mode. :good:
You can update without losing any of your installed application or data. To do this you need to edit one line in the flash-all.bat file (Windows) or the flash-all.sh file (Linux/Mac). This flash-all file is located in the tarball that contains the factory images. You simply need to remove the -w near the end of this file. So from...
this:
Code:
fastboot -w update image-bullhead-xxx##x.zip
to this:
Code:
fastboot update image-bullhead-xxx##x.zip
That way userdata is not wiped when you run the flash-all file.
To re-root I suggest you follow the guide HERE. Note that flashing the factory images will wipeout either of the root styles you may have at the moment.
EDIT: Obviously you need to reflash TWRP to flash SuperSU or any other flashable zip. If you aren't interested in Android Pay, you dont need to follow the instructions in the link i posted above. Simply flash the latest SuperSU.
EDIT 1: If you want to decript, might as well do it straight away. No sense in setting everything up that then wiping it out. Remember this is done by formatting data. You can do it just after flashing TWRP from within TWRP. Note wiping data and formatting data are two separate things.
Good luck.
Thanks for all the help, you guys are awesome.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Shoruk3n said:
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Click to expand...
Click to collapse
1. If you switch roms, always do a clean install (wipe all partitions) . If you want to get rid off all the mods wipe system and flash the same rom + gapps + root. You won't loose data since you are only modifying the system partition.
2. Stock recovery by Oneplus is as if says stock, you littery can't do anything with it apart from upgrading your OOS, wiping cache partitions and doing a factory reset. I do recommend the TWRP provided by Bluspark since that seems to be the only one I tried without any issues whatsoever.
3. Magisk is the new root method in my opinion, it supports Magisk modules which simply are mods that can be installed and removed with a single click (reboot required tho). You can compare it to xposed but very limited when compared.
4. Boot.img is your kernel, never flash standalone img files apart from TWRP since the kernel modifies more the only the boot img. Always flash the full zip.
Greetings. I received the OTA update (which I did not install!) on my OnePlus 5T today. I'm on OxygenOS 5.0.4 with magisk installed, phone is rooted, bootloader unlocked, stock recovery (no TWRP).
What's the right path to upgrade to 5.1.0?
I'm experienced with the command line and have no problems with it.
Based on my ideas, I think the path should be:
- Download full Oxygen OS 5.1.0 Full Zip
- Start TWRP using adb
Code:
fastboot boot
(which TWRP version?)
- Wipe dalvik and cache
- Flash the downloaded file
- Wipe dalvik and cache
- Flash magisk
That's it. Am I missing something? Do I need to reinstall magisk as specified as last step? Which TWRP version should I use (from the official website?)?
Thanks for your help :good:
Please go through the dedicated update thread that ive made for the update
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
The thread has all the instructions and files needed to update. As far as twrp is concerned i recommend latest codeworkx or or bluspark recovery. The links are available on the thread.
Feel free to post on the thread if you have any further doubts.
Thanks @Funk Wizard , I read that thread (I linked it in my post) but it mentions "For Stock Non Rooted Users with Stock Recovery" and "For Rooted Users with TWRP Recovery" while in my case I'm rooted with STOCK recovery, which doesn't fit any of those 2 sentences. Which one should I follow?
As you are rooted you can flash the full zip from stock recovery that would remove root or you need follow and flash via twrp. If rooted stock recovery is no good TBH and i recommend staying on TWRP.
You can flash twrp from fastboot and then follow the instructions on the flashing post.
In case you dont need root anymore you can just flash the full zip from stock recovery. It will remove root and you will stay on stock recovery. In both the cases, use the full zip to flash via twrp or stock recovery.
No good? Please be more specific, why it's no good? From my understanding keeping stock recovery with magisk installed and bootloader unlocked allows me to pass all SafetyNet checks, which is very helpful if you don't want to deal with apps complaining that you are rooted. I can easily boot to TWRP as long as I can plug my phone into my computer by just using the fastboot command. The only downside I could see is if I brick my phone and have usb debugging disabled, I can't fastboot from adb.
Flashing TWRP would make me fail SafetyNet checks, which I'm not interested into.
After I flash the full zip, do I also need to flash the OTA update?
Thanks by the way, basically the only real "special" thing I need to do is install Magisk again after flashing.
Flashing twrp doesn't break safety net. So it's upto you if you want to stay on stock recovery with no additional benefits or on twrp.
Also, if have full time zip then you don't need to flash ota zip again.
That's good! I'll definitely flash twrp in that case.
@sshivampp Sorry to resurrect this thread, but looks like it's important. On TWRP website itself it's stated that installing TWRP would break dm-verity. What's the consequence of this? https://twrp.me/oneplus/oneplus5t.html
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear