Database Users

[Q] Accessing logs on the debug

This is for: Samsung GT-I9300 (Android 4.1.2 Phone)
Context: We are mobile development consultants and one of a beta versions of the an app we did for client is crashing on client's devices. (It was delivered through Testflightapp but since the app immediately crashes before the testflight session begins, we don't see any debug logs or crash log via testflight)
We want our client to send us the logcat contents so we asked him to:
1) Turn on the Developer Options from Settings/About Phone/ and Touch 7 times on the "Build Number".
2) In Developer Options you will see "Take bug Report". Touch it and Touch Report and it will take some time to prepare the email. When the preparation is complete you will see a notification which will ask you to Share the Report.
He replied:
Looking in developer options and I don't see anything called "take bug report
We then actually checked the user manual of Samsung GT-i9300 Galaxy and it does not have the 'take bug report' feature.
Question: How can we access the logcat contents from the client's device without resorting to integrating a logging framework in the app ?

Dump state error log or adb

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!

[YT3-X90L] Lock state - locked - Recovery image needed

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

Xtrons Android 8.1 HU - Remote Access Via AnyDesk?

Hello - I have a very specific remote access requirement, however I’m a total novice with regards to Android. I wanted to provide the instructions I have been given to see if anyone in the know could simply summarise or advice how I can achieve this please?
I need remote access of my Android 8.1 Xtrons HU however am finding that all Android Apps fail to allow ‘clicking’ when accessing the device remotely (ie. TeamViewer/ VNC install and allow a connection, however ‘clicking’ can not be done remotely). I believe this could be a security and/or accessibility issue/function, however the closest solution I have found has been advised by both the App publisher and the Xtrons support team below.
Although technical, I don’t know what the exact steps are, or if this approach will even work, however I wanted to post it here to see if anyone could make sense of it please?
Advise from Xtrons (HU Manufactuer):
"After entering "adbon "in the factory set and opening ADB ,you can apply on the machine by yourself directly."
Advice from AnyDesk Development Team:
"For the manufacturer of the Android's ROM there is a process to get the APK signed, so that remote control for that ROM is possible.
This is our Control Plugin Creation Process:
1. Run AnyDesk on the destination device and send the trace file to [email protected]<mailto:[email protected]> or as reply to this mail.
- Open Anydesk on Android
- Open the menu
- Open about panel
- Click on: Send Support Information
2. Please tell us the name you would like for your plugin and whether you want it to be available in the app store.
3. We can extract the system signature hash from the trace files and will build a plugin for this system.
4. We will send you this plugin APK file.
5. You have to sign the plugin with the platform key of your ROM.
apksigner sign --ks YOUR_PLATFORM_KEY_STORE --out YOUR_ANYDESK_PLUGIN-signed.apk YOUR_ANYDESK_PLUGIN-unsigned.apk
6. Send us the signed plugin back.
7. If possible provide us with one of your devices for testing.
8. We will send you the updated anydesk.apk for testing, you will have to install the updated anydesk.apk as well as the signed plugin manually on the test device.
9. After your ok we will publish it with our next android release.
10. Once the plugin and the updated AnyDesk app are released, your devices can be remote-controlled by AnyDesk."

[GUIDE] Ultimate fix for Google Family Link onboarding loop

I've spent an embarrassingly long time on this last weekend and I believe there might be a small group of people that would appreciate the found solution for this issue.
tl;dr: When using opengapps copy https://gitlab.opengapps.org/opengapps/all/-/blob/master/product/overlay/PlayStoreOverlay.apk to /system/product/overlays reboot and the loop should be fixed. (Also make sure to have Family Link Manager and Family Link Helper installed as system apps).
The problem:
When using any custom ROM Google Family Link fails to be setup correctly no matter the opengapps version/size. The error is a loop at the "The Family Link Manager needs to be setup for this device" step and then it leads to a modal dialog "The profile manager is required for google accounts managed with family link.", when you click "Got it" you will be led back to the same page and a click to "Next" opens that same modal dialog again.
The solution:
The Family Link Manager (com.google.android.apps.kids.familylinkmanager) and Family Link Helper (com.google.android.apps.kids.flh) apps needs to be installed as system app (in /system/priv-app/). Besides that the PlayStore app needs specific resources set to make the callback intent to enable the Family Link Manager as Device Admin app work. Funnily enough there was https://gitlab.opengapps.org/opengapps/all/-/merge_requests/51 4 months ago but seemingly nothing copies that PlayStoreOverlay.apk to /system/product/overlays/, doing that manually using TWRP (or anything else that can write to /system/) does fix the loop and makes Family Link work properly.
Credits go to: https://gitlab.com/LineageOS/issues/android/-/issues/3383
I hope this helps somebody. Please move this post to the appropriate forum if it shouldn't live here.

Nexus2kSwiss, thanks for the post. It's the most helpful thing I've found so far. I'm still having a problem with the loop, but I seem to be getting farther along. There's probably some basic detail I'm missing.
Device: Moto G4 Play
ROM: LineageOS 17.1
I found that LineageOS has a built-in root feature that can be toggled. (That's awesome. Too bad it took me so long to find that out.)
My questions:
Does "Family Link Manager" and "Family Link Helper" need to be particular versions? Do they need to match versions? And what about just "Family Link"? That's a whole different version. I'm thinking that it either replaced the other two or it's just the piece you get from the Play Store, while the others may come baked in?
Does the "PlayStoreOverlay.apk" need to be a specific version.
In any case, should I copy all three of the Family Link files to /system/priv-app/?
Here are the steps I've written for myself:
1. enable developer options (tapping on the build number several times)
2. enable ADB developer options
3. enable root in developer options
4. On PC,
adb devices
adb root
adb remount
5.
adb push PlayStoreOverlay.apk /system/product/overlay/PlayStoreOverlay.apk
6.
adb push com.google.android.apps.kids.familylinkmanager.apk /system/priv-app/com.google.android.apps.kids.familylinkmanager.apk
7.
adb push com.google.android.apps.kids.familylinkhelper.apk /system/priv-app/com.google.android.apps.kids.familylinkhelper.apk
8. (not sure if this is needed)
adb push com.google.android.apps.kids.familylink.apk /system/priv-app/com.google.android.apps.kids.familylink.apk
I see the files are there now and I get farther along my journey. I'm able to select which apps should be allowed and it seems like I'm almost done, but I don't get to complete it. I get the message again about the profile manager that keeps popping up and won't let me past it. (I checked again and it actually just crashes at that point.)
Any thoughts?
Thanks.

You definitely need to reboot the device after putting the PlaystoreOverlay as I believe it doesn't get loaded automatically. Family Link Manager and Familylink helper should be the same version (just get the lastest from apkmirror or so).
The Family link app itself is not needed as it's just the UI for managing other devices.
Where do you get stuck now? Do you have gapps nano or bigger installed?
If I understand my original linked lineageos thread correctly there should be builds now available which do copy the PlaystoreOverlay correctly. So maybe using a newer build for your device fixes the issue.

Nexus2kSwiss said:
You definitely need to reboot the device after putting the PlaystoreOverlay as I believe it doesn't get loaded automatically. Family Link Manager and Familylink helper should be the same version (just get the lastest from apkmirror or so).
The Family link app itself is not needed as it's just the UI for managing other devices.
Where do you get stuck now? Do you have gapps nano or bigger installed?
If I understand my original linked lineageos thread correctly there should be builds now available which do copy the PlaystoreOverlay correctly. So maybe using a newer build for your device fixes the issue.
Click to expand...
Click to collapse
Thanks for the response. Good information!
I think I did the nano gapps install. It's about 400 MB. I'll look for a newer build that has the correct PlayStoreOverlay. Maybe that's the easiest.
I will report back if I get farther along.
Thanks again.

Okay, got it working!
I did a factory reset and wiped everything. Then, I reinstalled LineageOS 17.1 and the latest GApps.
lineage-17.1-20220204-nightly-harpia-signed.zip
open_gapps-arm-10.0-mini-20220204.zip
(I tried to install the "super" GApps, but found that "mini" was the largest bundle that would fit on this device without resizing the partition.)
On first boot-up:
I got an error for Speech Services. (Closed it.)
Connected to wifi.
"Checking for updates..." (automatic)
"Installing updates" (automatic)
"Copy apps & data" - Chose "Don't copy".
Signed in with my kid's account.
Agree to terms.
"Got get your parent" - Selected my (parent) account, logged in. Confirmed 2FA.
"Stick around for what's next" - "Next".
"Checking for updates..." (Again?)
"Please wait"
"Review apps" - This is where I select which apps to restrict for my kid. "Next"
"Google services" - "Accept"
"Protect your phone" - Screen lock settings.
"Access your Assistant with 'Hey Google'" - "Skip"
"Access your Assistant without unlocking your device" - "Skip"
"Anything else?" - "Done for now".
"LineageOS features" - leave "help..." selected. "Next".
"Restore apps and data" - "Skip"
Select "Start".
"Please wait"
"Your devices are connected" - "Next"
"Supervision ready!" - "OK"
It worked! I was beginning to doubt it.
So there you go. LineageOS 17.1 on Moto G4 Play with Open GApps ("mini") allows you to use Family Link / supervision.