I have a verizon S5 G900V. First it was marshmallow. i wanted to root it and unlocked bootloader. i got back lollipop and rooted, then unlocked bootloader with the help of this forum. After that I installed twrp recovery and flashed a marshmallow rooted rom. Everything just worked fine without one, my bootscreen show "Kernel not seandroid enforced" and a custom padlock icon. I tried to install root triangle away and reset flash counter. But it didn't work. If anyone know how to get rid of this problem, please share. I search a lot, but didn't find. (sorry for my bad English)
It's not a problem, is a badge of nerd honor
Bryanx86 said:
It's not a problem, is a badge of nerd honor
Click to expand...
Click to collapse
I know, it's not a problem. But is there any way to remove this symble of unlocked bootloader???
Ripon Raihan said:
I know, it's not a problem. But is there any way to remove this symble of unlocked bootloader???
Click to expand...
Click to collapse
Only by flashing full stock tar file to flash bootloader, because on 6.0 "download mode" has to display official to be able to flash bootloader.
Bryanx86 said:
Only by flashing full stock tar file to flash bootloader, because on 6.0 "download mode" has to display official to be able to flash bootloader.
Click to expand...
Click to collapse
If I flash full stock tar file, then my bootloader will be locked again. It's mean there's no way. right??
Ripon Raihan said:
If I flash full stock tar file, then my bootloader will be locked again. It's mean there's no way. right??
Click to expand...
Click to collapse
No way except go stock with locked bl
Bryanx86 said:
No way except go stock with locked bl
Click to expand...
Click to collapse
That's mean people who have unlocked verizon s5, everyone have this Kernel not seandroid enforced in their bootscreen??
Ripon Raihan said:
That's mean people who have unlocked verizon s5, everyone have this Kernel not seandroid enforced in their bootscreen??
Click to expand...
Click to collapse
Dude, you can't get rid of it, give it up. It's 3 seconds even you boot, there are more important things to worry about
Ripon Raihan said:
That's mean people who have unlocked verizon s5, everyone have this Kernel not seandroid enforced in their bootscreen??
Click to expand...
Click to collapse
You can get it to say kernel seandroid enforcing depending on what ROM you're on and what kernel you're using. What custom ROM are you on?
Bryanx86 said:
You can get it to say kernel seandroid enforcing depending on what ROM you're on and what kernel you're using. What custom ROM are you on?
Click to expand...
Click to collapse
I m on stock mm unlocked rooted rom.
Ripon Raihan said:
I m on stock mm unlocked rooted rom.
Click to expand...
Click to collapse
Are you using a custom kernel?
Bryanx86 said:
Are you using a custom kernel?
Click to expand...
Click to collapse
No, I m on stock kernel. Build number pf4.
Ripon Raihan said:
No, I m on stock kernel. Build number pf4.
Click to expand...
Click to collapse
OK, try this, download terminal emulator from play store, open, type su, grant root. Type " sentenforce 1" without quotations, it will change your selinux to enforcing but I don't know how that will affect root so you might want to make a backup first
Bryanx86 said:
OK, try this, download terminal emulator from play store, open, type su, grant root. Type " sentenforce 1" without quotations, it will change your selinux to enforcing but I don't know how that will affect root so you might want to make a backup first
Click to expand...
Click to collapse
Tnx, but didn't work. Ok, I don't need to remove that message. help me to remove "custom" padlock icon.
when my bootloader was locked, root triangle away worked. but after unlock bootloader it don't work.
Ripon Raihan said:
Tnx, but didn't work. Ok, I don't need to remove that message. help me to remove "custom" padlock icon.
when my bootloader was locked, root triangle away worked. but after unlock bootloader it don't work.
Click to expand...
Click to collapse
No, refer to my first post, and all posts thereafter. When done, refer to this post.
Related
I'm on 6.0.1 TW Ron with unlocked bootloader, and I fear I will need to wait for V7 of magisk, for Samsung support.
If not, I'm in search of a flashable unrooted rom (or instructions on how to extract it from a factory Tar, as to not overwrite my bootloader , thus locking it.
I've tried searching both Google and xda for unrooted 6.0.1 s5 verizon rom (as well as variations of the same concept) without anything that I could validate it did NOT include boot loader (mainly muinez "upgrade roms", for flash fire for locked bootloaders. Is there a way to flash a stock rom via custom recovery that does not have root but is root able systemless-ly via Magisk. Is my last option to backup and pray not only that unroot works, but that magisk is installable on s5?
Thanks in advance
Bootloader files are rpm abooot and sbl just don't flash those
Sent from my SM-G900V using Tapatalk
bbrabham said:
I'm on 6.0.1 TW Ron with unlocked bootloader, and I fear I will need to wait for V7 of magisk, for Samsung support.
If not, I'm in search of a flashable unrooted rom (or instructions on how to extract it from a factory Tar, as to not overwrite my bootloader , thus locking it.
I've tried searching both Google and xda for unrooted 6.0.1 s5 verizon rom (as well as variations of the same concept) without anything that I could validate it did NOT include boot loader (mainly muinez "upgrade roms", for flash fire for locked bootloaders. Is there a way to flash a stock rom via custom recovery that does not have root but is root able systemless-ly via Magisk. Is my last option to backup and pray not only that unroot works, but that magisk is installable on s5?
Thanks in advance
Click to expand...
Click to collapse
Do you have a bootlogo with "Kernel not seandroid enforced" and custom padlock icon???
Ripon Raihan said:
Do you have a bootlogo with "Kernel not seandroid enforced" and custom padlock icon???
Click to expand...
Click to collapse
Correct.
bbrabham said:
Correct.
Click to expand...
Click to collapse
Did you try to remove those ugly symble?? I tried, but couldn't. If you find a way, please share.
Ripon Raihan said:
Did you try to remove those ugly symble?? I tried, but couldn't. If you find a way, please share.
Click to expand...
Click to collapse
Downgrade?
http://forum.xda-developers.com/ver...ide-verizon-s5-bootloader-unlock-100-t3446139
bbrabham said:
Downgrade?
http://forum.xda-developers.com/ver...ide-verizon-s5-bootloader-unlock-100-t3446139
Click to expand...
Click to collapse
No, not downgrade. I want to stay unlocked bootloader in marshmallow but don't want to those custom padlock icon and Kernel not seandroid enforced message. Is there any way??
try flashing a mm boot img tar in odin if you do you will lose root but you can get it back on an unlocked bootloader by booting to custom recovery and flashing supersu.zip http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 download the twrp flashable zip
how are you everybody please can any one help me
i flashed android nougat on my phone via unofficial method via firmware finder app
and after i flashed it i found some apps dosnot exist and i found the build number is "nrd90m test-keys"
now i want to rollback to marshmallow
i unlocked bootloader but i cant install twrp
can anyone help me please
What exactly have you tried already?
Have you tried "fastboot flash recovery ***.img" ?
Of course, only the Nougat recovery will work.
Schlengge said:
What exactly have you tried already?
Have you tried "fastboot flash recovery ***.img" ?
Of course, only the Nougat recovery will work.
Click to expand...
Click to collapse
yes i tried this method with a nougat recovery but it says remote:command not allowed
i have bootloader unlocked but frb still locked
that shoud i do please
anamedo7mdy said:
yes i tried this method with a nougat recovery but it says remote:command not allowed
i have bootloader unlocked but frb still locked
that shoud i do please
Click to expand...
Click to collapse
Hmm command not allowed usually says that bootloader is locked. You did unlock it manually again right? Because it often is locked even though it says unlocked on the bootloader.
Schlengge said:
Hmm command not allowed usually says that bootloader is locked. You did unlock it manually again right? Because it often is locked even though it says unlocked on the bootloader.
Click to expand...
Click to collapse
no iam sure it is unlocked cause it shows me a message when opening the phone say that the phone is unlocked
but the frp is still locked is that the problem ???
should i unlock frp firsr or what shoud i do ??
anamedo7mdy said:
no iam sure it is unlocked cause it shows me a message when opening the phone say that the phone is unlocked
but the frp is still locked is that the problem ???
should i unlock frp firsr or what shoud i do ??
Click to expand...
Click to collapse
Nah that should not be an issue.
I don't know... Have you started fastboot with admin rights if on Windows?
Schlengge said:
Nah that should not be an issue.
I don't know... Have you started fastboot with admin rights if on Windows?
Click to expand...
Click to collapse
no i didnot
no one can help me ????????
it is uppset
Try to flash recovery with an app like Flashfy or FlashFire.
Potato997 said:
Try to flash recovery with an app like Flashfy or FlashFire.
Click to expand...
Click to collapse
is that dangerous or need root ???
anamedo7mdy said:
is that dangerous or need root ???
Click to expand...
Click to collapse
Yes root is needed.
Potato997 said:
Yes root is needed.
Click to expand...
Click to collapse
can i install root via kingroot
anamedo7mdy said:
can i install root via kingroot
Click to expand...
Click to collapse
I don't think it will work.. there is already a root method for nougat.
Potato997 said:
I don't think it will work.. there is already a root method for nougat.
Click to expand...
Click to collapse
can you tell me how can i root it
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
MissCherry1241 said:
To begin. My device, as mentioned in the title, is the Samsung Galaxy J3 sm-J320W8 running Android 7.1.1.
I tried to root it with the CF-Auto-Root. I matched all the info as needed, that being Model number and android version, and continued with the root as you normally would with Oden. After Oden says it passes. My device reboots, but instead of going into recovery and installing SuperSU it gives me the "Recovery is not seandroid enforcing" error at the top left of the screen. It then reboots once again and the phone starts as normal so thankfully I didn't break anything. But SuperSU was not installed and my device remains unrooted. I did notice that the SuperSU zip was transferred to my SD card though.
Does anyone know what the problem is? Hopefully with a solution as well.
Click to expand...
Click to collapse
Just use twrp to install SuperSU.
ashyx said:
Just use twrp to install SuperSU.
Click to expand...
Click to collapse
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
MissCherry1241 said:
I have yet to find twrp available for my device and I don't know how to compile one myself. CF-Auto-Root is the only root I have found so far for the j320w8
Click to expand...
Click to collapse
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
ashyx said:
Looking back over some posts it seems it was unclear whether this device has a locked bootloader or not.
I never actually got a real confirmation.
Check out the thread below, you will find a root method as yet unconfirmed!
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-j3-root-t3544157/page15
Click to expand...
Click to collapse
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
MissCherry1241 said:
From what I can tell in that thread since I have seen it prior to posting this one they have yet to have any confirmed rooting methods. And the j320w8 rooted boot file from what I remember is the one that soft bricked my device last time. I can try again though. I have a backup and recovery image so it's not a big deal if I get soft bricked again.
I could also check if there is a way to unlock the bootloader on my device... If that's even a thing. I'm still trying to learn what some of this stuff means.
Click to expand...
Click to collapse
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
ashyx said:
If the bootloader is locked there's no way to unlock it.
What was the soft brick, gave you got details?
Click to expand...
Click to collapse
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
MissCherry1241 said:
After installing one of the files through oden it just got stuck and wouldn't turn on. Couldn't access the Android Recovery and trying to turn on the device basically just made it get stuck on the samsung loading screen. I did still have access to the Download so I was able to reflash the original 7.1.1 firmware back into it
Click to expand...
Click to collapse
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
ashyx said:
It wouldn't have worked as it's a Marshmallow firmware and you are running Nougat. The 2 are not compatible.
Click to expand...
Click to collapse
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
MissCherry1241 said:
Ah. Would it be possible for me to downgrade firmwares in order to get the root? I'll take older rooted firmware over newer unrooted any day
Click to expand...
Click to collapse
What is your current firmware build?
ashyx said:
What is your current firmware build?
Click to expand...
Click to collapse
Right now I am on Android version 7.1.1
MissCherry1241 said:
Right now I am on Android version 7.1.1
Click to expand...
Click to collapse
No, please post the firmware build version in settings/about.
ashyx said:
No, please post the firmware build version in settings/about.
Click to expand...
Click to collapse
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
MissCherry1241 said:
Sorry. I'm not familiar with what that is. Here's a screenshot of my software information.
https://imgur.com/EL0E84O
https://imgur.com/46m4P8L
Click to expand...
Click to collapse
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
ashyx said:
OK you should be able to downgrade to J320w8VLU2AQA1 then flash the rooted boot with odin.
Click to expand...
Click to collapse
Goodie! I'll try that out now and come back to confirm whether or not it works
MissCherry1241 said:
Goodie! I'll try that out now and come back to confirm whether or not it works
Click to expand...
Click to collapse
OK. Ensure you make a note of what odin and the device screen reports.
ashyx said:
OK. Ensure you make a note of what odin and the device screen reports.
Click to expand...
Click to collapse
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
MissCherry1241 said:
I seem to have run into an Issue. I reinstalled Android 6.0.1 successfully and set up my device. Made sure that it was J320w8VLU2AQA1 and confirmed it through the about section.
Then I flashed the rooted boot that you linked. Oden showed success and my device rebooted as normal. But... My phone started as if nothing happened. No SuperSU installed and when I go into recovery mode it just has the basic Android Recovery. No TWRP.
Click to expand...
Click to collapse
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
ashyx said:
It's not TWRP its a rooted boot image.
Install the Superuser app from the Play store and hopefully you should have root priveledges.
After installing, open the Superuser app and report back its status.
Click to expand...
Click to collapse
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
MissCherry1241 said:
Alright. I installed SuperSU. It did an update and rebooted my device. Checked with Root checker app and I am in fact rooted!
I didn't realize that's what I had to do. So all of this is working and I have rooted my J320W8
Click to expand...
Click to collapse
Finally a proper confirmation.
Glad its worked for you. :good: You MAY be able to update to Nougat by flashing the stock firmware with FLASHFIRE.
Just ensure EverRoot is enabled.
Is there a way to get rid of the boring message showed up every time if you have unlocked your bootloader?
"Your device software can't be checked for corruption. Please lock the bootloader "
See attached file (not mi a1, but it' s pretty much the same)
Simply lock your Bootloder of phone.
prasanna0007 said:
Simply lock your Bootloder of phone.
Click to expand...
Click to collapse
What if i need it unlocked?
Example for custom roms
0lorenzo said:
What if i need it unlocked?
Example for custom roms
Click to expand...
Click to collapse
In my knowledge if u relock bootloader when u r in custom rom u will get some issues.
Also this boot message cannot fix in my knowledge. If u rooted then its not adviced to relock bootloader. Relock ur bootloader only if u r in pure stock and no root...
Unlocked bootloader needs for custom roms and root and twrp
Rajeev said:
In my knowledge if u relock bootloader when u r in custom rom u will get some issues.
Also this boot message cannot fix in my knowledge. If u rooted then its not adviced to relock bootloader. Relock ur bootloader only if u r in pure stock and no root...
Unlocked bootloader needs for custom roms and root and twrp
Click to expand...
Click to collapse
I have magisk correctly installed, but it looks like it' s not enought to get rid of the boot warning
0lorenzo said:
I have magisk correctly installed, but it looks like it' s not enought to get rid of the boot warning
Click to expand...
Click to collapse
Magisk won't help u to remove the boot warning. Its normal warning only when we unlock bootloader
Rajeev said:
Magisk won't help u to remove the boot warning. Its normal warning only when we unlock bootloader
Click to expand...
Click to collapse
Sorry i misunderstood your previous message, i understood that with root the warning would be gone.
I' m asking as newbie, can't we replace it with some other image, like they say on this thread?
https://www.google.it/amp/s/forum.x...move-corruption-warning-message-t3248441/amp/
0lorenzo said:
Sorry i misunderstood your previous message, i understood that with root the warning would be gone.
I' m asking as newbie, can't we replace it with some other image, like they say on this thread?
https://www.google.it/amp/s/forum.x...move-corruption-warning-message-t3248441/amp/
Click to expand...
Click to collapse
Thats because of my poor English:laugh:
Let me check that thread
I rooted my Mi A1 and magisk installed. But when i rebooted my phone then root is gone by itslef. I mean when i rebooted then its unrooted by itslef. Sorry for my bad english
I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.
zdxd3213 said:
I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.
Click to expand...
Click to collapse
Reflash stock
zdxd3213 said:
I've got bootloop even flashed stock rom.
and i can't flash twrp because "Only official released binaries are allowed to be flashed" comes up even OEM and FAP was unlocked.
Click to expand...
Click to collapse
If you came from custom rom thats totally normal and happened for me on many phones and many times
Did you tried to wipe cash/system partition from stock recovery?(don't remember what was the words exactly)
NecromancerViper said:
Reflash stock
Click to expand...
Click to collapse
if that works, i won't write this.
amirizad_7436 said:
If you came from custom rom thats totally normal and happened for me on many phones and many times
Did you tried to wipe cash/system partition from stock recovery?(don't remember what was the words exactly)
Click to expand...
Click to collapse
nah, not works.
zdxd3213 said:
nah, not works.
Click to expand...
Click to collapse
Would you please explain what exactly happened and what did you do to let us informed?
zdxd3213 said:
nah, not works.
Click to expand...
Click to collapse
then, be more exact, how did you brick it? And what were you trying before it?
amirizad_7436 said:
Would you please explain what exactly happened and what did you do to let us informed?
Click to expand...
Click to collapse
1. flash twrp
2. formatted / (< i think this is cause of main problem)
3. installed custom rom
-Bootloop-
4. formatted /system /data /cache
5. flashed stock
-Bootloop-
6. flashed dm-verity disable
-Booted-
-rebooted to install twrp-
-Bootloops by "Only Official released binaries are allowed to be flashed"-
7. flashed stock
-Bootloops-
zdxd3213 said:
1. flash twrp
2. formatted / (< i think this is cause of main problem)
3. installed custom rom
-Bootloop-
4. formatted /system /data /cache
5. flashed stock
-Bootloop-
6. flashed dm-verity disable
-Booted-
-rebooted to install twrp-
-Bootloops by "Only Official released binaries are allowed to be flashed"-
7. flashed stock
-Bootloops-
Click to expand...
Click to collapse
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting
garylawwd said:
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting
Click to expand...
Click to collapse
Maybe I rebooted before complete first boot?
garylawwd said:
How did you flash stock? You may have relocked your bootloader by doing so. That would explain the error you are now getting
Click to expand...
Click to collapse
sry i did twrp and flashed dm-verity disable with twrp.
and i booted when reboots bootloader relocked.
but the download mode could be accessable.
Hi,
how did you "flashed dm-verity disable"?
kind regards