Related
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, sounds doable
ABotelho23 said:
Technically you'll be updating your device by flashing the newest stock anyway. No need for OTAs. You can then re-root.
Click to expand...
Click to collapse
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
XDRdaniel said:
Yes, sounds doable
Click to expand...
Click to collapse
Yeah. Well.. I'm gonna try this out myself. Thanks! :highfive:
GTRanushka said:
Not what i meant. Let's say I'm on rooted OB18. But i want to update it to OB19. all i have is OB18 stock firmware. So, can i flash OB18 over rooted OB18 and then update it to OB19 (ota). Then re-root.
The reason I'm asking this is i have a very limited data internet connection. So i can save GBs if this is doable.
Click to expand...
Click to collapse
Plan to keep a copy of OB18 around? If so, then yea absolutely it should work. Root will either modify your system or your kernel depending on the method, which both get overwritten if you flash stock.
Issue you'll probably end up having in the future though is that if you always use OB18, when it comes time to install OB20, you'll be downgrading without a wipe, which I don't think is a great idea.
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Simone98RC said:
No you can't.
Because OTA will fail for "partition mismatching": the systemless root alters only but anyhow the /boot partition.
You must update with FOTA (Full OTAs), doesn't matter you're using stock or TWRP recovery.
The OxygenOS built-in updater should detects your system as modified and download only FOTAs.
Click to expand...
Click to collapse
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
XDRdaniel said:
Let's say he has open beta 18, rooted and twrp installed, if he flashes ob18 again over it, this will get rid both of the root and twrp, resulting in an untouched system, therefore, ota after this will be possible. He can then flash back twrp and root the device
Click to expand...
Click to collapse
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
This would be weird because I always had to flash magisk after a ota update..
GTRanushka said:
I wonder is it possible to flash stock unrooted OOS over rooted OOS in order to install small OTAs. After updates plan to root again. Does anyone know whether this is possible or not? And, any side effects could occur?
I search over internet and couldn't find any useful info about this.
Thanks in advance.
Click to expand...
Click to collapse
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
ajnexus5 said:
In order to flash OTAS has to have stock rom but also recovery stock and bootloader blocked but not installed the OTAS otherwise it tells you that you have something modified and you have to download the complete rom. (That does not suit you)
Click to expand...
Click to collapse
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Simone98RC said:
But practically speaking, it's crazy to unroot system only for OTA.
It would be more reliable to download FOTAs on rooted system.
Then, if @GTRanushka is running Magisk (MagiskSU) as root method, it could be working even after firmware update.
Because of its systemless nature.
Click to expand...
Click to collapse
Why i try to unroot and do OTAs is the much less download size compared to FOTAs.
Renosh said:
You don't need a locked bootloader for OTA just have to flash stock full ROM zip and stock recovery then you're good to go
Click to expand...
Click to collapse
I tried it with the bootloader open and I did not think that something is not right that it has to download complete the rom.:
Is it possible to unlock the bootloader and flash via adb magisk in order to root the phone but still able to mentain the oem recovery so i can flash the updates that are coming more easily?
if u r rooted u cannot flash OTA's, so no u can't
Yes it's possible, however when you install the update you will lose root and have to root it all over again.
Sent from my ONEPLUS A5010 using Tapatalk
I'm new to Oneplus, but Flashfire has worked for me when twrp cannot be installed.
Bradl79 said:
if u r rooted u cannot flash OTA's, so no u can't
Click to expand...
Click to collapse
How?
bkeaver said:
Yes it's possible, however when you install the update you will lose root and have to root it all over again.
Click to expand...
Click to collapse
The process will only be to flash magisk via fastboot, right ?
prologikus said:
Is it possible to unlock the bootloader and flash via adb magisk in order to root the phone but still able to mentain the oem recovery so i can flash the updates that are coming more easily?
Click to expand...
Click to collapse
You don't use adb... Patch the boot image with the Magisk Manager and then flash it with fastboot. There are instructions for it in the Magisk release thread.
When updating the OS you'll have to do it again.
In my opinion, the only reason to do it this way is if you've got limited bandwidth and can't download the full OTA zips. Using the full zip is way, way easier... Just download the full OTA file, flash in TWRP and then flash the Magisk zip right after. Done. You don't need a computer at all...
Didgeridoohan said:
You don't use adb... Patch the boot image with the Magisk Manager and then flash it with fastboot. There are instructions for it in the Magisk release thread.
When updating the OS you'll have to do it again.
In my opinion, the only reason to do it this way is if you've got limited bandwidth and can't download the full OTA zips. Using the full zip is way, way easier... Just download the full OTA file, flash in TWRP and then flash the Magisk zip right after. Done. You don't need a computer at all...
Click to expand...
Click to collapse
Can you give precise instruction hot to flash full ota over twrp???
I Have files... Than... Am on Honor View 10C432B130 wanna go to b140
So op 5t released a new update, whenever i open the update screen it says root detected, i would lose my root privileges if I update the phone.
I wanted to know whether i would only lose my root, or entire thing of bootloader getting locked etc?
After updating will I be able to just boot into recovery and flash root file? Or whole process I would have to do again
Thanks
Updates reinstall the stock recovery. You have to flash twrp then root.
virusshah1997 said:
So op 5t released a new update, whenever i open the update screen it says root detected, i would lose my root privileges if I update the phone.
I wanted to know whether i would only lose my root, or entire thing of bootloader getting locked etc?
After updating will I be able to just boot into recovery and flash root file? Or whole process I would have to do again
Thanks
Click to expand...
Click to collapse
When you install an OTA it will NOT relock your bootloader, it will reinstall the stock recovery since that is included in the OTA zip and is forced installed to be sure the update installs correctly.
You will lose the root temporarily until you flash a custom recovery again and your root of choice.
Misanful said:
When you install an OTA it will NOT relock your bootloader, it will reinstall the stock recovery since that is included in the OTA zip and is forced installed to be sure the update installs correctly.
You will lose the root temporarily until you flash a custom recovery again and your root of choice.
Click to expand...
Click to collapse
I have to flash TWRP again?
virusshah1997 said:
I have to flash TWRP again?
Click to expand...
Click to collapse
yes.
Misanful said:
yes.
Click to expand...
Click to collapse
Wait, really? https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips doesn't say anything about having to flash twrp again...
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse
Or does "100% stock images" mean the stock bootloader = flash twrp again?
Just to clearify, updating my phone by an OTA does not lock the bootloader but I'd have to flash twrp and magisk again..?
Yakumichan said:
Wait, really? https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips doesn't say anything about having to flash twrp again...
Or does "100% stock images" mean the stock bootloader = flash twrp again?
Just to clearify, updating my phone by an OTA does not lock the bootloader but I'd have to flash twrp and magisk again..?
Click to expand...
Click to collapse
yee, but after you have used the OTA you will need to flash twrp again since the OTA flashes the stock recovery, or modify your boot image but that is a pain in the ass. :silly:
Misanful said:
yee, but after you have used the OTA you will need to flash twrp again since the OTA flashes the stock recovery, or modify your boot image but that is a pain in the ass. :silly:
Click to expand...
Click to collapse
Means if I'd like to unroot my phone by doing nothing, this is probably the easiest way?
I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.