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?

TWRP (Boost) flash doesn't stick

Hi - I've read through almost every thread in this forum and, unless I am missing something - quite possible - I don't think that anybody has mentioned this problem.
I have a bootloader unlocked Boost Moto E4 and I can flash Squid's TWRP (I do get the "Image not signed or corrupt" message) and can boot from the bootloader after the flash into TWRP recovery. However, after I boot into the OS, the TWRP recovery gets overwritten with the stock recovery. Has anybody else bumped into this? Is there a step that I am missing somewhere to make TWRP permanent?
Thanks
D.

Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.

D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
Your problem is the stock rom flashing the stock recovery when you reboot. If you flash twrp then reboot recovery once before booting the os, it should change a file in /system recovery-from-boot.p to recovery-from-boot.p.bak which will stop the stock recovery flash. You can also mount /system in twrp and use the file manager to change it manually.

D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*

Francesco Franz said:
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Click to expand...
Click to collapse
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Sent from my Moto E (4) using XDA Labs

amarc78 said:
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Click to expand...
Click to collapse
than do this flash over default recovery and do reboot. twrp recovery removed from recovery partition on next boot.
also do this flash twrp and do allow modifications. your device ain't gonna boot. if you didn't flash no verity thing.
rooting will make it permanent. it's the same case in both marshmallow and nougat too as OP states his problem in first post.
it will permanent by doing this
fastboot erase recovery (remove default recovery from recovery partition)
than install custom recovery. it will be there no matter if your device is rooted or not.

Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.

D97 said:
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
Click to expand...
Click to collapse
which step actually help you?

DE SEXIEST said:
which step actually help you?
Click to expand...
Click to collapse
Whatever you do don't run "fastbootboot erase" anything unless you know for sure what by you're doing or you can screw up your partitions. I have flashed twrp many times with only running "fastboot flash recovery...", then flashing one of numerous zips to disable dmverity and forced encryption. As long as you have the option in twrp under " mount" that says "mount system read only" not checked and you may need to reboot twrp afterwards, twrp should stick. Flashing Magisk directly after the stock rom should also solve your problem and disable dmverity.

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:

Magisk Question, about updating the Rom.

Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks

Looking all over for a solution to this as well. Hopefully somebody gets back to you!

js2shanks said:
Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks
Click to expand...
Click to collapse
Do you have stock boot.img u can flash?
If you flashed a magisk patched boot.img then you won't have a backup.
If you flashed magisk through twrp then it must have been deleted. If so just flash magisk and after boot try the restore option.

Deleted

js2shanks said:
Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks
Click to expand...
Click to collapse
You probably didn't install root with magisk, so you don't have a backup img.
Install OTA then root again using fastboot to boot temporary on TWRP then flash magisk zip installer. This way you'll have the backup boot.img created for next time

Striatum_bdr said:
You probably didn't install root with magisk, so you don't have a backup img.
Install OTA then root again using fastboot to boot temporary on TWRP then flash magisk zip installer. This way you'll have the backup boot.img created for next time
Click to expand...
Click to collapse
That's what I ended up doing as well. Except I just decided to keep TWRP.
In case anyone doesn't know how to do this..
Booting temporarily into TWRP:
Enter fastboot on your phone
Open command prompt on PC
Type in fastboot boot twrpname.img
That boots you into TWRP. Then flash the OTA.zip, then optionally flash TWRP.zip to keep TWRP on your recovery you have to reboot to to recovery once. Then you can flash the magisk.zip and this will create a stock backup image.
But you can skip flashing TWRP.zip and just do ota.zip then flash magisk.zip, this will still create your stock backup images but not keep TWRP as your recovery.

GuestK00179 said:
That's what I ended up doing as well. Except I just decided to keep TWRP.
In case anyone doesn't know how to do this..
Booting temporarily into TWRP:
Enter fastboot on your phone
Open command prompt on PC
Type in fastboot boot twrpname.img
That boots you into TWRP. Then flash the OTA.zip, then ...
Click to expand...
Click to collapse
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
---------- Post added at 09:30 PM ---------- Previous post was at 09:24 PM ----------
alangt said:
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
Click to expand...
Click to collapse
I'm terribly sorry, don't mind my post. I'm on the wrong phone thread (seems to be the only thread that says about the magisk wihout backup).
So sorry!
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
alangt said:
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
Click to expand...
Click to collapse
I'm terribly sorry, don't mind my post. I'm on the wrong phone thread (seems to be the only thread that says about the magisk wihout backup).
So sorry!

How to install Magisk with stock 12.0.6

I can't install Magisk with several procedures.
Thanks for who explains us with precision how to install Magisk

Have you already unlocked bootloader and TWRP?
If so, download Magisk, reboot to TWRP and there rename the magisk ".apk" file extension to .zip, e.g
Magisk-v22.0.apk to Magisk-v22.0.zip and flash in TWRP as usual.

Everytime I flashed thé zip file I reboot to recovery

simhoc said:
Everytime I flashed thé zip file I reboot to recovery
Click to expand...
Click to collapse
Have you tried patching the boot.img from your phone's fastboot ROM, and flashing the patched image using fastboot flash boot boot.img?

How can I do that.?

simhoc said:
How can I do that.?
Click to expand...
Click to collapse
Follow this https://topjohnwu.github.io/Magisk/install.html#patching-images.
When you patch the boot image, you need to do that on the same phone (POCO M3) in the Magisk app, also you can copy the patched image manually to your PC, you don't need to use adb command to copy.
If you still don't understand how to do it, you can ask me again, I will give more detailed steps.

0

cbw said:
Follow this https://topjohnwu.github.io/Magisk/install.html#patching-images.
When you patch the boot image, you need to do that on the same phone (POCO M3) in the Magisk app, also you can copy the patched image manually to your PC, you don't need to use adb command to copy.
If you still don't understand how to do it, you can ask me again, I will give more detailed steps.
Click to expand...
Click to collapse
I will try Thanks

simhoc said:
I will try Thanks
simhoc said:
I will try Thanks
Click to expand...
Click to collapse
I fail
Click to expand...
Click to collapse

I just tried to patch boot.img using Magisk V22.0, and it was finished without errors.
I think maybe your boot.img was corrupted.
I have uploaded the boot.img from the V12.0.6.0.QJFMIXM Fastboot ROM.
You can try to patch again in Magisk using this file.

cbw said:
I just tried to patch boot.img using Magisk V22.0, and it was finished without errors.
I think maybe your boot.img was corrupted.
I have uploaded the boot.img from the V12.0.6.0.QJFMIXM Fastboot ROM.
You can try to patch again in Magisk using this file.
Click to expand...
Click to collapse
I could flash and boot.img from the V12.0.6.0.QJFMIXM Fastboot ROM. But after flashing the patched boot.img I always boot to ofox recovery. Do you think the problem was with ofox

simhoc said:
I could flash and boot.img from the V12.0.6.0.QJFMIXM Fastboot ROM. But after flashing the patched boot.img I always boot to ofox recovery. Do you think the problem was with ofox
Click to expand...
Click to collapse
I don't know, but you can try to install TWRP on the phone.
I used TWRP, and never had any problem like that, the phone could boot to system with Magisk installed.
Or if you don't need a custom recovery, you can just install the MIUI stock recovery, Magisk with patched boot.img will work without a custom recovery.