Database Users

Trouble with booting after rooting, help.

Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.

Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
Hard to help if you do not write in detail. Such as phone type, links you have used, etc etc

Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
You need to flash SuperSU manually.
1. Flash TWRP
2. Format data
3. Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip

You simply brick your phone. You need to know that there is not Chainfire-AUTO-Root for Nougat, so you need first flash Stock FIRMWARE from Sammobile, then flash TWRP and flash SuperSU
Or you can flash many of 100 roms with prerooted supersu and busybox.

Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.

seppdep said:
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
Click to expand...
Click to collapse
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.

doclorenzo said:
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
Click to expand...
Click to collapse
Thank you doclorenzo.
I had success with the latest stock version (xxu1dqd7) and your recomendation to format data in TWRP.
In short: Boot in Download mode, Install TWRP via Odin, Boot into TWRP - format data, supersu (2.82) + dm-verity
and then restore all data. Unfortunately it requires lot of time (at least 4 hrs to restore the apps + more for fine tuning)
Thank you and hope to have a better way with the next stock update and TWRP

Installing Magisk v14 on galaxy s4 gt-i9515

Hello friends, I am trying to install Magisk on a Galaxy s4 gt-i9515, non-rooted, with TWRP recovery device.
I tried both methods described in the official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both tries failed. I will now explain in more detail what I've done.
Before, note that I have a TWRP recovery of the state before flashing any zips/boot.img s, so I am constantly going back to the previous state which passes safetynet.
First try:
I simply took the magisk-v14.zip file and installed through TWRP. The installation had no errors and in the end TWRP claimed "success". TWRP asked me to reboot now.
I clicked on "Reboot", and then TWRP told that "My device is currently not rooted" and asked if I want to install root or reboot anyways. I rebooted anyways (I didn't let TWRP install his own root).
When the device boot up, I got into magisk manager, but sadly it was written that I am not rooted, and I don't have a magisk installed. Now, it also failed to pass safetynet.
At this point I used my Backup and got back to the state which I could pass safetynet (I've checked it again to make sure).
Second try:
I got the boot.img of the stock firmware I am currently using (I recently flashed this firmware, so it has to be the right boot.img).
I got into Magisk Manager and patched the boot.img. Magisk patched it into a file called "patched_boot.img.tar".
I got into download mode on my device, and flashed the .tar file via ODIN (AP option, ODIN version 3.12.3).
The device rebooted after the installation was "complete" according to ODIN: <OSM> All threads completed. (succeed 1 / failed 0).
When the device booted up, I entered the Magisk manager, and still, no root + no magisk installed. This time tho, it passed SN.
I used my backup again.
Now I am stuck. I really don't know what can I try anymore. Please suggest me ideas.

Up. I still need answers.

i have mnanaged to install latest stable version of magisk using latest twrp 3.1.1.0, and root management is in function. however, i cannot install any magisk module, tested xposed api21 but it does not install, also greenify4magisk still nothing to be noticed, unfortunately as there is yet no response i suppose its a lost cause, well lets just root manually supersu or things like that.

hi, Samsung S4 i 9505 I have not solved with Magisk and I don't even try "patched_boot.img.tar" the problem in it is apk and not the file it TWRP starts I remember apk EdXposed 2 years ago there were failures I thought about installing stock firmware/Rom with Frja Tool we talk about android 10/11 is android 5.0.1 I think there is only one way is SuperSu this root does not pose problems there is a saying: the more cooks around a dish, the more they ruin it"

I was able to install Magisk v24.3 today on my Galaxy S4 Mini LTE (GT-I9195) using partially the "Patching Images" method and TWRP 3.2.3. I had Magisk v23 installed but since a couple of weeks ago it kept crashing. So, I did the big mistake of uninstalling it to update to the latest version. It costed me half a day around this.
I could not flash zips in TWRP recovery (it always failed with Updater process ended with ERROR:1)
1 - Get a copy of the boot.img (for this step I had to find the installation file of my ROM. I did not know for sure which was it since it was installed 2 years ago. I have an AOPK based ROM and all the files from their website are not available anymore. All I could find was an older one on androidfilehost "aokp_serranoltexx_pie_unofficial_2020-01-18_1053.zip". Uncompress this zip to get the boot.img file.
2 - Copy the boot.img to your device filesystem.
3 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash boot.img, reboot
4 - Download and install the latest Magisk v24.3 apk
5 - Press the Install button in Magisk app (this means pressing the second “Install”, the one on front of App.)
6 - It should ask you to choose “Select and Patch a File”. Search and select the boot.img
7 - If all goes well, it should create a file named magisk_patched_[random_strings].img
8 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash magisk_patched_[random_strings].img, reboot
9 - Reboot and confirm in Magisk app if it says “Installed 24.3 (24300)“.
Now I get a warning "Your device needs additional setup for magisk to work properly... reboot" when entering Magisk, but it seems to work fine.
I have a bottle of champagne saved for the day when windows laptops are miniaturized and android is discontinued from the market. Bootloaders, recoveries, ramdisk, getting root, knox, odin, oem unlockings, CSCs, APs, customs kernels, adb, vbmeta, adoptable storage, se policies, fastboot modes, download modes... damn. They couldn't make it more complex if they tried.

Trouble with unrooting and boot loops

Hey there!
So i thought it would be easy to unroot my S7 Edge SM-G935F on magisk or superSU without wipe all the data.... until i wanted to do so two days ago :silly:
Problem is no matter what "official" variation i use for magisk (uninstaller flashed in twrp or full uninstall / switch images in the manager) or superSU (option in the app) im getting a boot loop. can only get out of it when i reinstall magisk or superSU via twrp.
Today i found a flashable uninstaller for superSU, used it and it workted without causing the loop but it says i needed to reflash the original boot.img. but when im flashing the boot.img that i can find within the "AP" part from the decompressed rom im using its again boot loop time.
(After that ive tried to fix the loop caused under magisk uninstaller with flashing the boot.img out of the rom under twrp afterwards... but its looping on)
i realy dont understand that and its pretty frustrating because i've tried so many different things but all the time it ends in the loop.
hope someone can help me with that! :crying: (Rom is from Sammobile G935FXXS2DRA9_G935FDBT1DQJ1_DBT)
thanks for your time and answer
greetings
Chris

HELP only official released binaries are allowed to be flashed

Hi guys today i tried to root my device with twrp and magisk. After flashed magisk from twrp, it said i should format the phone and i did. Then the problem happened. I tried flash stock rom from odin but it failed every time. How can i solve this problem?
device G950FD
when rooting, oem setting was on.

Help error samsung (only official released binaries are allowed to be flashed)
help me, I wanted to root on my j5 prime SM-G570M phone and first was giving trouble to install twrp (remembering that the device is under warranty) until I finally succeeded. I put the zip file to do the ROOT and it worked. When I rebooted the device appeared a message saying that the android system could have been violated, had to restart. When I rebooted the device gave this error (only official released binaries are allowed to be flashed). He calls and does not leave this text in red.
Please help me, I'm desperate. I searched a lot and did not find the answer. I only read answers that maybe I have to wait 7 days. But I'm not sure

HELP! S8 won't boot up!

I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!

Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...

tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!

cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage

I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).