https://www.youtube.com/watch?v=Kr46ugrpL6U
I kinda have the same issue it just twrp works. I was trying to install a new rom... It did and when i clicked reboot to system on twrp (latest 2.8.4.0) then it show the error in the video and reboots me back to twrp.
i had a backup of stock samsung and it boots up perfectly fine... but when flashing a custom rom it reboots to:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
then it
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then reboots to twrp
If it boots into TWRP and then boots normally, ignore it. That's just Knox.
Sent from my toaster
blackknightavalon said:
If it boots into TWRP and then boots normally, ignore it. That's just Knox.
Sent from my toaster
Click to expand...
Click to collapse
If TWRP is stuck in bootloop, just boot into download mode and install previous version of TWRP with Oden. I tried to update TWRP from 2.8.2.0 to 2.8.4.0 and had the same issue, reinstalled 2.8.2.0 with oden and all is now good.
Related
Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Longlast said:
Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Click to expand...
Click to collapse
You should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
thisisapoorusernamechoice said:
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.[/QUOTE
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
Longlast said:
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
thisisapoorusernamechoice said:
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
Click to expand...
Click to collapse
when i run supersu a message appear that there is no su binary installed, and supersu connot install it. if you just upgrade to android 4.3 you need to manually re-root.
the current version is 4.4.2 bn3
So i recently installed OOS 3.1.3 with Twrp recovery; the phone works fine, now i just need to enable root with superSU but i can't get back in recovery: i just get stuck on the loading screen with the 1+logo..
any ideas on how i could fix this?
LauraBHR said:
So i recently installed OOS 3.1.3 with Twrp recovery; the phone works fine, now i just need to enable root with superSU but i can't get back in recovery: i just get stuck on the loading screen with the 1+logo..
any ideas on how i could fix this?
Click to expand...
Click to collapse
Flash twrp in fastboot mode
Fap4k said:
Flash twrp in fastboot mode
Click to expand...
Click to collapse
And just after the flash, directly reboot on the recovery using the buttons.
Kéno40 said:
And just after the flash, directly reboot on the recovery using the buttons.
Click to expand...
Click to collapse
Thanks it worked fine, don't know how i didn't think of this before
LauraBHR said:
Thanks it worked fine, don't know how i didn't think of this before
Click to expand...
Click to collapse
So i got into recovery and installed superSU.zip but when i reboot it just boots forever so i went back into recovery and uninstalled superSU with a script.. so my opx is still unrooted; should i be using a different version of superSU or what? the one i flashed in the recovery was 2.46 but it didn't work so i uninstalled it and flashed 2.76 and it gave the same problem
LauraBHR said:
So i got into recovery and installed superSU.zip but when i reboot it just boots forever so i went back into recovery and uninstalled superSU with a script.. so my opx is still unrooted; should i be using a different version of superSU or what? the one i flashed in the recovery was 2.46 but it didn't work so i uninstalled it and flashed 2.76 and it gave the same problem
Click to expand...
Click to collapse
You have to use a special SuperSu version with this config.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP 3.2.1.0 working on stock Oreo？？？
TWRP, yes but i cant root with magisk. After flash latest Magisk 16.2, i hang in "not trusted" screen
I get the boot loop.
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
GGerniWhite said:
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
Click to expand...
Click to collapse
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
GGerniWhite said:
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
Click to expand...
Click to collapse
If you already have the ROM installed, use adb to flash TWRP and without booting flash Magisk and then boot to system. If you are on stock ROM, follow THIS.
For entering into TWRP, use the key combination of volume up + power buttons.
You can use the encryption compatible TWRP (search for it) instead of the official one.
I have realme 7 pro unlocked bootloader, and when I installed derpfest 12 ROM from TWRP it successfuly installed but I cannot no longer boot to recovery (I tried TWRP and orangefox recovery )
Can someone pls help?
so you tried to flash other custom recoveries and it didn't work?
Yes, but it didn't work
I had this problem too
Mine was caused by wrong custom recovery.
For some reason, this device needs a different custom recovery according to the android version installed.
I have no idea how or why but it is what it is
If you have orangefox for A11 and bootloop upon entering recovery try installing A12 orangefox.