yashsingh1/xdaforums huggingface dataset:
[Moto G5 Plus Guides, News, & Discussion] BlackScout:
How do I proceed if I want to fastboot flash stock so I can receive official OTAs? Do I first need to run the commands to fix the permissions of persist? ?

Is it bad that I made the backup after flashing a custom ROM?

Can I restore the permission of persist while running an Oreo ROM and be fine?
[Moto G5 Plus Guides, News, & Discussion] jason veltman:
So it seems that after messing with my APN settings and setting radio to LTE only, I got volte back and everything works now. I immediately backed it up...then restored my havoc 8.1 backup ..restored persist and efs...volte works perfectly (for now ha)

Thanks
[Moto G5 Plus Guides, News, & Discussion] Psycake:
Hey guys.

I found this thread, did the test and I found out I got a bad persist. I'm currently on a custom Oreo ROM, and don't plan on installing any stock Nougat or Oreo ROM, though Iwould like to install a custom Pie ROM in the near future when they start rolling out. I also got several EFS backups stored in multiple places.

Now, my question is: do I have to fix my persist in this case?

Now that I found out about this, I want to backup my persist, but I want to make sure if it's good if I backup my bad one, or if it's better to backup my good one.

I have no problems with my IMEI, and my persist is intact.

Thanks!
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Hey folks, grouping all the replies into one...

The commands are only applicable to Stock Nougat roms. Custom Oreo roms change the ownership, that is expected. If Volte or something else doesn't work on the custom rom, then it may be a bug in the custom rom, or a setting. If you fully revert back to stock and apply the ownership fix, then it should work.

Yes, I get an H+ icon on my phone, so that would be what you'd want if the procedure worked. If Volte doesn't work on the custom rom, then it's a custom rom issue.

Best thing to do is to run the ownership fix in TWRP via the zip fix, and then immediately reboot to bootloader and apply the fastboot commands.

The test is for running in Stock Nougat only. Oreo custom roms will change the ownership, so that is expected that you get owners like oem_2952 or similar. You don't need to 'fix' persist if you continue to run your custom rom.

As a general piece of advise, back up your persist now as it is so that you can always restore it in future if you really need to. If you went back to Nougat, then if you have problems you can apply the fix.
[Moto G5 Plus Guides, News, & Discussion] Jrhotrod:
Having an odd issue that I thought wouldn't be a problem. I had no problems with the procedure - just to clarify. It appears to have worked perfectly.

When I ran the commands and completed the procedure, I had my "cached" EFS restored onto my phone. It's the workaround that people have been using to get around the issue - if they had an IMEI and cell signal on a custom ROM, they backed up their EFS and could restore that on the stock ROM to get IMEI and signal back.

Upon completing the procedure, I booted into TWRP and restored my partitions from the original, untouched stock ROM - specifically: EFS, persist, system, recovery, and logo. Usually, restoring this EFS would render me with no IMEI or cell signal, since it didn't have that information cached in it like the backed-up one did. However, since the procedure was successful, I had my IMEI and my signal - everything appeared to be good!

A few days later, I rebooted my phone (like I usually do every few days) and was met with no cell signal. "Searching for Service" appears in the top-left of the lock screen and in quick settings. For a hotfix, I attached my phone to my laptop and ran the fastboot commands:

fastboot erase modemst1
fastboot erase modemst2

This fixed my issue for the time being. However, every few times I reboot now, I will once again have no signal and have to run the commands.

I don't know why it's happening, and it might be an issue that has nothing to do with this. But I thought I'd post it here in case anyone else had the same problem, and hopefully were able to solve it.

Thanks for any assistance!
[Moto G5 Plus Guides, News, & Discussion] bra1niac:
- Which version of STOCK rom are you on? Oreo 2nd soak test, Build OPS28.85-3

- Are you rooted, and running the commands under root privileges? Yes, with Magsik 16.7 and yes.

- Have you ever flashed someone else's, or another device's persist? Yes, I was involved early in this thread: https://xdaforums.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524

- What functionality are you missing and trying to restore (e.g. IMEI=0, VolTE, etc)? IMEI=0

- Do you get any error messages when trying to execute the commands? Yes, there is no rfs user to make the owner of these directories.

potter:/ # ls -l /persist

ls -l /persist

total 100

drwxrwx--- 2 system system 4096 1969-12-31 20:01 alarm

drwxr-xr-x 2 mot_pwric mot_pwric 4096 2018-07-16 10:35 batt_health

drwxrwx--- 2 bluetooth bluetooth 4096 2018-08-13 10:05 bluetooth

drwx------ 2 root system 4096 1969-12-31 20:01 bms

drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 20:01 bt

drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1970-01-05 21:11 camera

drwxrwx--- 2 system system 4096 1970-01-05 21:11 chargeonly

drwx------ 4 system system 4096 1969-12-31 20:01 data

drwxrwx--- 2 system graphics 4096 1970-01-05 21:11 display

drwxrwx--- 2 system system 4096 1969-12-31 20:01 drm

drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 1969-12-31 20:01 factory

drwxrwx--- 3 oem_2903 oem_2904 4096 1969-12-31 20:01 hlos_rfs

drwxrwx--- 2 root root 4096 2018-08-13 10:05 lost+found

drwxrwx--- 2 radio radio 4096 1970-01-05 21:11 mdm

drwxrwx--- 2 system system 4096 1969-12-31 20:01 misc

drwxrws--- 2 mot_tcmd mot_tcmd 4096 1970-01-05 21:11 paks

drwxr-xr-x 11 mot_tcmd mot_tcmd 4096 1970-01-05 21:11 public

drwx--x--x 6 oem_2903 oem_2903 4096 1969-12-31 20:01 rfs

drwx------ 2 root root 4096 1970-01-05 21:11 sds

drwxrwx--- 2 system system 4096 1970-01-05 21:11 secnvm

drwxrws--- 2 drmrpc drmrpc 4096 1969-12-31 20:01 security

drwxrwx--- 2 system system 4096 2018-08-18 11:19 time

drwxrwx--- 2 media media 4096 1970-01-05 21:11 vpp

drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 20:01 wifi

drwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 20:01 wmdrm

potter:/ # find /persist -type f

/persist/.twrps

/persist/batt_health/age

/persist/mdm/oma_dm_update

/persist/public/hiddenmenu/data/activation_date

/persist/public/hiddenmenu/data/mobile_data_rx

/persist/public/hiddenmenu/data/mobile_data_tx

/persist/public/hiddenmenu/data/wifi_data_rx

/persist/public/hiddenmenu/data/wifi_data_tx

/persist/bluetooth/.bt_nv.bin

/persist/time/ats_2

/persist/time/ats_1

/persist/time/ats_16

/persist/rfs/shared/server_info.txt

/persist/rfs/msm/mpss/server_check.txt

/persist/chargeonly/cooldown

potter:/ # chown -R rfs:rfs /persist/rfs

chown -R rfs:rfs /persist/rfs

chown: bad user 'rfs'

1|potter:/ # chown -R rfs:rfs_shared /persist/hlos_rfs

chown -R rfs:rfs_shared /persist/hlos_rfs

chown: bad user 'rfs'

See additional comments here: https://xdaforums.com/showpost.php?p=77387674&postcount=55
[Moto G5 Plus Guides, News, & Discussion] ST Dog:
Oreo (stock or otherwise) doesn't have the rfs user.
[Moto G5 Plus Guides, News, & Discussion] bra1niac:
I'm sure that's only going to be the start of my issues. Before I flashed the 1st Oreo soak test, I ran these commands on the phone as well. At that point I was running the Nougat flashable ROM w/June 2018 sec updates linked in the OP. There the ownership of rfs and hlos_rfs were correct, but the bin files under /persist/rfs were not there.

Without an EFS backup to restore, I'm not sure if there is a next step here.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Yeah, unfortunately without those bin files you're out of luck. The Oreo soak test builds I did do back up the EFS on install though, so if you had IMEI before installing the Oreo build then you could hopefully get your IMEI back that way. As long as you still have your internal storage intact (i.e. didn't go and delete everything) they are there - they'll be named /sdcard/backup_20180820_modemst1.img or similar, etc. Refer to the second post in the Oreo thread for more details. (And sorry to send you back and forth between posts.)
[Moto G5 Plus Guides, News, & Discussion] bra1niac:
Yeah I didn't have an IMEI running the Nougat June sec update stock ROM either, so the EFS backup there wasn't any help. I might wipe it all and try a custom Oreo ROM and run through some trial and error.
[Moto G5 Plus Guides, News, & Discussion] samsingh4u:
Sir anyway to fix imei issue if i flashed someone's persist accidently amd i didnt have any backup for mine.
[Moto G5 Plus Guides, News, & Discussion] echo92:
As far as I understand, I don't think there's a way to fix your IMEI issue if you do not have your original persist partition if you're on the stock Nougat ROM.

You may be able to temporarily fix it if you have an EFS (modemst1/modemst2) backup, however, applying an OTA update that updates your modem erases that (possibly because an old EFS may not be compatible with the newer modem), and as you have a different persist, the subsequent rebuild of the modemst1/modemst2 may not work and so you'll have no IMEI.

Your best bet may be to revert back to custom ROMs - you could give the TWRP Oreo soak test flashable a try but please read the initial post first. https://xdaforums.com/g5-plus/development/oreo-twrp-flashable-stock-builds-coming-t3830482
[Moto G5 Plus Guides, News, & Discussion] negativzeroe:
Ok so I'm not sure where to go at the moment, just need a nudge in the right direction. I have EFS looks like because I still have IMEI so I'm wanting to do this correctly. Haven't worried unil now because allegedly the issue comes from going down to N from O. Well apparently I need to downgrade back to stock N before flashing Stock O. So now I'm here.

IN RECOVERY persist shows 0mb to back up. EFS shows 4mb to back up.

With the info above, I am thinking I just flash the persist fix, back them both up, flash N, restore them both, flash O. That sound about right?

EDIT, I have a similar output as [MENTION=5422877]SupaJ[/MENTION]
[Moto G5 Plus Guides, News, & Discussion] darknite39:
LTE came back but disappears after reboot

Here are my findings with what appeared to be a bad persist based on the terminal output, but it didn't totally match the example so I tried the persist fix anyway.

I lose LTE after a reboot unless I restore my EFS from a backup, run the persist fix zip, and wipe cache/dalvik. After a series of tests (my verizon signal is always ****ty, so just look at the speed comparisons rather than the total speed for each test):

Straight reboot – no signal at all

Restore EFS, then boot – LTE came back (1.43 down / basically no up--like 0.01)

Restore EFS + fix – LTE came back (2.31 down / basically no up)

Restore EFS + fix + wipe cache / dalvik – LTE came back (better ping, 9.03 down / 1.43 up)

I am now going to do the restore/fix/wipe and make a complete backup.

THANK YOU FOR YOUR HELP! It's taken me more than 15 hours of tinkering to fix this. I've learned a lot in the process.

Edit: Uh-oh. It looks like the LTE doesn't "stick" even after the full process described above. After maybe 10 mins the LTE performance takes a dump. Sigh.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Hi - your persist looks intact. Back it up now and save it to the cloud. The ownership looks normal for an Oreo custom rom, and if you were to try stock oreo, it would change the ownership anyway.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
The size of persist in TWRP is normal, it's only some number of KB that gets rounded down to 0MB.

You can do a clean flash to Stock O soak test, no need to go to Stock N first. Stock O changes ownership on boot, so no fix is needed there.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
[MENTION=7896819]Jrhotrod[/MENTION] was having similar issues on stock Nougat, but I think tried upgrading to the stock Oreo soak test - How did that turn out for you Jr?

If it works better for him, then maybe just try that? Also, can you confirm which rom you're currently using?
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Edit: Deleted due to time travel issue with XDA forums...
[Moto G5 Plus Guides, News, & Discussion] darknite39:
I'm running 7.0, Nov 1 security patch

Baseband M8953_37.46.07ePOTTER_NA_CUST

Kernel 3.18.31-perf-g4524a37

hudsoncm@ilclbld99#1

Mon Nov 20 09:32:29 CST 2017

Build NPN25.137-92

(I know this is probably more info than needed, but I figured more detail might be useful.)

I did a test of my LTE every 10 mins to see when it goes wonky. 10min was good, but 20 resulted in a dip in performance but not as bad as before (the area may be more congested than this morning--my upload speed was near zero before but now it's back to around 2Mbps--it's just the download that dropped in half). The testing followed the procedure described above, after which I made a full backup--including persist--and rebooted. And I am somewhat tempted to try to flash my backup (sans modems) of PixelExperience--everything was working so well except LTE. :/

Edit: OK, it stuck for an hour, so I tried a straight reboot, and it's now getting a signal (1x) for about one out of every 15 seconds.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
That version of stock nougat is quite old, and there have been minor updates to the modem since then. You could try flashing a more recent nougat and see if that improves things too.

Also I note your baseband ends with an E. That means there's an issue, can't remember which though, might be bad persist?
[Moto G5 Plus Guides, News, & Discussion] darknite39:
I updated to the June security patch, and the behavior is the same (can't just boot straight into the OS and keep connectivity). I'll tinker a bit more tonight and see if anything helps. I'm not sure about the baseband, but I think the difference is between an E and an R at the end (I read that somewhere, but I didn't pay enough attention at the time).

Edit: The newest nougat build exhibited the same behaviors, and the oreo soak gives me no signal no matter what I do.
[Moto G5 Plus Guides, News, & Discussion] Jrhotrod:
Working great! Super battery life, total stability - and no more signal drops :victory:
[Moto G5 Plus Guides, News, & Discussion] negativzeroe:
The thread for the ROM states that there are known partitioning issues and that we need to flash stock N first? Or have these not been issues when wiping all or something?
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Sorry man, out of ideas... I could only really suggest you downgrade back to a full stock nougat that gives you some signal again, and then if you really want to you could try some custom ROMs and stick with whatever gives you the best signal.

Edit: also because your baseband ends with E, indicating that the is an issue, you just may never get back full functionality.
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
The issues I think you're referring to are when going to custom Oreo ROMs after flashing the oreo soak test. The issue is the binaries (blobs) are incompatible. The best way of going back is to flash the full stock nougat first, then flash the custom Oreo rom. But if you're just sticking with stock Oreo ROM, just flash and forget :)
[Moto G5 Plus Guides, News, & Discussion] negativzeroe:
Well I'm coming from custom Oreo, Resurrection Remix. Just want to make sure it's as glorious and smooth a process as a fiber-induced poop lol.
[Moto G5 Plus Guides, News, & Discussion] darknite39:
Eh, I got it for $105 off of swappa, so I'm not that worried about it. All it means is that if someone steals it that they'll never get it to work. :)

I appreciate your thoughts!
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Hey, looks like it's normal there. Do you have your IMEI? If you're just having baseband issues, I wonder if it's just that you need to erase your EFS and reboot? Take a backup of your EFS before doing that step though. Easiest way to erase EFS is probably to reboot into fastboot mode and issue these commands from your PC:

fastboot erase modemst1
fastboot erase modemst2

If that doesn't work, or you don't have your IMEI, reboot into TWRP, try typing in these commands from TWRP (either via terminal or adb):

mount /dev/block/bootdevice/by-name/persist /persist
hexdump /persist/rfs/msm/mpss/dhob.bin | head -n20
hexdump /persist/rfs/msm/mpss/dhob.bin.bak | head -n20

The output from the last two commands will tell me what your dhob.bin and dhob.bin.bak looks like.
[Moto G5 Plus Guides, News, & Discussion] SupaJ:
Hi. I was running a custom OREO. Everything worked fine(LTE, Fingerprint, etc) Last night, I tried the the TRWP Stock Oreo for the Moto G5 Plus. I then reverted back to the custom OREO by flashing a TWRP backup which I made before I install the official stock Oreo. Now, my fingerprint isn't working. I connected my phone to a PC and tried the following from the OP via adb:

chown -R rfs:rfs /persist/rfs

This command complains about rfs being a bad user:

chown: bad user 'rfs'

Where do I go from here?
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
The chown commands are for stock nougat. The issue that you have is covered under the first and second posts on the TWRP flashable Oreo thread. You need to downgrade to full stock nougat first.
[Moto G5 Plus Guides, News, & Discussion] stormrider57:
hi there, i have the same issue, im now on bootleggers custom rom, everything is good, but i lost my volte, i have no issue with imei,LTE is shown ont the top of the taskbar, but switch to h+ when im calling, so no volte.

I have saved all my stock rom (nougat) included EFS

When i go to secret menu *#*#4636#*#* informations .......everything is checked volte provisioned etc...

when im looking to IMS statut there is a sh** no registration ims ?

im rooted

im on twrp (r20)

i don' t have issues with my IMEI

im a noob, i can flash, root, or unlock bootloader ;)

thx

g5s plus, xt 1805, 32,4 gb ram

---------- Post added at 12:54 PM ---------- Previous post was at 12:50 PM ----------

some pictures

total 100
drwxrwx--- 2 system system 4096 1970-01-01 01:01 alarm
drwxr-xr-x 2 oem_5001 oem_5001 4096 1970-01-01 01:01 batt_healthdrwxrwx--- 2 bluetooth bluetooth 4096 2017-07-27 08:45 bluetooth
drwx------ 2 root system 4096 1970-01-01 01:01 bms
drwxr-xr-x 2 oem_5004 bluetooth 4096 1970-01-01 01:01 bt
drwxr-xr-x 4 oem_5004 oem_5004 4096 1970-01-01 01:01 camera
drwxrwx--- 2 system system 4096 1970-06-13 05:32 chargeonly
drwx------ 6 system system 4096 2018-03-12 04:42 data
drwxrwx--- 2 system graphics 4096 1970-06-12 23:05 display
drwxrwx--- 2 system system 4096 1970-01-01 01:01 drm
drwxr-xr-x 5 oem_5004 oem_5004 4096 2017-07-27 08:45 factory
drwxrwx--- 3 oem_2951 oem_2952 4096 1970-01-01 01:01 hlos_rfs
drwx------ 2 root root 4096 1970-01-01 01:00 lost+found
drwxrwx--- 2 radio radio 4096 2017-07-27 08:45 mdm
drwxrwx--- 2 system system 4096 1970-01-01 01:01 misc
drwxr-xr-x 11 oem_5004 oem_5004 4096 1970-06-13 05:32 public
drwx--x--x 6 oem_2951 oem_2951 4096 1970-01-01 01:01 rfs
drwx------ 2 root root 4096 1970-01-01 11:17 sds
drwxrwx--- 2 system system 4096 1970-06-12 23:05 secnvm
drwxrws--- 2 oem_5007 oem_5007 4096 2018-03-12 04:43 security
drwxrwxr-x 2 root root 4096 1970-01-01 01:01 sensors
drwxrwx--- 2 system system 4096 2018-08-22 17:37 time
drwxrwx--- 2 media media 4096 1970-06-12 23:05 vpp
drwxr-xr-x 2 oem_5004 oem_5004 4096 1970-01-01 01:01 wifi
drwxrwxr-x 2 oem_5003 oem_5003 4096 1970-01-01 01:01 wmdrm

so i think i have a bad persist, am i right ?

edit: this commands are from custom rom ,not stock.
[Moto G5 Plus Guides, News, & Discussion] stormrider57:
is this a solution maybe ?

https://xdaforums.com/apps/magisk/module-v4-volte-enabler-t3649613
[Moto G5 Plus Guides, News, & Discussion] echo92:
Hmm, what happens if you set your network type to LTE/UMTS auto (PRL) rather than LTE/CDMA/UMTS? Also, can you confirm that your SIM still receives VoLTE (e.g. by testing in another device)?
[Moto G5 Plus Guides, News, & Discussion] stormrider57:
hi , what happens ? nothing, it was just a test to give a try to "LTE/cdma/umts,by default it was on LTE/UMTS auto prl

---------- Post added at 03:48 PM ---------- Previous post was at 03:45 PM ----------

before the custom rom flash i had volte (hd)
[Moto G5 Plus Guides, News, & Discussion] NZedPred:
Hi. Looking at the output of your command (well, the first anyway - there's also the second one 'find /persist -type f' would also give some other useful information), that's normal for an Oreo custom rom. But as you say that you have volte before the custom rom, and by that I assume that you mean when on stock, so does it work if you go back to stock?

If you want to try going back to stock, I have TWRP flashable of stock Nougat for Sanders here:

https://www.androidfilehost.com/?w=files&flid=280579

Note that you will need to flash both the persist fix and the full Nougat rom.

I have a very simple philosophy when it comes to things like Volte - if it works in stock with the fix applied, but doesn't work with a custom rom, then it is a bug or issue with the custom rom (in which case raise it with the maintainer, or change roms).

Also, while you're doing this, please back up your persist now anyway and save it to the cloud. If your version of TWRP doesn't support backing up persist, there's an alternative detailed in the second post of this thread.
[Moto G5 Plus Guides, News, & Discussion] barbaroja:
Tried erasing modemst1 and 2. Bootlooped a few times and again baseband (not found in BL... unknown in android) I think the phone knows the IMEI bc FASTBOOT GETVAR ALL outputs the number.

Output from hexdump /persist/rfs/msm/mpss/dhob.bin | head -n20:

0000000 027f cec0 c0d1 eaf1 2c57 a50b b0a7 bfb1
0000010 937b a0c7 5899 ad19 164b 78c1 6b19 fe2d
0000020 fe2d 5f83 4f37 aa1c b56b d5d5 17ef d77e
0000030 ec50 38b0 282f d203 4a4b f7e3 b755 90d0
0000040 da79 0c95 d599 ea25 aca7 27d4 3dcf 87bf
0000050 7205 b510 06f8 e42d 6002 6248 c65e b4c2
0000060 37e2 4901 f07b bfc5 a47d 6d57 7260 4b47
0000070 446c 6525 c5c3 ff9f 63a8 8278 fc3c dd8b
0000080 93ca dbe6 66f6 9c16 be74 d9a7 f59a 56fb
0000090 998f 407b f3c9 9a08 35a7 d371 063e 2a54
00000a0 27c4 c8c0 b7df 5ece 93e6 36df fad6 032f
00000b0 83e0 7f27 68c7 72ff dbac a706 4413 0117
00000c0 81c7 a6f1 1052 42a9 cb9f 111b fac9 812e
00000d0 b4d9 a4b8 629e 9aa5 6df2 77a0 4461 0013
00000e0 c2a4 6b4d 2d62 5478 1462 a7d0 f9b3 5193
00000f0 8250 98ca b5e2 37f5 205c df9a 39fd 1c55
0000100 502e 6570 d3f8 d55c e4d0 d521 037c 6423
0000110 ef42 16ec f2c7 a7b8 7088 9607 7e17 824e
0000120 545b 3e53 09d0 2a17 5fc4 5aea 4c2c d756
0000130 196a b2db 4111 87f3 57f1 4e6c 5e71 ec25

Output from hexdump /persist/rfs/msm/mpss/dhob.bin.bak | head -n20:

0000000 0846 3bba bcee 056c 35c2 52fc 35fb 445c
0000010 00a6 9e7e a1eb 56b1 3b93 4a81 6ad5 b9c7
0000020 e21d 2f45 e6a1 0635 6834 9ff5 6f01 15f1
0000030 28fb c1c5 a0c0 340d 8a7b 9cb7 aa36 f445
0000040 d2b2 f67f 6541 7a3e c03b 8490 d034 0fe9
0000050 5923 bcb0 c77b 939a e180 78f4 0a80 1ce0
0000060 57f3 6e6f bb91 5cc4 b4c1 24e0 9fe7 55f3
0000070 2c5e 441e dd8e f333 f6e1 1ea3 5003 7036
0000080 61ea 4ba1 4cc9 6980 8bad d597 6c18 3886
0000090 516c bff8 f39c a190 fc70 dd17 94f1 88ea
00000a0 5d2d 7de4 b75e 20fe 4b74 b16b 7e95 d04c
00000b0 4445 29c3 3d77 0b22 3352 7dfd 32b2 00ea
00000c0 c6e8 1908 0a56 6e1e cd4e 7e36 35c4 536b
00000d0 c619 a137 98b1 3389 208c 757a 18ce e6d7
00000e0 916d e102 76f5 d5d9 0777 0dfa a60f 9144
00000f0 4b9e 049e 1585 6614 f095 1d28 b1cd f11e
0000100 3cba 70b2 6175 5ce4 7233 d01d 060d 5638
0000110 f2b9 d060 659e 5726 c092 4aec 0d2b b827
0000120 ea28 c2c8 1c97 8297 daff d814 6b66 033c
0000130 f459 1167 2d6d fc66 df6c b84f 3a54 31d5

Thanks for your help. You are basically the only person I think is able to fix this. BTW. It happened while taking an OTA. No mod from my side apart from rooting and a kernel that enabled magisk to work fine.