Develop Bugs

Recovery after 6.0

Hey all,
Trying to get my TWRP recovery back after upgrading to M.
Flashed recovery a number of different ways but always end up back at the stock recovery after flashing. I've tried going straight into it before rebooting etc with no luck.
Any ideas?
Thanks

Basttrax said:
Hey all,
Trying to get my TWRP recovery back after upgrading to M.
Flashed recovery a number of different ways but always end up back at the stock recovery after flashing. I've tried going straight into it before rebooting etc with no luck.
Any ideas?
Thanks
Click to expand...
Click to collapse
if your trying to flash recovery from your LP to get back to old back-ups in LP - you have to downgrade to LP first
There is only a recovery for flashing a patched SU / boot to give you root in MM.

Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.

Basttrax said:
Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.
Click to expand...
Click to collapse
To flash twrp recovery, your bootloader needs to be unlocked. For now, there's no way to unlock the bootloader on MM. The only option is to downgrade to LP if you need twrp or customs roms.
I hope you understand my explanations.

Basttrax said:
Thanks for the reply.
Not trying to get back to LP backups. Just trying to get TWRP back on the phone again.
Click to expand...
Click to collapse
this will work as a temporary recovery and you will be able to install SU and Xposed.
Here:
http://forum.xda-developers.com/showthread.php?t=3404321
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. Do it at your risk and I won't be able to answer your questions.
3. There is no unlock for Android 6.0 atm. Device will be locked once you upgrade to 6.0.
4. Good thing is you can always downgrade to Lollipop to unlock your device following the instructions in this thread.
5. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0. If you upgrade to 6.0 from locked Lollipop, you have to downgrade to unlock it, then upgrade to 6.0.
2. Once you are in Android 6.0, fire the following command to boot twrp. is the twrp recovery file. This TWRP is recommended.
adb reboot-bootloader
fastboot boot
Click to expand...
Click to collapse
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade:
Refer to Asus Zentalk Forum and grab the required files from there.
**Note that the first commnad line has been revised by @shakalaca and it should work without bricking the device.
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Then you can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
Sent from my ASUS_Z00AD using XDA-Developers mobile app

Is it possible to root the OP3 without a custom recovery?

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

Bootloader relocks itself after reboot!

I need some help guys!
My N5X bootloader relocks itself after rebooting.
EDIT #1:
I have TWRP and a custom kernal installed, but my bootloader is locked.

SHiiFTv2 said:
I need some help guys!
My N5X bootloader relocks itself after rebooting.
EDIT #1:
I have TWRP and a custom kernal installed, but my bootloader is locked.
Click to expand...
Click to collapse
Unfortunately, your phone is dying sing of memory failure

Stevica Smederevac said:
Unfortunately, your phone is dying sing of memory failure
Click to expand...
Click to collapse
I had my phone on warranty one day. I totally killed it after flashing a corrupted file. So LG just brought that phone back to life and shipped it back?

SHiiFTv2 said:
I had my phone on warranty one day. I totally killed it after flashing a corrupted file. So LG just brought that phone back to life and shipped it back?
Click to expand...
Click to collapse
That was software issue but this sounds like a hardware thing. That's the problem

Stevica Smederevac said:
That was software issue but this sounds like a hardware thing. That's the problem
Click to expand...
Click to collapse
Atleast i got TWRP and such working!
Thanks dude!

Your problem seems to be the same as in the following thread: http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-n5x-t3290923/page6
Its the same for me after my mainboard was replaced.

I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..

Driver007 said:
I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..
Click to expand...
Click to collapse
Hi bro,
I have a few questions.. First of all, are u able to unlock the bootloader after rooting the phone using this method? I have the same problem here with the missing rpmb partition on the EMMC.
My second question, is it possible to unroot ur phone after rooting it via this method?
I hope to here from u soon

Driver007 said:
I have same situation, warranty changed my motherboard and now I can't fully unlock bootloader. But I find solution how to Root it whit out TWRP.
Thanks to this Phh's root solution.
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Downloaded https://superuser.phh.me/nexus/bullhead/ su.nocrypt.img
Flashed whit fastboot
After restart install Phh's superuser app!! not chainfires superuser but Phh's. Somehow chainfires app doesn't understand su binary.
But root works whit phh's, installed busybox, root checker apps shows that root is working.
Did full backup whit Flashfire it makes full restore zip which can be used whit fastboot.
Maybe I will not sell this phone..
Click to expand...
Click to collapse
For me FlashFire not see root and don't want to work. But Franco kernel updater see root and i can write Franco Kernel and it's work! But root go out :crying:

aalleexxnn said:
For me FlashFire not see root and don't want to work. But Franco kernel updater see root and i can write Franco Kernel and it's work! But root go out :crying:
Click to expand...
Click to collapse
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:

Driver007 said:
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:
Click to expand...
Click to collapse
If TWRP works, are u able to flash custom roms?

buckflitz said:
If TWRP works, are u able to flash custom roms?
Click to expand...
Click to collapse
yes, but I prefer stock rom

Driver007 said:
yes, but I prefer stock rom
Click to expand...
Click to collapse
Iam now running the latets ota, 7.1.1. What do i have to flash to get root? Which file?

buckflitz said:
Iam now running the latets ota, 7.1.1. What do i have to flash to get root? Which file?
Click to expand...
Click to collapse
download:
1. https://dl.google.com/dl/android/aosp/bullhead-nrd90s-factory-d6bf1f56.zip
2. https://superuser.phh.me/nexus/bullhead/NRD90S/boot-bullhead-NRD90S-su-nocrypt-r265.img
all data will be wiped, even photos and so on because of fastboot unlock command.
whit fastboot commands write each file from factory image:
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
don't flash kernel from factory image, flash this one "boot-bullhead-NRD90S-su-nocrypt-r265.img"
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
after it boots you need: https://play.google.com/store/apps/details?id=me.phh.superuser
and it should be rooted.

Driver007 said:
download:
1. https://dl.google.com/dl/android/aosp/bullhead-nrd90s-factory-d6bf1f56.zip
2. https://superuser.phh.me/nexus/bullhead/NRD90S/boot-bullhead-NRD90S-su-nocrypt-r265.img
all data will be wiped, even photos and so on because of fastboot unlock command.
whit fastboot commands write each file from factory image:
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
don't flash kernel from factory image, flash this one "boot-bullhead-NRD90S-su-nocrypt-r265.img"
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
after it boots you need: https://play.google.com/store/apps/details?id=me.phh.superuser
and it should be rooted.
Click to expand...
Click to collapse
Bro ur awesome! thanks u so much!
If i understand correctly, iam now downgrading my firmware? I have never done this before cuz of the fact that iam quite new to nexus5x ( used a galaxy nexus before this one). Do i have to unlock the bootloader over and over after each step? And when do i have to flash the kernel?

buckflitz said:
Bro ur awesome! thanks u so much!
If i understand correctly, iam now downgrading my firmware? I have never done this before cuz of the fact that iam quite new to nexus5x ( used a galaxy nexus before this one). Do i have to unlock the bootloader over and over after each step? And when do i have to flash the kernel?
Click to expand...
Click to collapse
also had galaxy nexus :good:
about the downgrade, there isn't newer kernel from phh's website, so thats why you need to downgrade
it needs radio and bootloader from that factory zip (it should boot whit out those two) but I still prefer to flash it, so you will need to do:
fastboot unlock
fastboot flash radio radio.img
reboot the device
again:
fastboot unlock
fastboot flash bootloader bootloader.img
reboot the device
and for last time
fastboot unlock
and flash all the files, don't need to reboot every time, type one command at the line
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
oh and don't forget vendor!: fastboot flash vendor vendor.img
and kernel from ph:
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
finally boot to the system :good: I guess you should know how to use fastboot, if not google it

Driver007 said:
also had galaxy nexus :good:
about the downgrade, there isn't newer kernel from phh's website, so thats why you need to downgrade
it needs radio and bootloader from that factory zip (it should boot whit out those two) but I still prefer to flash it, so you will need to do:
fastboot unlock
fastboot flash radio radio.img
reboot the device
again:
fastboot unlock
fastboot flash bootloader bootloader.img
reboot the device
and for last time
fastboot unlock
and flash all the files, don't need to reboot every time, type one command at the line
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
oh and don't forget vendor!: fastboot flash vendor vendor.img
and kernel from ph:
fastboot flash boot boot-bullhead-NRD90S-su-nocrypt-r265.img
finally boot to the system :good: I guess you should know how to use fastboot, if not google it
Click to expand...
Click to collapse
Galaxy nexus, the good old times
I remember spending all my hard worked money on it
Bro thanks u! iam going to give it a try!

Driver007 said:
so flash stock rom whit fastboot whit ph's kernel, don't need stock kernel, after that download ph's app, check if root is working (needs ph's app from playstore, to check if root is working download root checker app), download busybox, set to permissive and flashfire should work, after that you can flash stock rom whit franco kernel and select in flhasfire that it needs to be rooted, after that you should have stock rom whit superuser.
For now I am using stock rom whit superuser and everything works (also otas works perfectly, even updates radio and bootloader, don't need fastboot for that)
Even twrp works but twrp works when it is written from twrp app which is in playstore :good:
Click to expand...
Click to collapse
OK, second attempt and i have NRD90S + root + FlashFire.
can you take some instruction to update to NMF26F (7.1.1 final) by FlashFire

aalleexxnn said:
OK, second attempt and i have NRD90S + root + FlashFire.
can you take some instruction to update to NMF26F (7.1.1 final) by FlashFire
Click to expand...
Click to collapse
Just download ota package and in flashfire select zip option (not firmware option), also select Franco kernel and root

Is there a way to install Cyanogenmod if root is possible? thanks!

Root and update OTA?

Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;

If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.

jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.

jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.

shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??

Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?

I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?

ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.

Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling

Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?

Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them

[GUIDE] How to finally root EMUI9

Hey guys,
here is just a short guide on how to root EMUI9 with the newest Magisk 18.1 canary builds just release by John Wu.
This is not my work! All credits for this go to John Wu, the developer of Magisk.
You can try this of your own risk. I'm not responsible for any damage.
NOTE:
With the new Magisk, John Wu remapped the restart button in the standard power menu, so when you reboot with that button, you'll always reboot with root.
The power button works as normal.
You can revert to the stock recovery or an TWRP recovery at any time but without root.
- Download the TWRP app from Google PlayStore and install it.
- Go to the TWRP app and download the lastest twrp image for P20 Pro.
- Downlod one of the Magisk apk's from here and install it.
- Open the Magisk app, go to settings, put the update channel to manual and insert one of the links shown ontop of this page.
- Go back to the first page of Magisk, refresh it and make sure to install the lastet magisk apk. Open it again.
- You'll get asked to download and install the lastest Magist.zip. Do this and choose to patch only the boot.img. Choose the TWRP.img you've downloaded before.
- Plugin you device to a PC and download the patched img to your PC. Now reboot to fastboot mode and flash the patched img with "fastboot flash recovery_ramdisk patched_image.img"
- Now unplug your device and shut it down. Reboot it with holding vol-up button. Now it should boot fine with working root.
Have fun and thank you John Wu for your great work!

Not working

It's working for me. Finally have a root for EMUI 9

Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk

delete

works great

otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : LINk2PATCH
Click to expand...
Click to collapse
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards

ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.

CaseyS said:
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.
Click to expand...
Click to collapse
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!

ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
I think you'll need to unlock bootloader before unless you receive the EMUI 9 update. But you may still need an unlocked bootloader. Better docrhst before you proceed. This is only coming from somone with an unlocked bootloader so I'm not sure if it's possible without.

ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
It almost certainly will come with 8.1
They've been boxed for sometime now

ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.

otonieru said:
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.
Click to expand...
Click to collapse
Thanks for clarifying that!
So I start with unlocking the bootloader (funkyhuawei .club/ buycodes - $55 )
Then see if there's an official upgrade to EMUI 9 available,
if not I will flash it myself(?),
then flash this premade patched_boot.img to recovery_ramdisk.
Another nooby question, what is it exactly that's changed on this .img?
Thanks!

ArtaxXP said:
NOTE: YOU HAVE NO MORE RECOVERY AFTER THIS AND YOU HAVE TO ALWAYS REBOOT WITH HOLDING VOL-UP BOTTON. (reboot to recovery)
Click to expand...
Click to collapse
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
Click to expand...
Click to collapse
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?

colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?

colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.

ArtaxXP said:
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.
Click to expand...
Click to collapse
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)

colthekid said:
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)
Click to expand...
Click to collapse
xactly what i thinking,
curently i swapping between root and non root simply by rebooting.
---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------
ZHARQ said:
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?
Click to expand...
Click to collapse
my file patched with magisk as well of course,
difference is, author of this thread using TWRP image as base, while am using a pure stock recovery ramdiak from .168 EMUI 9 firmware
TWRP image can work as well, but may cause issue in some devices with different firmware version,
after all, topjohnwu tell you to use recovery ramdisk image, not TWRP right

Thanks
It worked fine, but not with TWRP img, I used my own recovery img

Can´t get to rooted EMUI 9. Always ended in non-rooted even after multiple reboots to recovery