Database Users

[GUIDE] Fix WiFi not working properly after unlock

Hello XDA Team, I've had a problem with my Canadia Galaxy S4, i requested an unlock to a guy which unlocks phones with some Octopus or Z3X box, for some odd reason the program would not read the phone's codes to unlock so the unlock process failed, before leaving this guy clicked on some "repair NVM" button in the program, when in home i noticed the phone's wifi wont turn on properly, half-greened button & when it managed to turn on it would not save the passwords once i connect to some network, it's a very similar problem as this: http://forum.xda-developers.com/showthread.php?t=2661859 , i've flashed Stock Telus Firmware & other canadian carriers with no luck, except by CyanogenMod11 where it works perfectly, done full wipes for clean installs, i also tried to move the CM11 etc/wifi/ files to the Stock firmware which makes it to turn on a little faster, but still no luck saving the passwords, the phone was in 4.3 version then updated to 4.4.2, didn't worked neither.
I have searched all over google for a solution but couldn't find any
Is there any solution to this? or this guy really damaged the NVM thing he clicked? he had my phone for almost a month with no success repairing, any suggestions ? Any help would be greatly appreciated.
***********EDIT****FIXED****************
Hello everyone again, i managed to fix this problem by setting all permissions to all EFS folder files, This may fix your WiFi problems after an Box unlock procedure.
Hello, i took a couple of screenshots to be the most specific & easiest for you all.
First of all you need to be rooted.
1.- Install Root Explorer & open it up, it will show you this once you open it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.- Look for the EFS folder & go throught it, after that select all the files and folders inside.
3.- Press menu softkey & select the Permissions option.
4.- Select all of the permissions as shown in the image & click Ok.
After you done that, reinstall your Stock Firmware or simply reboot, & check if it's working properly again, I hope this helps.

How do you set all permissions to all EFS folder files?
Starnel said:
Hello XDA Team, I've had a problem with my Canadia Galaxy S4, i requested an unlock to a guy which unlocks phones with some Octopus or Z3X box, for some odd reason the program would not read the phone's codes to unlock so the unlock process failed, before leaving this guy clicked on some "repair NVM" button in the program, when in home i noticed the phone's wifi wont turn on properly, half-greened button & when it managed to turn on it would not save the passwords once i connect to some network, it's a very similar problem as this: http://forum.xda-developers.com/showthread.php?t=2661859 , i've flashed Stock Telus Firmware & other canadian carriers with no luck, except by CyanogenMod11 where it works perfectly, done full wipes for clean installs, i also tried to move the CM11 etc/wifi/ files to the Stock firmware which makes it to turn on a little faster, but still no luck saving the passwords, the phone was in 4.3 version then updated to 4.4.2, didn't worked neither.
I have searched all over google for a solution but couldn't find any
Is there any solution to this? or this guy really damaged the NVM thing he clicked? he had my phone for almost a month with no success repairing, any suggestions ? Any help would be greatly appreciated.
***********EDITED****FIXED****************
Hello everyone again, i managed to fix this problem by setting all permissions to all EFS folder files, This may fix your WiFi problems after an Box unlock procedure.
Click to expand...
Click to collapse

Kelvinfe said:
How do you set all permissions to all EFS folder files?
Click to expand...
Click to collapse
tanx
pls further explain !! you how to solve wifi problem ?
my device i337m 4.4.2 bell canadian

I'm having the same issue, how do you set permissions to the EFS Folder, do you have to be rooted and get root browsers pls help.
Sent from my XT1031 using XDA Free mobile app

/bump
Sent from my XT1031 using XDA Free mobile app

Yes, you do need to have Root browser, but i'd recommend you to use Root Explorer because you cannot set permissions to all files at once with root browser.

Thanks!!! It works, followed your steps and rebooted, auto connected to WiFi. Thanks a bunch. I recommend this tutorial if anyone is have WiFi issues with their GS4.
Sent from my XT1031 using XDA Free mobile app

Hiii....I am also having the same problem.My phone was unlocked by a guy and everything was working fine then.From next day the i could not turn on WiFi(It would go grayish for some time and then return to normal).I tried searching for it online and found the following soln
1)Reboot and check(Didn't work)
2)Factory Reset:After doing this it worked for that initial scanning but again was back to normal once wifi was switched off
3)Factory reset and installed root browser(my phone is rooted as i was able to install root explorer) and tried renaming the wpa-supplant config file
.This was worked for me for like 4 days.
After that again the problem is back and its even worse.It is immediately turning off as opposed to delay in previous case.When i tried to follow the same procedure the config files are not present.I could not on wifi even after factory reset even once
As i am a new around here detailed help would be appreciated;
My Device Features:
1)Andriod:4.4.2,SGH I337
2)Baseband:I337UCUFNC1
3)kernel Version:3.4.0-1125940
4)Build No:KOT49H.I337UCUFNC1

Starnel said:
Hello XDA Team, I've had a problem with my Canadia Galaxy S4, i requested an unlock to a guy which unlocks phones with some Octopus or Z3X box, for some odd reason the program would not read the phone's codes to unlock so the unlock process failed, before leaving this guy clicked on some "repair NVM" button in the program, when in home i noticed the phone's wifi wont turn on properly, half-greened button & when it managed to turn on it would not save the passwords once i connect to some network, it's a very similar problem as this: http://forum.xda-developers.com/showthread.php?t=2661859 , i've flashed Stock Telus Firmware & other canadian carriers with no luck, except by CyanogenMod11 where it works perfectly, done full wipes for clean installs, i also tried to move the CM11 etc/wifi/ files to the Stock firmware which makes it to turn on a little faster, but still no luck saving the passwords, the phone was in 4.3 version then updated to 4.4.2, didn't worked neither.
I have searched all over google for a solution but couldn't find any
Is there any solution to this? or this guy really damaged the NVM thing he clicked? he had my phone for almost a month with no success repairing, any suggestions ? Any help would be greatly appreciated.
***********EDITED****FIXED****************
Hello everyone again, i managed to fix this problem by setting all permissions to all EFS folder files, This may fix your WiFi problems after an Box unlock procedure.
Click to expand...
Click to collapse
What did you set the permisdions too? Or are you saying there were none? Thanks.
Sent from my SAMSUNG-SM-T217A using XDA Free mobile app

pckarma112 said:
What did you set the permisdions too? Or are you saying there were none? Thanks.
Sent from my SAMSUNG-SM-T217A using XDA Free mobile app
Click to expand...
Click to collapse
Can you pls explain me how to do this fix

rammohan518 said:
Can you pls explain me how to do this fix
Click to expand...
Click to collapse
I edited first post with the instructions of what i made to fix it.

pckarma112 said:
What did you set the permisdions too? Or are you saying there were none? Thanks.
Sent from my SAMSUNG-SM-T217A using XDA Free mobile app
Click to expand...
Click to collapse
check out the updated first post, see if it can help you out.

Starnel said:
I edited first post with the instructions of what i made to fix it.
Click to expand...
Click to collapse
Not Working..I have tried your procedure and rebooted.still not working

rammohan518 said:
Not Working..I have tried your procedure and rebooted.still not working
Click to expand...
Click to collapse
Okay then follow this guide: http://forum.xda-developers.com/showthread.php?t=2663545 an user with this problem fixed his WiFi with that guide, i believe you're using AT&T Galaxy S4. king regards.

Thanks it works
Thanks for the great idea for modifying the permission.
It works on my SGH I337 NI1 Unlocked & of course Rooted.
I uses ES Explorer with Root Explorer enabled.
Using this explorer, I have to modify the file one by one, but it is fine.
One problem that is still unsolved for my S4 is: it keeps forgetting the wifi networks after it is restarted.
Perhaps any other file(s)'s permissions need to be modified?

Thank you so much. This problem has been driving me nuts. I just fixed the permissions and WiFi is now working the way it is supposed to.

Yaaaayyy THANXXX it worksss

Thanks!
Wow, it worked. Now I wonder why... Surely it's not a great idea to give global permissions to every file in this folder, and also surely there is just one or two files that need changing.. perhaps just the wifi folder?
Anyway, thanks a lot! And if anyone knows why this works, I'd love o know.
Oh, I'm on an AT&T S4.

mschreck said:
Wow, it worked. Now I wonder why... Surely it's not a great idea to give global permissions to every file in this folder, and also surely there is just one or two files that need changing.. perhaps just the wifi folder?
Anyway, thanks a lot! And if anyone knows why this works, I'd love o know.
Oh, I'm on an AT&T S4.
Click to expand...
Click to collapse
I believe it corrupted the efs folder while in the unlocking process.
Sent from my Galaxy S4.

So I have AT&T SGH-I337 with NJ4 build and baseband. I recently rooted and installed Safestrap recovery and everything was fine, but then messed up when flashing a rom and softbricked my device. When i restored it by flashing an NB1 stock build, wifi was fine, and then i went and installed safestrap again and restored from nandroid. I then noticed that my wifi wasn't on. From then on, the wifi will NOT turn on, no matter what I try. I tried factory resetting, flashing the right modems, etc etc, and i just can't fix it. Any help?

Please help me with my S7 Edge SM-G935F

Hello everyone,
My brother has just offered me a s7 edge SM-G935F / 32G, Rom stock without operator that he used for 2 months after purchase.
My pb is that after resertting this phone, then reboot, I am asked the google account with which this phone was syncing (it's of my bro). Normal!
Then I enter the data account google of my brother and then Passwords ... and there, a verification code sent him that communicates me by sms after receiving.
But helas, every time I get it, the phenomenon is repeated and so I can not use the phone for use!
My idea was to flash the last ROM Stock...but no way, the pb is always the same...the warning message !
For info, the dl and recovery mode are operational but I am without root so without TWRP and other ++++
However, the dev mode of the system is not activated too ...
Thank you for your help...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
B
sorry for my bad english !:silly:

Bishopandme said:
Hello everyone,
My brother has just offered me a s7 edge SM-G935F / 32G, Rom stock without operator that he used for 2 months after purchase.
My pb is that after resertting this phone, then reboot, I am asked the google account with which this phone was syncing (it's of my bro). Normal!
Then I enter the data account google of my brother and then Passwords ... and there, a verification code sent him that communicates me by sms after receiving.
But helas, every time I get it, the phenomenon is repeated and so I can not use the phone for use!
My idea was to flash the last ROM Stock...but no way, the pb is always the same...the warning message !
For info, the dl and recovery mode are operational but I am without root so without TWRP and other ++++
However, the dev mode of the system is not activated too ...
Thank you for your help...
B
sorry for my bad english !:silly:
Click to expand...
Click to collapse
You are facing FRP issue which is factory reset protection security feature by google..So everytime you will reset your device, you will be askd for the same google account which was previously added to device..Are you on marshmallow or nougat? IF your phone is functioning well then enable developers option by pressing build no for 7-8 times from software info you will find in about device from settings..After enabling developers option enable Oem unlocking..Hope this will help you..You can also flash latest stock firmware for your device usinh odin after enabling Oem unlocking from developers option

@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B

Bishopandme said:
@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B
Click to expand...
Click to collapse
Just download latest 7.0 stock firmware for your device from sammobile.com though your already on nougat..firmwares there are updated according to security patches timely..so my suggestion is download latest nougat firmware for your model and country and flash usinh odin as described above..You will boot normally...If after flashing latest nougat if your device stuck at Samsung logo i.e. called bootloop..Press volume up+power +home button, you will boot into stock recovery..from there choose wipe data/factory reset option..you will boot up normally..
---------- Post added at 02:48 PM ---------- Previous post was at 02:40 PM ----------
Bishopandme said:
@DroidHackeR,
I'm in nougat because i have flash the latest Rom Stock yet with odin (4 files) + factory restet!
But the pb is the same...because i can't enable Oem unlocking from developers option by pressing build no for 7-8 times from software info
I have no access to do that, My procedure stops until the moment to put the login of gmail ... I do not go beyond that after the flash !
Another idea pl?
How can i enable Oem option directly by odin for example?
I can't flash custom rom because of it too...
Ths for your help.
B
Click to expand...
Click to collapse
You can also refer this video by root junky which will give you option to overcome frp
https://m.youtube.com/watch?v=JzywoFS_r9U&time_continue=2

Ah ok...just after the reboot i doesn't let the phone start and must to reboot in recovery mode for doing the wipes and reset option.
ok i will do it as soon as...
wait for a moment pl!
B

@DroidHackeR,
i have just test your first idea and...it dosen't work !
I will test the video way ...it's seem no easy to me!
Ths for your help.
B

Bishopandme said:
@DroidHackeR,
i have just test your first idea and...it dosen't work !
I will test the video way ...it's seem no easy to me!
Ths for your help.
B
Click to expand...
Click to collapse
Go ti video reference and follow the steps carefully hope it will help you..Or another tricks are there to overcomd FRP issue i.e. using adb commands and otg cable..You can search on google.

DroidHackeR said:
Go ti video reference and follow the steps carefully hope it will help you..Or another tricks are there to overcomd FRP issue i.e. using adb commands and otg cable..You can search on google.
Click to expand...
Click to collapse
when i read the differents backs experiences...there's apparently a pb with the camera step way!
They said "On Samsung Galaxy s6 Edge plus there is no camera when you restart the phone. What's the Problem?"
and others phones too....
:crying:

i find this....for S7 Edge
https://www.youtube.com/watch?v=ChC...id=video:3e542a13-8bf9-4684-b336-004044a96320
tic tac

Bishopandme said:
i find this....for S7 Edge
&feature=iv&src_vid=JzywoFS_r9U&annotation_id=video%3A3e542a13-8bf9-4684-b336-004044a96320
tic tac
Click to expand...
Click to collapse
Yes refer this video to overcome FRP...Watch the video carefully and follow the steps described

Hi @DroidHackeR,
I realize that this video is no longer current because dating several months ... besides, nothing makes clear if this manupulations was made under Nougat or old versions ...
Recent updates may have blocked it, hence the large number of errors identified ...
what do you think?
Thank you !
B

Bishopandme said:
Hi @DroidHackeR,
I realize that this video is no longer current because dating several months ... besides, nothing makes clear if this manupulations was made under Nougat or old versions ...
Recent updates may have blocked it, hence the large number of errors identified ...
what do you think?
Thank you !
B
Click to expand...
Click to collapse
Will you please checkout the video i am going to provide link below? It claims about bypass of google FRP protection on devices running Nougat..i.e.s7edge is also included..Please watch this video carefully and report if it helped you or not
http://pangu.in/nougat-remove-google-verify-account-samsung-frp/

@DroidHackeR, OUrahhhh!!!!
Successfully with this method, look here: ....https://www.youtube.com/watch?v=8g4MG0ZRF1M&t=67s
Ths for all !
Enjoy !
B

Bishopandme said:
@DroidHackeR, OUrahhhh!!!!
Successfully with this method, look here: ....
&t=67s
Ths for all !
Enjoy !
B
Click to expand...
Click to collapse
Ohhhk dear @Bishopandme i am very glad to see your phone is saved and all of our quotes and comments are reserved in this thread to help any other suffering from same issue..Cheers..

Samsung TAB A SM-P580 FRP Bypass

Can anyone help me with this issue?
I have factory reset this device and reflashed with JOdin3. The device has been rooted in the past. I got into this mess by turning on FRP accidently after rooting. When I turn on device I am taken to language settings, then wifi settings, then to terms and conditions, after I am faced with Google verification.
I do get a notice on start-up... Notice states:
"An unauthorized attempt has been made to reset your device to factory default settings. Connect to a Wi-Fi or mobile network to verify identity."
Any ideas on how to bypass FRP?

firstly you have to download Bypass Samsung Google account verification app apk.
1. then, Copy the apk file to your USB.
2. Using the OTG cable connect your USB to phone.
3. Once connected, it will popup the file manager app and install the apk app.
4. You should now have access to phone settings.
5 .Scroll down and find Backup and reset.
6. Tap Factory data reset and Reset device or Erase everything which will erase the following from your device:
Google Account
System and app data
Device settings
Downloaded apps
Music, Pictures and all other user data.
7 .Finally your phone will reboot normally and may take some time while booting and that is normal after resetting your device.
This information may be helpful for you.

rohnallen said:
firstly you have to download Bypass Samsung Google account verification app apk.
1. then, Copy the apk file to your USB.
2. Using the OTG cable connect your USB to phone.
3. Once connected, it will popup the file manager app and install the apk app.
4. You should now have access to phone settings.
5 .Scroll down and find Backup and reset.
6. Tap Factory data reset and Reset device or Erase everything which will erase the following from your device:
Google Account
System and app data
Device settings
Downloaded apps
Music, Pictures and all other user data.
7 .Finally your phone will reboot normally and may take some time while booting and that is normal after resetting your device.
This information may be helpful for you.
Click to expand...
Click to collapse
Thank you for replying. Will this method work with the Wifi Tab A SM-P580? This device is not a phone.
I have factory reset this device and reflashed with JOdin3. The device has been rooted in the past. I got into this mess by turning on FRP accidently after rooting. :crying:When I turn on device I am taken to language settings, then wifi settings, then to terms and conditions, after I am faced with Google verification.
I do get a notice on start-up... Notice states:
"An unauthorized attempt has been made to reset your device to factory default settings. Connect to a Wi-Fi or mobile network to verify identity."
Help...

rohnallen said:
firstly you have to download Bypass Samsung Google account verification app apk.
1. then, Copy the apk file to your USB.
2. Using the OTG cable connect your USB to phone.
3. Once connected, it will popup the file manager app and install the apk app.
4. You should now have access to phone settings.
5 .Scroll down and find Backup and reset.
6. Tap Factory data reset and Reset device or Erase everything which will erase the following from your device:
Google Account
System and app data
Device settings
Downloaded apps
Music, Pictures and all other user data.
7 .Finally your phone will reboot normally and may take some time while booting and that is normal after resetting your device.
This information may be helpful for you.
Click to expand...
Click to collapse
Do you have a link to the apk bypass file for this device?

Any method to bypass RFP? im on 6.01 from 17 Jan 2017 with security patch 2017-01-01

xhitm3n said:
Any method to bypass RFP? im on 6.01 from 17 Jan 2017 with security patch 2017-01-01
Click to expand...
Click to collapse
Try to downgrade firmware, mine is PH6 , downgrade to Hong Kong firmware which has lower build.
Then you can bypass FRP easily, it can be done within 3 minutes

If you go to YouTube and do a search for "bypass google account samsung tab a" about 15 video's pop up walking you through it.
Just wade through the results as they are mixed in with the phones also.
Dont feel like typing ??
Click ME I will take you there.
..
..
<end>

Thibor69 said:
If you go to YouTube and do a search for "bypass google account samsung tab a" about 15 video's pop up walking you through it.
Just wade through the results as they are mixed in with the phones also.
Click to expand...
Click to collapse
Google watched and blocked these methods already.
Try to activate FRP in your tablet by hard reset and see which one you can bypass
You should be specific as most are not working with current build.

Beut said:
Google watched and blocked these methods already.
Try to activate FRP in your tablet by hard reset and see which one you can bypass
You should be specific as most are not working with current build.
Click to expand...
Click to collapse
New method worked! Search youtube for "Samsung Galaxy Tab A T580 FRP with Wifi Only". Just did it on my SM-T580 Wifi only with firmware 6.0.1 MMB29K.T580UEU2APL4.

ImRickJames said:
New method worked! Search youtube for "Samsung Galaxy Tab A T580 FRP with Wifi Only". Just did it on my SM-T580 Wifi only with firmware 6.0.1 MMB29K.T580UEU2APL4.
Click to expand...
Click to collapse
Thanks for being specific and confirmation. I did it today and success with the latest build PL4 which I failed to downgrade.

ImRickJames said:
New method worked! Search youtube for "Samsung Galaxy Tab A T580 FRP with Wifi Only". Just did it on my SM-T580 Wifi only with firmware 6.0.1 MMB29K.T580UEU2APL4.
Click to expand...
Click to collapse
This method works with build PL4, but not with the older build PG1 or Android 7, QE7 from Germany.
Build PG1 I have to downgrade firmware to bypass FRP. Tested with SM-T280 and SM-T560, this method doesn't work either because there is no Assist to open a browser. This build PG1, it has to be downgraded or upgraded to work with a certain method, I prefer upgrade as I don't have to do the update later.
Depending on your build, not every method will work. The statement you read everywhere : " work with all models " is not true from my experiments with FRP bypass.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Failing installing TWRP with Only Official Released Binaries Allowed

Hey.
I unlocked the bootloader (unlock oem under developer options, and with vol up + down when plugging the usb cable in + vol up for 5sec)
When I try to flash the according TWRP tar I get an error on my tab5se, it says "Only official released binaries are allowed to be flashed(recovery)
And Odin says "Fail! (Auth)"
I got no clue where to go from here.
I want to install Lineage 17.1 onto the Tab5se.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lvlanson said:
When I try to flash the according TWRP tar I get an error on my tab5se, it says "Only official released binaries are allowed to be flashed(recovery)
Click to expand...
Click to collapse
LuK1337's Instructions need to be followed exactly, dont add anything, dont skip anything (Dont wipe anything unless listed). Did you flash the VBMeta image?

OhioYJ said:
LuK1337's Instructions need to be followed exactly, dont add anything, dont skip anything (Dont wipe anything unless listed). Did you flash the VBMeta image?
Click to expand...
Click to collapse
I was following faulty instructions. I came across this post a little later and added the VBMeta after I managed to install TWRP. Weirdly I did work and I could manage to install Lineage OS17.1 by now.
Thanks for your assistance

lvlanson said:
I was following faulty instructions. I came across this post a little later and added the VBMeta after I managed to install TWRP. Weirdly I did work and I could manage to install Lineage OS17.1 by now.
Thanks for your assistance
Click to expand...
Click to collapse
When that happens it means you skipped a step, usually this means you didnt flash something and boot system to verify OEM unlocking is still on, or atleast thats my experience.

I'm having the same message, but in an early stage. I can't even flash vbmeta.tar. Any idea how to solve this?

svierkant said:
I'm having the same message, but in an early stage. I can't even flash vbmeta.tar. Any idea how to solve this?
Click to expand...
Click to collapse
have you found a solution?

kaho_tam said:
have you found a solution?
Click to expand...
Click to collapse
i need some help , i currently have an s8 everytime i try to flash twrp i get an error saying "only official binaries are allowed to be flashed (recovery) .i downloaded a new stock firmware an flashed it an everything went fine ,but when i went to flash twrp i got the same error (please help)

romell0018 said:
i need some help , i currently have an s8 everytime i try to flash twrp i get an error saying "only official binaries are allowed to be flashed (recovery) .i downloaded a new stock firmware an flashed it an everything went fine ,but when i went to flash twrp i got the same error (please help)
Click to expand...
Click to collapse
i got same problem. my usb debug is on and oem unlock is on. already flashed the stock firmware and when i try to install twrp in odin i got error of only official binary allowed. please help

Same
ling12fanny said:
i got same problem. my usb debug is on and oem unlock is on. already flashed the stock firmware and when i try to install twrp in odin i got error of only official binary allowed. please help
Click to expand...
Click to collapse
Same problem for me as well, S9+ G956F/DS

oh man, I'm having the exact same issue and all I could find (none of which has worked) is to somehow get rid of the triggered Knox security (boo, Samsung). I'll update you all if I manage to get something working but... I think it's a lost cause so far

Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc).
Thank you XDA.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
I got super excited and immediately wanted to test it out but I still get FAIL in Odin when I try to flash TWRP and "Only official released binaries are allowed to be flashed (RECOVERY)" at the bot left in Download mode under all the text. Weirdly enough though, every time I change the date and restart the phone, it goes back to 28 June 2021 (this may be when I tried installing the stock firmware again but it didn't work either... why can't I just connect to the Samsung servers and automatically get the correct version for my phone, which also doesn't have stuff like jackpotlte in the description... I know I can get the correct firmware from sammobile but I feel like it should be more REAL )

nasko7 said:
I got super excited and immediately wanted to test it out but I still get FAIL in Odin when I try to flash TWRP and "Only official released binaries are allowed to be flashed (RECOVERY)" at the bot left in Download mode under all the text. Weirdly enough though, every time I change the date and restart the phone, it goes back to 28 June 2021 (this may be when I tried installing the stock firmware again but it didn't work either... why can't I just connect to the Samsung servers and automatically get the correct version for my phone, which also doesn't have stuff like jackpotlte in the description... I know I can get the correct firmware from sammobile but I feel like it should be more REAL )
Click to expand...
Click to collapse
Was the wifi turned on when you changed the date? Please Turn the wi-fi on, and then repeat the same requirements I mentioned above. When you're in Downloading mode install TWRP and IA it will be done.
It will definately work out, It was showing me the exact same issue but then I changed the date, powered off, booted it into download mode and installed the TWRP and even setted up the ROM (Noble ROM 1.5 By AlexisXDA). Also once you change the date to 2 August 2019, and you confirm it's changed. Then you have to turn the phone off and boot it into download mode (dont restart) but download TWRP via Odin and boot into the RECOVERY MODE directly.
Also if OEM unlock option is not being displayed in DEV options, changing the date to 2 August 2019 will show automatically unhide the option. The point when TWRP will be installed successfully, still don't let in boot to the system, go to the Recovery mode) i.e new TWRP.
Try to repeat the methods with the WI-FI on and let me know here again.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
2 August 2019 doesn't always work. To find out what date you should change to, go to
"About Phone" and search for Android Security Patch Level, at the very bottom of the list.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
Can't believe this actually worked.. thank you.

I was working with my tablet SM-T295 after I noticed that start lag after android 11 update, so.. I tried to downgrade it from 11 to 9, and that using TWRP, after backup data, I flashed it, and Odin exe said that the operation successfully done, but my tablet didn't did because it saying SECURTY FAIL : RECOVERY.img , so I tried booting it, and it surprisingly booted up! But I let it turned on until I goes to eat first, and I'm back... I founded that she turned off herself, I tried booting it up but it saying this...(jpeg)
Really need help, this is my main device.

El Khalil Bouzelmate said:
I was working with my tablet SM-T295 after I noticed that start lag after android 11 update, so.. I tried to downgrade it from 11 to 9, and that using TWRP, after backup data, I flashed it, and Odin exe said that the operation successfully done, but my tablet didn't did because it saying SECURTY FAIL : RECOVERY.img , so I tried booting it, and it surprisingly booted up! But I let it turned on until I goes to eat first, and I'm back... I founded that she turned off herself, I tried booting it up but it saying this...(jpeg)
Really need help, this is my main device.
View attachment 5558213
Click to expand...
Click to collapse
Have seen such messages in the past but don't remember the exact sequence of steps.
Always try flashing the vbmeta file from Odin whenever you get an official error. If error still persists, then flash TWRP once and then the stock recovery.

i'm stuck while installing vbmeta with odin :
<ID:0/003> vbmeta.img

Usually you can't flash your device with custom os using Odin directly, you need at least a recovery mode like TWRP, the first thing you need is TWRP recovery for your device model, then install it in your device using Odin toolkit, after that you gonna remove the nand from your device by deleting system data using TWRP, but be sure you already had the Firmware galaxy tab S5e in your PC in case you want to use your tablet again, after deleting sys data, cache...get an SD card (at least 4gb) and put the custom os in the SD card, then put it in your tablet, and select install option in TWRP, select the custom os, and start installing the os.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc).
Thank you XDA.
Click to expand...
Click to collapse
i want to kiss you all over your face, its 6:36 in the morning, i've been trying to fix this problem for the past 6 hours

[Solved] SM-G950F - My device is not certified - Factory defaults ROM

Hello all,
I'm having the Samsung Galaxy S8 (SM-G950F) the device with the Exynos CPU.
Everything worked fine with Android 9.0 and the One UI 1.0 until I decided to install TWRP and a custom ROM using Odin software.
Lots of things with a custom ROM isn't working correct.
Such as the NFC, apps for e-banking, Netflix etc. I didn't root my device.
So, I need to go back to factory defaults.
I downloaded the proper firmware from sammobile and installed it using Odin.
I extracted the zip file and followed the instructions from sammobile's site.
1. Extract the 5 firmware files (i.e. to folder c:\Odin)
2. Open Odin
3. Power off your phone
4. Reboot Phone in Download Mode
Connect USB-cable to your computer. Hold down Volume up and Volume down at same time. While holding down, connect the USB-cable to your phone
5. Wait until you get a blue sign in Odin
Add the firmware files to their designated slots (AP in AP, BL in BL, CP in CP, HOME_CSC in CSC). Do not tick any extra boxes. The only options to be ticked are F. Reset Time and Auto-Reboot.
Click the start button to begin flashing the firmware update
6. Click the start button to begin flashing the firmware update
Click to expand...
Click to collapse
My phone is working, but now I'm having an issue with my Google account.
My device is not certified.​
I found instructions online to fix it but none is working.
What I'm missing here?
The method i used is the proper one or not?
Thank you in advance.

Read this... probably a Samsung Experience center at Best Buy be able to sort it out.
On my Samsung's I never touch the firmware unless there's corruption (not happened so far). Don't even update/upgrade it. Zero issues.

Thank you @blackhawk for your instant reply.
I have done this a few days ago.
The uncertified message is displayed in Google Play settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have used the Device ID app in the device registration website by Google.
When I'm trying to paste my Google Services Framework Device ID the box is turned into red as the screenshot below and a pop up message appears with Value already registered.
The list contains two entries. I don't know what these are regarding.
I'm also having an Android TV box with the same Google account.
Gmail, Google Photos, Google Drive and other Google stuff is working, but Google Pay & Netflix is not working.
I tried also clear the cache and data from Play Store app.
Is there anything else i can do?

You're welcome.
Gookill is a mess. If it's generating any error code messages look them up.
Try deleting the Google account on the phone, reboot and set it up again... I hope this works.

I have done this too.
I removed the Google account, I forced stop the Play Store. I cleared the cache and data. I rebooted my phone and I signed to Google. The message had gone in Store's settings. I tried to access the Google Wallet (Pay) or Netflix with no luck!
The message appeared again!

fatammag said:
I have done this too.
I removed the Google account, I forced stop the Play Store. I cleared the cache and data. I rebooted my phone and I signed to Google. The message had gone in Store's settings. I tried to access the Google Wallet (Pay) or Netflix with no luck!
The message appeared again!
Click to expand...
Click to collapse
Try again but clear Playstore data too. The cause maybe be in other Google apps data.
Don't know...

Thank again @blackhawk
As I said before, I deleted data and cache.
I don't know..
anyone else knows another way of fixing that issue?

fatammag said:
Hello all,
I'm having the Samsung Galaxy S8 (SM-G950F) the device with the Exynos CPU.
Everything worked fine with Android 9.0 and the One UI 1.0 until I decided to install TWRP and a custom ROM using Odin software.
Lots of things with a custom ROM isn't working correct.
Such as the NFC, apps for e-banking, Netflix etc. I didn't root my device.
So, I need to go back to factory defaults.
I downloaded the proper firmware from sammobile and installed it using Odin.
I extracted the zip file and followed the instructions from sammobile's site.
My phone is working, but now I'm having an issue with my Google account.
My device is not certified.​
I found instructions online to fix it but none is working.
What I'm missing here?
The method i used is the proper one or not?
Thank you in advance.
Click to expand...
Click to collapse
Hi bro,
Go to setting and turn on developer option by pressing 4to5 times of build number and go back to developer option and turn off OEM Unlock thats it simple.. now better reset/restart your mobile then go and check play store play protection its show device is certified.

fatammag said:
Thank again @blackhawk
As I said before, I deleted data and cache.
I don't know..
anyone else knows another way of fixing that issue?
Click to expand...
Click to collapse
Is your bootloader unlocked? If you're trying to return to bone stock, you'll need to relock the bootloader to pass hardware attestation.
Or...
Root with Magisk and install the Universal SafetyNet Fix module.

V0latyle said:
Is your bootloader unlocked? If you're trying to return to bone stock, you'll need to relock the bootloader to pass hardware attestation.
Or...
Root with Magisk and install the Universal SafetyNet Fix module.
Click to expand...
Click to collapse
Thank you for your reply! @anbalaganaero solution fixed my problem.
anbalaganaero said:
Hi bro,
Go to setting and turn on developer option by pressing 4to5 times of build number and go back to developer option and turn off OEM Unlock thats it simple.. now better reset/restart your mobile then go and check play store play protection its show device is certified.
Click to expand...
Click to collapse
A big thank you! It works!

fatammag said:
Thank you for your reply! @anbalaganaero solution fixed my problem.
A big thank you! It works!
Click to expand...
Click to collapse
Welcome