Edit: This thread was originally started as a help thread, but I'm pretty sure it's a real bug now, so I've entirely edited the content of my first post to summarize the problem (for clarity).
After flashing 4.4.2 with MOP and rebooting into download mode to flash the bootloader with desktop Odin, some users were reporting Samsung keyboard force closes.
If you reflash the firmware with MOP and reboot normally, your keyboard will work, but handwriting recognition will not, and if you call *#1234# you will not have a CSC number.
If you reflash and reboot into recovery, your keyboard and handwriting recognition will work, and you WILL have a CSC number. However, if you were to check your call logs or messages, you will see contact numbers, but not names, even though the contacts are on your phone.
Let me illustrate with a fictitious contact: John Doe, 12345678. You will see a message from 12345678, not John Doe, even though you have a contact named John Doe with the number 12345678 in your contacts.
This problem has been verified by one user already: http://forum.xda-developers.com/showpost.php?p=51155409&postcount=722
Fix found: Remove Google account, reboot, and re-add Google account.
Related
Hello,
The attached CSV file can be imported to your gmail contacts. It contains most of the Secret Codes that I've currently found.
When imported, it will add the codes to two different Groups;
Samsung Galaxy Tab
Starred in Android
The only thing that actually makes this work (as far as I found) is the 'Starred in Android' as it adds them to your favorites. Trying to call from "Contacts" does not work.
==========
I did not include the following code as it requires input unique to your specific device:
Change Product Code: *#272*THE_IMEI_OUTPUT(ONLY 15 DIGITS)#
I did not include the following codes as they are DESTRUCTIVE!!
WARNING!! Do not try these codes without knowing knowing what you are doing!!
Hard Reset: *2767*3855#
Factory Reset: *#*#7780#*#*
Hi,
Dear All,
Ok, the problem is very famous i.e. i factory reset my device and when powered one like a fresh piece, i cannot add google account on my G900F (can't establish a reliable connection to the server).
i have searched a lot over the internet. Read about the HOSTS files description as well. All i found was the modification of the "etc/hosts" with the clients.google.... following "#" so that 127.0.0.1 localhost is only the operational entity.
My device is un-rooted and just for the confirmation of the above mentioned, i opened the hosts file via HTML Viewer (just readonly) and found that the etc/hosts file on my S5 has 127.0.0.1 localhost only and no any other information, which i think should be available for your device to work normal and google accounts can be added. See attached screenshot.
Need your kind help in resolving my issue please.
Try clearing caches from recovery
Still same issue...
Might be worth factory resetting again
How did you access the HOSTS files without being rooted?
did the factory reset 3 times but nothing, issue stands unresolved.
i opened the HOSTS file through RARLAB. Actually it allows you to view the root folder and all of its contents even if your phone is un-rooted.
Could try removing the device from Google Play
https://support.google.com/googleplay/answer/2407656?hl=en-GB
Create a new Google account as a test to see if the issue is the phone or the account
If that doesn't help, Id flash a stock ROM through ODIN, this will NOT trip KNOX if you are still 0x0
Are you sure all your data connections are working properly, WiFi/3/4G ?
*Detection* said:
Could try removing the device from Google Play
https://support.google.com/googleplay/answer/2407656?hl=en-GB
Create a new Google account as a test to see if the issue is the phone or the account
If that doesn't help, Id flash a stock ROM through ODIN, this will NOT trip KNOX if you are still 0x0
Are you sure all your data connections are working properly, WiFi/3/4G ?
Click to expand...
Click to collapse
ok here are some interesting occurrences:
Worth mentioning that i was operating over Wi-Fi.
1) - i flashed a stock Kitkat ANG2 ROM via odin and the problem still persists.
2) - Then i flashed stock Lollipop BOB7 and still the same.
3) - Then i created a new account via the first sign in page on the phone (after flashing the new ROM), and i was able make a new account(through my phone) but still it was unable to login on the phone.
4) - Then i installed a Proxy/VPN betternet and then i was able add an account successfully and also Play store is working fine.
5) - Means there is some issue with my wi-fi adapter routing (may be inside the phone or the carrier) etc.
6) - Then i switched off the wi-fi and enabled LTE (of my SIM card provider) and connected my phone through it, say what! its working fine.
7) - again i tried over the wi-fi and the issue started to happen again
Well, one important thing, i am using wi-fi which is also a LTE carrier (having the google issues) and the second LTE (which worked fine) is by the SIM card operator.
So , is there any problem with my wi-fi (inside the phone) or may be with the operator from which i am getting my services??
its quite confusing at the moment. well i am going to try the whole thing over the Wi-Fi of another operator and will feedback the results.
Mean while any suggestions ??
Reboot the router you are connected to WiFi from?
Doesn't sound like the phones fault, unless you have a proxy enabled in WiFI settings or something, sounds like the issue is with your ISP/Router
Hi all, before I forget about this and move on, I just thought I'd share my experience, as most "fixes" for the Factory Reset Protection that I could find online related to google account-based lockout, rather than samsung account-based lockout. The lockout in question says something like "This device is locked because of an abnormal factory reset. Sign in to the Samsung account that you have already signed in to on this device to confirm it belongs to you."
Apologies for the vagueness of the final step (5) below - I wasn't setting out to document what I did, so wasn't taking notes. I am in a rush now but when I have time I'll try to be more specific. Perhaps someone else may jump in with their detailed experience in the meanwhile!
Background: My workplace passed on to me a used Galaxy E7 (specifically SM-700H). Not knowing about the infuriating "Factory Reset Protection" protection, I simply wiped it via the stock bootloader the moment I got it. Then I discovered it was now locked - and that the previous user/employee had walked without sharing the samsung account and password used. All purchase info etc lost in the mists of office disorganization so no chance of an unlock via Samsung, I assumed .
Anyway, so I found the installed 5.1.1 rom (specifically, LMY47X.E700HXXU1BPA1) was resistant to tricks I read elsewhere designed to give access to the phones settings, so I downgraded to an older kitkat rom, then found I could access settings from that, as this hole presumably hadn't been patched. The following worked for me:
1. Download ODIN (I used ver 3.11)
2. Download a stock kitkat rom to use to downgrade to. I used E700HXXU1AOE4 which is from Nepal I think, but the region doesn't seem to matter. (Most free firmware download pages are deliberately crippled, I found they are super slow and always timed out before completing; but this free page has fast downloads: http://www.theandroidsoul.com/galaxy-e7-stock-firmware/#jump-model-no-sm-e700h )
3. Flash that newly downloaded firmware using ODIN (you can use the instructions here: "How to Install/Update Official Firmware on Galaxy E7 SM-E700H Manually through Odin:" http://www.androidofficer.com/2016/01/e700hxxu1bpa1-android-511-xxu1bpa1.html )
4. Boot up, connect to the internet via wifi. I signed into my google account at some point, but not sure if that was necessary. That step comes before the Samsung Account lockout screen presents itself.
5. (SORRY this is a little vague, will come back to it later, but trust me, this worked for me!) Click about through the several available pages and settings which appear before the Samsung Account lock page until you find any piece of disclaimer/info text, I was looking for some which included a URL, but it turned out I think that wasn't even required. Highlight some text, touch it again, and look for a search/globe/internet icon. Amazingly, that will launch the phone's search function via google now/its internal browser.
6. At that point, you're essentially outside of the "lockdown" intro screens. What i did was put the word "settings" into the google now search box, then at the bottom of the results page, slid the category slider from the default "web" results source, past "apps" and "images" etc across to "phone", which delivered a link to the phone's actual settings.
7. At that point, you can drill down to "Security" then deactivate the "Reactivation lock" setting, enable developer mode, unsigned apps, etc - whatever you feel needs doing - then restart the phone in the normal manner. The setup screen is back after restart, but without the lockout. Voila, a working phone.
Notes: So no need to download sideload any external apks. Also a gotcha - I subsequently created a new random Samsung Account to sign into, because i was afraid the unknown samsung account lockout curse would return - then i noticed that by signing in to that, it had once again ticked the "Reactivation lock" setting - watch out for that!
Hello XDA-Community,
I've got a Yoga Tab 3 Pro YT3-X90L from a customer.
He was telling me, that he wanted to unlock his device with the pattern, mismatched for several times and now its locked and requires the owners google account. Or something like that. He never had the owners google account. He told me that his seller has activated his device for him. And he has no clue who it was.
Now here is my part.
I've researched and obviously it's a FRP. The owners google account information are stored in the FRP-Partition. And this partition won't get deleted with a simple factory resett.
What i've tried so far:
1.) https://www.youtube.com/watch?v=nCzrnnh2K1w I was able to follow this tutorial to minute 9:08. But the option "Email and password" is not there anymore. I guess they patched it with 6.0.1.
2.) I tried to flash a stock rom or twrp with LenovoDownloader(QcomDLoader). The stock rom file is: Lenovo_Yoga_Tablet_3_YT3-X90L_ENG_S200028_1609230146. even its a german device this file was the only one i could find. But the LenovoDownloader won't recognize my device. The windows stays white, no entries. I guess i installed the correct driver for this device and Windows recognizes them as removable device if i plug it in via usb.
3.) I've tried to use adb and fastboot boot oem unlock. But this commands aren't working in locked state.
4.) With a trick i could open the Settings and was full of hope to active the developer options to set usb debbuging to active. But this developer options aren't available either with this "user".
5.) There is an apk for showing the "Email and password" interface. I could install it, but it force closes right after starting it.
6.) I've tried several tools to bypass this FRP: WinDroid Toolkit, D-G Unlocker, Realterm, but NOTHING.
What could i do further? I'm out of ideas right now.
I've read about a factory_update.img but i cant find anything, except the stock rom file, for this device.
Or downgrading the device, so i could use the "Email and password" but. But i can't even flash the stock rom.
Specs for the device:
Lenovo Yoga Tab 3 Pro YT3-X90L
Lenovo/YT3_l0_row_lte
6.0.1/MMB29M/LenovoYT3-X90L_S200307_170614
i appreciate any help i can get
greets
redplate
I've wrote it down. Hope this helps.
Situation:
"Confirm account: The device has been reset. To continue, sign in with a Google Account that was previously synced on this device. "
Explanation:
The device has been blocked by repeated input of the wrong password, pattern, etc. and can only be unlocked with the Google account of the owner.
A factory reset or hard reset does not help here, as the account information is saved in its own FRP partition and will not be deleted when the factory state is restored.
Solution:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
7. You can now not only browse the Internet through this search, but also search for and open installed programs.
8. We are looking for Chrome, open the internet browser, go to www.google.com and search for DPC test.
Link: https://www.apkmirror.com/apk/sampl...-release/test-dpc-4-0-6-android-apk-download/
9. After downloading this application, go back to the Google search application.
10. Here we enter "Download" to search for the download application.
11. In Downloads we can now find and install the downloaded app.
12. To allow the installation of this .apk, you must allow the installation of "unknown sources" in the settings.
13. Either you go here on the installation itself on "Settings", or you search for "Settings" on the Google search app.
14. After completing the installation of the DPC-Test program, start it with "Open".
15. The app itself is will register as a device owner and now allows us to set up a new Google Account as owner.
16. If this is set up, it will also be included in the FRP partition.
17. In the event of a new factory reset, the device is reset, the DPC-Test program is removed and the device can be freshly set up in the factory settings.
after the takeover of the owner, the reason for blocking the device was not present anymore and the old owner was overwritten. This will be overwritten in the FRP partition aswell with the new account and the old one no longer queried.
You, mister, are my savior! Thank you very much.
Solve works for Lenovo Yoga 3 tablet
Just a big giant thank you! My dad passed away leaving me a Lenovo Yoga 3 tablet, unable to gain access due to information stored in the FRP partition. :highfive:
Hi
I followed your instructions for first 5 points
redplate said:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
Click to expand...
Click to collapse
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance
marOOn1971 said:
Hi
I followed your instructions for first 5 points
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance
Click to expand...
Click to collapse
Hi. Actually I'm not into this anymore. Could be possible they removed it since it might was reported.
If I have any idea I'll let you know it
As you may noticed since last week google wants us, the custom rom users to manually register our android_id to the link https://www.google.com/android/uncertified/
It looks simple isn't it?
But there's a catch. Each google account can register up to 100 ids. So if you keep registering new ids after every clean install you'll more likely to hit that 100 ids limit soon. That's even worse for fhe rom developers as they may flash up to 20-30 roms a day.
I'm figuring out that in a different way though. The procedure I'm following is:
A. BEFORE ANYTHING
If you're doing this first time:
1) Copy this database from /data/data/com.google.android.gsf/databases/gservices.db
2.1) Open the database with a sql editor or from adb shell or a terminal emulator in sqlite3, see android_id with this sql command:
SELECT *
FROM main
WHERE name="android_id";
2.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "SELECT * FROM main WHERE name = \"android_id\";"'
3) Then save the value you're seeing to somewhere else, and register to your account at https://www.google.com/android/uncertified/
B. THEN FOR EVERY CLEAN INSTALL
1) Backups and wipes.
2) Flash rom (pt roms with vendors have the firmware included).
3) Flash gapps.
4) Optionally flash a custom kernel.
5) Reboot and configure your device.
6) Flash magisk, reboot.
THEN THIS PART IS IMPORTANT:
7.1) Again copy this database /data/data/com.google.android.gsf/databases/gservices.db and open in a sql editor (or with sqlite3 in terminal emulator, or adb shell) and execute this sql command:
UPDATE main
SET value=XXXXXXXXXXXXXXXXXXX
WHERE name="android_id";
7.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "UPDATE main SET value=XXXXXXXXXXXXXXXXXXX WHERE name = \"android_id\";"'
Note: XXXXXXXXXXXXXXXXXXX is your android_id as you've learned and registered to your account before (You can see the android_id s you've registered at the same google link).
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Deleted
Deleted
muff99 said:
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Click to expand...
Click to collapse
Yes that works too but this is the manual method for the gsf android_id. Wifi only devices doesn't have IMEI for example.
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
G4B33 said:
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
Click to expand...
Click to collapse
Yes so now we don't have to do that much of hacky-wacky stuff just to get gsf certified status anymore. #YayGoogle? ?
What if you don't do that?
seems not working. After rebooting, it went back to previous id
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
ccelik97 said:
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
Click to expand...
Click to collapse
I think the display will always stay on "not certified", but you are atill able to use the Google services (which unregistered custom ROM users are not any more, if I understood correctly).
This is just a guess on my side, I have not tested this (and I can't since I added all kinds of IDs to that registration page ...).
All in all the information flow from Google on this topic has been spectacularly bad, imho.
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
image45 said:
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
Click to expand...
Click to collapse
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
muff99 said:
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
Click to expand...
Click to collapse
Do I need to convert it or is that an accepted way to submit the information please?
If I try to resubmit it advises already registered.