Database Develop

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root

Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.

I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.

Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?

Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks

You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.

This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/

Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?

JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.

JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.

ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks

I am in fact stuck in the boot as well. Anyone's got stock image we can flash?

nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870

JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.

SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.

ANDROID 7.0 Nougat for UMI Super, Max and Plus

Hi,
Android 7.0 is coming (rumors said this Christmas) :
link
link2

Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.

nougat on umi plus
mafury said:
Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.
Click to expand...
Click to collapse
my experience is very good .ive rooted the phone and flashed also adblock gps is working good internet very fast lte for the price just amazing

After Update Bootloop
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it

Preisschild said:
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it
Click to expand...
Click to collapse
Use flashtool to reflash firmware.

New UMI Super Android 7.0 beta update
New UMI Super Android 7.0 beta V7.01_20170114 update
Flashing through SP Flash Tool.
Camera, flash LED and on-screen buttons fixed!
The list of known bugs:
The camera still needs some adjustments
No standby Harlequin LED (only basic notification LED settings)
Other minor bugs
ROM link(UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar):
mediafire.com/file/hpzw37aca481bvc/UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar
SPFT link (SP_Flash_Tool_v5.1648.rar):
mediafire.com/file/2g6qau85a7fvnjq/SP_Flash_Tool_v5.1648.rar
Original post:
community.umidigi.com/thread-6169-1-1.html
Aditional IMPORTANT update info:
community.umidigi.com/thread-5265-1-1.html
Sorry, I can't attach links
This version should be stable with the mentioned minor bugs but please, post your feedback to check the correct performance, if there is any issue found, let us know!
Dora te quierooooooooo

So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve

steveharman said:
So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve
Click to expand...
Click to collapse
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.

Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve

steveharman said:
Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve
Click to expand...
Click to collapse
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.

Creedo4Life said:
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.
Click to expand...
Click to collapse
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve

steveharman said:
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve
Click to expand...
Click to collapse
That's correct, you browse the img file on the ticket recovery (the only one that should be ticked.) click on "download only" while your phone is switched off and then connect it through the usb. It will then flash TWRP and let you know when its done. Now disconnect your phone and hold in power button and volume up simultaneously. When you see the umi logo let go of the power button but keep holding volume up. When you see the TWRP logo you can let go. The first time you boot into TWRP you need to swipe the bar which will allow modifications, you will only have to do that once, the system will then remember it. Good luck and happy rooting.

Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve

steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
That's very odd. I used the exact same supersu myself and never encountered that problem. That version is also compatible with Nougat. Try one of the other versions on https://www.chainfire.eu/
Maybe that solves your problem.

Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?

[email protected] said:
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?
Click to expand...
Click to collapse
You have full root, you just don't know it.
If you want to edit anything in any system folders you need to change r, rw permissions. I use file explorer for this. Look at the attached SS to understand what I mean.

TWRP Install
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks

pollock49 said:
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks
Click to expand...
Click to collapse
No, you need to flash beta 2 using SPFT, there is no zip file to use with TWRP for this.
http://community.umidigi.com/thread-6169-1-1.html

steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
I have a similar problems. However in my case many of the apk still working include play store. Just the apks that needs internet quit working.

Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
Hello,
I have the problem that SPFT shows me 100% wehn I am flashing TWRP to the UMI Super but still hangs at 100% and does nothing more.
I'm using the Android N V7.01_20170123.
I also tried an Android scatter from Android 6 before I flashed Android 7, but it also doenst work.

New to Rooting: Huawei honour 4x Android 6.0. Need help.

Hi,
I'm working with a Huawei Honour 4x, Android 6.0, Stock Rom, Model: CHE-TL00, EMUI 4.1
I'm looking to root it but could not find anything specific on google or XDA. I've read about systemless root for Android 6.0 but the material largely concerns the nexus phones.
I've got quite an odd brand with a specific model make which differs from other models of the Honour 4x.
Simply put, i'd like to root the device. Can anyone point me towards more information to achieve this ?
I've searched and failed. I'm hoping someone else may know where to look.
#Update: I have twrp installed.
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Back to square one. Any help would really appreciated.
#Update 3: Problem Solved. For anyone who has the same device, here are the steps to take.
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
TWRP source: https://twrp.me/huawei/huaweihonor4x.html

Thanks for your sharing.

Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
Click to expand...
Click to collapse
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back

follow the steps anyway, dont worry if it say conecting in hisuite, and be sure u have hisuite installed, i.e, u have an hisuite.exe in the folder C:\Program Files (x86)\HiSuite\ .... and for the space, in hi suite desktop app u can uninstall some, goodluck!

Coedy said:
Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back
Click to expand...
Click to collapse
I had the same issue. There're a lot of bloatware apps pre-installed which take up crucial internal space. It seems like it is a driver issue.
My process of achieving root was essentially trial and error, so there was a lot of google searching and installing; without making note of everything i installed (when concerning drivers).
So i won't pretend to be an expert but I'll list the most useful places i checked out.
Firstly, i download the basic Android command line tools from the SDK webpage.
Secondly, i followed the steps on the TWRP webpage (can't link as i'm a new user) I download their recommended drivers too.
Thirdly, (Since Huawei do support modification to an extent, you can find a set of their recommended drivers on google or on their webpage). I googled a set of USB drivers for the Honor 4x and downloaded these too.
Following this, I was able to connect my device successfully.
(Failing this, Google has a lot of content on connecting the Honour to Minimal ADB Flash and Boot. Check it out.) :good:

sr993 said:
Hi,
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Click to expand...
Click to collapse
Hi, my model is Ch2-L11 and I'm very noob and very likely to mess up the whole phone, so I was wondering How did you created a nandroid backup?
I installed the minimal adb tool that you suggested in your post. should I use "adb backup all" in cmd? or creating a nandroid backup is different?

Why not sharing where you sourced the TWRP you used is a mystery and makes this correctly referenced thread rather worthless.

thanks for share..

[Mate 10 Pro] Stuck in bootloop, need help with stock firmware

After unlocking the bootloader, I installed the latest versions of TWRP and Magisk. It worked after a few reboots, but after installing the Xposed Magisk module the phone got stuck in a boot loop.
I tried to use the Magisk uninstaller, didn't work, tried to use eRecovery and HiSuite recovery, and then I get an error how my phone is unsupported or how there was an issue getting package information for my device.
I tried to flash the SYSTEM.IMG of the same version thinking how it will let me factory reset my phone... and it didn't work. Tried using HWOTA (Which in the end fixed my problems)*, but then I realised it only works for Mate 10 Lite (or maybe I'm just dumb)
I got my phone softbricked and cought in a bootloop, and I don't know how to unbrick it. So I'm asking You guys for help because I really f***ed up, and Your help would be very much appreciated.
Model BLA-L29 (C432) - Europe
*Edit: Fixed by following this guide https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814

Boot to twrp and flash install the same exposed module (you can find it in MagiskManager folder) it should uninstall and get you out of bootloop. Hope it works!

Read You dingus
Nevermind it turns out it was error on My part (which I think You guys all expected), because it looks like I suck at reading REAL easy instructions.
So the problem was I didn't pay attention to one of the prompts of this tool/guide: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
After downloading all 3 stock firmware/update files, dropping them, and then renaming them in the HWOTA8_Mate10\repack folder so I could run the repack.bat that would patch them. I did that part just easy, but then I managed to screw up a even easier thing, which was running the ota.bat and following the instructions.
What went wrong was I didn't press ENTER after opening the recovery, so My device never got to do the updating/installing part that all these previous steps were leading up to.
Lesson learned: Read, and follow the steps, it really isn't that hard
SOLVED

Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.

_hunter said:
Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.
Click to expand...
Click to collapse
Xposed oreo beta 4? Or an another version?
Sent from my HUAWEI BKL-L09 using XDA Labs

Magisk 16.4 with Pixel XL and OTA

Hi,
I am trying to install an OTA using Magisk and the method johnw has outlined. (start Magisk, uninstall and replacing the modded image/boot with the stock ones, then install the OTA, before it asks for a reboot and you reboot - install Magisk on the other boot slot.) this works up to the point where it reboots the phone - then it gets caught in a bootloop for about five times, and then a message appears that it couldn't install the OTA.
Has anyone been able to install the OTA using the outline method?

Basically same Problem here with the non-XL Pixel 2. However after the I think 5 times boot loop I ended up in the Google Logo screen with the Progress bar. However after over 50 minutes it wasn't gone. Hard reset didn't help - stuck again at the same Situation. Will now reflash the phone.
Would be also interested in Feedback from others on how to install the OTA successfully.

srynoname said:
Basically same Problem here with the non-XL Pixel 2. However after the I think 5 times boot loop I ended up in the Google Logo screen with the Progress bar. However after over 50 minutes it wasn't gone. Hard reset didn't help - stuck again at the same Situation. Will now reflash the phone.
Would be also interested in Feedback from others on how to install the OTA successfully.
Click to expand...
Click to collapse
I have run into similar issues in the past. I wasn't sure if I was not getting the sequence of steps correct or not. In the end, I decided that the more straightforward and easiest method for me was just to flash the full factory update (removing the -w to preserve my data). Once upgraded to the latest release successfully, I just fastboot boot TWRP (don't install TWRP), then flash Magisk zip from there. This has worked for me the last several updates with no issues and the entire process takes less than 30 minutes. Perhaps not as elegant as the method recommended in this forum, but less moving parts and steps that can go wrong in my experience.
Good luck!

sb1893 said:
I have run into similar issues in the past. I wasn't sure if I was not getting the sequence of steps correct or not. In the end, I decided that the more straightforward and easiest method for me was just to flash the full factory update (removing the -w to preserve my data). Once upgraded to the latest release successfully, I just fastboot boot TWRP (don't install TWRP), then flash Magisk zip from there. This has worked for me the last several updates with no issues and the entire process takes less than 30 minutes. Perhaps not as elegant as the method recommended in this forum, but less moving parts and steps that can go wrong in my experience.
Good luck!
Click to expand...
Click to collapse
Thanks for your feedback.
Here's another way that I just tested successfully:
E.g. for updating from April to May:
- Still being on April patch Level, patch boot.img from May using MagiskManager, transfer to Computer
- Boot into Bootloader. Flash stock boot Image from April
- Boot into the stock recovery and install the OTA, e.g. using adb sideload
- After the OTA is installed, select to boot into the Bootloader again
- In the Bootloader Flash the patched boot.img from May that was created in the first step
- Reboot phone and enjoy the May update
@sb1893: I think your way is more comfortable though as one doesn't need to prepare a boot Image file.

@srynoname and @sb1893, thanks for the workarounds. I am doing what srynoname suggested, and while it works without any hiccups, I was really really hoping to be able to install either the OTA or a full factory image (without wiping the data) but with preserving magisks and root *without* having to connect my phone to a computer
So if you have any other ideas...
And to be honest... I am more than surprised that we're the only ones struggling with the update process.

@topjohnwu
Do you habe any hints about what we're doing wrong?