Database Users

- fixed -

- fixed via clockwork recovery -
hi!
I have recently undone mimocan's fix successfully (as shown here: http://forum.xda-developers.com/showthread.php?t=765393) and applied CFLagFix 1.80, also successfully.
however, market downloads are no longer working; I think this may have to do with the following error as market uses gtalk in some way; alogcat reads:
E/GTalkService ( 2463): createAccount: gls.getAndroidId () returned 0!
E/GtalkService ( 2463): create GTalkConnection: account is null!
GTalk immediately closes after running it.
so I am wondering if there's a way to fix this without a complete wipe...?
thanks for your help!
thomas

[Q] Encrypt phone feature bugged on Defy starting from 4.0

Hi Guys,
Has anyone tried the encryption feature found in Security settings? I'm using a recent nightly CM11 from Quarx/Blechd0se (Thanks, brilliant work!) quite stably for days now, but fail to make the encrypt phone function work...
When fully charged and USB powered, which are requirements, the successive encrypt phone buttons end up on a green android picture. This screen misses text and a progress bar which should normally appear on top of the screen, as seen on some screenshots. Even left for several hours, nothing progresses and a simple press on back button cancels action immediately which proves nothing has been encrypted in the meanwhile.
Took a Catlog and the only interesting message is the following:
Code:
01-02 01:34:23.732 E/Cryptfs ( 1197): Cannot get size of block device
In case it helps, find attached the output of mount command : View attachment mnt.txt
Could you have a look / help me out? (add to bug list if it applies)
In fact, for me, this function needs to be activated for connecting to my professional mails ...
Thanks in advance! :good:
Cheers

Further tested...
Hello all,
Just some more info... I flashed back to Quarx' CM9 and quickly tested once more the encryption and face the same problem but I didn't catlog, neither checked the mounts... Then I flashed Epsylon3's CM9 and quickly checked with the same result too...
But then I checked at catlog and now I get another type of error... Which is interesting and maybe promising as I already read some posts about this message...
Code:
04-14 21:11:13.101 E/Cryptfs ( 2219): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Problem seems to be more general than only Quarx/Blechd0se's CM11 but a friend uses a CM9 flavor on a Samsung Galaxy S and has encrypted the phone successfully...
All in all it's linked with the filesystem (block device or not), how it is formated (yaffs/ext3/ext4) and mounted (mount/mount_all)...
Some interesting reading on jira.cyanogenmod.org/browse/CYAN-87 (not linked, I don't have 10 posts yet)...
Hope to find, test and come back with some more info soon...:fingers-crossed:
Cheers!

[Q] G900F HOSTS FILE is normal but couldn't add a Google account

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

N910C - broken fingerprint sensor, backup password not working, don't want wipe...

Hello,
N910C, COJ5, noroot. Suddenly my phone stopped to use fingerprint sensor and backup password I am providing is not being acceptable.
Short list:
- notifications, network, sms and incoming calls are working, BUT nothing else
- after restarts, removing battery, tries to use ODIN(3.07 & 3.10) or TWRP or kernel with permissive - not working (blocked by R/L) - I wanted to use root privileges to remove files in /data/system responsible for fingerprints and backup password.
- ADB is working
- I want to recover data before wipe - some free soft like Android Recovery Tool or sthg like this ?
Any ideas?
Thanks in advance!
--
Szymon

I see three ways:
-Try to unlock with the fingerprint, it will give you the option to enter a secondary password. Put a random pass 5 times until the device blocks you to keep entering wrong passwords. After that, a new button saying "Unlock with your google account" should appear. Touch it, put your email and password and wait for a couple of seconds. The device will unlock and will set the lockscreen to "Swipe".
-If that doesn't work (rare), try this, it shoud work: http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 (since your device is locked you can't access to the MTP functions. You have to put the zip file in a external sd card and flash it with TWRP.
-If that doesn't work either (dafuq?), make a data backup in TWRP ("Backup" option, then select data only), wipe your device, flash a rom and then flash the backup again.
Also remember: "Wipe data" option in TWRP erases all ylur apps and configs, but your pesonal info like photos, documents, downloads, etc will still be at there.

galaxynote2 said:
I see three ways:
[...]
Click to expand...
Click to collapse
I see that you did not read my post
All of these 3 options you mentioned are not possible.
Any other ideas?
I just copied via adb in shell all important files from internal memory and now after I wiped it out I got strange info that "This device is locked because of an abnormal factory reset"
I am not using Find My Mobile Samsung service so WTF ?! Why is it asking me for something that I am not using and it will be not working ???
Regards,
add-on: there was a Find My Mobile by Samsung block, but I used some mystery account I forgot about Now everything is up and running

Success: Bypassing *samsung account* lock after factory reset

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!