Database Develop

Flash oxygen os 5.0.5 on OP3T with magisk using TWRP ??

Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..

I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??

Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??

2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)

deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.

I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!

Bootloop installing xposed framework

Hey guys,
I have installed the xposed installer from the magisk downloads, and then i have rebooted the phone. Now the phone is in a bootloop and i can't delete the installer from the magisk app.
I have tried to install the xposed sdk26 from the twrp, but that doesn't work. I have downloaded the xposed uninstaller too and flash it, but that doesn't work either. When is at the loading screen, after a while, the phone reboots and gets into the twrp.
I don't know what to do, please help

Backup your data to a PC from TWRP, clean everything and flash again.

rmrbpt said:
Backup your data to a PC from TWRP, clean everything and flash again.
Click to expand...
Click to collapse
I have tried and the same happens...

Try with miflash using the option to erase everything (but not the option to lock the device!).

Startup Hang after Installing Magisk v18.0

Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?

Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.

SpikyAndroid3 said:
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Click to expand...
Click to collapse
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Sent from my #FlagshipKiller3T using Tapatalk
---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------
StreamingMT said:
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
Click to expand...
Click to collapse
Weird :/
Did you check the Magisk release thread for people facing similar issues? I'm still on v17.3.
I'm really reluctant to move to v18.0 after reading such things... Moreover, I always wait for feedbacks before trying out things that play with the boot.img's & stuff, because I already got /data partition of my last device corrupted [emoji52]
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Click to expand...
Click to collapse
Alrighty! Just went ahead and did the flash and it successfully reboots! Tried to reboot into recovery to flash Magisk 17.3 and lo and behold TWRP is still there
Guess I'll wait until there has been an update or patch of some sorts if @StreamingMT is also getting this issue, maybe there are others too. Thanks for the help @DarkSJ1998

I will try to remember that @DarkSJ1998.
I was excited to have a new update, just got reckless...
Anyways, I replied to the official thread about the details, just search through it. I just restored my phone to the way it used to...
All my saves... Gone to trash.

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.

Same here on a mi max 2, updated manager and magisk directly from app, now stuck in bootloop. im downloading my rom as im typing to restore stock boot image. will flash v17.1 instead.

I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
E:\Program Files\Android\platform-tools>
Click to expand...
Click to collapse

I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying

tmicrd68 said:
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Click to expand...
Click to collapse
Using Xiaomi Mi Max
Using your method and it work just took afew for it to boot back up :good:

netsonic said:
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
Code:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
Click to expand...
Click to collapse
Try 'Revoking USB Debugging' and restart the adb server. Then reinstate its authorization by plugging it back in with USB Debugging enabled. And just to check, make sure you run cmd as administrator, and ensure MTP is on.
huzeifa88 said:
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
Click to expand...
Click to collapse
Try flashing the uninstaller which you can get here. Then reinstall/reflash Magisk with a previous version that worked for you.

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
DarkSJ1998 said:
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't work.
The cellular boot but stops in the Miui Screen with the unlocked symbol
I tried a dirty install of the rom but don't work
I need to install a clean global stock rom to boot correctly.

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Doesn't look like a flashable zip too me. It stores a *.img file in it, which I think is flashable as an image from TWRP. But, I'm not 100% sure about it.
Great discovery though dude there
Sent from my #FlagshipKiller3T using Tapatalk

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Hello, I do this with my Nexus 6, it's OK. Flash again Magisk (v17 not 18 for me) and all is OK for me.

Boot loop for me too after upgrading from v17 to v18 . I'm on Nexus 6. Any official information about this bug?
Fixed by installing TWRP then restored backup through TWRP and selected only boot image. I guess TWRP or me saved backup at some point, don't remember exactly. Will have to use v17 for now.

Tried root with Magisk and now my phone doesn't start.

Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11

Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.

Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?

F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip

antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?

F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.

MIUI 12 update with TWRP

Hi everyone!!
I have the update notification for 12.0.2.0 global, but I have a rooted phone with TWRP installed.
If I wish to update through TWRP without losing my data, apps and root what can I do?
Is there any method?
Where can I download the update file to flash with TWRP?
Thank you for any help!!

hi there,
if you also have the Mi 9 CEPHEUS- Global version, just download the .zip Rom from here:
https://bigota.d.miui.com/V12.0.2.0.QFAMIXM/miui_CEPHEUSGlobal_V12.0.2.0.QFAMIXM_a559c4c1fe_10.0.zip
this link is provided in this page from XDA: https://www.xda-developers.com/down...ing-out-several-xiaomi-redmi-mi-poco-devices/
install normally with TWRP, and then flash Magisk 20.4 as well and reboot.
What I personally did, was taking a backup of my apps with Titanium and wiped (Dalvik, Cache, System root, Vendor and Data) in TWRP before flashing the Rom to prevent any possible bootloops.
Bu you can also try it without the major wipes and see if it works.

aze89 said:
hi there,
if you also have the Mi 9 CEPHEUS- Global version, just download the .zip Rom from here:
https://bigota.d.miui.com/V12.0.2.0.QFAMIXM/miui_CEPHEUSGlobal_V12.0.2.0.QFAMIXM_a559c4c1fe_10.0.zip
this link is provided in this page from XDA: https://www.xda-developers.com/down...ing-out-several-xiaomi-redmi-mi-poco-devices/
install normally with TWRP, and then flash Magisk 20.4 as well and reboot.
What I personally did, was taking a backup of my apps with Titanium and wiped (Dalvik, Cache, System root, Vendor and Data) in TWRP before flashing the Rom to prevent any possible bootloops.
Bu you can also try it without the major wipes and see if it works.
Click to expand...
Click to collapse
Thank you for for reply and help.
So I did exactly like you explained, but before going into TWRP I removed my mi account and any fingerprint/passwords, then in TWRP i did only wipe dalvik and cache to avoid losing everything from apps.
And voilá! It worked!
Thank you again!!!

Oh brilliant!
And yes you did it right about removing your account and lock screen, which I forgot to mention.