I tried to root my new SM-A710M with CF-Auto-Root-a7xelte-a7xelteub-sma710m and I got Recovery is not seandroid enforcing.
The only way to get back phone was flashing back with last stock rom.
I try with A710MUBU1APF1 (5.1..1) and A710MUBU1BPH1 (6.0.1) and got the same error
I tried using TWRP and got the same error
I seted unblock oem to true and usb debug to true and verify usb app to false and the rooting continue to fail and the phone goes to Recovery is not seandroid enforcing.
Where I am making mistake?
Related
As it says in the title I've already unlocked and flashed several times (downloaded multiple versions of TWRP to see if it was just the download itself, as well as checking the MD5 to see if it was corrupt.) I flash it it gives the usual partition message when I go to boot recovery I just get a Bootup failed. Lost as to what to do from here. Trying to root my phone. My phone still works as I'm able to use it atm but I don't know what else to do.
It seems if I reboot, and try going into recovery then it doesn't give me a bootup failed message but I get the android icon where he fell over and has the red triangle coming out of his chest.
Dunno if this is part of the issue but my phone isn't being detected as a adb device either, and there's not ADB debugging option to enable under developer setting just usb debugging which is enable. The drivers are install so I know it's not a driver issue.
First off, sorry if this is the wrong section for this.
Basically, I tried rooting my phone (Galaxy S6 SM-G920T) using KingRoot, and it got to 20% and shut off. Now on boot I get "KERNAL IS NOT SEANDROID ENFORCING, CUSTOM BINARY BLOCKED BY FRP LOCK"
I'd appreciate if someone could let me know whether or not there is a fix for this.
Thanks.
Kingroot is not for the Tmobile variant. You need to download Odin onto your computer and flash TWRP and Unikernel (unikernel will root the phone).
I would suggest you restore your phone to factory status by downloading Samsung Kies software.
Once that completes then enable Developer options and turn on OEM and allow USB debugging.
Then once you've done that, use the Odin to root the device and install recovery.
https://www.youtube.com/watch?v=F7W-3yo89UI&feature=youtube_gdata_player
guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
Hello I have a VTR-L09 (Australian) with stock Pie on it. I unlocked the bootloader with the code from Huawei. Then I installed the openkirin AOSP 10 Preview 2 on it which led me to not being to connect to the internet and only occasionally being able to make calls, so that was junk...
Then I tried to install TWRP and FutureROM, but something must have gone wrong (pos user error) and now I can't even use the erecovery as it, after getting the last firmware, throws a "can't verify" error. I since tried to install TWRP via fastboot, but even though it reports success, when I try to boot into TWRP recovery all I get is a screen similar to the fastboot screen only with the below message
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
When I try to boot iut just gets me to the FASTBOOT&RESCUE MODE screen
Is the phone bricked? Where to from here to get it back on stock ROM?
Thank you kindly!!!
Perhaps the device cannot verify the recovery image.
If bootloader is still unlocked, try to flash stock recovery and see what happens.
Hi, so one day, my RP2 was acting up, so I tried flashing 9.0 MR2 on it. When I did, it said this device is corrupt, and wouldn't boot up. I tried redownloading, reflashing nothing worked. So, I downloaded the first Oreo image, and flashed it. Booted up just fine, no device is corrupt error. After I flashed Oreo, I updated to MR3 over the air. When my phone booted up, didn't reflash anything, after updating, it says "Your device is corrupt". But this time, if I hit the power button to continue, it will actually work. Does anyone have a solution?
If you're rooted try.
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
If not rooted make sure USB Debugging is on.
from computer type:
adb reboot "dm-verity enforcing"