Related
I have ZE553KL international version and install the Magisk via the boot.img method (didn't want to touch the recovery for upgrade reasons). Below is what I did after Magisk has successfully after installed:
1. I install Systemless Xposed, but give me the error "Xposed is installed, but not active".
2. After reading around on Xposed git issue, some user were having SELinux issue, so, I load the Systemless SELinux changer and change to permissive - Xposed worked after that.
3. I installed "Roaming Control" and "Smart Network" from Xposed Repo
4. After enable the Xposed module, the phone crashed on restart (would give me warning on Android UI, keyboard crash, and among others. I would stuck at unlock screen with no way of unlock the phone), I restart the phone and hit the power and volume key and it started and seems to work. Including the two Xposed module.
5. After that I enable systemless host file and install Ad-away, and some Magisk module - CloudflareDNS and Sony Music module.
6. Restart the phone, and the phone crash hard, non stop. Took me many restart and pressing the button around to get the phone started. After which I uninstall the two Xposed module, the phone still crashing. So I decide to uninstall Systemless Xposed totally.
7. After that, it seems the system is restarting normal, but still crash randomly. Decide to install Systemless Greenify, restart, phone started crash heavily like when sytemless Xposed was installed.
8. I remove the all Magisk module, thinking it would clear the systemless partition. Restart.
9. Decide to install something simple, install Magisk Cloudflare DNS module, restart phone, start crashing again.
So now, it at the point if I have any Magisk module installed, the phone would crash hard and stays at lock screen. So I enable Core mode, which pretty much is what is the same as what I can do to make the phone stable. I have attached what I can extract from the logcat, hope it will help some debugging.
[2018-07-01] Thought I would like to update. after running safely in core mode for awhile, the urge of play around on getting Xposed running came up again. I change the update channel into Beta, and Magisk Manger immediately prompt for 16.4 version available and whether I want to install it. Choose, yes, and use direct install (as it the recommended method). Quickly, it prompt for me to restart, and this is where the horror comes. After the usual warning about unlock bootloader, Asus logo then it got a new message indicate the system are corrupt, and it would restart by itself again, warning on unlock bootloader, Asus logo - froze.
- Have tried, flash back the stock boot image
- I have tried flash patched boot image via 16.0
Still not working.
Than I was forced to flash TWRP (@shakalaca, thanks you the man), pretty much defeat my purpose of keeping the original recovery of intend easier upgrade for Oreo.
- Tried to flash the original WW-71.60.139.30 rom I was on using TWRP
- Use the Magisk-uninstaller-20180627.zip
Still not working.
It was among some other useless stupid thing that I tried also didn't help, eventually I believe this two step made the phone boot again:
1) Flash the original boot.img at fastboot
2) Flash Magisk 16.0 zip file via TWRP
Wolla, phone booted, no data lost, so far all okay. Hope this may help some people.
Im trying to Root my Samsung Tab Active2 ( SM-T397U ) but im having problems finding the combination files and stock firmware, any chance someone can link me to them?
Thanks
I still need help.
check my post [RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]
There are links for TWRP recovery for SM-T397, including the use of SuperSu for root.
Shedaim said:
check my post [RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]
There are links for TWRP recovery for SM-T397, including the use of SuperSu for root.
Click to expand...
Click to collapse
is this for the SM-T395 or SM-T397U
EKNOZHF said:
Im trying to Root my Samsung Tab Active2 ( SM-T397U ) but im having problems finding the combination files and stock firmware, any chance someone can link me to them?
Thanks
Click to expand...
Click to collapse
I was able to root an SM-T397U running 8.1.0 using the recovery in the above thread (twrp-3.2.3-0-SM-T397-7.1.2.tar) even though that was for 7.1.2 and not 8.1.0 (assuming these versions are even related). The SuperSU flashing method led to a "Verification Failed" error, and at one point I was able to totally bootloop the device by doing a data wipe from TWRP (bad idea!). Make sure you have stock firmware on hand - I downloaded it from sammobile but it took friggin forever.
NOTE! I bricked the device at least once, and had to restore to stock via ODIN (this is the stock FW I used: https://www.sammobile.com/samsung/firmware/SM-T397U/ATT/download/T397UUES4BSF3/290259/). These instructions are purely at your own risk! Note that the above link contains the full firmware (bootloaders + system + recovery + etc). If you just need the stock recovery for whatever reason, message me (for some reason I can't attach it to the post).
What ultimately worked was:
1. Factory wipe the tablet from inside Android
2. Put Magisk-v19.3.zip on your sdcard (latest stable as of this writing; this is what I tested)
3. Enable Developer Options from inside Android
4. Enable "OEM Unlock" under Developer Options, and do a wipe if it forces you
5. Power down
6. Hold Home + Volume Down + Power until you get to the bootloader
7. Press VolUp (I think) to continue into the bootloader
8. Open Odin3, click "AP", select twrp-3.2.3-0-SM-T397-7.1.2.tar (leave the other boxes blank). Odin might give you an option to NOT reboot after flashing. If you find it, (un?)check the box that prevents reboot after flashing (not sure if matters). Then, do the flash. It only takes a few seconds.
9. Power down device (do not let it boot into Android, but that may not matter)
10. Hold Home + Volume Up + Power until the Samsung Galaxy logo appears, then let go. This boots you into TWRP. The boot into TWRP takes a little over a minute. Be patient.
11. Inside TWRP, ignore any Wipe-related options. It'll ask you to swipe to allow modifications (do that). Then, click on INSTALL (or is it "FLASH"?), then scroll down to "external_sdcard", then find Magisk-v19.3.zip and click on it.
12. Let the Magisk installer do its thing
13. Reboot from TWRP (don't wipe anything, and click DO NOT INSTALL when prompted for the TWRP app). It may take a minute or so to reboot
14. Let the device boot to Android. It may take like, 3 minutes.
15. Uninstall the Magisk Manager app that is now present on the device (it may crash, but this is just a placeholder anyway)
16. Install the *actual* most recent (stable?) Magisk Manager app. I used MagiskManager-v7.3.4.apk.
17. Open Magisk Manager. It may tell you there's an additional download that's needed. Let it do that, then let the device reboot.
18. You should now be good to go, but you might need to disable the annoying "device compromised" nag screens from some mcafee samsung security junk that will pop up sometimes.
Again, this is all at your own risk. Good luck!
-evilwombat
hi
i may be not in the correct topic
can your sm-t397 make phone calls?
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS),
i am not responsible if anything goes wrong. You are still the one who tryed to flash the files. Even tough this should work as it worked for me and some friends.
Hello XDA
This is my first post (sorry if one already exists)
Today i am going to tell you how to root the Galaxy S9 International on android 9 Pie on stock touchwiz rom.
First of all download all these files;
Prince comsy odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Team win recovery https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
ElementalX Kernel https://elementalx.org/devices/samsung-galaxy-s9/
No verity encrypt: https://androidfilehost.com/?fid=962187416754474353
Magisk 18.0 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now for the root
First you need to unlock OEM, you can do this in developer options,
If there is no developer options you need to enable this
you can do this in: Settings>About Phone > software information > click 5 times on build number.
When you unlock OEM everything on your phone gets wiped so make a backup!!
When the wiping is complete, turn off your phone and go to download mode (Vol down + Bixby + Power)
Then connect the phone to your pc and start odin
In odin go to options, and disable f.reset and auto reboot.
Then press the AP button and select the TWRP image you downloaded.
When TWRP is flashed, force reboot your phone (Vol down+ Power) when it is powered off quickly press Vol Up + Bixby + Power to get into recovery
Swipe to allow modifications. And format /data
Then reboot into recovery.
When rebooted mount USB Storage and connect the phone to the PC
Then you can click&Drag the other files (elemental, Magisk, No verity)
When the files are on the phone, go to install and search for the files you just put on the phone.
Install in this order:
Flash No-Verity-Encrypt
Then flash the custom kernel (ElementalX)
And as last flash Magisk.
When you did this, you want to Factory reset, Wipe cache and Dalvik.
Then you can reboot the phone, and install it.
(It is possible that you stay at the boot logo for a long time (Not the galaxy s9 one but the next one) What you need to do then is let it boot for 5 minutes, then force reboot (vol down+Power) and then the phone boots fine)
Again, just to make sure check if OEM is still unlocked (sometimes this get locked again)
Please note that when you do this, you lose secure folder and other functions, also is the knox tripped (0x1)
But the Fingerprint, Irisscanner and samsung account works.
SOMETIMES IT IS NEEDED TO INSTALL THE MAGISK MANAGER MANUALLY, YOU CAN JUST DOWNLOAD THE FILE FROM THE LINK IN THIS POST
Hope this helps.
If you do have any questions, please do the following first;
Note any errors that odin or your phone gives you. I want to help you, but i do need to know what is going wrong.
(Sorry for my bad english)
reserved
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
sarius02 said:
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
Click to expand...
Click to collapse
If you dont use the custom kernel, you will get RMM error.
Iris scanner wont work, Fingerprint wont work, Samsung account wont work. When you reboot the phone you get a little "Bootloop" at the lockscreen (Screen flashes and is unusable and your pattern isn't saved)
I dont know what else breaks because i cant even get past the lockscreen with stock kernel
(Also you get better performace and battery life)
Hope this helps
work it with s9+?
Sorry for my English...
Yes, but you want to use tgpkernel then otherwise it will not work (problems described abovel
https://www.androidfilehost.com/?w=files&flid=288240
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
effry said:
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
Click to expand...
Click to collapse
Yes, the knox will still trip (0x1).
In europe, when you can show that the root is not the cause of the problem, they have to fix it under warranty.
Also there are some functions you will lose (forever)
Knox,
Samsung pass,
Samsung Pay,
S-Health(you can fix this one with a build.prop tweak)
Secure folder
If you plan to use one of these (exceptpt s-health) It is better not to root your phone (there are still external app's you can use if you plan to root your phone)
Is there a way to update the stock firmware when you have root? Or do i have to do all over again?
I have this lock screen flashing bootloop issue, what is the fix? I have tried factory restores but get the same results once I set a lock/passcode and reboot. Samsung Account and Bixby also do not work as you mentioned.
You can use TGPkernel then,
Some phones have this issue, some not.
I have seen that 3 friends of mine it worked, and also on 3 not, so this is a very weird issue
What was the fix with them is to install TGPkernel
@co9
The only way i know is to install a custom kernel,
Otherwise you have to download latest stock rom, and flash this using odin.
wich changes your recovery.img and boot.img, aswell as the kernel. so you have to flash this all over again
Thanks for the answer. I already have a custom kernel. So if i always want to have the latest Samsung firmware i have to flash it through odin and do the whole root procedure again?
I tried this method but now everytime I reboot the phone my bluetooth paired device are lost. They also get deleted if I turn ON and OFF the Airplane mode. Anyone else having the same issue ?
Is anyone else experiencing an issue where the password, pin, or pattern set before setting up fingerprint scanning acts like what was entered is incorrect, not allowing you to setup fingerprint scanning?
I've tried setting up fingerprint scanning on initial setup as well as skipping and trying after the phone has been setup but had no luck. What ever I set initially will not work when I'm prompted later on when trying to setup fingerprint scanning or tying to access other secure features. The phone just prompts to try again acting like I entered in the wrong password, pin, or pattern. I've even tested by setting up a REALLY simple password with no luck.
I have confirmed in the settings that Elemental is installed.
Edit: I did find this thread https://forum.xda-developers.com/galaxy-s9/help/root-galaxy-s9-exynos-9-0-android-pie-t3884267. I tried the no-verity-opt-encrypt-6.0.zip that was suggested in some posts but had no success. I've also tried the TGPKernel but had not change in the issue. I am able to setup fingerprint scanning on fresh firmware install but after installing TWRP and everything else the above issue happens.
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
menhammer said:
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
Click to expand...
Click to collapse
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Emre67511 said:
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Click to expand...
Click to collapse
My personal experience is i have rooted using this method and have had no problems
Hi all,
I tried to flash twrp but never succed.
S9+ last firmware from samsun android 9 pie (update from smart switch)
Then option developper activated, no oem unlock menu found,
boot into download mode and there is written oem unlock desactivated so ok
with odin try to flash (ap, reboot freset unchecked)
then fails and message in red on the phone :
"only official released binaries are allowed to be flashed recovery"
History :
I was in galaxy project oreo, i wanted to upgrade with pie, but reboot cycle
so rescue with odin and original oreo firmware, then update to pie
thanks for help
regards
To get the oem unluck button visible.
After fresh install, go to time/date in settings, choose manual and set the date 1 mount prior (march will be februar)
Than go to software update, choose manual en click on dowload updates manually.
Restart your phone and the oem unlock button in developer options will be there
Cheers
thank's for answering,
Update done, reboot ok but still not oem options in developpers section
Anyone was able to Root Note 9 Exynos android 10 ?
i have tried dr.ketan as well as forcedecrypt/magisk 20.2 all combos and stuff ,it results in bootloop.
if anyone is able to root please write steps thanks!
EDIT :- METHOD TO ROOT N960FXXU4DSLB (ANDROID 10) for Exynos version.
i got so many briks today trying different methods to root android 10 latest update, please dont use TWRP recovery posted here which is latest v3.3.1 for Q that is the main issue, dont use dr.ketan root.zip either again bootloop.
SIMPLY FOLLOWS these steps:-
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.
Magisk 20.2 bug. Try with Magisk 20.1
i fixed it, i even ripped all device today when here was only download mode saying goto smartswitch nothing was working, follow steps above you are good to go!
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html
BytesReverser said:
A
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.
Click to expand...
Click to collapse
thank you I have been tring to root android 10 since the Dec 20th I kept doing these steps but it wasn't working for me the main issue was twrp I was using 3.3.1 for Q and for Pie none of them were working I changed twrp to 3.2.3 now it is working perfectly thank you again
but you should upload those files so no one would use a wrong file
anyone has a solution for TWRP? now I have rooted my phone but one small problem after the first autoreboot after installing these files data encryption comes back so after that auto reboot if you go to TWRP you'll need to format data again then you can make modification
I need twrp so I can restore my data and I already tried to restore data before first and then install magisk , RMM bypass and no verity encryption then flasshong RMM bypass again but then it wont boot it will stuck at samsung logo (not first logo)
XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
I faced that same problem and it is caused by No Verity file you flashed
Solution is
1. Reflash Android 10 with odin (All files) (flash reguler CSC not HOME CSC)
2. Do the above steps in order as @BytesReverser mentioned But skip step 8 and 10
you'll have root access but you will still have one problem after you reboot your phone if you want to install anything or want to make modification with TWRP then you need to format your data again cause after first reboot data encryption reactivates it self
Thats right it still stays but i have took backup using smart switch now, will restore later cuz even fstab removed the forceencrypt still it stays encrypted
Sorry root success, but fingerprint stop working after root!
I can no longer log in to the samsung account. why?
Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery
BytesReverser said:
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html
Click to expand...
Click to collapse
Help please
I followed this steps and i´m stuck in boot screen
Got the TWRP 3230, tried with your Magisk file and the version 20.3
Need help to root your Note 9.
Any new method with TWRP without problem?
nothing but adds on those links no matter where i click :S
Zer0De8th said:
Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery
Click to expand...
Click to collapse
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
which method works for you? twrp?
Am getting error :/
TWRP file please?
inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The method from the link works for me as well. But be aware that you will not be able to install TWRP afterwards. You will only have the rooted N9 on Q that works fine.
I was using my phone normally and closing the browser while suddenly the phone restated and went to download mode. I am not able to do anything except going into recovery mode. The normal restart, power off/on goes to download mode. This happened all of a sudden. I have not dropped my phone or anything. I’m my phone is rooted and do have magisk installed. What should I do to make the phone work again? Also, is there any way to save the data?
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
XTrail02 said:
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
Click to expand...
Click to collapse
I didn’t install any module and also my phone isn’t going into recovery mode. It goes into download mode automatically. I can go into recovery mode but the recovery mode is the basic one not something like TWRP so it does not have that file manager you are talking about.
zaidbaby said:
I didn’t install any module and also my phone isn’t going into recovery mode. It goes into download mode automatically. I can go into recovery mode but the recovery mode is the basic one not something like TWRP so it does not have that file manager you are talking about.
Click to expand...
Click to collapse
Sorry to hear that. I can only think of flashing your stock Rom to make your phone run again, but to do this will most prabably wipe your data.
XTrail02 said:
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
Click to expand...
Click to collapse
Is there a way to install TWRP in this state? So I can at least copy over my files to the SD Card?
zaidbaby said:
Is there a way to install TWRP in this state? So I can at least copy over my files to the SD Card?
Click to expand...
Click to collapse
Yes, twrp is installed in download mode via Odin, on my device, Samsung Galaxy. I don't know about your phone unit. Follow the instructions on your phone's twrp forum.