Database Develop

[RECOVERY][v500/palman] OFFICIAL TWRP [3.2.1]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10

Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?

Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.

So, now we should be able to just flash the .img file directly within TWRP to update.

Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.

Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?

fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?

luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?

fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.

fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work

I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.

aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.

fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!

luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.

@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.

bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.

New version
TWRP 2.8.7.0 released.

fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!

Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.

D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.

[Kernel] Stock Kernel + SafetyNet Patch + DRM Fix /FW Nougat 2.33

Stock Kernel + SafetyNet Patch + DRM Fix​
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox (E6633,E6653,E6683)
Current version: 32.3.A.2.33 -perf-g1016077
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430

please port for E6853

anjelz2012 said:
please port for E6853
Click to expand...
Click to collapse
Try the Zach's Kernel, in it the SafetyNet check is partially disabled.

Great work!

delete

Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.

rrdna said:
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
Try to install TWRP 3.1.1.

grayleshy said:
Try to install TWRP 3.1.1.
Click to expand...
Click to collapse
Thanks, 3.1.1 worked for me

rrdna said:
Thanks, 3.1.1 worked for me
Click to expand...
Click to collapse
It's great that TWRP came up and Magisk hides root.

Thanks for the work!!! Any chance for E6633?

christis said:
Thanks for the work!!! Any chance for E6633?
Click to expand...
Click to collapse
If the kernel don't work for You, give me Kernel.sin, then I will do it for E6633.

Thanks for the work. @grayleshy
SIN Files : https://drive.google.com/drive/folders/0B9v3aNFonkyMWlFMbF9yME5EaTg
Did you use sultanxda safetynet patch?

Added kernel for E6633.
sceryavuz said:
Did you use sultanxda safetynet patch?
Click to expand...
Click to collapse
I will soon lay out the source code. There and see, what patch is applied.

Thanks a lot. Can't wait to see the source code! Do you have an eta?

rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
I've the same issue...

MichaMichaMicha said:
Can't wait to see the source code!
Click to expand...
Click to collapse
Patch in kernel from @Sultanxda . Patch of may 23.
Earlier I didn't publish information on a patch as checked this patch.

Looks like you're working on an all in-built kernel ?
If you're making an progress towards in-built MHL please, please let us know
The magic seems to be in the configuration or additional patches (I had it working in the SunKernel Corona source)
but it doesn't seem to work out of the box with Sony's source [or I missed something],
anyway:
Keep up the good fight !

rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
When you install magisk is the drmfix still active? The last time I installed magisk I was facing issues where I'd get white noise when taking pictures and no post processing being done

Thank you!
Now I can use OTA updates for my Z5!!

The_Miggs said:
Thank you!
Now I can use OTA updates for my Z5!!
Click to expand...
Click to collapse
This is not about OTA. SafetyNet : https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/

[BETA] TWRP 3.1.1 for Mi A1

Hey,
TWRP 3.1.1 Touch Recovery beta version is released for Xiaomi Mi A1.
Download - Go to downloads tab
Update:
1. Magisk v13.4 is working fine.
Workaround for Xposed:
Xposed is not installing through TWRP and when tried with App, still it's giving errors. So below is the temporary solution till we get a permanent one.
1. Don't flash TWRP. Just boot into it from bootloader by using command - fastboot boot recovery_name.img
2. Flash latest SuperSU zip.
3. Reboot to System.
4. Your phone will be rooted now and install Xposed through app.
Important:
1. Don't flash it, just boot into it.
2. If flashed, re-flash the latest stock boot image.
Instructions:
1. Download the twrp image and twrp installer zip
2. fastboot boot twrp-3.1.1-tissot-beta.img
3. Flash twrp-installer-tissot-3.1.1.zip
4. Reboot to recovery
Flash Magisk v13.4 built for Pixel devices by @Goodwin_c. Available in the downloads tab.
Issues:
1. Flashing SuperSU will break TWRP. SuperSU will work, but TWRP will be gone.
2. Xposed won't flash without modification.
Future update:
1. Make TWRP and SuperSU to co-exist
2. Compatibility with Xposed and Latest Magisk
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom recoveries, roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
XDA:DevDB Information
TWRP 3.1.1 for Mi A1, Tool/Utility for the Xiaomi Mi A1
Contributors
mahefooz4u, ravinder0003, Thanks to @Dees_Troy and TWRP Team
Source Code: https://github.com/mahefooz/android_device_xiaomi_tissot
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-15
Created 2017-10-13
Last Updated 2017-10-16

good work bro waiting for development to start

Great work!

Celebrations
The first step towards the good community has been taken

Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks

great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?

deepakmohank said:
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
Click to expand...
Click to collapse
Yes, Aroma installer is working

thank-you. Have you tried the way Pixel devices boot twrp, send twrp zip to internal, then flash?
---------- Post added at 11:28 AM ---------- Previous post was at 11:01 AM ----------
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?

Coolio

lakyman said:
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
Click to expand...
Click to collapse
Don't expect too much from now.
Wait for sometime as this is ported

Great work waiting for stable version... ?

great, thank you very much!!!
deepakmohank said:
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Click to expand...
Click to collapse
yea good question, I'd like to know about it too..

marhensa said:
great, thank you very much!!!
yea good question, I'd like to know about it too..
Click to expand...
Click to collapse
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312

Surprise!!!
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
Link:
https://www.androidfilehost.com/?fid=962021903579484616
Update Test 2: https://www.androidfilehost.com/?fid=962021903579484804
If it works, please don't forget to hit thanks...

deepakmohank said:
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Click to expand...
Click to collapse
No support for a/b system. Only active system can be reached
Thanks for great effort by devs

thanks for sharing~
hope it works~

Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.

ghpranav said:
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
If it works, please don't forget to hit thanks...
Click to expand...
Click to collapse
unfortunately it does not work
h**p://kephost-image.tk/files/64k6re0jfsp4zmienhkr.png

TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
Somehow Magisk is not yet working in Mi A1. Either flashed through recovery or other method, getting bootloop and other issues.

TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
If you know then Magisk is not supported officially for A/B partitons devices including Pixel

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.

How To Guide GUIDE to Root your X7 MAX

Prerequisites:
Bootloader unlocked
TWRP
Bootloader unlock guide : https://forum.xda-developers.com/t/guide-bootloader-unlock-on-rui-2-0-based-on-android-11-r.4286451/
TWRP : https://forum.xda-developers.com/t/twrp-recovery-unofficial-for-realme-x7-max-rmx3031.4336503/
Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now
Steps :
To Root Your Phone Install above mentioned version of magisk manager
Pull your boot.img from recovery
adb pull /dev/block/by-name/boot boot.img
check boot image in directory you extracted your adb zip
Patch your pulled boot.img from apk given below
Flash it via Twrp in Boot Partition
Now u successfully rooted your device
Troubleshooting:
One issue I personally faced was driver problem (Fastboot Device Not detecting) which I was easily able to fix with the help of this video : https://cutt.ly/wEEit33
use this only if you are also facing this issue
Sources : here

Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??

Aditya8520 said:
Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??
Click to expand...
Click to collapse
NO, that's not how it works

Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw

borkakoz said:
Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw
Click to expand...
Click to collapse
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"

Harsh raj sah said:
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"
Click to expand...
Click to collapse
As I mentioned in my reply, I tried multiple versions of Magisk, and version from post too. Is there any other way to get that patched boot img?

I also noticed that flashing process is almost instant. It takes only like a split second. Can it be the issue?

it's not stable at all
are there any other options?

i had arranged all the things fix all the issue and make an article of root realme x7 max. all the command is provided here even downloads file