Hi guys, I rooted a friends s3 to enable aws on it and it was working , yesterday she calls me and tells me that it is not working anymore. So I check it and notice there is no root access.
I try to install it using CFRoot . odin flashes fine , I see it running on the phone but once you boot in Supersu states it is not rooted.
Next tried a slew of programs, towelroot apk but nothing works.
Next tried to factory reset, boot in to twrp and I get asked for a password, hit cancel and I get in to the menu. I try to mount the sd card and it fails, trying to install zip from sd fails, factory reset seems to work, wipe data fails and ask for a decrypt code.
I also tried using CWM recovery with basically the same results.
THe last thing I tried was downloading the same firmware 4.4.2 and flashing with odin, it says successful but after rebooting, the phone is exactly the same, nothing changed , it has the same apps, same wallpaper.
I am wondering if my friend let her son play with the phone and turned on some kind of encryption or security that is stopping it from getting wiped back to stock.
Try flashing stock ROM again but uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, factory wipe, reboot.
To root, flash twrp, then flash supersu.zip from recovery.
Download the latest tar version of TWRP from here: https://dl.twrp.me/d2att/
Download supersu from here: http://forum.xda-developers.com/showthread.php?t=1538053
Save supersu to the phone's internal or memory.
When flashing TWRP in Odin, uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, flash supersu.zip, reboot.
Related
I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28
Flash a different rom.
sent from my Dinc
How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.
Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.
Hi, I have a rooted s4 sgh m919. I am running twrp custom recovery. So I just flashed cm 13 nightly build for the s4 and it worked and ran through boot up and everything. Then I realized that I had stupidly forgotten to backup my apps(I though I had but it was a twrp backup). So I returned to recovery mode using adb because my up volume buttons dont work(biggest problem for me now) and used twrp restore of a backup I made before the new rom. Now I know that my twrp backups work because I have successfully restored before but that was using the same rom, this is the first time flashing a new rom. Since I am a noob, I didn't know that I have to factory reset and delvik cache wipe before I restored my backup since they were different roms. Now after booting up and getting past the boot animations it goes straight to a black screen with a bunch of "Unfortunately ______has stopped" for just about every single app I have including system apps and UI. I can boot into the download mode prompt(where it says volume up to download mode, down to reboot) but since my volume up button doesn't I cant boot into recovery or download and do a factory reset. I can boot into safe mode but I still get the same black screen with a bunch of "Unfortunately ______has stopped". I also can't do it through adb since I have no access to phone settings and when I connect to the computer, the computer make a sound recognizing something was plugged in but won't show my phone in the libraries and when I use "adb devices" my phone isn't there. I stored my backup onto my ext sd card if that helps. Is there anyway to get into recovery mode or even just do a factory reset without using volume buttons or the computer? And has anyone else had this problem and if so what is it called(hard brick, soft brick, bootloop.....). Thanks!
You need to fix your up-vol button.
There is also a special micro USB loopback plug which I think can make the device boot into a special firmware loader mode. Then you would use heimdall/odin to replace the firmware, but I have never done that.
As for what to call the problem, I say "dumb user with broken hardware". You knew that your up-vol button was broken and what would happen if you could not get into recovery. Now that it has happened you want a magical fix instead of doing what you already know you need to do. Sorry for honesty.
1st- buy a usb jigg, they go for less than $5 amazon, eBay etc.
2nd - while phone is powered off use the USB jigg to put it into download mode
3rd- use Odin to flash the latest ok3 firmware.
4th - use Odin again to flash cf auto root. (No need to check if it has root the recovery you flash should be able to root it)
5th- use Odin again to flash Philz touch cwm recovery.twrp causes lots of problems when flashing. Philz recovery has been flawless.
6th- flash any rom of your choice. If you can't get into recovery theres an app called quickboot that can put you in recovery as long as you're rooted.
Magisk v20 worked stable on Galaxy A50 but If you want to use Magisk v19.3 you can patch and downgrade it using Magisk Manager - Custom Channel Update https://www.youtube.com/watch?v=vcF0pfdQyW8
-----------------------------------------------------------
Complete Guide for Rooting Samsung Galaxy A50 using Magisk v20 / v19.3 ( tested on SM-A505F ):
* Download the firmware Galaxy A50 (SM-A505F).
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager apk to your phone.
* Install Magisk Manager on your phone.
* In Magisk Manager: Install → Install → Select and Patch a File
* Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
* Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key,* When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears.
* Select Wipe data / Factory reset, Select Reboot to bootloader.* Connect your Samsung Galaxy to PC using USB Cable.
*Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do. Checked "Auto Reboot" and "F. Reset Time" only in options.
* Magisk is now successfully flashed to your device and Rebooting!
* After the device is booted up, do the usual initial setup. It need more time and patient.
* Connect the phone to Internet copy Magisk Manager apk to your phone and Install it
* Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
* Done! You can use Root Checker to check it, Enjoy!
New video Install and Root with Magisk v20 / v19.3 https://youtu.be/ILvgki0pFHE
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Rooting with TWRP+Magisk ( ASH2 baseband version only ), you can watch this video https://youtu.be/kYwJAKBzX1E
well donw
thanks i rooted latest stock F2 firmware
it works
FYI: To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Oh I wish I could get magisk on my phone. Unfortunatly I can't find the firmware, for my phone, anywhere on the internet (A505W). Will do directly once I can!
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
Have you attempted to change your IMEI recently?
Ertogrul said:
Have you attempted to change your IMEI recently?
Click to expand...
Click to collapse
Nope, the only thing i want root for is spoofing with gps joystick.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
I have tried everything but failed, I have tested on some device but it's only happen to A50
will this work with a505gn?
redymedan said:
I have tried everything but failed, I have tested on some device but it's only happen to A50
Click to expand...
Click to collapse
That's seem pretty unstable as it is right now. Was tempting to try this on my A505W, but I'm reluctant now.
Now I'm just wondering why the heck my root is still active with 2 random reboots. Last 20 runs the random reboots made it lose root and got stuck with constant rebooting.
When i started the recovery of samsung backup, it rebooted again (3rd time) (again root is somehow still active). Screw it, gonna forget about the backup and keep it like this. I think the random rebooting seems to happen often when installing much apps.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
Click to expand...
Click to collapse
Read my First post, I have updated it for fixing lost magisk root after reboot
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
Flash whole stock rom. Boot and login. Connect to wifi. Wait few minutes. Flash magisk rom again.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
redymedan said:
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
Click to expand...
Click to collapse
Oh, thanks, I was not able to find this trick, there are lot of infos everywhere and it's hard to find out. Thanks. So both volumes holding and plugin cable.
Thanks again
redymedan said:
Solved: Lost Magisk Root After Reboot
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Click to expand...
Click to collapse
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
AliasGprime said:
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
Click to expand...
Click to collapse
Mine is still rooted since friday. It sometimes reboots randomly. Then i have to reset with volume down and power button or else is keeps restarting. Root is still active then. Battery also died yesterday. Could start up with power key only and root is still active. I still don't understand why but im good.
(I used the root mode function with volume up and power key till logo popsup only once after the flashing of magisk patcher to let it install magisk manager. )
I'm still wondering if I'm the only one with random reboots or constant reboots
Worked great for my SM-A505G.
In summary, after installing Magisk:
(Powering up normally) → (System with NO Magisk)
(Volume UP + Power) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Volume UP + Power) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.