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.
Related
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.
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
meraj99 said:
While H2OS was loaded, I flashed TWRP. After that I rebooted to recovery, cleared all the essential things, flashed a ROM followed by a Gapps package. After that, when I chose reboot to system, the phone stays stuck at the OnePlus logo screen. I can't access the recovery either. I flashed 3 different versions of TWRP, but still couldn't boot to recovery. P.S.: Bootloader is unlocked
What can I do now?
UPDATE: BluSpark's modded TWRP works, but after flashing the ROM nothing boots
Click to expand...
Click to collapse
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Kéno40 said:
You should fastboot flash old OOS 2 stock recovery, then full OOS 2.2.2 Rom.
Then root and install offical TWRP (not BS V41).
Then install what you want (but not Oxygen or hydrogen on MM)
Click to expand...
Click to collapse
oh, root access is compulsory?
Just tinking about root, because I used it to install TWRP but you're right, fastboot flash could do it
for some reason whenever I flash supersu or Magisk the phone just hangs at the MI logo with 7.6.15 global beta rom, I do the same flash method every time and this is the first time it has happened..
try 1
zcx twrp, flash 7.6.15, flash supersu, reboot and it doesnt boot
try 2
zcx twrp, flash 7.6.15, flash magisk, reboot and it doesnt boot
try 3
zcx twrp, flash 7.6.15, reboot, -boots fine
edit:
try 4 .
zcx twrp, flash 7.6.15, flash just supersu 2.82, reboot and it boots, so now I can say it has something to do with Magisk or Xposed
so I might now try to flash Magisk, but run the xposed uninstaller incase the magisk.img image still carries xposed module from previous installs this way I can narrow it down from xposed or magisk
I'm having the same issue. I try to flash Super SU after flashing MIUI 7.6.15 and I also try to flash Xposed but it hangs on the Mi logo and won't boot properly. If I hols the power button down for ten seconds to turn the phone off and then get to recovery mode by holding down the volume up button with the power button I can reflash MIUI and it works fine on its own. Wonder is it a Super SU issue? Might try an older version of MIUI....
Same issue, tried everything. :'(
Magisk and zcx super su working but not xppsed niether systemless nor solarwarez editon.
+1
just updated my phone via zcw twrp. su and magisk works fine, only xposed got me stuck at the logo.
No problem with magisk v12, boot normal
Problem with xposed v87, stuck in logo
now back to v7.6.7, and waiting for FIX
Flashed v87.1 xposed
Worked
adiversion said:
Flashed v87.1 xposed
Worked
Click to expand...
Click to collapse
Link?
Sent from my kenzo using XDA Labs
Flash the modified xposed, it's working with the latest global beta. Link:
https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634/page77
Btw: why u guys still use xposed? Any recommendations for modules except YouTube adaway which I should try?
the issue is with SuperSu 2.86, should flash Supersu 2.76, im in build 7.6.8+Supersu 2.76 and all works fine and Xposed not work fine in this builds
i am on Android Pie , version MIUI Global 10.3.1.0
i tried to put twrp on my phone but it won't boot into twrp after successful process in the fastboot, its stuck in the mi logo. tried to flash different twrp but no luck either still stuck in the mi logo.
Flash orange fox recovery
DJTH said:
i am on Android Pie , version MIUI Global 10.3.1.0
i tried to put twrp on my phone but it won't boot into twrp after successful process in the fastboot, its stuck in the mi logo. tried to flash different twrp but no luck either still stuck in the mi logo.
Click to expand...
Click to collapse
Flash twrp, boot into twrp from faatboot, again flash twrp from twrp as recovery, then flash no variety zip..done..now reboot to recovery..it will be permanently installed..
Or flash orangefox R9 instead
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.