Database Info

HELP! SM-G920i TWRP Issue

Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance

Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.

Tbnitz said:
Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.
Click to expand...
Click to collapse
Can you tell me which specific rom you tried i downloaded latest I can find for Aus rom but still having the same issue. Any chance give a step by step guide on what you did exactly.
Thanks in advance

I just used the New Zealand firmware.

I am from Brazil and with the orginal rom the same thing happened, im flashed the generic one and worked.
This one seems to be the general rom to Australia
http://www.sammobile.com/firmwares/database/SM-G920I/XSA/
But i used the zto version from Brazil

hoglak said:
Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance
Click to expand...
Click to collapse
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.

d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.
Click to expand...
Click to collapse
I'll give this a go tonight hopefully it will work.
Thanks mate

d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.[/QUO
Thanks mate that worked perfectly.
Click to expand...
Click to collapse

S6 920F stuck at first boot screen

Hi everyone my story goes like this...
im currently on axism rom which is lollipop 5.0.2 and i wanted to go to 'xtrestolite deo-dexed rom' which is lollipop 5.1.1 and noticed i needed to flash bootloader and modem for 5.1.1 so i did this using odin and now it will not boot i now realise that it says this will not work with a stock kernel which im geussing the axism rom has so how do i get myself out of this mess any help asap would be greatly appreciated

JamieBlues said:
Hi everyone my story goes like this...
im currently on axism rom which is lollipop 5.0.2 and i wanted to go to 'xtrestolite deo-dexed rom' which is lollipop 5.1.1 and noticed i needed to flash bootloader and modem for 5.1.1 so i did this using odin and now it will not boot i now realise that it says this will not work with a stock kernel which im geussing the axism rom has so how do i get myself out of this mess any help asap would be greatly appreciated
Click to expand...
Click to collapse
Have you tried just flashing the stock ROM? May not be axism but could at least get you out of the situation for now

im just hunting for a stock rom now that i can flash using odin
also do i just load the stock rom i download through the 'AP' button in odin

JamieBlues said:
im just hunting for a stock rom now that i can flash using odin
also do i just load the stock rom i download through the 'AP' button in odin
Click to expand...
Click to collapse
Yup, thats it I got my ROM from here when my phone wouldn't boot >> http://forum.youmobile.org/downloads/?cat=42

Thanks! im downloading one from sam mobile so i will let you know how it goes in an hour
and when i unzip the download will i get a .tar file from it?

JamieBlues said:
Thanks! im downloading one from sam mobile so i will let you know how it goes in an hour
and when i unzip the download will i get a .tar file from it?
Click to expand...
Click to collapse
Yup either a .tar or .md5 as far as I remember, then just mount on AP and hit start

i extracted it to get the md5 file but it has failed in odin i dont know what to do now someone help please

Right im stuck now so heres exactly what i have done
i was on a 5.0.2 custom rom and wanted to go to a 5.1.1 rom (xtrestolite) so i went and flashed the bootloader and modem for 5.1.1 and it was just stuck on the first boot screen i then noticed it said somewhere that this will happen if i had a stock kernel i have tried to flash stock 5.0.2 firmware through odin but it fails so im asking if im doing anything wrong or what to try next
thanks alot in advance, Jay

JamieBlues said:
Right im stuck now so heres exactly what i have done
i was on a 5.0.2 custom rom and wanted to go to a 5.1.1 rom (xtrestolite) so i went and flashed the bootloader and modem for 5.1.1 and it was just stuck on the first boot screen i then noticed it said somewhere that this will happen if i had a stock kernel i have tried to flash stock 5.0.2 firmware through odin but it fails so im asking if im doing anything wrong or what to try next
thanks alot in advance, Jay
Click to expand...
Click to collapse
The stock rom that you tried to flash just previously there, was that 5.0.2 or 5.1.1?

Bricked the S6 SM-920I. I'm at wits' end.

I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:

Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.

Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!

ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.

ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin

1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?

Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq

ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.

Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:

1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.

Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.

ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.

Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!

ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:

Soft bricked and nothings working

I have a galaxy s6 edge its sprint and it was originally running 5.1.1 I tried to flash twrp recovery and it bricked ive use Odin to too reinstall the stock recovery and firmware the stock recovery passes but the stock firmware always fails please help.

KingJ55 said:
I have a galaxy s6 edge its sprint and it was originally running 5.1.1 I tried to flash twrp recovery and it bricked ive use Odin to too reinstall the stock recovery and firmware the stock recovery passes but the stock firmware always fails please help.
Click to expand...
Click to collapse
You can't flash TWRP without flashing the rooted kernel first. What firmware did you Odin?

I had a rooted s6 edge and tried installing twrp through flashify and my phone keeps freezing at the Galaxy S6 Edge screen and says recovery is not seandriod enforcing. I have tried to install other stock firmwares as well and they always fail. What's am I supposed to do?

Soooperstar said:
You can't flash TWRP without flashing the rooted kernel first. What firmware did you Odin?
Click to expand...
Click to collapse
I used Odin 3.10.7 and i actually have twrp running on it now i just need to find a rom to install or should i just install the stock firmware? I want a custom rom i just cant find one for sm-g925p.

Edcar445 said:
I had a rooted s6 edge and tried installing twrp through flashify and my phone keeps freezing at the Galaxy S6 Edge screen and says recovery is not seandriod enforcing. I have tried to install other stock firmwares as well and they always fail. What's am I supposed to do?
Click to expand...
Click to collapse
I used odin and flashed twrp from there and it worked now I jus need a rom

Edcar445 said:
I had a rooted s6 edge and tried installing twrp through flashify and my phone keeps freezing at the Galaxy S6 Edge screen and says recovery is not seandriod enforcing. I have tried to install other stock firmwares as well and they always fail. What's am I supposed to do?
Click to expand...
Click to collapse
Use Odin and make sure your bootloader is unlocked

KingJ55 said:
I used odin and flashed twrp from there and it worked now I jus need a rom
Click to expand...
Click to collapse
any recommended roms?

KingJ55 said:
any recommended roms?
Click to expand...
Click to collapse
There's 3 in the bottom of the OP in my thread
http://forum.xda-developers.com/showthread.php?t=3102034

Custom Recovery for SM-G900V running Lollipop 5.0 latest release (OK3)

Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!

cd2xtac said:
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
Click to expand...
Click to collapse
On OK3 the bootloader is locked. You cannot downgrade to 4.4.2 or 4.4.4 or any other previous version. You also cannot install custom recoveries like ClockworkMod or TWRP. You are relegated to Safestrap or FlashFire as discussed in jrkruse's threads.

You can ONLY use SafeStrap. TWRP and Clockworkmod cannot load because we have a locked bootloader.
You must flash a kitkat kernel to boot into safestrap, which I gather you didn't do. Then when you're done in Safestrap, flash a safestrap-flashable lollipop kernel BEFORE EXITING SAFESTRAP to boot back into your ROM.

@ landshark68
 @painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?

cd2xtac said:
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
Click to expand...
Click to collapse
You will remain tied to OK3

@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.

Dudash said:
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Click to expand...
Click to collapse
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go

jrkruse said:
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
Click to expand...
Click to collapse
Thanks for clarifying