So I tried to root my device using Kingo root first but after 73% it failed to root the device.
Then I tried to do it manually. First I tried to install TWRP but even it failed and some green notice appeared in recovery mode saying "Custom binary FRP lock on" or something like that (Cannot remember the exact phrase.)
Then again I searched and found out this bypassing apk and tried to off the FRP lock and it was successfully done and after that I booted the TWRP even that was successfully completed (as the odin said) :fingers-crossed:
But when I tried to boot to TWRP mode it gave some kind of error message and again I went in to the same old stock recovery mode. That means booting the TWRP wasn't successful as odin mentioned and then I noticed again "FRP lock ON".
What is the solution for this problem? I seriously need to root this device but I don't want to use pre rooted firm wares cause it will give base band problems and such things! Any solutions guys? :highfive:
Doesn't anyone have a proper solution for this?
chamathka_sooriyapala said:
So I tried to root my device using Kingo root first but after 73% it failed to root the device.
Then I tried to do it manually. First I tried to install TWRP but even it failed and some green notice appeared in recovery mode saying "Custom binary FRP lock on" or something like that (Cannot remember the exact phrase.)
Then again I searched and found out this bypassing apk and tried to off the FRP lock and it was successfully done and after that I booted the TWRP even that was successfully completed (as the odin said) :fingers-crossed:
But when I tried to boot to TWRP mode it gave some kind of error message and again I went in to the same old stock recovery mode. That means booting the TWRP wasn't successful as odin mentioned and then I noticed again "FRP lock ON".
What is the solution for this problem? I seriously need to root this device but I don't want to use pre rooted firm wares cause it will give base band problems and such things! Any solutions guys? :highfive:
Click to expand...
Click to collapse
What is your Galaxy Grand Prime model
tasnim_tamim said:
What is your Galaxy Grand Prime model
Click to expand...
Click to collapse
It is SM-G531F Model!
FRP lock off
Remove google and Samsung account
And lockscreen passcode
Then it turn off FRP
It works for me ??
Related
Hello, I had successfully rooted via PingPong method and then I attempted to flash custom recovery TWRP to it via TWRP Manager as mentioned on the TWRP page (I cannot link it as I am a new user)
after rebooting during the process, I am now greeted by a message at the boot screen that says "System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help." It will not go past this screen. I ensured that it was indeed, the correct recovery to flash according to the app. I can still enter Odin Mode, however.
I
hayateyoshida said:
Hello, I had successfully rooted via PingPong method and then I attempted to flash custom recovery TWRP to it via TWRP Manager as mentioned on the TWRP page (I cannot link it as I am a new user)
after rebooting during the process, I am now greeted by a message at the boot screen that says "System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help." It will not go past this screen. I ensured that it was indeed, the correct recovery to flash according to the app. I can still enter Odin Mode, however.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3105398
hayateyoshida said:
Hello, I had successfully rooted via PingPong method and then I attempted to flash custom recovery TWRP to it via TWRP Manager as mentioned on the TWRP page (I cannot link it as I am a new user)
after rebooting during the process, I am now greeted by a message at the boot screen that says "System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help." It will not go past this screen. I ensured that it was indeed, the correct recovery to flash according to the app. I can still enter Odin Mode, however.
Click to expand...
Click to collapse
Having root does not mean you can flash a custom recovery. You need an unlocked bootloader which still cannot be done.
I have the same issue. I can't load in to recovery, only downloading mode. I've tried Odin, Smart Switch, Kies 3 and no result
Please HELP.
Any chance you can share the info on the fix? I'm having the same issue on same phone and have tried the same troubleshooting.
Thanks
also need help
http://forum.xda-developers.com/att-...t3105398/page7
mihaisereden said:
Error ocurres when a wrong root is present, as far as I know, there is no root for this version available till now
Click to expand...
Click to collapse
Do you know the solution?
I need this file for S6
https://androidfilehost.com/?fid=95916177934554805
Can anyone create such file for S6?
http://forum.xda-developers.com/att...equest-create-g920a-debricking-image-t3449844
First off, sorry if this is the wrong section for this.
Basically, I tried rooting my phone (Galaxy S6 SM-G920T) using KingRoot, and it got to 20% and shut off. Now on boot I get "KERNAL IS NOT SEANDROID ENFORCING, CUSTOM BINARY BLOCKED BY FRP LOCK"
I'd appreciate if someone could let me know whether or not there is a fix for this.
Thanks.
Kingroot is not for the Tmobile variant. You need to download Odin onto your computer and flash TWRP and Unikernel (unikernel will root the phone).
I would suggest you restore your phone to factory status by downloading Samsung Kies software.
Once that completes then enable Developer options and turn on OEM and allow USB debugging.
Then once you've done that, use the Odin to root the device and install recovery.
https://www.youtube.com/watch?v=F7W-3yo89UI&feature=youtube_gdata_player
So after doing the new update to EPF1 from Samsung and updating thru Odin i was first able to flash twrp via odin and SuperSU beta via Twrp. I rebooted my after having minor issues with the new EPF1 rom being slow since i came the Boot logo with FRP lock on. Poored thru several forums and sources found several types of solution's such as KIES, Smart Switch, Odin (back2Stock), i have attempted all of these the Boot logo with frp lock on is now off i can now boot to the rom. BUT i cannot flash TWRP anymore because in download mode it shows FRP lock On anyone have sometype of resolution for this specific issue with Download only?
EDIT: after several attempts with smart switch it turned off FRP lock
hey can you please explain how you did it in details, i am in the same3 situation... please!!!!
britchel1 said:
hey can you please explain how you did it in details, i am in the same3 situation... please!!!!
Click to expand...
Click to collapse
While in Android, enable developer mode, and find the Enable OEM Unlock item. Turn it on; this disables the Factory Reset Protection and should let you flash a custom recovery in Odin.
So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
galaxynote2 said:
So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
Click to expand...
Click to collapse
What post shows you how to bypass? Please link it and I will help. I've never seen such a post despite countless searches and watching the boards.
But regardless, if you are getting the only official binaries screen, your haven't fully bypassed rmm. It sounds like whatever you did is letting you have custom recovery but not custom boot, as the dmv fix modifies there boot image, despite it not being needed on these devices. If what I'm saying is true, I can probably fix it, but I need this bypass guide to test
Hi! I've tried following dr.ketan's post on rooting a Note 9 with the first method ("(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only").
After that I've flashed RomAur via TWRP, booted up and while setting up my account the screen became black with the message "only official released binaries are allowed" . I've then tried to flash the stock firmware via Odin but on the screen of my phone I get a "SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1" error.
Odin seemed stuck so I unplugged my phone and then got a screen saying "An error has occured updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
My phone's a N960F/DS
After further research I've come to the conclusion that:
1) SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1 means the firmware I was trying to flash was too old and Samsung decided that downgrading isn't an option anymore.
2) I'm unable to flash anything else besides Samsung official firmware for a 7 or more days because of a Knox Guard (RMM/KG state prenormal). So reinstalling any custom recovery to then flash a new Rom can't be done since there's no way to bypass this time period on Pie.
I did end up flashing stock but I can't mod my phone until the kg state goes back to normal or checking
I've tried waiting for 168 hours twice since the last post. KG State won't change from prenormal. I should mention that my OEM unlock option is available but I can't flash anything besides Samsung binaries. Last week I've flashed TWRP despite the KG State not changing and I got the same "only official released binaries are allowed" error followed by a red fail box in ODIN. At this point I have no idea how to fix it. Does anyone have any suggestion?
I've downloaded the latest stock (N960FXXU4DSLB) and installed it. After that it looks like the prenormal state went away. Immediately I've toggled the OEM Unlock option, waited for the factory reset to be done and checked to see if the toggle was still there. The OEM unlock option works just like before BUT I've successfully installed geiti94's latest TWRP (3.2.3 ATM). Flashing RMM-State_Bypass_Mesa_v2.zip no-verity-opt-encrypt-6.0.zip and Magisk 20.2 seem to be able to get root working but there are some weird bugs:
- can't set up any security measure such as a pin, patter or biometrics
- if I try to log into my Samsung account I get a "processing failed" pop up
- restarting my phone causes it to bootloop