Hi.
I recently rooted my pixel 7 pro, everything went well until... i restarted my phone 2 days later to a boot loop, flashed init_boot back to stock, uninstalled magisk, now when i try to root again it just boot loops, everything seems good when i flash back to stock.
followed multiple guides how to root, did everything right apparently.
Pixel 7 pro
Build number: TQ1A.230105.002
Moishev1 said:
Hi.
I recently rooted my pixel 7 pro, everything went well until... i restarted my phone 2 days later to a boot loop, flashed init_boot back to stock, uninstalled magisk, now when i try to root again it just boot loops, everything seems good when i flash back to stock.
followed multiple guides how to root, did everything right apparently.
Pixel 7 pro
Build number: TQ1A.230105.002
Click to expand...
Click to collapse
Do you have a Magisk mod that may need disabling?
I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?
Lughnasadh said:
Do you have a Magisk mod that may need disabling?
Click to expand...
Click to collapse
I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?
Moishev1 said:
I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?
Click to expand...
Click to collapse
How did you uninstall Magisk? Did you use the "Complete Uninstall" option in the Magisk app?
Lughnasadh said:
How did you uninstall Magisk? Did you use the "Complete Uninstall" option in the Magisk app?
Click to expand...
Click to collapse
i'm afraid not, i just uninstalled, i did however run the adb command after flashing while booting adb wait-for-device shell magisk --remove-module, that didn't help.
Moishev1 said:
i'm afraid not, i just uninstalled, i did however run the adb command after flashing while booting adb wait-for-device shell magisk --remove-module, that didn't help.
Click to expand...
Click to collapse
Try booting into safe mode and then rebooting (should disable mods). Could also be it's something else besides a mod. Someone recently reported that Greenify was messing with Smart Lock settings and causing a bootloop, so if it isn't a mod it could be something like that (a root app causing problems).
Lughnasadh said:
Try booting into safe mode and then rebooting (should disable mods). Could also be it's something else besides a mod. Someone recently reported that Greenify was messing with Smart Lock settings and causing a bootloop, so if it isn't a mod it could be something like that (a root app causing problems).
Click to expand...
Click to collapse
So i did boot into safe mode, then restarted, then flashed magisk. also uninstalled any root app that i downloaded.
currently that didn't help.
Moishev1 said:
So i did boot into safe mode, then restarted, then flashed magisk. also uninstalled any root app that i downloaded.
currently that didn't help.
Click to expand...
Click to collapse
Reboot into safe mode after flashing Magisk and while you are bootlooping.
Lughnasadh said:
Reboot into safe mode after flashing Magisk and while you are bootlooping.
Click to expand...
Click to collapse
IT WORKED!!!!!! Thanks so much!
Moishev1 said:
IT WORKED!!!!!! Thanks so much!
Click to expand...
Click to collapse
Glad it worked. Disabling modules via safe mode only works while you are actually rooted so that's why it worked this time
Related
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
What version of SuperSU are you using? Older versions will cause you to get stuck on the boot animation.
Try v2.79. It should reboot once or twice during first boot after flashing.
Alternatively, you can also root by flashing Magisk v11.1.
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
First, reflash OS to get a stable starting point. Then use the unofficial beta release of twrp to flash. I have heard of success with a fork ( blu something) but basically he merged the same patches.
Check the dm-verity thread for more details
Sent from my ONEPLUS A3000 using Tapatalk
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
Follow this guide:
https://www.youtube.com/watch?v=wwd31NU7VC0&t=4s
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
sguy156 said:
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
Click to expand...
Click to collapse
U can't get rid of this msg.
Navi44 said:
U can't get rid of this msg.
Click to expand...
Click to collapse
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
damiensturdy said:
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
Click to expand...
Click to collapse
Have you tried that personally?
Which version of SU is the system version 2.79 ? First thing is to get the phone to boot first
Navi44 said:
Have you tried that personally?
Click to expand...
Click to collapse
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
damiensturdy said:
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
Click to expand...
Click to collapse
Thank you for telling this.
This was a normal thing in rn3 thread.
Where even we flashed roms with locked bootloader. And whatever we can do through recovery we did with locked bootloader.
Didn't try it here though.
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
sguy156 said:
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
Click to expand...
Click to collapse
Someone said to use system root.
And then lock the bootloader. Since the su is in system, it won't be wiped.
Haven't tried it but should work THEORETICALLY
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
sguy156 said:
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
Click to expand...
Click to collapse
Regular su.
Earlier su used to be system root.
The systemless root started quite recently.
So do I need to use seamless root or SU for 7.0
On using systemless root it will be deleted when you lock bootloader.
You need to use system root for naught
Keep in mind that if you update OOS after locking the bootloader,you'll lose root. Afterwards, you'll have to unlocked the bootloader again - and wiping your device in the process - to reroot.
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted
Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.
i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.
geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.
Hello everyone.
I have some trouble rooting my Redmi 9 and I hope you can help me and that I posted in the right forum.
So far I unlocked the bootloader, installed TWRP and tried to install Magisk with help of TWRP. But if I push the Magisk App button in Android, I get the messages below. It wants to install the full Magisk Manager. If I click okay it displays "Downloading", and that forever. I left it over night. Nothing happened. Only "Downloading" until I reboot the system.
I even tried uninstalling Magisk again. So I renamed a copy of the Magisk .apk to uninstaller.zip. But somehow it didn't work. I don't know how to uninstall it otherwise because I can't open the app.
Does anyone have an idea how to fix it? Or maybe there is another way to get root access without Magisk?
I'm happy for each answer.
Thank you
iHimbo said:
Hello everyone.
I have some trouble rooting my Redmi 9 and I hope you can help me and that I posted in the right forum.
So far I unlocked the bootloader, installed TWRP and tried to install Magisk with help of TWRP. But if I push the Magisk App button in Android, I get the messages below. It wants to install the full Magisk Manager. If I click okay it displays "Downloading", and that forever. I left it over night. Nothing happened. Only "Downloading" until I reboot the system.
I even tried uninstalling Magisk again. So I renamed a copy of the Magisk .apk to uninstaller.zip. But somehow it didn't work. I don't know how to uninstall it otherwise because I can't open the app.
Does anyone have an idea how to fix it? Or maybe there is another way to get root access without Magisk?
I'm happy for each answer.
Thank you
Click to expand...
Click to collapse
first: this is mi 9 forum haha
second: u can rename the zip to apk and install the apk, and maybe works
It seems I mixed that up. Sorry for that.
I guess I will just try to flash a complete image that is already rooted.
iHimbo said:
It seems I mixed that up. Sorry for that.
I guess I will just try to flash a complete image that is already rooted.
Click to expand...
Click to collapse
i mean, flash the zip in the recovery and after that reboot to system and rename the file to .apk and install it in the system (no recovery)
My galaxy s10 is restarting as soon as it enters the OS, i can briefly see the adb device and enter the adb shell, but then the phone restarts, i got the last_kmsg file, anyone might have an idea of what's causing this?
This happened after i installed LSPosed and the xdowngrader module, strange thing that i manage to get both working, but after another restart this started to happen.
Already tried to remove the lsposed from /data/adb/modules and i removed the /data/adb/lspd
GamingSoldier said:
My galaxy s10 is restarting as soon as it enters the OS, i can briefly see the adb device and enter the adb shell, but then the phone restarts, i got the last_kmsg file, anyone might have an idea of what's causing this?
This happened after i installed LSPosed and the xdowngrader module, strange thing that i manage to get both working, but after another restart this started to happen.
Already tried to remove the lsposed from /data/adb/modules and i removed the /data/adb/lspd
Click to expand...
Click to collapse
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
V0latyle said:
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
Already tried, and I realised that the folder /data/adb/modules was empty after the command, but I will try again
V0latyle said:
It sounds like modules are causing the bootloop.
You can disable Magisk modules during boot by using this ADB command:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
I tried again, didn't work, it's not the first time this has happened, strange thing is that the phone had booted fine once after installed a new magisk module, it's just the second boot that it enters this "bootloop", I never tested uninstalling magisk, from what I've seen is easy, just rename to uninstaller.zip and flash using twrp, but I wonder if that could make things worse
GamingSoldier said:
I tried again, didn't work, it's not the first time this has happened, strange thing is that the phone had booted fine once after installed a new magisk module, it's just the second boot that it enters this "bootloop", I never tested uninstalling magisk, from what I've seen is easy, just rename to uninstaller.zip and flash using twrp, but I wonder if that could make things worse
Click to expand...
Click to collapse
Well, I don't think it would make things better, since the modules are already removed.
What modules did you install?
V0latyle said:
Well, I don't think it would make things better, since the modules are already removed.
What modules did you install?
Click to expand...
Click to collapse
I only installed LSPosed and the xdowngrader module, after installed it asked for rebooting, so I did, and the phone booted fine, the module was working, but the second time it wasn't booting anymore, maybe it's the LSPosed?
GamingSoldier said:
I only installed LSPosed and the xdowngrader module, after installed it asked for rebooting, so I did, and the phone booted fine, the module was working, but the second time it wasn't booting anymore, maybe it's the LSPosed?
Click to expand...
Click to collapse
Did you change anything before you rebooted the second time?
The only thing I can really suggest at this point is to reflash with Odin and start over.
V0latyle said:
Did you change anything before you rebooted the second time?
The only thing I can really suggest at this point is to reflash with Odin and start over.
Click to expand...
Click to collapse
I only downgraded 1 app (and the app worked fine), and that's it, i'm really not surprised by this, it has happened before, but it will be an relief if I managed to get it working again without reinstalling the rom, it's really such a pain in the a**... I already "played" with rooting with 2 other phones, and none of them bothered me so much as this s10 hahahahaha
I think I have a twrp backup of the rom somewhere, I will try to locate and restore using that, last time I tried flashing with odin I had to update the phone and patch the magisk all over again :/
GamingSoldier said:
I only downgraded 1 app (and the app worked fine), and that's it, i'm really not surprised by this, it has happened before, but it will be an relief if I managed to get it working again without reinstalling the rom, it's really such a pain in the a**... I already "played" with rooting with 2 other phones, and none of them bothered me so much as this s10 hahahahaha
I think I have a twrp backup of the rom somewhere, I will try to locate and restore using that, last time I tried flashing with odin I had to update the phone and patch the magisk all over again :/
Click to expand...
Click to collapse
Yeah, if you reflash using Odin it will overwrite everything except user data as long as you use the HOME_CSC
If this is a custom ROM you can try wiping /system in TWRP and reinstalling the ROM. Shouldn't wipe data.
V0latyle said:
Yeah, if you reflash using Odin it will overwrite everything except user data as long as you use the HOME_CSC
If this is a custom ROM you can try wiping /system in TWRP and reinstalling the ROM. Shouldn't wipe data.
Click to expand...
Click to collapse
I found the twrp backup, and restored the partitions cache, data, system and boot, now the phone is working again, it isn't the latest backup, but it's better than using odin
GamingSoldier said:
I found the twrp backup, and restored the partitions cache, data, system and boot, now the phone is working again, it isn't the latest backup, but it's better than using odin
Click to expand...
Click to collapse
You probably just needed to restore system alone, but glad you got it working.