[Completed] Q: Galaxy A8, "kernel is not seandroid enforcing" "custom binary blocked by frp" help - XDA Assist

Q: Galaxy A8, "kernel is not seandroid enforcing" "custom binary blocked by frp" help
Hi,
This is Ejaz from Afghanistan. Yeah! from Afghanistan.
I bought a new Galaxy A8 and I tried to root it. I used space x kernel and Odin to root my phone. It didn't work. Some thread in XDA said, after rooting your phone, install Supersu from playstore. I did it and then tried to update binary files. It restarted my phone and this freaky android icon showed up with something moving in its belly. And then this message showed up, "kernel is not seandroid enforcing" "custom binary blocked by frp". Then the phone turned off. Now the same message shows up, when I turn on the phone and then it goes back off. I wiped the phone and the cache partition, still no good result.
Someone in the web said, download the Stock firmware and reinstall it using Odin. I am downloading it, and it takes hours. Yeah, I said I am from Afghanistan, that's why it takes hours. The internet is slow.
So anyone with good heart, please save my life. Coz I spent 600$ to buy this phone.
Thanks in advance.

ejazi said:
Hi,
This is Ejaz from Afghanistan. Yeah! from Afghanistan.
I bought a new Galaxy A8 and I tried to root it. I used space x kernel and Odin to root my phone. It didn't work. Some thread in XDA said, after rooting your phone, install Supersu from playstore. I did it and then tried to update binary files. It restarted my phone and this freaky android icon showed up with something moving in its belly. And then this message showed up, "kernel is not seandroid enforcing" "custom binary blocked by frp". Then the phone turned off. Now the same message shows up, when I turn on the phone and then it goes back off. I wiped the phone and the cache partition, still no good result.
Someone in the web said, download the Stock firmware and reinstall it using Odin. I am downloading it, and it takes hours. Yeah, I said I am from Afghanistan, that's why it takes hours. The internet is slow.
So anyone with good heard, please save my life. Coz I spent 600$ to buy this phone.
Thanks in advance.
Click to expand...
Click to collapse
Before rooting your device you have to go into your settings/about device and tap the build number until developer options is unlocked. The go into developer options and click the OEM UNLOCKING toggle. After that then proceed to root your device. You did everything correct but not having OEM unlocking ticked it stopping the phone from booting since it's not a stock kernal. What your gonna need to do now is Odin back to complete stock uprooted and then do what I said above then you will be able to proceed to root your device as you did before.

SICKMADE said:
Before rooting your device you have to go into your settings/about device and tap the build number until developer options is unlocked. The go into developer options and click the OEM UNLOCKING toggle. After that then proceed to root your device. You did everything correct but not having OEM unlocking ticked it stopping the phone from booting since it's not a stock kernal. What your gonna need to do now is Odin back to complete stock uprooted and then do what I said above then you will be able to proceed to root your device as you did before.
Click to expand...
Click to collapse
Thanks God, my phone is alive. I downloaded the stock firmware and I flashed it. Rooted my phone again. And did whatever you said. But now the SU Binary wouldn't update. PLease help. By the way, I am running 5.1.1.
Thanks for the pro steps on the OEM Unlocking toggle. :good: :good: :good: wish you were close, I would buy you a pizza.

ejazi said:
Thanks God, my phone is alive. I downloaded the stock firmware and I flashed it. Rooted my phone again. And did whatever you said. But now the SU Binary wouldn't update. PLease help. By the way, I am running 5.1.1.
Thanks for the pro steps on the OEM Unlocking toggle. :good: :good: :good: wish you were close, I would buy you a pizza.
Click to expand...
Click to collapse
So your opening au and it's saying it needs to update binaries? Instead of choosing custom recovery method use stock recovery method when it pops up and see if that works

Related

[Q] Stuck on boot! Any Help?

Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.

Trying to unroot a Galaxy S6...losing the will to live :(

Can anyone help? I spent a big chunk of my hard earned money on a refurbed S6 for my daughter, she's had it about a week (she's Pokemon mad btw). The latest update for Pokemon Go came out and now she's blocked from the game as it appears the phone has been rooted. If I'd known, I wouldn't have bought it. Anyway, for the last 2 days my partner and I have been trying to unroot it. We've used various versions of Odin to no avail. I had a lot of trouble finding the right firmware because it looks like the phone was Polish according to the version and CSC numbers, and tbh I'm still not sure if we're trying the right one. Software is 5.1.1. right now. I've tried installing SuperSU but it won't run, it just crashes the phone and forces a reboot. We've tried manually unrooting with a file manager but the su files we need to delete reappear seconds after they're deleted. I'm at the end of my tether, does anyone have any ideas?
You won't be able to unroot it until you flash stock firmware. I don't know if the game checks the knox status.
Give this a go
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Enjoy
Unforunately my partner spent almost all night trying to flash the firmware. According to him it 'nearly' worked, however, I now have a phone stuck in a boot loop. :crying:
Run emergency recovery on Smart switch
ccalixtro said:
Run emergency recovery on Smart switch
Click to expand...
Click to collapse
Do I need to have smart switch installed on the phone for this to work?
amber_1978 said:
Do I need to have smart switch installed on the phone for this to work?
Click to expand...
Click to collapse
No, run it on your pc.
Thanks, I'll give it a go after work.
ccalixtro said:
No, run it on your pc.
Click to expand...
Click to collapse
Smart switch won't work, says it doesn't recognise the device
I think I would give original firmware of your country and odin a try. One of possible ways is to download all needed files from the site of sammobile.
For me this way works every time when I stuck in boot loop. Odin functionates when you are in download mode. Switch off your s6, then start by pressing home-, powerbutton and Volume down at the same time.
Then start Odin on PC, then connect USB and so on.
Greetz JG
amber_1978 said:
Smart switch won't work, says it doesn't recognise the device
Click to expand...
Click to collapse
When you select emergency recovery theres an option where you have to write the device model and the serial number
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
fahad999 said:
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately I've tried Kies already and I can't get it to work at all. I get a message telling me my device is not compatible and the whole thing just stops. I'll give it another go though, no harm in trying. Thanks
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
socal87 said:
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
Click to expand...
Click to collapse
Really? Did you do the latest update in the game and it still worked ok? This phone has definitley not been used for location spoofing by us and I'm pretty sure there were no apps of that nature on the phone. I downloaded a root checker when everything went wrong the other day, it said the phone was rooted. I'm totally at a loss tbh. Right now it's still in a boot loop. Trying to flash it with Odin as we speak.
Just an update. Tried Smart Switch. Tried the model and serial numbers on the back of the phone case, these weren't recognised so I went to the recovery screen and hit the home button and got a completely different set of numbers. Different IMEI, model number, you name it. I'm assuming this is why Odin won't work, I'm looking for the wrong firmware? I obviously have Frankenstein's phone. No idea what to do now.
Best thing to do is to flash TWRPP and try to flash a custom stock rom through the TWRP recovery which does not have root installed..... If that doesn't work try to find a generic stock firmware for Odin, meaning a firmware that can run in any country..... If all else fails update it to 6.0.1 stock firmware. Try the closest firmwares to your location.
And if you do manage to get to the Samsung logo let the phone sit there for a good 10 minutes even if it reboots....
When I bricked my Samsung I used masiks custom 6.0.1 rom based on stock, but had all the links to bootloaders cscs radios and what not so giv that a shot if you can find it.
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Link to rom that helped me http://forum.xda-developers.com/galaxy-s6/development/masik-marshmallow-1-0-jan-20-2016-t3297961
do you have lucky patcher playstore installed ?

ODIN Fails Every Time

Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^

bricked s8+ trying to root

ive tried to root my s8+ following the step by step guide but now its a brick
i have never rooted before and tried it for the first time, everything seemed to be going correctly until i pressed wipe and swiped to confirm, i got error message unable to mount storage, now i have a continuous loop of samsung s8 logo
i have tried connecting to odin again and no joy.
is there any hope or is it for the bin ?
gutted
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
i have model SM-955F
Download the stock ROM and download mode should be reachable, where you can then flash it
Pedroc1999 said:
Download the stock ROM and download mode should be reachable, where you can then flash it
Click to expand...
Click to collapse
i need more information if possible ? i have no idea how to do it, its my first and probably last attempt at rooting
It's probably not binned, don't worry. Can you get into Download mode again?
- Press and hold the Bixby, Volume down and Power buttons together until you see anything on screen.
- When you see a warning screen, hit Volume Down to continue to download mode.
GibMcFragger said:
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
Click to expand...
Click to collapse
Come on man, if you had a snapdragon version, you can't root or even get that far.
yes i can get into the screen where it says downloading do not turn off
It does look like it's the usual snapdragon variant, yeah. You need the Exynos version for its unlocked bootloader, if you want root and whatnot.
Honestly unless you have specific reasons for root, you probably don't need it.
I was pleasantly surprised at how much I don't miss it so far, but I can't speak for everyone else. I know Brava27 wouldn't dare.
Edit: Okay good. So the Stock ROM is basically the factory image always intended for your phone, from Samsung. You just have to find and download that, then flash it as usual via Odin.
PLEASE triple check around and do your research on whether this link provides you the right one, but here is a first-hit I found when searching for a stock rom for your model. https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022
brilliant thank you i will give it a try
does it unroot it also if i flash it back to stock and put knox back to normal or is that history now ?
That's right, it's completely stock, so it'd be like you got the phone fresh. It'll be unrooted if you get it working.
So that said, ensure your SIM is in the phone before you set it up, or it'll reset on you again when you insert it later.
I'm not sure what Knox's status would be and if the e-fuse has triggered... you'll know when you're powering on the device, I think. It's no real matter, unless you're concerned about warranty. In which case, you were going to stop caring about that right after attempting to root anyway.
I'm still not certain on what firmware file you want. Might want to search around for something that matches your carrier.
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
galarond said:
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
Click to expand...
Click to collapse
can you use them on rooted devices with knox triggered ?
No, I was not able to use Samsung Pay on my Note 5 after I tripped knox. It does some sort of security check on start-up of the app.
The bigger question is whether it "rooted" yet or not. With some luck, the e-fuse has not triggered yet and it's a clean device still.
widget2k13 said:
can you use them on rooted devices with knox triggered ?
Click to expand...
Click to collapse
yes with custom roms can be done or with some build.prop mods too.
So the snapdragon version is not rootable? Damn, I didn't know that.
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
widget2k13 said:
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
Click to expand...
Click to collapse
For the "Security notice" try this:
root explorer go to /system/app/SecurityLogAgent delete folder
For "S-Health" to work, follow this:
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Good luck.
Totaly different sittuation but I think I have this right from what you say in this thread.
That Knox being tripped cant be reversed? and that Knox is a fuse so it cant be bypassed with otg cable backup?

Phone flashed with unauthorized software.

Hello everybody! I just joined and am basically a complete noob at this, so thanks for the help in advance. I bought a Samsung Galaxy S10 about a year and a half ago off of Amazon to replace my S9. However, whenever I booted it up, it would give me this message; "Security Error: This phone has been flashed with unauthorized software and is locked". I didn't return it at the time like I should have and now I'm stuck with it. I've already tried flashing it with Odin and using the latest firmware that I got off Frija, and hard resetting as well, and still the same damn message pops up whenever I turn it on. I'm pretty much at a loss here, I don't know what could be tripping the security error at this point. Any advice would be greatly appreciated, thanks in advance.
SteelSpoon00 said:
Hello everybody! I just joined and am basically a complete noob at this, so thanks for the help in advance. I bought a Samsung Galaxy S10 about a year and a half ago off of Amazon to replace my S9. However, whenever I booted it up, it would give me this message; "Security Error: This phone has been flashed with unauthorized software and is locked". I didn't return it at the time like I should have and now I'm stuck with it. I've already tried flashing it with Odin and using the latest firmware that I got off Frija, and hard resetting as well, and still the same damn message pops up whenever I turn it on. I'm pretty much at a loss here, I don't know what could be tripping the security error at this point. Any advice would be greatly appreciated, thanks in advance.
Click to expand...
Click to collapse
When you flashed the firmware, did Odin give you any errors?
Also, what is the specific model number of the device?
Droidriven said:
When you flashed the firmware, did Odin give you any errors?
Also, what is the specific model number of the device?
Click to expand...
Click to collapse
The specific model is GM973U and Odin gave me the green PASS message upon completion
SteelSpoon00 said:
The specific model is GM973U and Odin gave me the green PASS message upon completion
Click to expand...
Click to collapse
That isn't normal by any means. Are you sure that USB debugging was enabled in settings and are you sure you did everything correct?
Droidriven said:
That isn't normal by any means. Are you sure that USB debugging was enabled in settings and are you sure you did everything correct?
Click to expand...
Click to collapse
I did turn on developer mode and allow USB debugging, though I didn't turn off the OEM option because I didn't see it, if that matters. I followed the instructions online to the letter and used Frija and Odin, I'm not sure at all what could have went wrong in the whole process. I was thinking of trying to use ADB to disable Knox or anything else that could be getting in the way, but I'm still not really sure how that works.
Try flashing an older rom, like the build that the phone came with.
Please i beg you, i have exactly the same problem, with a samsung sm-t380, after telling my boss i know how to flash a phone, now the phone has been with me for up to 3 months, still showing blue screen with (Security Error: This phone has been flashed with unauthorized software & locked)...
Please everybody or anybody help me solve this. I beg you, thanks.

Categories

Resources