When I reboot into recovery, all I have is an android robot with a red triangle and ! and the words "no command".
Totally stock, not unlocked or rooted. KRT16M.
How do I get a working recovery mode without losing any data or settings?
EDIT: finally figured it out - click +volume in the 'no command' screen
I flashed CO15 Bootloader and Modem in ODIN. Reboot went fine. Held down power and tried to reboot into recovery. Stuck on splash screen. I can only get into Fastboot. I installed TWRP through ODIN but still can't get into recovery. Not sure what to do?
Stuck on Samsung Galaxy note 5 Screen
On top of screen in red text: RECOVERY IS NOT SEANDROID ENFORCING
Tried holding Volume up, Power, Home to enter recovery but not working
re-flash coi5, and let it boot all the way out.. at this time (for me) it will bootloop at the tmobile screen. catch the reboot with vol up + home + power, and let whatever happen happen (for me it said no instructions or something after the little green man) then click down to factory reset/wipe data, click that, then let it reboot all the way out to home screen.
THEN flash the stuff yo uwant.
I tried to reflash twrp and the boatloader and the modem but none of that worked. I had to download and extract stock firmware package(over night) because sammobile has very slow download speeds for free users. This morning I flashed package, rebooted into fastboot and flashed Twrp and was finally able to boot into recovery and restore.
Thank you
UnderCoverLover said:
I tried to reflash twrp and the boatloader and the modem but none of that worked. I had to download and extract stock firmware package(over night) because sammobile has very slow download speeds for free users. This morning I flashed package, rebooted into fastboot and flashed Twrp and was finally able to boot into recovery and restore.
Thank you
Click to expand...
Click to collapse
Do you still have the RECOVERY IS NOT SEANDROID ENFORCING on the boot up screen? Instead of recovery mine says "KERNEL is not seandroid enforcing" and I'm not stuck in a boot loop. And I'm assuming that after you flashed the stock firmware you attempted root, and after root was the message gone?
raider09 said:
Do you still have the RECOVERY IS NOT SEANDROID ENFORCING on the boot up screen? Instead of recovery mine says "KERNEL is not seandroid enforcing" and I'm not stuck in a boot loop. And I'm assuming that after you flashed the stock firmware you attempted root, and after root was the message gone?
Click to expand...
Click to collapse
The "recovery is not seandroid enforcing" message is normal for having a custom recovery installed & should only appear when booting to custom recovery, well for TWRP anyway.
The "kernel is not seandroid enforcing" message will appear for a number of custom kernels on every bootup, at least in my experience. I don't get this message when using arter97's kernels.
I have a Sprint S6 Edge. I recently used CF Auto-Root and TWRP, but I must have done something wrong because now I'm stuck on the boot screen with the red message "Recovery is Not Seandroid Enforcing." The volume up-home-power combination to take into recovery mode does nothing, only the volume down-home-power combination works, taking me to the download mode. I have tried flashing my stock rom but it says failed. What do I do?
Flashed LineageOS on my SM-G920R4 with TWRP and it's not working correctly
On boot the device says "Not seandroid enforcing" and then boots after a few seconds. Once the device is booted I can't do anything because touching the screen does nothing, but all buttons work fine including the touch buttons.
I don't have a lot of experience with android phones.
You need to flash stock ROM via Odin. None of AOSP ROMs are stable now.
I tried to install a kernel on my G920I but it crashed on the boot screen with the message "kernel is not seandroid enforcing". The usual procedure to resolve would be to reinstall the original rom, but my device does not go into either download mode or recovery mode. No matter what key combination I use, it always goes back to the boot screen or load screen when I plug the cable into it.
Ps: Before bootloop the phone only went into download mode through JIG, but went into recovery mode normally. What to do?