Database Users

[Guide] Flash OTAs with TWRP (OS 2.1.3/ 005)

Firstly, you cannot install OTA's with TWRP. You'll have to get back to stock recovery in order to install patches.
Thanks to @eng.stk, with the recovery compiled from source, we now can flash OTA Zips from TWRP.
Download TWRP 2.8.7.0: http://forum.xda-developers.com/devdb/project/dl/?id=15364
Download the following OTA's and move them to internal/external storage and proceed to install them from TWRP.
OxygenOS_X_Rom.zip (003)
OTA Patch 003-004.zip
OTA Patch 004-005.zip (Uploaded by @Razertje)
____
Stock Recovery (Just in case if someone requires it)
- Stock_Recovery.img

I got an error when I try to flash it

PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
Are you rooted? Did you flash TWRP recovery?

PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.

Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?

PoloB49 said:
Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?
Click to expand...
Click to collapse
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996

SpiritBreak3r said:
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996
Click to expand...
Click to collapse
Thanks, i wasn't sure it was the full rom because of the "ota" in the name.

SpiritBreak3r said:
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.
Click to expand...
Click to collapse
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?

Savya said:
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?
Click to expand...
Click to collapse
By flashing the system dump I meant, install this zip package http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996. This zip package is stock system dump bearing version 03. Then flash to 03-04 patch.

is this OTA solved the problem with microsd cards?

Can anybody help with a generic error trying to flash the stock recovery again?
No reason why just says failed. I am rooted with TWRP and trying to revert to stock to be able to OTA. Last android was a nexus 4 and been away a little while so I may be missing something.. I don't want to have to wipe all my data and such can somebody assist and refresh my understanding?

Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,

Dizzyrul3z said:
is this OTA solved the problem with microsd cards?
Click to expand...
Click to collapse
I don't know about you guys, but I have the E-1003 model, SD card is working fine. I have a Samsung EVO+ 32GB card.
BakedGoodsX said:
Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,
Click to expand...
Click to collapse
You need to flash to Stock recovery as well. I'll be updating the OP.

So this update is newer than the one mentioned here right ? : https://forums.oneplus.net/threads/oxygenos-2-1-2-will-start-roll-out-to-oneplus-x-today.402637/
Thanks

SpiritBreak3r said:
Just received this OTA mins ago.
Size: 17MB
https://drive.google.com/file/d/0B3AIip-hiOnNb1pBeGNlcUIyYmc/view?usp=sharing
Instructions:
1. Switch to Stock Recovery if you're running TWRP. But how to do it? Restore this backup from TWRP.
2. Flash the system dump available at this thread.
3. Now flash this update/patch.
4. Then fastboot flash TWRP recovery if you only need it.
Just my 2 cents, boot TWRP instead of flashing it. I personally suggest.
Code:
fastboot boot twrp_directory_of_your_pc.img
PSA: You'll need Stock recovery to patch official updates.
PS: My Memory Card is working exceptionally fine. I am using a Samsung EVO+ 32GB.
Click to expand...
Click to collapse
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?

umpalumpa1799 said:
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?
Click to expand...
Click to collapse
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img

CafeKampuchia said:
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.

umpalumpa1799 said:
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.
Click to expand...
Click to collapse
even better, download the img from the op.

SpiritBreak3r said:
even better, download the img from the op.
Click to expand...
Click to collapse
my fault, I downloaded the stock recovery from a nother post

Thank you for the update OP.
To clarify, when you say '...stick with stock recovery, disable the apps instead of deleting them...' what exactly does that mean?

Rooted Nexus 6P - Possible to get OTA updates?

I recently unlocked the bootloader and rooted my Nexus 6P and just this evening received an update for the November Security Update. This downloads fine but when the phone reboots to install, it just goes to TWRP and doesn't install.
This is most likely incredibly simple and stupid for me even to ask, but is it possible to install one I've unlocked/rooted?
Any advice will be much appreciated.

You need the stock recovery to take otas Thats why it won't work
Sent from my Nexus 6P using XDA Free mobile app

Before, it initiates an update install. It checks root status. If it finds the device is rooted then it stops OTA install, to prevent any further damage to the phone.

In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk

Thanks for the quick answers guys. Many thanks.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.

Does anyone have the stock recovery img handy? Should be easy to get OTA's with flashify that way.

HyperM3 said:
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.
Click to expand...
Click to collapse
I was hoping to stay stock and use xposed when it is ready. So, no, I haven't gone that far in a long time.
Sent from my Nexus 6P using Tapatalk

The best way to get the ota updates for you would be to download the factory image from Google and Fastboot flash. If you dont wipe user data you should be able to keep most of your settings. You will also need to reflash chainfire's boot Img.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Click to expand...
Click to collapse
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP

rsmolen said:
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk

rborg said:
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.

Phazmos said:
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.
Click to expand...
Click to collapse
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?

Cares said:
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?
Click to expand...
Click to collapse
Uhhh the most obvious answer would be no other peripherals required.

Phazmos said:
Uhhh the most obvious answer would be no other peripherals required.
Click to expand...
Click to collapse
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.

Cares said:
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.
Click to expand...
Click to collapse
Sorry, but if ya think it's slower or harder to download a rom and flash it, I don't know what to tell ya.

I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk

rborg said:
I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Xposed is very unstable. Most of the time causes reboots.

rsmolen said:
[/COLOR]
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Did anyone try this? Did it work? I am rooted but I have stock recovery (instead of flashing TWRP I just booted into it with fastboot for the SU install). Do I still need to flash the stock boot and recovery img's? I'm not sure what changes when SU is intalled. Thanks!
Edit - Does the "full unroot" button on SuperSU work? Is this all I would need to do since I did not permanently flash TWRP?

just did this. works perfectly. all data still there.
thanks!!!

Stock recovery img for lg Leon Lte MS345

So i recently attempted to install twrp to my leon via twrp recovery manager. When i reboot into recovery it gives me a boot verification error. Would anyone be able to upload the stock recovery.img
Thanks for any help

Flash this with flashify, it will work...
. stock recovery? Never.
https://www.androidfilehost.com/?fid=24052804347772357
Sent from my XenonHD-phone using Tapatalk

It keeps giving me secure boot error 1003 my bootloader is locked that is why I would need stock recovery back

You have to enable oem unlock under developer settings in order for a custom recovery can be used. I had this same problem when I first installed TWRP custom recovery on my leon.
Sent from my LGMS345 using Tapatalk

dandanbkk said:
So i recently attempted to install twrp to my leon via twrp recovery manager. When i reboot into recovery it gives me a boot verification error. Would anyone be able to upload the stock recovery.img
Thanks for any help
Click to expand...
Click to collapse
I have the same problem and want to go back to stock recovery. Maybe the app Partition Backup from Play Store could help. I found this app after I flashed twrp. I just need the stock img to try to flash it back to see if it works. Could somebody with stock recovery try the app?

Same here. I need the stock IMG so I can take the ota update. Anyone?

I dont have but i have a twrp img ms345 version but its not the stock recovery u can try flashing your rom again and unlock the oem than install twrp via twrp manager from google play

stock recovery

I have restored my stock backup of the original Moto x style/pure so it's clean no root or mods, can I just go back to stock recovery from twrp ?
I've tried going back to stock using the correct firmware but I end up in a boot loop, I'm hoping I can just abd the official recovery and I'll be able to install the ota

BackDaws said:
I have restored my stock backup of the original Moto x style/pure so it's clean no root or mods, can I just go back to stock recovery from twrp ?
I've tried going back to stock using the correct firmware but I end up in a boot loop, I'm hoping I can just abd the official recovery and I'll be able to install the ota
Click to expand...
Click to collapse
Just download the full rom firmware image that is the same version as you have installed, and extract recovery.img from it, you can flash this with fastboot or TWRP.

acejavelin said:
Just download the full rom firmware image that is the same version as you have installed, and extract recovery.img from it, you can flash this with fastboot or TWRP.
Click to expand...
Click to collapse
Thanks mate it worked

Android Pie 9.0 root possible ??

Hi guys, I had read many posts about rooting essential phone. But those articles aren't mention if it is suitable for android Pie version. Is there anyone knows how to root my essential phone with Pie 9.0 ??

See this thread.

prabs99 said:
See this thread.
Click to expand...
Click to collapse
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:

Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
eric672913 said:
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Click to expand...
Click to collapse
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
Click to expand...
Click to collapse

prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
Click to expand...
Click to collapse
Got it , I will try this. Thanks so much:laugh:

eric672913 said:
Got it , I will try this. Thanks so much[emoji23]
Click to expand...
Click to collapse
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Click to expand...
Click to collapse
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.

NaterTots said:
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
Click to expand...
Click to collapse
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?

jwinstonsf said:
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
Click to expand...
Click to collapse
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.

NaterTots said:
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
Click to expand...
Click to collapse
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Click to expand...
Click to collapse
Boot.img

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Boot image should go to the boot partition.

Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
When installing Magisk zip, Sideload it.

manr1mg said:
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
Click to expand...
Click to collapse
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.

After you flash twrp, go into twrp, install boot.img, MAYBE make sure system is mounted THEN install magisk. I've read some of the red errors happen regardless so I'd just fire up the phone afterwords and see if it works.

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.

luisoman2000 said:
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
Click to expand...
Click to collapse
Thanks for your reply. I am sure that I check "boot" when flashing stock img. Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.

manr1mg said:
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
Click to expand...
Click to collapse
Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.:fingers-crossed:

Painful thread to read.