Database Users

Huawei Mate 8 FRP ( Google Account) Locked!

Hello guys,
Just got this Mate 8 NXT-L29 which locked by the Google Account security,
{
"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"
}
-Bootloader is locked
Can someone help in this ?
Thanks in advance

If that is the first and only screen that is displayed after turning the phone on, then the phone might have been protected by the previous owner using the Android Device Manager app, and therefore it can be unlocked only accessing the original Google account.

themissionimpossible said:
If that is the first and only screen that is displayed after turning the phone on, then the phone might have been protected by the previous owner using the Android Device Manager app, and therefore it can be unlocked only accessing the original Google account.
Click to expand...
Click to collapse
It's not locked by Android Device Manager App, This is FRP Lock (Factory Reset Protection),
And yes, it asks for the previous owner's account, but there is a way to get around that and bypass the lock,
And since i couldn't find any guide for how to do that for this model, I'm asking here.
BTW: I have DC-Unlocker and it can remove the lock in 1 min, but i need to know how exactly it works.

mirosaw2 said:
It's not locked by Android Device Manager App, This is FRP Lock (Factory Reset Protection),
And yes, it asks for the previous owner's account, but there is a way to get around that and bypass the lock,
And since i couldn't find any guide for how to do that for this model, I'm asking here.
BTW: I have DC-Unlocker and it can remove the lock in 1 min, but i need to know how exactly it works.
Click to expand...
Click to collapse
same problem how can i fix this

kawadarsim said:
same problem how can i fix this
Click to expand...
Click to collapse
Actually, i did it with DC-Unlocker via Fastboot mode, i can do it remotely for you, but i can't do it for free cuz it costs me 4 dc credits, like 10 bucks,
But you can hold on for a while, for sure someone will find a way to bypass it.
Sent from my mshibo-s6e using Tapatalk

Factory reset via recovery also solves this problem.
Like off the phone.
Press vol-up+power and.This.boots.into recovery.
Do factory reset and then reboot. Works.just fine

mirosaw2 said:
Hello guys,
Just got this Mate 8 NXT-L29 which locked by the Google Account security,
-Bootloader is locked
Can someone help in this ?
Thanks in advance
Click to expand...
Click to collapse
Irrelevant with the post but i think you put your tempered glass the wrong way!

bluheart said:
Factory reset via recovery also solves this problem.
Like off the phone.
Press vol-up+power and.This.boots.into recovery.
Do factory reset and then reboot. Works.just fine
Click to expand...
Click to collapse
How come you don't know about FRP man !!!
Please, read this
http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
Sent from my mshibo-s6e using Tapatalk

icy20 said:
Irrelevant with the post but i think you put your tempered glass the wrong way!
Click to expand...
Click to collapse
I think it's a Mate 7 protector, with the gap in the protector for the sensors on the left side... :good:

I know, but we reset on Sammy phone and it worked
Any way, could you by pass the screen?

same problem how can i fix this
same problem how can i fix this

same problem how can i fix this , have any bypass solution?

I see solution here as done by one of my friend who owns a mobile shop.
Unlock boot - Flash TWRP - wipe-format data- Flash decrypted boot and then flash International Rom and do set-up.

Try this...

Hey guys!
Maybe this ...
https://www.dc-unlocker.com/huawei-android-phone-frp-unlock

if some one need such service let me know i can do

here is working method

I got stuck with a FRP and nougat without keyboard... was what the method that works?? the video link is death

I don't have the problem but found this by accident http://www.androidmobiletools.com/2016/11/huawei-frp-lock-remove-bypass-tool-free.html
Maybe it helps?

rophiroth said:
I got stuck with a FRP and nougat without keyboard... was what the method that works?? the video link is death
Click to expand...
Click to collapse
I face the same and below worked for me.
1. reset the password of my google account (I have change to something which can be applied with Google voice input since i don't have keyboard)
2. After reset the password we can try it again on the phone after 72 hours (72 hours restriction is there by Google)
3. Enjoyed without smartphone for 3 days.
4. On 4th day I have retried with new password (through google voice).
5. Worked fine for me.
6. After I was successfully in then installed google keyboard through voice commands
Right now Bluetooth is not working and looking for a solution.
Regards
Naeem Akhtar

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..

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

Update not listed in software - "n910cxxu2dvh2"

Recently I reinstalled the system and I did not have time to install SU and an update popped out. Unfortunately, I can't download this version anywhere, either there is a problem or this version does not exist. Can anyone help me with this? The phone is SM-N910C / XEO.
Log from SAMFIRM:
SamFirm v0.5.0
Checking firmware for SM-N910C/XEO/N910CXXU2DVH2/N910COXA2DVH2/N910CXXU2DVH2/N910CXXU2DVH2
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Checking firmware for SM-N910C/XEO/N910CXXS2DRI2/N910COXA2DQK1/N910CXXU1DQG1/N910CXXS2DRI2
Model: SM-N910C
Version: N910CXXS2DRI2/N910COXA2DQK1/N910CXXU1DQG1/N910CXXS2DRI2
OS: Marshmallow(Android 6.0.1)
Filename: SM-N910C_1_20181115200627_9ug633aafa.zip.enc4
Size: 2228227696 bytes
LogicValue: iekgyc5u90o1sh58
Click to expand...
Click to collapse
Photos of the version from the phone:
{
"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"
}
How can you download 1 and 4 files soft for this?

@Tomasz Dulak did you try with old samfirm version?
That doesn't work any longer as Samsung changed its server addresses afaik.
Try SamFirm_Reborn_0.3.6.3.

Still the same :/

Tomasz Dulak said:
Still the same :/
Click to expand...
Click to collapse
May work when you switch to manual and fill the fields below with entries needed.
Had that on a VZW phone as well.
But afaik that will only work if it's the latest stock and for me it seems there's a later one:
XEO-N910CXXS2DRI2-20181204144801.

I also fail to enter manually.
Well, mine isn't there at all, and it's dated August 12, 2022, looking at the kernel version after the update. It's just that someone posted an update after 4 years.
The last one available for today is: "N910CXXS2DRI2", but when you install it, you get the update to "N910CXXS2DVH2".

@Tomasz Dulak How's the progress? Did you flash it with DRI2, or stays with DVH2?

I haven't installed N910CXXU2DVH2 patch yet.
I'm trying to add a Samsung account and receive an error like:
Code:
403
Sorry, the resource you want to access is forbidden, so this request has been refused. If you have any questions, please contact the administrator.
*
WIPV2nullnull_XXXXXXXXXXXXXX_99999-YYYYYYYYYYY.999.
I can easily log in via a web browser.
Can anyone log into Samsung account without this fix?

@ze7zez
I have N910H here and flashed system.img, boot.img, and csc_sec.zip from XEO DRI2 N910C firmware. There's no problem in adding Samsung account.
The problem that I'm facing is that, I couldn't get the DVH2 OTA update, since it will throws me the message of "The operating system on your device has been modified in an unauthorized way..."
It may be fixed if I also flash the bootloader from N910C or might also tweak it, but that's such a painful thing to recover if it went brick, I don't want to risk it yet.

UnknownPlanet said:
@ze7zez
I have N910H here and flashed system.img, boot.img, and csc_sec.zip from XEO DRI2 N910C firmware. There's no problem in adding Samsung account.
The problem that I'm facing is that, I couldn't get the DVH2 OTA update, since it will throws me the message of "The operating system on your device has been modified in an unauthorized way..."
It may be fixed if I also flash the bootloader from N910C or might also tweak it, but that's such a painful thing to recover if it went brick, I don't want to risk it yet.
Click to expand...
Click to collapse
Thanks for the information.
I will insert the SIM card and check again.
I wouldn't risk flashing the bootloader from the N910C to the N910H. Are you sure the system will boot?

@ze7zez
No I'm not sure, I've done a hex compare and they are different. There are 90 out of 1,034,240 bytes of param.bin and 9487 out of 1,632,800 bytes of sboot.bin that is different from N910H bootloader.
That would be tedious trying to decode what makes it differs and thus tweak it..
In the end, I'm stuck with DRI2 firmware. I'd like to try DVH2, but there's no software available that I know at the moment that is able to download it.
Just ask help here again if you need help on your Samsung account.

ze7zez said:
I haven't installed N910CXXU2DVH2 patch yet.
I'm trying to add a Samsung account and receive an error like:
Code:
403
Sorry, the resource you want to access is forbidden, so this request has been refused. If you have any questions, please contact the administrator.
*
WIPV2nullnull_XXXXXXXXXXXXXX_99999-YYYYYYYYYYY.999.
I can easily log in via a web browser.
Can anyone log into Samsung account without this fix?
Click to expand...
Click to collapse
Got that issue on a S8 and 2 S7 Edges. had to send them back

dave678 said:
Got that issue on a S8 and 2 S7 Edges. had to send them back
Click to expand...
Click to collapse
I solved the problem and described in the thread.
dave678 said:
Got that issue on a S8 and 2 S7 Edges. had to send them back
Click to expand...
Click to collapse
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com

ze7zez said:
I solved the problem and described in the thread.
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com
Click to expand...
Click to collapse
Too bad your post came way too late as I already returned the devices mentioned. Those devices were running Android 7.0.

ze7zez said:
I solved the problem and described in the thread.
I solved the problem and described in the thread.
[STOCK ROM][NO ROOT][Android 4] Correct login to Google account after phone reset
There are devices with android 4 in which after a reset to factory settings or very long ago not updated, there is no way to log in to a Google or Samsung account. Here is a proven repair method. Before you proceed with the repair, you need to...
forum.xda-developers.com
Click to expand...
Click to collapse
I had this same issue on a Tab S I bought off Ebay and it was luckily solved by downgrading to 5.0.2 Lollipop.