Hi everyone
This is my second s5. I managed to root the first one using cf autoroot and twrp recovery.
However this new phone runs lollipop and I cannot flash either cf autoroot or twrp recovery. I used odin and the flash completes with PASS message. However when I try to reboot to recovery I just get RECOVERY IS NOT SEANDROID ENFORCING message then the screen goes blank.
I have tried downgrading to kitkat but I am still getting the same message.
Has anyone got an idea of what is going on here?
Thanks
Jeff
Try flashing TWRP 2.8.7.0 with ODIN if you haven't tried that version yet, seems to work for some people with the same problem
Try different ODIN versions too, 3.07 > 3.10.7
Brilliant!! I flashed with TWRP 2.8.7.0 and it works.
Thank you so much. Jeff
Nice one
Related
Hello guys,
I need help My Samsung note 3 n9005 was rooted before and i flashed the stock rom on it and try to root it again. i was able to finish flashing CWM by using odin no problems encountered, but when i tried to install supersu by booting my phone to recovery mode it shows . recovery booting.. seandroid enforcing and after the phone reboots and boots to normal mode.
I already tried different version of Odin and CWM, also tried TWRP and Philztouch but still no luck.
I know i can access superuser by using CF auto root by cf auto root comes with default recovery and wasn't able to install custom roms via zip file.
i hope you all guys can help me out here.
TIA.
Hello,
I have a Galaxy S5 G900F and when I try to flash a custom recovery on my phone via Odin I always get the fail logo.
I tried CWM and TWRP tried different guides with no success. I get a message of my phone screen "secure check fail : recovery".
What can I do to successfully Install a custom recovery? please help.
Thank you.
Grab TWRP 2.8.7.0 build and ODIN 3.10.6 and flash that
*Detection* said:
Grab TWRP 2.8.7.0 build and ODIN 3.10.6 and flash that
Click to expand...
Click to collapse
Didn't help.
still same problem.
After reading through a couple more forums I found that it was the Samsung Reactivation Lock that was blocking me. Upon booting the phone, going into Apps > Setttings > Security and then typing in my samsung account password I was able to disable the lock and then Download mode allowed me to root everything successfully.
ilialazerson said:
After reading through a couple more forums I found that it was the Samsung Reactivation Lock that was blocking me. Upon booting the phone, going into Apps > Setttings > Security and then typing in my samsung account password I was able to disable the lock and then Download mode allowed me to root everything successfully.
Click to expand...
Click to collapse
Hello did you on Lolipop bootloader.
what custom recovery that you use? can you upload here.
Hi i tried flashing philz touch version 6.57.8 flashed it with odin version 3.10.6 however it's still the same end result, the recovery still in stock.
any advice?
Samsung Galaxy S5 G900F
Using New Bootloader (Lolipop) BOE3
Rvl7 said:
Hello did you on Lolipop bootloader.
what custom recovery that you use? can you upload here.
Hi i tried flashing philz touch version 6.57.8 flashed it with odin version 3.10.6 however it's still the same end result, the recovery still in stock.
any advice?
Samsung Galaxy S5 G900F
Using New Bootloader (Lolipop) BOE3
Click to expand...
Click to collapse
Hello Rvl7,
I tried flashing philz touch version with no success, then I tried TWRP 2.8.7.0 withe Odin 3.10.6 and it worked like a charm. Now Im fully rooted with no problems.
Hi Guys,
trying to flash a custom Rom on my Note 3. It is a UK model supplied by EE but is unbranded.
Flashed several phones before, just running into some issues this time round.
Got my Rom, Autoroot, CWM and Odin downloaded.
Flash Autoroot with Odin - no problem.
Flash CWM with Odin - no problem - until i try to boot into recovery anyway.
No error message etc on Odin but when i try to boot into recovery it keeps saying "cannot do normal boot" and puts me into download mode.
I can get to download mode to reflash and have tried TWRP with the same results.
It is saying "custom binary" when in download mode, and my Knox counter has tripped to 1 (phone out of warranty so not fussed).
Ive searched online and cannot find a thread where they actually manage to sort the problem.
Presumably what I want to do (install a custom Rom) is not impossible as there are so many Roms etc available for the Note 3, I am just a bit stuck as to my next step.
Any help appreciated.
Thanks
Use TWRP or Philz Recovery .
Thanks for the reply JJEgan, I tried Twrp also to the same effect. I did try Cwm first though, is this a common thing when using Cwm or have I done something wrong?
Im going to flash a stock 4.4.2 from SamUK and try again from scratch to see if it made a difference coming from 4.4.2 instead of 5.0 and then TWRP
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
Hi Guys
I believe you guys on here will be able to help. Let me first tell you about my device and what I want to do and then what I did and what problems I encountered.
Device: Samsung Note 4 International Model SM-N910H (Exynos CPU)
OS: 6.0.1
Build Number: MMB29K.N910HXXU2DPE2
I only want to root my device and install Custom Recovery like CWM. I don't want to install a Custom ROM!
So I downloaded CF-Auto-Root-tre3g-tre3gxx-smn910h.tar.md5 and used Odin 3.12 to flash tar file to phone. After that phone rebooted and got stuck into the "Samsung Galaxy Note 4" Screen displaying in red letters on top left Corner "Recovery is not seandroid enforcing"
So I downloaded CWM Recovery v6.0.3.6.tar and flashed with Odin again, this time the phone rebooted back into my Working Phone OS and all seems fine. SO I wanted to test if CWM is installed? Powered phone down and booted into recovery & then got the same "Recovery is not seandroid enforcing" message on screen, so rebooted phone normally and it goes back into the OS. Also SuperU is not installed and phone is not rooted
So how do I solve this issue getting a Custom Recovery on my Phone Since I don't have any Recovery Mode option when booting into recovery. Your help, effort and time will be appreciated
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Thanks a mil, however I did manage to fix the issue and still wanted to resolve this post. I downloaded SuperU Beta 2.74 and different version of CWM. Installed CWM 6.0.5.1 (1113).tar with Odin 3.10.7 and it worked installing CWM Recovery. Then installed the SuperU 2.74 with CWM and everything works great. Phone now rooted and CWM installed :good::victory::victory:
******** Resolved ************
wilcovh said:
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Click to expand...
Click to collapse
I have the n9100 as well with the hong kong rom. I'm having the same problem while trying to root with cf-autoroot. I really want to root the phone while keeping the stock rom.
Is there any way to do so??