Hey,
So I'm attempting to flash a stock ROM from Samsung on my S6 using ODIN and download mode. It does not allow me to do so, there is a 'FAILED' dialogue in ODIN and on the phone, it says 'SECURE CHECK FAIL: BOOTLOADER'. I tried Googling the answer and nothing showed up at all. How can I fix this problem.
BTW, I've tried flashing TWRP, CMW, a custom ROM, stock ROM, a custom bootloader, a custom 'pit' file and tried using Samsung Kies' emergency restore feature, none of which worked.
Did you try booting into recovery mode, wiping everything and flashing from a USB OTG flashdrive?
Hey guy... try this, flash newest CF AutoRoot by ChainFire via odin... then let it finish and boot... now your rom should back to stock recovery.. then flash arter97+twrp... now you can restore (if you have one) or flash new rom via custom recovery.... good luck.
graphbyte said:
Hey guy... try this, flash newest CF AutoRoot by ChainFire via odin... then let it finish and boot... now your rom should back to stock recovery.. then flash arter97+twrp... now you can restore (if you have one) or flash new rom via custom recovery.... good luck.
Click to expand...
Click to collapse
Hey, thanks for the reply. I tried this and everything was successful execpt when I try to boot into recovery, it freezes and the 'Samsung Galaxy S6 - Powered by Android' screen and says 'RECOVERY IS NOT SEANDROID ENFORCING' in small red text at the top right. I cannot boot into recovery.
TheGoldenMagikhrp said:
Hey, thanks for the reply. I tried this and everything was successful execpt when I try to boot into recovery, it freezes and the 'Samsung Galaxy S6 - Powered by Android' screen and says 'RECOVERY IS NOT SEANDROID ENFORCING' in small red text at the top right. I cannot boot into recovery.
Click to expand...
Click to collapse
hey... its kernel related.. this happen becuz kernel in not supporting newest TWRP.. or kernel not updated...
try flash other supported kernel for s6 and flash twrp again...
in my case i"m on PureStockXralite V5.5 .. then i flash new TWRP... when i try to boot into recovery, it stuck at samsung logo (same as your case"Powered by Android' screen and says 'RECOVERY IS NOT SEANDROID ENFORCING' in small red text at the top right")
(the solution) reflash CF AutoRoot and its boot back like normal... but recovery back to stock... so i flash arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5 via Odin ,,,, done.
Related
I need help
I have a Tmobile Galaxy s4 M919.
After the 4.3 update, i am not able to completely flash a stock rom in order to have my phone working again.
Tried root, tried CWM ot TWRP, Odin stock, Kies, but every attempt got stuck for ever on the boot logo screen with blue letters on the left hand up corner saying recovery booting.
I can't access download mode but not recovery.
Only onceworked, and i could flash thru KIES and the download screen after that shown:
System Official Samsung
Binary Official.
After that i start to have an issue with SIMCARD non detected, and had to restart and never worked again.
Seems like Knox is dealing with custom rom or bootloader and keeps on bootlogo screen.
Any help will n]be very appreciated.
Augusto.Nascimento75 said:
I need help
I have a Tmobile Galaxy s4 M919.
After the 4.3 update, i am not able to completely flash a stock rom in order to have my phone working again.
Tried root, tried CWM ot TWRP, Odin stock, Kies, but every attempt got stuck for ever on the boot logo screen with blue letters on the left hand up corner saying recovery booting.
I can't access download mode but not recovery.
Only onceworked, and i could flash thru KIES and the download screen after that shown:
System Official Samsung
Binary Official.
After that i start to have an issue with SIMCARD non detected, and had to restart and never worked again.
Seems like Knox is dealing with custom rom or bootloader and keeps on bootlogo screen.
Any help will n]be very appreciated.
Click to expand...
Click to collapse
Best thing to do is use odin on your pc and get the stock rom from samsung or another source, then completly flash it so it will wipe out you phone completly and then reinstall stock. This happened to my m919. If you need more help on how to completly replace the stock rom using odin there are plenty of videos that show you step by step. You just soft bricked your phone so it's fixable.
Olycius said:
Best thing to do is use odin on your pc and get the stock rom from samsung or another source, then completly flash it so it will wipe out you phone completly and then reinstall stock. This happened to my m919. If you need more help on how to completly replace the stock rom using odin there are plenty of videos that show you step by step. You just soft bricked your phone so it's fixable.
Click to expand...
Click to collapse
I have flashed several times via odin and kies, but everytime i still with Binary Official and System Custom.
Seems like the flash does not overwrite the kies bootloader, thats why i am stuck on boot revovery.
Once it worked, the system and binary became official, then i flashed knox free stock rom via recovery.
As i told, i can acces download but not recovery.
Does anyone know any knox free stock rom flashable via odin???
Hello, i just tried to install TWRP recovery on a Galaxy S Advance. Everything went great, odin didn't show me any error and when it finished the phone rebooted. After that it won't turn on ( stuck on the Galaxy logo) and i can't access the recovery. I tried to install another TWRP but i get the same error.
Abyel26 said:
Hello, i just tried to install TWRP recovery on a Galaxy S Advance. Everything went great, odin didn't show me any error and when it finished the phone rebooted. After that it won't turn on ( stuck on the Galaxy logo) and i can't access the recovery. I tried to install another TWRP but i get the same error.
Click to expand...
Click to collapse
Where did you get TWRP for Galaxy S Advance. I can't find it in the supported device list: teamw.in/twrp_view_all_devices
If you can't get past the logo and can't access recovery, you should try flashing stock firmware for you device and carrier from sammobile.
(sammobile.com/firmwares/ Enter your device model and download the latest firmware for your carrier and region)
You can flash via Odin.
If you still can't boot after flashing original firmware, then try going into recovery again (press and hold volume up + home + power) and do a factory reset.
After that, if you still want to install custom recovery, I recommend rooting your phone (you can easily find tutorials on that) and after, use an app like Rom Manager or Rom installer to flash a recovery. Both of these are available on the play store.
Good luck.
Hi, this is not my first time flashing TWRP on this phone. And I have been successful so far.
Today I use Odin to flash TWRP, and it went through just fine (see screenshot), but when I enter the recovery mode, it says "Android system recovery <3e> LMY47X.G920FXXU2COH2 on top and I am very confused. I tried a few times and apparently I cannot enter TWRP while Odin kept telling me I have flashed it successfully...
Did you have "Auto-Reboot" ticked on Odin? On my Note 4 that used to mean the kernel would reflash the stock recovery upon booting. You need to untick this, turn the S6 off after flashing and then boot directly into recovery using power + home + vol up
Nope. On the S6 auto-reboot menas what it does. The phone gets rebooted after the flash is done.
To the OP: You used the correct file to flash? USed AP mode in ODIN?
I had same problem. I think you need to have rooted kernel through odin first. Idk, that us what i did.
Just so everyone knows how I solved this. I wiped everything and flash TWRP and it worked. I am not sure why, but that's how I got it to work.
I have the sprint variant of the note edge running 5.1.1
I understand it cant be rooted with cm-autoroot unless the beastmode kernal is flashed.
The edge is currently stock. In the sprint note edge development thread, it was mentioned that it was possible to odin twrp, then flash the kernal and custom rom. I tried to odin twrp and it passed, but when i booted into recovery, the stock recovery still boots. Can this not be done on a non-rooted phone?
Guess you'll have to pull battery and pull the USB cable when the first boot screen comes, right after the recovery is flashed. It's when the status window in odin says reset and is blue. At least it is blue if you're using one of the newest odin.
Otherwise the system will overwrite twrp recovery and exchange it with stock recovery.
When the phone is off just boot into twrp recovery with the 3 button push method.
Sendt fra min SM-N915FY
Cundis said:
Guess you'll have to pull battery and pull the USB cable when the first boot screen comes, right after the recovery is flashed. It's when the status window in odin says reset and is blue. At least it is blue if you're using one of the newest odin.
Otherwise the system will overwrite twrp recovery and exchange it with stock recovery.
When the phone is off just boot into twrp recovery with the 3 button push method.
Sendt fra min SM-N915FY
Click to expand...
Click to collapse
I tried this on SM-N915P to NO AVAIL didn't boot TWRP after I pulled battery & cable after 1st bootscreen, 'Samsung Galaxy Note Edge Powered' by 'Android' ( this is the 1st boot your talking about rite) ???
the screen in Odin 3.07 & Odin v3.10.5 both said 'Pass' & was Blue
So what am I doing wrong here
Ickyz said:
I tried this on SM-N915P to NO AVAIL didn't boot TWRP after I pulled battery & cable after 1st bootscreen, 'Samsung Galaxy Note Edge Powered' by 'Android' ( this is the 1st boot your talking about rite) ???
the screen in Odin 3.07 & Odin v3.10.5 both said 'Pass' & was Blue
So what am I doing wrong here
Click to expand...
Click to collapse
Yes this is the screen I'm talking about. But you gotta be really fast. As soon as you see it boot into this screen pull the cable and battery. Otherwise it will overwrite with stock recovery.
Sendt fra min SM-N915FY
I'll give it another shot after work!
No go,
Can someone post the md5 they used for TWRP (Sprint or Tmobile) plz
so I can try it
Worked!
I tried to root with chainfire, while one 5.1.1 and it didn't let me boot, but i flashed twerp and SSU and its still not rooted but it booted and have Twrp Recovery...
it was absolutely terrifying! but it ended up all good.
Links : https://www.youtube.com/watch?v=mYw77M2jRHg
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.