Database Users

How to root on stock 7.1.1 using Magisk

So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?

auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.

marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.

Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.

auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.

marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?

auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.

How should I update my phone's software if I have rooted it?

Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.

Ebeninyo said:
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Click to expand...
Click to collapse
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda

strongst said:
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
Click to expand...
Click to collapse
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.

Ebeninyo said:
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Click to expand...
Click to collapse
With which recovery and rom are you able to access your internal storage?

strongst said:
With which recovery and rom are you able to access your internal storage?
Click to expand...
Click to collapse
I've only tried using TWRP as my recovery, Pixel experience rom and oxygen os rom. The thing is because upon entering the phone after flashing a rom you can't access the internal storage of the phone with TWRP because phone encrypts itself. That means I can't dirty flash it and need to wipe everything out with TWRP then reboot TWRP again and install new rom after that flash magisk and reboot to system and set everything up from the scratch.
When I started this thread I didn't knew how to dirty flash a rom. Now I know and realize the problem I'm having is phone's encryption.

UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.

Ebeninyo said:
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Click to expand...
Click to collapse
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.

strongst said:
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
Click to expand...
Click to collapse
Can you be able link me that patch and instructions?

Ebeninyo said:
Can you be able link me that patch and instructions?
Click to expand...
Click to collapse
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.

strongst said:
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
Click to expand...
Click to collapse
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.

Ebeninyo said:
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Click to expand...
Click to collapse
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.

strongst said:
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
Click to expand...
Click to collapse
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.

Ebeninyo said:
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Click to expand...
Click to collapse
Cool:good:

.

.

HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?

HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.

.

.

HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.

.

OP6T brick, how to recover without data loss?

Hey folks, I somehow bricked my OP6T and I hope for help to recover without data loss.
OP6T
OxygenOS (stable, not the latest though, I guess it's 10.3.2)
TWRP Recovery (twrp-3.3.1-31-fajita-installer-mauronofrio.zip)
Rooted with Magisk (not the newest version, the one before)
How this happened...
I wanted to update Magisk from within the app via the recommended way. But the first click on the button did not start the installation, so I clicked again, few seconds later the first installation dialog appeared, installation ended with a positive result. Then the second installation dialog appeared and ended with an error.
I rebooted and it ended up with the bootloader screen. No recovery, no system booting up. The TWRP 3.3.1-31 did not start using this command:
Code:
sudo ./fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img
But TWRP finally started using the newer twrp-3.3.1-32-fajita-installer-mauronofrio.zip. However, neither slot a nor slot b will boot into system.
Booting system from slot a leads to bootloader, booting system from slot b ends up in a boot loop. Also, using the file manager within TWRP shows me encrypted directories and files. Now I am lost.
Is there a way to recover / unbrick without losing all the data?

Try restoring the stock boot image of whatever ROM you're using.
or You can use magisk patched img, instructions in magisk thread.
I read somewhere that you should not manually change the boot slots. The system decides when it must change the slot.

devilrulz4ever said:
Try restoring the stock boot image of whatever ROM you're using.
or You can use magisk patched img, instructions in magisk thread.
I read somewhere that you should not manually change the boot slots. The system decides when it must change the slot.
Click to expand...
Click to collapse
Restoring means losing data. This is what I wanted to avoid. I use stock OxygenOS, as mentioned above.
Since my system does not boot up, the system won't decide. Actually I hoped that things are not that bad and if I change the slot I maybe could have been lucky and system is booting up from that slot, but obviously nothing worked out yet.

benkxda said:
Restoring means losing data. This is what I wanted to avoid. I use stock OxygenOS, as mentioned above.
Since my system does not boot up, the system won't decide. Actually I hoped that things are not that bad and if I change the slot I maybe could have been lucky and system is booting up from that slot, but obviously nothing worked out yet.
Click to expand...
Click to collapse
Since you'll only replace the boot image your data will be safe. Boot and data are stored in different partitions.
You can use fastboot to do that or TWRP.
You will have to extract the boot image of OxygenOS before you can flash it. You'll need payload dumper to do that.
I suggest you google how to use it and all; check the guides section as well. If you need any more assistance then ask here.
Since the boot partition was corrupted it couldn't change the boot slot.

I think he means flash the same stock image you are currently running. This can fix many system issues with no data loss

devilrulz4ever said:
Since you'll only replace the boot image your data will be safe. Boot and data are stored in different partitions.
You can use fastboot to do that or TWRP.
You will have to extract the boot image of OxygenOS before you can flash it. You'll need payload dumper to do that.
I suggest you google how to use it and all; check the guides section as well. If you need any more assistance then ask here.
Since the boot partition was corrupted it couldn't change the boot slot.
Click to expand...
Click to collapse
bladestonez said:
I think he means flash the same stock image you are currently running. This can fix many system issues with no data loss
Click to expand...
Click to collapse
Thanks guys. For some reasons (???) the last attempt with TWRP (twrp-3.3.1-32-fajita-Q-mauronofrio.img) lead to access to all files via TWRP. So atm I create a complete backup of /sdcard pulling everything via adb, which kind of takes a lot of time due to USB 2. After that I push latest OOS ROM, TWRP and Magisk and give it a try. At least I get even not clouded data back.
Will keep you updated... please stay tuned. :fingers-crossed:

benkxda said:
Thanks guys. For some reasons (???) the last attempt with TWRP (twrp-3.3.1-32-fajita-Q-mauronofrio.img) lead to access to all files via TWRP. So atm I create a complete backup of /sdcard pulling everything via adb, which kind of takes a lot of time due to USB 2. After that I push latest OOS ROM, TWRP and Magisk and give it a try. At least I get even not clouded data back.
Will keep you updated... please stay tuned. :fingers-crossed:
Click to expand...
Click to collapse
Backup completed
pushed OOS ROM
TWRP and Magisk
dirty flashed ROM
rebooted to recovery
flashed Magisk
rebooted to system
That's basically it and everything works again. The most important step was, that for some reason TWRP let me access the decrypted file system. And then ADB is very helpful, brought my device back to live.
Thread will be closed shortly.

Thread closed at OP request

I cleared dalvik cache

Well i was just flasing my new boot.img that was patched with magdisk dowloaded the correct version 11.0.4.4 - EU IN11BA -IN2023 package from oficial one plus sites after the flash evering worked kinda ok the device rebooted like 3 times it was already rooted before so magdisk was loading all modules i guess everything loaded ok after third reset i ve gone ahed tested it for some time then something happend i was all of sudden unable to launch any apps and the ones that launched crashed withni 10s well i said to myself i ve seen this before on my huawei p9 and what i did there to fix this was clearing dalvik cashe then reset (huawei was running RR from open kirin and android 8) on huawei the main cause for this was messing with the cahe with lucky patcher well it even has a clear dalvik cache funuction so i launched the app on one plus and cleared the dalvik cache and after restart i got into boot looping with no ending (well after that i went to internet to read that dalvik cache is not even a think) so i tried to flash back the stock boot well that didnt fix so if somebody could point me to how to restore the device with keeping the data it would be appreciated i tried some restores like flashing some system partitons and overall trying to flash stuff from this guide https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/ with the updated version 11.0.4.4 of the ota package well nothing really happed half of the partitions are renamed and i dindt find the names for them anywere so i gave up to find help here.
So yea just a simple reboot to fix the device isnt enough for me i always have to "fix" something diferently.
well i ve let the device boot loop for some time and well i got at least some error
Boot Reason : fs_mgr_mount_all
unable to parse kernel log. for more debug information.
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
So i maybeee destroyed the partitions i guess. (well my thinking is that the LP didnt find the partiton so it tried to format something that was similar to it maybe acros multiple partitons and did kinda nasty wipe.)

First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck

dladz said:
First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck
Click to expand...
Click to collapse
Well i would like to try booting it into safe mode but the pohone after i ve letted it to boot loop for like 10 mins desnt event try to boot again i changed nothing so i guess something got modified in the phone to prevent bootloops when i power it on it just reboots into recovery and it would be really nice if you could give me links to those guides i just cant find them thanks