When i boot in to Recovery i get this message. Recovery is not seandroid enforcing. I dont belive its something i shuld be worried about but just to be on the safe site. i will like some kind on confamation on this.
Can i just go ahead and flass custom rom / kernel and it will go away or do i have to flash another Recovery ?
Thanks in advanced
nyvang101 said:
When i boot in to Recovery i get this message. Recovery is not seandroid enforcing. I dont belive its something i shuld be worried about but just to be on the safe site. i will like some kind on confamation on this.
Can i just go ahead and flass custom rom / kernel and it will go away or do i have to flash another Recovery ?
Thanks in advanced
Click to expand...
Click to collapse
1. On what ROM are you?
2. What's stopping you from flashing via odin/heimdall?
spamtrash said:
1. On what ROM are you?
2. What's stopping you from flashing via odin/heimdall?
Click to expand...
Click to collapse
Well im on stock rom just rooted the phone. and flashed custom recovery.
This message shows in the top left conor when i Boot in to revocery.
stock rom 4.3 from samsung
nyvang101 said:
Well im on stock rom just rooted the phone. and flashed custom recovery.
This message shows in the top left conor when i Boot in to revocery.
stock rom 4.3 from samsung
Click to expand...
Click to collapse
If it only appears when u boot in recovery is the normal coz u changed the STOCK recovery for this custom one. If u flash other KERNEL the logo appears when u boot the phone. Anyway now u can flash KERNEL/ROM that u prefer
Recovery is not seandroid enforcing Knox set to 0x1
Hi guys, Just had the same messages on booting : KERNEL/RECOVERY IS NOT SEANDROID ENFORCING and Knox set to 0x1
First, DO NOT FLASH OLDER ANDROID VERSION (4.2.2 / 4.1.2) OVER THE ANDROID 4.3 UPDATE
If ever its done already and you need to Unbrick your samsung device, read the following post to restore :
Just had the same messages on booting : KERNEL/RECOVERY IS NOT SEANDROID ENFORCING and Knox set to 0x1
just after I flashed 4.2.2 based Custom Rom using an OTG cable/FlashDrive over Android 4.3 Stock and/or Custom Roms.
I had these at boot in red and yellow : Warranty void and Knox set to 0x1. But in About device, Android version went from 4.3 to 4.2.2 then i tryied some different custom kernels but nothing to do, wifi keeps crashing plus i had these bootup messages. I did FULLY wipe/restore the device to stock android 4.3 on my SGH-I337M phone using odinv3.09 and I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5
file and it worked after something like the 3rd try, why the importance to FULLY wipe system, data, dalvik cache, cache using a custom Recovery before starting the restore
I dont recommend to flash older android version over The update 4.3. It was such a waste of time to restore it!
Just saying, if you guys had the same issue, your phone ISNT bricked, It took me around 15 hours to find and download Odin and Samsung stock 4.3 firmware plus ReRoot and flash it with odin... ive used my OTG cable to flash kernels or to restore from backups and now, my phone
is FIXED :good:
Related
Hi, i used old philz recovery to restore nandroid backup (without selinux option) and now i have this new line in download mode: eMMC burst mode: enabled
unfotunately now i get red warning everytime i boot with custom kernel (top of the screen, red warning: knox kernel warranty void or so..) it is very annoying.
Can i go back to previous state? when i had no messages at boot with custom kernel or recovery? i flashed with odin MJ7 XEO and even MJ3 leak (without botloader ofc because its blocked when trying). i did full wipe, no help...
i had knox warranty bit void 0x1 science day one cause i tried to flash MGA before i read it will void my warranty so no worry about voiding my warranty now, i can flash everythig - please help me to remove this burst mode! thx
Kriomag said:
Hi, i used old philz recovery to restore nandroid backup (without selinux option) and now i have this new line in download mode: eMMC burst mode: enabled
unfotunately now i get red warning everytime i boot with custom kernel (top of the screen, red warning: knox kernel warranty void or so..) it is very annoying.
Can i go back to previous state? when i had no messages at boot with custom kernel or recovery? i flashed with odin MJ7 XEO and even MJ3 leak (without botloader ofc because its blocked when trying). i did full wipe, no help...
i had knox warranty bit void 0x1 science day one cause i tried to flash MGA before i read it will void my warranty so no worry about voiding my warranty now, i can flash everythig - please help me to remove this burst mode! thx
Click to expand...
Click to collapse
hi there, you should be able to flash a stock 4.3 rom. This is what i did. I no longer get anything come up when booting the phone besides the samsung logo. I however want to get back to a 4.2.2 rom.. None of them work.. I can only flash 4.3 roms.
nixxss said:
hi there, you should be able to flash a stock 4.3 rom. This is what i did. I no longer get anything come up when booting the phone besides the samsung logo. I however want to get back to a 4.2.2 rom.. None of them work.. I can only flash 4.3 roms.
Click to expand...
Click to collapse
Yes i can flash stock 4.3 mj7 system is working, but every time i run philz or use custom kernel i get this annoying red messages on the top of samsung i9505 logo ... and emmc burst mode still is enabled.
Kernel is not seandroid enforcing
Recovery is not seandroid enforcing.
Kriomag said:
Yes i can flash stock 4.3 mj7 system is working, but every time i run philz or use custom kernel i get this annoying red messages on the top of samsung i9505 logo ... and emmc burst mode still is enabled.
Click to expand...
Click to collapse
i only get that message going into download mode.. If just rebooting the phone i get nothing.. Hopefully someone will find a way to reset the phone phone back to default.
Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay
kratumay said:
Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay
Click to expand...
Click to collapse
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine
jaythenut said:
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine
Click to expand...
Click to collapse
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.
kratumay said:
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.
Click to expand...
Click to collapse
Based on what I read so far regarding the 4.4.2 update, if you flashed it on your device, there seems to be no way to go back to 4.3 ( I'm not sure if that means custom roms based on 4.3 as well ). Best thing to do is just flash the official 4.4.2 and hang in there until custom roms based on 4.4.2 comes out or people find a way to go back to 4.3. The reason the file from firasusman didn't work is probably because there might be difference in how kit kat deals with efs compared to jellybeans which it was written for in the first place.
Sent from my SM-N9005 using xda app-developers app
You probably are right as it doesn't really work. Anyway I'll keep waiting
Sent from my SM-N9005 using XDA Premium 4 mobile app
same here
Yip you won't be able to go to a lower bootloader than you are on with KK, CM based ROMs are currently running (MJ7) _ will have to wait until the new bootloader is implemented into new(er) builds.
Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app
kratumay said:
Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.
tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
I'm assuming you're on 4.3, you have to use this in pda/ap on odin. After flashing phone will restart with android and texts in color. After that it will reboot again to system and you will have root. SEandroid Enforcing is normal if you're rooting you're device. Have you checked with root checker if you have root? Also, once you root your device you will have to flash a custom recovery like cwm or twrp to be able to boot to those recovery.
Hakired said:
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.
Click to expand...
Click to collapse
Thanks a lot !
It Works !
tritri71 said:
Thanks a lot !
It Works !
Click to expand...
Click to collapse
Awesome enjoy kitkat
n9005 cm11 20140226 problems
yesterday i installed cm11 nightly 20140226 on my n9005 via twrp 2.6.3.7 (before i have had 4.3)
it all works fine except 2 little problems:
1. whenever i plug the charger or usb cable to computer, the phone is turned on automatically without pushing the power button.
2. my time & date settings can't be saved, and each time on turning on it goes back to 2013 and 12:00
Thanks in advance to all answers
Same problem
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''
Kjetilz said:
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''
Click to expand...
Click to collapse
First you will have to update to stock 4.4.2 then you can flash any 4.4.2 roms.
Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?
Mediaspot said:
Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?
Click to expand...
Click to collapse
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.
hey_joe said:
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.
Click to expand...
Click to collapse
I just tried flashing this rom but the same thing. http://forum.xda-developers.com/showthread.php?t=2671039 will try to look for stock firmware and be back with results
I am getting same error but after that phone boots up fine
OK guys,
well after i updated to new lolipop via kies i didn't like it so i downgraded again to kitkat 4.4.4. Now its been almost 2 weeks trying everything i know and can to root my phone again but so far i can not .
i used CF-Auto-Root-a7lte-a7ltexx-sma700fd with base "A700FDXXU1AOA2_HOME.tar" all via odin and still won't work everytime i try to root i get this stupid error "Recovery is not Seandroid Enforcing set | warrnty bit: recovery"
i tried everything wipe date-hard factory reset .... everything it just won't get done -_->
so i tried kingroot and now boom it worked BUT i want to install SuperSu and it won't install bianry i tried everything from supersu me to terminal console trick and still won't get done and i need SuperSu coz i like it more and it works better with Lucky Patcher plus i already got it premium XD
so what did i do wrong? why i can't root it and get this stupid error ?
P.S
1-in odin mode there is this blue text 'Secure download on "
2-could this all relate to knox some how ?
"Recovery is not Seandroid Enforcing set warranty bit: recovery" is not an error, its a warning and means nothing.
When downgrading to kitkat you need to wipe the data partition.
Flash the stock firmware, wipe the Data partiton, boot to android (10mins), reboot to download mode, flash cfautoroot.
If cfautoroot doesn't work flash TWRP then flash Supersu.
ashyx said:
"Recovery is not Seandroid Enforcing set warranty bit: recovery" is not an error, its a warning and means nothing.
When downgrading to kitkat you need to wipe the data partition.
Flash the stock firmware, wipe the Data partiton, boot to android (10mins), reboot to download mode, flash cfautoroot.
If cfautoroot doesn't work flash TWRP then flash Supersu.
Click to expand...
Click to collapse
u mean installing CF-Auto-Root-a7lte-a7ltexx-sma700fd via Odin again but after re-install the firmware and wipe data partition?
also why would i tried to flash TWRP before and it caused the phone to freez in samsung logo with same error ""Recovery is not Seandroid Enforcing set warranty bit: recovery""
?
OnMission said:
flash cfautoroot? u mean installin it via Odin ? and can i have link for it please ?
also why would i tried to flash TWRP before and it caused the phone to freez in samsung logo with same error ""Recovery is not Seandroid Enforcing set warranty bit: recovery""
?
Click to expand...
Click to collapse
You already have it: CF-Auto-Root-a7lte-a7ltexx-sma700fd
Are you sure you used the correct TWRP?
ashyx said:
You already have it: CF-Auto-Root-a7lte-a7ltexx-sma700fd
Are you sure you used the correct TWRP?
Click to expand...
Click to collapse
i don't know ? how can i till ? i clicked on vol up +home button+lock button and open recovery mode ( before trying TWRP)
OnMission said:
i don't know ? how can i till ? i clicked on vol up +home button+lock button and open recovery mode ( before trying TWRP)
Click to expand...
Click to collapse
Which TWRP did you flash -link?
ashyx said:
Which TWRP did you flash -link?
Click to expand...
Click to collapse
this one here
http://forum.xda-developers.com/android/development/recovery-galaxy-a7-t3085266
OnMission said:
this one here
http://forum.xda-developers.com/android/development/recovery-galaxy-a7-t3085266
Click to expand...
Click to collapse
I don't think that is for your device.
This one is t700fd: http://forum.xda-developers.com/showthread.php?t=3253126
ashyx said:
I don't think that is for your device.
This one is t700fd: http://forum.xda-developers.com/showthread.php?t=3253126
Click to expand...
Click to collapse
i tried it all again and it worked like charm i flashed using same link verion i posted above and it worked
after hard reset>flash frimware>using odin to root it worked i think the problem was in the frimware i used
thanks guys for helping out
how did u downgrade from 5.0.1 to 4.4.4. pls explain in detail
Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
WelshY1987 said:
Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
Click to expand...
Click to collapse
Go to this thread-https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 and download recovery of your model
aarush.chaurasiya said:
Go to this thread-https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 and download recovery of your model
Click to expand...
Click to collapse
that is the one i'm using j500FN
WelshY1987 said:
that is the one i'm using j500FN
Click to expand...
Click to collapse
That's for Android 5.1..1 you need this one [RECOVERY] [TWRP-3.0.2-0] Samsung Galaxy J5 [MM][Android 6.0.1]
About the "seandroid enforcing" just ignore it, it's because your rom was modified.
American_Jesus said:
That's for Android 5.1..1 you need this one [RECOVERY] [TWRP-3.0.2-0] Samsung Galaxy J5 [MM][Android 6.0.1]
About the "seandroid enforcing" just ignore it, it's because your rom was modified.
Click to expand...
Click to collapse
even with that one it's still booting and glitch crashing unless i boot into download or recovery. It even do the pixel fade with the 2 errors on top just by plugging in charger and not even turning it on
WelshY1987 said:
even with that one it's still booting and glitch crashing unless i boot into download or recovery. It even do the pixel fade with the 2 errors on top just by plugging in charger and not even turning it on
Click to expand...
Click to collapse
Working after flashing official rom and TWRP, BUT can't flash other roms (update process ended with ERROR: 7
WelshY1987 said:
Working after flashing official rom and TWRP, BUT can't flash other roms (update process ended with ERROR: 7
Click to expand...
Click to collapse
Check if your flashing the right ROM for your phone model.
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing
Click to expand...
Click to collapse
American_Jesus said:
Check if your flashing the right ROM for your phone model.
Click to expand...
Click to collapse
i have tried with 2 rom downgrading to 5.1
https://forum.xda-developers.com/ga...m-cyanogenmod-13-0-samsung-galaxy-j5-t3519580
and 6.0.1
https://forum.xda-developers.com/galaxy-j5/development/p-resurrectionremix-v5-7-4-t3497445
WelshY1987 said:
i have tried with 2 rom downgrading to 5.1
https://forum.xda-developers.com/ga...m-cyanogenmod-13-0-samsung-galaxy-j5-t3519580
and 6.0.1
https://forum.xda-developers.com/galaxy-j5/development/p-resurrectionremix-v5-7-4-t3497445
Click to expand...
Click to collapse
Post your problem on ROMs thread, CM13 installation works fine, but you need firmware from 5.1.1 and TWRP for the 5.1.1 .
You need the right TWRP for your current firmware, like if CM13 uses firmware from 5.1.1 you need to 1st downgrade to Android 5.1.1 and then install TWRP for 5.1.1.
Same for rom that uses other firmware version
Try flashing stock using TWRP recovery. If you have a PC, you can enable MTP in the Mount menu in TWRP and connect it to PC and then move the firmware file and install it using TWRP again.
Alternatively, you can boot into download mode (Vol. Down+Home+Lock Screen simultaneously) and install the stock firmware using ODIN.
You can also create a backup of your apps in TWRP so that you can restore them after you have installed stock firmware.
Ready to help if you need more elaborate steps or any other information.
Had completely same problem with My bootloader. I just downgraded to 5.1 stock with Odin and flashed twrp by Nick Verse. After that I had no problems flashing any roms.
WelshY1987 said:
Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
Click to expand...
Click to collapse
Have you reflaahed the stock firmware set up all the phone and then reflash the recovery ? This could fix
Welcome guys,
I have Galaxy S4 and I wanted to install Custom ROM. Unfortunately when I installed TWRP (the newest build), my phone displays "Set warranty bit: kernel" and then it boots into Recovery Mode (twrp works fine), but stock ROM doesn't boot. I don't know how to deal with it. Will custom ROM install fix that problem? I don't want to brick it.
I have access to download mode, TWRP (as I said before, when I turn phone on, it boots into TWRP instantly), but unfortunately ODIN doesn't recognize phone at all.
Please help :crying:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
audit13 said:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
Click to expand...
Click to collapse
I'm such an idiot. When knox is tripped you cant run stock ROM, so basically I just installed LineageOS and it works hah
Tripping knox does not prevent a phone from running a stock ROM.
audit13 said:
Tripping knox does not prevent a phone from running a stock ROM.
Click to expand...
Click to collapse
So it's strange though. I couldnt boot stock ROM and the only thing I had to do was install a custom one. Anyway, thanks for the answer
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
audit13 said:
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
Click to expand...
Click to collapse
Aaaand here we got the problem. I tried to install twrp many times and unfortunately the stock one stopped running (dont ask, i dont know how it happened). Despite this everything worked but I wanted to install custom ROM and then that problem happened. It was just the lack (??) of stock ROM or knox blocked the availability to boot it.
Oh, completely forgot. I installed TWRP by LineageOS' tutorial on their page
It all worked out in the end which is the important part.
Thanks for sharing your solution.