Related
OK when I first got the handset but now unable to play any videos ( including the pre-loaded demo). Getting the error message "The source filter for this file could not be loaded" under a "Windows Media" heading.
Not sure what I have done but any ideas would be welcome - if possible without a hard reset. Thanks
Problem sorted by playing with the settings in streaming media. This was the response that I got back from HTC - perhaps the answer to all and everybodys problems....
New Response From [ Alex Nyberg (Europe Support (Tech)) ]
Dear Sir/Madame, Thank you for contacting HTC Europe. To get your device working properly, try the following steps: * Do a soft reset: take the battery out for about 10 minutes, put it back in and start the phone. * Do a hard reset: go to Start > Settings > System > Clear storage. This will restore the device to factory default. Before doing this, make sure the encryption is turned off and that you have a backup of important data. * Check for updates for your device: You can find all available updates at the HTC homepage. Go to www.htc.com, press "Support", select your device and then go to "Software Download". Type in your serial number to download the updates (the serial number can be found under the battery) and download the update. Then follow the instructions on the homepage. * As a last way to solve the issue, send it in for repair. We hope this will answer you question but feel free to contact us using the reference number above. Best Regards, Alex Nyberg HTC Europe www.europe.htc.com
Running the Android Compatibility Test Suite on TF101
Background: what CTS is
The Android Compatibility Test Suite is an automated test harness which tests one or more devices to ensure that they offer a fully-compliant running environment for 3rd-party applications.
Passing these tests is required to use the Android brand name for retail devices and it's also the basic prerequisite for acquiring a Google Play license for OEMs.
Background/2: what CTS isn't
As of the current CDD (Compatibility Definition Document) the CTS still doesn't enforce stability or performance requirements for devices, even though some of its tests are taxing enough for the device to expose subtle problems. Some performance tests are nevertheless included, but they're not run by the main CTS plan, nor are they part of the current CDD.
Background/3: why it's important for TF101 users
Given the way the CTS stresses the system, it is useful as a standardised testing procedure for some of the problems some users are currently experiencing with ICS on TF101. It also can help ensuring that the device works as intended with (most) 3rd-party applications straight out-of-the-box.
Requirements: host
The host should be a Linux-based workstation with the Java 6 JDK installed (either Oracle's or OpenJDK - IBM JDK or GNU gcj are not supported, while Oracle/OpenJDK JDK 7 are untested), a fully working installation of the Android SDK and about 3 or 4 GB of disk space available for downloaded media files.
Test results are best viewed with a recent version of Firefox, otherwise you can post-process them into an HTML file using an XSLT 2.0 engine (tested with Saxon).
Requirements: target device
The target device should be a completely stock and unrooted TF101 running 9.2.1.24. It is possible to run the CTS on custom roms, but the tests assume that the device is running a user build (not eng, not even userdebug) in secure mode. YMMV, expect unpredicted failures.
Required files
You're going to need the following files from the CTS downloads page:
Android 4.0.3 R2 Compatibility Test Suite (CTS)
CTS Media 1.0
The following files are optional:
Compatibility Test Suite (CTS) User Manual (if you want more information about the test harness)
Android 4.0.3 R1 CTS Verifier (used to perform user-assisted tests - I didn't run this yet, if you feel brave go ahead and post the procedure you used)
You may also need a log collecting application, even though the CTS should be capable of collecting device logs on its own (it didn't work for me). LogDog (if you have it) is strongly recommended.
Host-side setup
Download the required files and unzip them into a folder of your choice, then change the first line of media/copy_media.sh from:
Code:
#!/bin/sh
to:
Code:
#!/bin/bash
so that the script runs successfully on Debian-based systems (the script is full of bashisms which make dash complain and exit with multiple errors).
Ensure the user you'll be running CTS under has the proper privileges to run adb.
Device setup
First and foremost: perform a full Factory Data Reset (either through the Settings menu or using the VolDown+Power chord at boot time and selecting "Wipe Data").
As soon as the system boots after the wipe, perform the first run wizard selecting English (US) as the system language, connect the device to a wireless network, do not add any Google account (yet), and then reboot the device again to regain access to the system bar widgets (known 9.2.1.24 bug).
Once the system is back up, open Settings and perform the following actions:
disable Quick Settings (ASUS customized setting → ensure Use ASUS Quick Setting is unchecked)
disable System bar lock (ASUS customized setting → System bar lock → ensure Enable system bar lock is unchecked)
disable ASUS Sync (Accounts & sync → ensure Launch ASUS Sync is unchecked)
disable the internal GPS to save battery (Location services → ensure GPS satellites is unchecked)
deactivate all screen locks (Security → Screen lock → None)
temporarily enable Unknown sources (Security → ensure Unknown sources is checked)
under Language & input, ensure that the default input method is Android Keyboard
enable USB debugging (Developer options (dismiss the nag dialog) → ensure USB debugging is checked)
enable Allow mock locations (Developer options (dismiss the nag dialog) → ensure Allow mock locations is checked)
Now go back to Accounts & sync, turn off synchronization and add the Google Account you normally use for Google Play, but don't restore anything, nor accept to synchronize anything - you're going to need this just to install WakeLock.
Close the settings, open Google Play Store, go to its settings and deactivate automatic updates and the infamous auto-add for widgets, then install WakeLock.
Now go back again to Settings → Accounts & sync and nuke the account you just set up.
At this point, you're ready to upload CTS test files, so connect the device via USB to your host, disconnect any other Android device (emulators included!), ensure adb is on your PATH and then run the following commands from the directory where you unpacked the CTS archives:
Code:
cd media
./copy_media.sh all
This will upload the CTS media files (Big Buck Bunny) on the device, it will take a bit of time.
When it's done, you have to install the instrumentation apks:
Code:
cd ..
adb install android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk
adb install android-cts/repository/testcases/CtsDeviceAdmin.apk
Now back on the device, open Settings again and perform the following actions:
enable Accessibility → Delegating Accessibility Service
go to Security → Device administrators → check all android.deviceadmin.cts.* administrators
This is a good time to install LogDog and reboot the system if you wish.
After that, go back to Security and ensure that Unknown sources is unchecked.
Unplug the device from USB and charge it fully.
After the device is charged, plug it back to the host, go to Settings → Developer options (again, dismiss the nag dialog) → ensure Stay awake is checked even though it won't work.
Launch WakeLock, select FULL_WAKE_LOCK as lock type, deselect "Show notification?", select "Start on boot?" and then "Acquire lock".
>>> Press the Home button to go back to the home screen.
Congratulations, you're ready to start the test harness.
Running CTS
On the host, run android-cts/tools/cts-tradefed. It will detect the device and print its android device id, then wait for a command.
To start the full CTS suite, issue run cts --plan CTS. It will take several hours and the battery will barely last for the entire duration. DO NOT INTERACT WITH THE DEVICE IN ANY WAY WHILE THE TESTS ARE RUNNING!.
After the test is finished, just type exit to terminate the test harness utility. Test results will be in android-cts/repository/results/<start time>/testResult.xml, open it with Firefox to see them or process them with saxon-xslt to produce an html file.
If you were running LogDog during the tests, archive the logs now and transfer the log archive to the host.
Post-run caveats
Wipe the device to ensure that any leftover is cleared. If you wish to run the tests again, restart from the "Device setup" step.
reserved for future notes
Thanks for the in-depth guide, very interesting!
Hi all,
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Thanks!
GnobarEl said:
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Click to expand...
Click to collapse
IIRC there is a way to tell tradefed to run a specific test, but I don't have the CTS documentation and tradefed itself ready at hand.
Try issuing 'help' at tradefed's prompt, it should provide with the necessary syntax to run a single test instead of a full-blown test plan.
Hi,
you can do something like "add --derivedplan -result fail" and run only failed tests. The problem is that creats another report, and not update the first report.
I wanted to have only one report in the end.
thanks for your reply.
Debloater by Gatesjunior
Disclaimer:
I nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying my code or redistributing it is not allowed without prior approval from me. Yes, that includes Kanging it, I will be able to tell. Neither is trying to use any of my code to create an apk file with my code logic allowed without prior approval from me.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture.
Background:
So after many times of going back and forth blocking / disabling apps on my devices through the command line and or shell, I decided to write a program to make this all much easier for myself. Well, after I got it all finally running and doing what I wanted, for each particular device I own, I decided that his was a pretty nice program and I wanted to share it with the community. After all, this community is where I started and learned a lot of the things I know today. So why not share with my family of Android enthusiasts.
Requirements:
The program requires that your manufacturer USB drivers are installed for your specific device as well as the following:
• Windows Operating System
• USB Debugging turned on for your device
• Root or KitKat and above running on your device
Some people have had trouble getting their PC to see their device, even with the device manufacturer drivers installed. Watch your device when you plug it in and authorize your computer to access it, the device should display a popup something for you to grant access to the PC. If it does not, go into Settings, Developer Options and look for an option that says something about Revoke USB debugging authorizations and tap it. Click ok. Now, unplug your device and plug it in while watching your device and click on the option to always allow this computer and then grant when the popup window displays.
What does it do?:
• Block / Disable applications on your device
• UnBlock / Enable applications on your device
• Allow UnBlock / Enable all applications at once on your device
• Allows filtering of the displayed packages for quicker decision making
• Allows exporting your blocked / unblocked listing to a file (Right click on Read Device Packages after list is loaded)
• Allows importing your blocked, or someone else's, listing (Right click on Read Device Packages after list is loaded)
• Allows complete removal of application(s) if you have root (It will backup the original folder structure and apk for you, just in case you need to restore the application(s) back to your device.
So, essentially what it does is this. It will disable / block any system and third party application on your device with ease and allow you to enable / unblock the application just as easy. It also reads everything, real-time, directly from your device, so that there are no messy batch files, scripts and txt files, etc. that you have to maintain and keep track of for every device you own. I mean let’s be honest, most of us own more than one device. Phones, tablets, etc. Who wants to maintain all those scripts and files for every device? The other nice thing that this program does is allow you to, at a granular level, control what is blocked/disabled and what is not. There are quite a few scripts and things like this available in the community that give everyone a start on what to disable/block, but who wants to scour through these scripts and decide what they want or don’t want with something someone else put together. The other nice feature of the program is it will display information for you about your device. Such as Model number, Serial number and battery status. As well as whether or not your device is rooted or not.
What audience of device does it support?:
This program supports many devices. It will support any device running KitKat or above, whether rooted or not. That’s right, if your running KitKat or above, your device does not need to be rooted. If you’re running anything other than KitKat or above, your device does need to be rooted. As long as these requirements are met the program will run. The program will also auto-detect whether or not your device is supported. So if you are not sure, plug it in and let the program tell you. If your device is not supported, it will put up a message saying as much and close the program.
Program Functionality:
The first thing you need to make sure of is that USB debugging is turned on for your device. The video at the end of this OP is a must to watch. It will describe this process as well as allowing adb shell permissions.
So when you first connect your device you will need to wait for the program to detect your device and whether or not it is supported. Once this is established, usually within a couple of seconds, it will display a warning message to you reminding you to be careful with what you disable and block. Yes, it will allow you, if your device is supported, to disable/block even system dependent applications. This message will also include, if your device does not support block mode, a message indicating that block mode is not supported and that it will disable the applications. Here is a sample screenshot of this.
{
"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"
}
Once the program has initialized, and the warning message has been presented, it will put you into the main program screen itself which will look like the following.
From here the first thing you need to do is click the Read Device Packages button on the upper left. This will initiate the process to start reading all of the applications on your device and then list them in a list in the window. It will also indicate to you what it detects as applications that are already disabled/blocked on your device by putting a checkmark in the box next to the application. It will look similar to this.
As you can see it will tell you in the upper right how many applications it detects as blocked and not blocked. You will notice that on the bottom left it has an indicator that is labeled Synced. As you make changes to the device application listing this will turn red. In other words, it will indicate whether you have made changes to the device application listing since the last sync. Also, in the upper right there is a counter labeled Changed. This indicates the number of changes you have made to the device application listing since last sync.
Once you have made any changes to the device application listing an Apply button will show up in the upper left replacing the existing Read Device Packages button, it will look like the following.
Once you click the Apply button the existing changes you made to the device application listing will be applied to your device. Keep in mind that you can disable/block and enable/unblock applications all at the same timeand then apply those changes to your device. After you have applied the changes to your device a message will be displayed stating the status of your changes as seen below.
Once the changes are applied to your device you now just click the Read Device Packages button again to reload the information from your device and you will now notice that the application(s) you just made changes to will indicate as much in the refreshed listing. As seen below.
You will notice that the particular application I asked it to disable/block has now a check mark next to it indicating that the device itself has disabled/blocked this application.
So now on to filtering. Lets say you want to limit the listing to specific items you are searching for within the package name. Like packages that contain "vzw" for Verizon. You will see below by clicking the filter checkbox and then typing in what I want to filter on, it will limit the list to your specific filter criteria immediately.
And here is the results of our filter below.
From here I can make changes to the listing, by checking the box next to the packages or I can simply uncheck the filter checkbox and return back to the full listing unfiltered.
O.k., so far so good. Now let’s say that you want to enable/unblock all the applications on your device. Maybe you’re selling it or maybe you have an issue with it and you want your carrier to take a look at it. By clicking the Unblock All Packages button and then click Apply this will enable/unblock all applications on your device. As if it is back to factory with no changes made.
Remove mode turned on. For all you root users, this will completely remove the application(s) in the exact same manner and will keep a backup for you in the install folder under Backup of the original apk files. They will also be kept in the original file structure they came from on the device so that it will make it easy for you if you have to push one back to your device. Here is an example of the remove mode turned on and the warning you will receive when it is active for the device that is rooted.
Also, after you have removed the application(s) you want, if you Reload Device Packages again, you will notice them in the list and checked. This is in fact accurate, it sees them as removed / uninstalled. To not have them show up in the list any longer, just reboot your phone and run the program again and you will see that they no longer show up in the listing.
Sharing your blocked list or re-import it to your device:
So there are times when you get a replacement device and do not want to have to go through all the pain remembering what you had blocked. Well to the rescue comes the export/import functionality of the application. This will allow you to export and import your blocked list. You also might want to share it with someone. So this is how it works:
Once you launched the program and have clicked the Read Device Packages and your list is up, you can right click on the Read Device Packages button and export the blocked packages to a file and share it. Then the person receiving it just does the same process, but when they right click on the Read Device Packages, they just choose import blocked packages and then click the Apply button. Done.. You of course can do this yourself to your device. This can come in very handy if you have to Wipe Data, because you blocked something you should not have and your device is experiencing issues.
Well community people that is it. I hope you enjoy the program as much as I do and look forward to your feedback. Gatesjunior signing out…
Full Install:
Download link: https://1drv.ms/u/s!AjfH26Z4pHaFk1V8rA5Zj_p5vtkx
Upgrade Install: (Just replace debloater.exe in your "Crogram Files (x86)DebloaterDebloater" folder)
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
OSX Version (dmg file): Thank @eyekyu for the port over with Wineskin..
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
Mirror: https://onedrive.live.com/redir?resid=8576a478a6dbc737!831
Video by our own RootJunky:
Credits:
RootJunky - For finding the original KitKat weakness
Misterxtc - For all of his hard work already on helping people with a script process for this purpose
Er. Aditya - For testing with me and going back and forth with builds to finally resolve the no packages issue
XDA:DevDB Information
Debloater, Tool/Utility for the Android General
Contributors
gatesjunior
Version Information
Status: Stable
Current Stable Version: 3.85
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2018-01-12
Change Log:
01/09/2015: Initial Release
01/10/2015: Updated the handling of application filtering determining what is disabled / blocked
01/11/2015: Updated application (v2.1) to hopefully help address the local Administrator issues
01/12/2015: Major update v2.8 (Fixes all the users not being able to see packages - Xposed Framework fix)
1/13/2015: (v2.9) Fixed an issue with an Out of Bounds Exception in certain cases.
1/15/2015: (v2.10) Complete rewrite of the filter engine, all interactive and immediate now. Also some cleanup.
1/16/2015: (v3.0) Root mode added with ability to completely remove application(s), with backup feature.
1/17/2015: (V3.1) Added new intro screen as well as import blocked list functionality.
1/18/2015: (V3.2) Added some hover helper text. If you hover over a major item it will display helper text.
1/19/2015: (V3.3) Fixed some more Xposed framework issues that would impact rooted users and removing packages as well as fixed some import logic to make it more reliable and optimized.
1/23/2015: (V3.4) Major update and bug fixes as follows:
•Interactive search now also supports searching through the package name(s) as well as the apk file(s)
•Bugs related to duplicate entries showing up when you Read Device Packages multiple times with filter on and off are fixed. This could have caused issues with some users saying it will not remove something.
•Blocking mode fully supported on 4.4.x, found a major bug that was preventing this with rooted devices
•APK file backups now include Odex files if they exist with the APK
•Remove option now completely removes both apk and odex, so yes, previous builds would have left the odex files behind. They will not hurt anything, but take up space. I will release a quick fix for the cleanup of those soon, if you cannot do it yourself.
•Buttons appearing where they should not at times with filter is fixed
•If you have disabled something on the phone itself or in a script, and are rooted, the program will not care any longer and will unblock them anyway.
(1/31/2015: (V3.5) Major logic update. I think I finally put a nail in the coffin with the Xposed Framework issues and removing applications. Also added the functionality where once you import a blocked list all the items will turn red for the changes it has made.
(2/6/2015): V3.6 Quite a few additional options. Including the following:
Ability to only show blocked packages, unblocked packages and all packages. (Just right click on either Read Device Packages button or Apply button after initial package listing is displayed.)
Ability to right click now on not only the Read Device Packages button, but also the Apply button.
Ability to import unblocked listing (Yes, changes will be made red to identify what would be unblocked before Applying)
Ability to sort by either APK Filename or Package Name and be able to sort in either Ascending order or Descending order in each area.
Complete removal of all associated data and folders that pertains to a package if the Remove option is selected (Root Mode only)
(2/7/2015): V3.7 Added a checkbox identifier on Display mode to let users know which Display Mode they are in currently.
------ (Fix was placed into this build later that fixes the UnBlock All Packages button bug..)
(3/28/2015): V3.8 Added Lollipop support for rooted / non-rooted users. It will now support hiding the packages, if you are rooted it will disable them instead. Also, you will notice if you right click on the Read Device Packages after it loads there is also a Backup / Restore menu option. Do not use those yet, I am still working on them.
(4/4/2015): V3.85 Fixed issue with base.apk flags being read incorrectly from device. Logic issue.
(4/12/2015): Updated a logic issue in the detection of the device and it's abilities. Same release number, v3.85
(5/24/2015): Fixed an issue during import of a blocked list that would flag all "base.apk" files..
(1/7/2018): Added newer Android Debug Bridge Files..
Hold
For me..
Looking Good video coming soon
I can't wait to give this a run.
Well be getting a note edge soon for testing, and looking forward to giving this a shot.
OP updated now with Video..
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Just tried it on my AT&T Note 4. It seemed to work, great job and thanks for building this app.
0rtli said:
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Click to expand...
Click to collapse
Try this one and let me know:
https://drive.google.com/file/d/0B31X8bH_5Gl-OHpva0dCbHBTb2c/view?usp=sharing
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
[email protected] said:
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
Click to expand...
Click to collapse
Look back a post and try that one.. Also, send me a screen shot.. Make sure USB debugging is on and in the correct mode as well.
This version works, thanks!
Will be great if this soft give option to disable modem fast dormancy service without root access.
Anyway, thanks.
My AV detects Malware.
Using licensed ESET - no malware detected.
Just disabled FastDormancy.apk (com.motorola.fastdormancy) - how to check if its disabled? In Running programs still see this service is running.
Maximus1a said:
My AV detects Malware.
Click to expand...
Click to collapse
It doesn't like the behavior of the program LOL
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Great job on this project addition. I'll be adding your link to my XDA signature this afternoon. Like you and many others, I too believe that until root is achieved on our devices (for those unable to at this time) that having this capability to do with our devices is the next best thing; hands down!
Again, great job to you and to the others like RootJunky and Misterxtc for making this possible for the community here at XDA.
Dear gatesjunior,
I wonder how you'r software disable/enable apk's?
For example: on my device (xt907) I'm not able to complete disable fast dormancy service (see screenshot) only "Force stop" it for a while.
Wonder which method you are using to disable it complete (are you disable it or just force stop it?)
howellcp said:
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Click to expand...
Click to collapse
Make sure your USB debugging is on and in the right mode.
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
********** ANNOUNCEMENT - Beta Enrollment without Banner (OPEN NOW - Nov 16,17) - Read More Here
INTRODUCTION - Hello all. Now Samsung wants us to go to Members app and keep looking for banner to sign up for Android 11, One UI 3 Beta . It went live October 27th, 10:20 PM EST, As fate would have it, i went to sleep early, i missed it and the banner refused to show up for me in the morning. Download was only showing up for people with unlocked variants on ATID firmware.
DISCLAIMER / NOTICE - Flashing is always risky. I am not responsible for anything that may happen to your device including but not limited to it turning against you, making you its slave and sucking you into the Matrix.
This post is a collection of wisdom, research and hard work of many people over many years across many forums and not just XDA. I will try to credit and link to their original posts.
TIP -Keep in Notice -This SHALL NOT Factory Reset Your Device or Format Data, it is still a good idea to Take Back Up - Just a Suggestion - Always have a latest Back Up
******** UPDATE - It seems ATT devices are getting wiped now if its CSC or the Sim remains to be tested.
i don't have ATT hence cant verify but in case you have an Unlocked device (N986U1) with ATT sim, then, removing sim and Changing the CSC to XAA/XAA/XAA before sideloading Beta is advisable.
PROBLEM STATEMENT - Missed the One UI 3.0, Android 11, Beta Sign up Banner in Members app or got the banner but didn't get the download and I really want it NOW.
Not sure if you want it now? - Find the BETA CHANGELOG HERE
GRAB YOURSELF A COFFEE / DRINK, because depending on where you at and how fast you/your internet speeds/your Machine is this may take anywhere between 7 to 45 MinsSOLUTION -
1. Pre-Requisites - Make sure Following Conditions are met before you start
You need a PC/Laptop along with your phone and USB Cable.
You need ADB installed, you can use ADB on Linux too - NOTE If your ADB Tools are not working, download my ADB Folder called platform-tools. Then extract it somewhere easy to remember/ find, like desktop
Remember the Location of the folder where you have ADB installed / Location of platform-tools- This is the location containing adb.exe file.
You may or may not need ADB/USB Drivers if any errors in ADB please Download Drivers from here and Install on your PC.
This following one step is relevant Only for flashing Beta 1
Use Odin to Flash Unlocked (SM-N986U1) ATID Firmware if you are not on that. Refer this thread to get your Firmware.
For changing Firmware from N986U to N986U1 and / or GUIDE TO FLASHING USING ODIN Refer This thread
______________________________________________________________________________________________________________________________________________________________
2. Now Download the relevant Beta File that you intend to flash - note that to Sideload Beta 2 you need to be on Beta 1 first. Mandotory Sequence = Beta 1>>Beta 2>>Beta 3 There is no skipping versions possible here.
BETA 1 (ZTGJ) Get the Beta1.zip file from here Thanks to @thatotherguy.. for the original zip.
BETA 2 (ZTK1) Get the Beta2.zip file from here
BETA 3 (ZTK9) Get the Beta3.zip file from here
______________________________________________________________________________________________________________________________________________________________
*************** Apply Update from SD card failed for me (Feel free to try that ) but here we will be using ADB Sideload Feature in Stock Recovery*************
HOW TO - Using ADB Sideload - Windows -The Process is Similar for Linux too
1. Copy the downloaded zip file to the ADB Folder (From Pre-Requisite step). ADB Folder is the folder containing ADB.exe it might be named differently for you (The one i have posted is called platform-tools)
2. Open Command Prompt Window as Admin.
3. Type in
Code:
cd Copy-paste the location of your ADB folder here
4. Connect the phone to the PC using USB Cable and Unlock it. Go to Developer Options and Switch on USB Debugging.
To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu
5. On your PC Type in Command Prompt
Code:
adb devices
6. Give Permission that appears on your phone and PC - I check the box Always Allow, you should do the same.
7. Now type the following and the phone will reboot to recovery.
Code:
adb reboot recovery
8. Once you see recovery on your phone Use Volume Keys to scroll down to Apply Update from ADB and press Power Button.
9. Now on your PC, Type the following in Command Prompt; this is just to be sure, it should show the device name with Sideload next to it.
Code:
adb devices
10. Type
Code:
adb sideload Beta1.zip
For Beta 2 use adb sideload beta2.zip Similarly For Beta 3 use adb sideload beta3.zip. Use whatever you have named the zip file. Most people use update.zip. The commands here are for the attached files in this post and their naming convention.
11. Wait for it to finish and Done
2nd (Second) BETA Is Out- How To Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Second Beta should be flashed After Beta 1. Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 1st Beta. Download the 2nd Beta (ZTK1) Zip File to flash Here Thanks to @hayabusa1300cc for the FOTA Link.
3rd (Third) BETA Is Out- Nov 16, 2020 Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Third Beta should be flashed After Beta 1>>Beta 2. Third Beta (ZTK9) can not be flashed unless you have Second Beta (ZTK1). Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 2nd Beta. Download the 3rd Beta (ZTK9) Zip File to flash Here
OPTIONAL THINGS TO DO POST UPDATE
If you want to enable RCS (In the Native SMS app) and Native Video calling (This feature is on Tmobile) have a look at this thread.
Check out this Guide Service Mode and CSC Guide/Enable LTE/5G Bands and Services/5G Low Band on U1 by @mellojosh
TROUBLESHOOTINGSome people might run into "cant read update.zip" error for that we need to make ADB Large address aware. Follow the Steps Here I use the Advanced mode as it shows the true false flags. - This wont happen if you use the ADB Tools provided by me above under the Pre-requisites section.
************** FOR FUTURE BETA OTA Questions / Bugs - Observations and some more info - Go Here ********Please dont ask questions without reading.
QUESTIONS, HELP & SUPPORT ?? - See if I am Online here on this Live Chat
If it helped HIT THAT THANKS BUTTON, what are you waiting for ? Cheers !!
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
I get "adb: failed to read command: No error"
ekerbuddyeker said:
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
Click to expand...
Click to collapse
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
d_ganggreen said:
I get "adb: failed to read command: No error"
Click to expand...
Click to collapse
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
warriorvibhu said:
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Click to expand...
Click to collapse
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
d_ganggreen said:
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
Click to expand...
Click to collapse
Are you on ATID Firmware?
warriorvibhu said:
Are you on ATID Firmware?
Click to expand...
Click to collapse
I am, I odin flashed it a few weeks ago.
1gorelo said:
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
Click to expand...
Click to collapse
Too early in the morning to go out and test that. This is Beta and i have already encountered some bugs. So you have to be up for that.
Good Lock wont work, gesture navigation is buggy, you can not even apply wallpapers from the Galaxy Themes app.
Wallpaper Service on the other hand is greatly improved. Fingerprint sensor is much faster.
d_ganggreen said:
I am, I odin flashed it a few weeks ago.
Click to expand...
Click to collapse
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
warriorvibhu said:
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
Click to expand...
Click to collapse
Thank you! Whatever it was, that worked. I am able to get it running with your tools. I am running it now.
CHANGELOG - Android 11_OneUI 3 Beta
************ Notice: This changelog is compiled from various different resources online, verification of these features rests with the users **********
Code:
[COLOR="SeaGreen"][CENTER]BETA CHANGELOG[/CENTER][/COLOR]
[B]Home screen[/B]
– Touch and hold an app to add an associated widget
– Turn the screen off by double-tapping on an empty are of the Home screen. You can turn this on in Settings > Advanced features > Motion and gestures.
Lock screen
– Dynamic Lock screen now has more categories, and you can select more than one.
– Lock screen widgets are improved.
[B]Contacts, Phone and Call Background[/B]
– Added the ability to edit multiple linked contacts at one time.
– Added an option to help you quickly delete duplicate contacts.
– Enhanced the search experience.
– Extended the storage period of the Trash bin from 15 to 30 days.
– Added the ability to customize the call screen with your own pictures and videos.
[B]Messages[/B]
– Created a Trash bin to store recently deleted messages.
– Call & Text on other devices
– Added the ability to turn Call & text on other devices on or off with Bixby Routines.
[B]Calendar[/B]
– Events with the same start time are now shown together in month and agenda view.
– Reorganized options for adding and editing events.
– Improved layout for full screen alerts.
[B]Reminder[/B]
– Improved layout for full screen alerts
[B]Camera[/B]
– Improved auto-focus and auto exposure functionality and usability.
– Improved stabilization when taking pictures of the moon at high zoom levels.
[B]Photo editor[/B]
– Added the ability to revert edited pictures back to their original versions.
[B]Bixby Routine[/B]
– Grouped preset routines help you get started quickly and learn how to build your own routines easily.
– You can now see what actions are reversed when a routine ends.
– New conditions have been added, such as a specific start time, the disconnection of a Bluetooth device or Wi-Fi network, a call from a specific number, and more.
– New actions have been added, including talking to Bixby and accessibility actions.
– You can add a customized icon for each routine and add routines to the Lock screen for quick access.
[B]Digital wellbeing and Parental controls[/B]
– Added trends to your weekly report. You can see how your usage has changed since the previous week and check your usage time for each feature.
– Added phone usage time while driving to the weekly report.
– Added a lock screen widget so you can check your screen time without unlocking your phone.
– Added separate profiles for personal and work modes so you can track your screen time separately.
[B]Internet[/B]
– Added ability to block websites from redirecting you when you tap the Back button.
– Added warnings and blocking options for websites that shot too many pop-ups or notifications.
– Rearranged menus to make things easier to find.
– Added several new add-ons, including one that translates websites.
– Added option hide the status bar for a more immersive browsing experience.
– Increased maximum number of open tabs to 99.
– Added ability to lock and reorder tabs.
– Improved design for tab bar which is now supported on all devices.
– Ended support for Samsung Internet edge panel.
[B]Quick panel[/B]
– See your conversations and media more conveniently in their own sections when you swipe down from the top of the screen.
[B]AOD[/B]
– Always On Display widgets are improved.
[B]Accessibility[/B]
– Get quick access to the most important accessibility settings during device setup.
– Get recommended accessibility features based on what you use.
– Set the Accessibility shortcut more easily in settings.
– Sound detectors now work with your SmartThings devices such as TVs and lights to give you more visible alerts when the doorbell rings or a baby is crying.
[B]Samsung Keyboard[/B]
– You can find the keyboard in settings more easily under General management in Settings, and the settings have been reorganized to put the most important ones first.
Samsung DeX
– You can now connect to supported TVs wirelessly.
– New touchpad multi-gestures let you change screen zoom and font size more easily.
Feel free to add anything else that you observe.
warriorvibhu said:
Wohooo Fingers Crossed. Did it finish ?
Click to expand...
Click to collapse
Yes it did, running 3.0 beta now!
warriorvibhu said:
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
Click to expand...
Click to collapse
I'm on n9860 which is a snapdragon. I'm not sure if it's the same. Anyone want to try?
My US unlocked stuck at 16% when sideloading? Is it normal?
jianansong said:
My US unlocked stuck at 16% when sideloading? Is it normal?
Click to expand...
Click to collapse
Since how long ?
Which step are you at?
warriorvibhu said:
Since how long ?
Which step are you at? (See Pics)
Click to expand...
Click to collapse
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
jianansong said:
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
Click to expand...
Click to collapse
Yes thats too long Cancel and restart, It took me 97.5 seconds to verify the package.
Your ADB is fine dont change that. For firmware you can try using the second link from google drive. do you meet the criteria Unlocked and on ATID ?
warriorvibhu said:
Yes thats too long. do you meet the criteria Unlocked and on ATID ?
Click to expand...
Click to collapse
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------
jianansong said:
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
Click to expand...
Click to collapse
At the command line, I clicked "control + C" and surprisingly the progress number starts moving again, and now I am at 53% and it's still going...