yashsingh1/xdaforums huggingface dataset:
[Asus ZenWatch 2] manjulapra:
Hi,

Had a ZenWatch and recently bought a ZenWatch 2. I was trying to make calls through the watch but could not. So, I unpaired the watch, which factory resets it and uninstalled Android Wear and ZenWatch Manager. Reinstalled everything and synchronized. Now I have a additional problem other than the previous one. When I go to the contacts screen it says "No Contacts found. Add contacts to the Contacts App" and I had contacts showing before I unpaired the watch. I checked the Bluetooth Settings, both Phone Audio and Contact sharing is ON for the watch. I have given all the permissions in the watch for all the apps. Also I have enabled Phone Audio in the bluetooth settings in the watch. When I make a call (by manually entering the phone no) the call opens on the phone and audio is directed to the phone.

Watch;

Watch Android wear 1.5.0.3364142

Google Play Services 10.0.84

watch OS 6.0.1 Build M6E69S

Phone;

Nexus 6P

Android 7.0

Build NBD91K
[Asus ZenWatch 2] manjulapra:
I've resolved by giving all access rights to Android Wear in the phone. Initially it did not work, but started after multiple reboots.
[Asus ZenWatch 2] mitchiesue:
Same problem!

I am having the same problem. I got my watch a week ago, and have not been able to make calls with it at all. I did the Unpair, and now my contacts are not found. How do you give all access rights to Android Wear in the phone, because I think I've done that, but I'm not completely sure.

Thank you!!
[Android Q&A, Help & Troubleshooting] lerpicus:
I have a Samung s5 with marshmallow 6.0.0999999, or thereabouts. I am eager to learn how to flash a new rom, but my reading up on the steps to be followed leads me to a brick wall of the the difficulty of changing setenforce to permissive.

Would it make any sense to downgrade marshmallow to a version which doesn't have the setenforce problem and then flash my rom?

cheers
[Android Apps and Games] webmonch:
Hi everyone!

I want to share my new game - Cheetah Family Sim.

I bet you all have seen many simulators but this one really has some cool features that others don't - like interaction with each member of your family and upgrading your house (more are coming really soon).

The game is frequently updated and new features are added all the time.

We all know how hard it is to promote a new game without a userbase :(

Thanks for attention!
[Android Apps and Games] MirzaAwais:
Thanks for your work bro looking good and addictive. Good luck
[Android Apps and Games] cherriod:
It looks very good, nice work!
[Galaxy S 5 Q&A, Help & Troubleshooting] mr_reaper:
i need a bunch of help. getting TWRP on my galaxy S5 S930VL, rooting, and all the other good stuff. if anyone has time to help, id appreciate it.

Thanks XDA Community.
[Galaxy S 5 Q&A, Help & Troubleshooting] mortj19:
Bump
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
if it has an unlocked bootloader, just flash twrp 3.0.2 and root from recovery. but do NOT flash a pit unless instructed to do so by a dev or very knowledgeable senior member

also, i assume that youre referring to the s903vl, not the s930vl
[Galaxy S 5 Q&A, Help & Troubleshooting] mortj19:
Flashing twrp ends in fail auth with odin, phone says secure check fail: recovery
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
usually the sign of a locked bootloader
[Galaxy S 5 Q&A, Help & Troubleshooting] mortj19:
Pretty sure its not locked, its straight talk and they have unlocked bootloaders
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
im not saying it is locked, im just saying the error youre getting is usually the sign of a locked bootloader. what version of twrp are you flashing?
[Galaxy S 5 Q&A, Help & Troubleshooting] mortj19:
I tried the latest twrp for different versions of the s5 nothing has worked thus far
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
there arent different versions of the S5 as far as TWRP is concerned. There is only the qualcomm and xynos. Try a different Odin (3.7.10 is whats worked most universally for me when flashing stuff on many different galaxy devices) and dont use a twrp past 3.0.2. Stay away from 3.0.2-1 and 3.0.2-2
[Galaxy S 5 Q&A, Help & Troubleshooting] mortj19:
Tried it with same results, also if yiy check out the page for the s5 qualcomm it indeed has different versions for each model of s5
[Galaxy S 5 Q&A, Help & Troubleshooting] qkzoo:
Mortj19 did you ever get your device rooted?
[Galaxy S 5 Q&A, Help & Troubleshooting] gurnsey101:
The bootloaders on the sm-s903vl are sadly locked I am positive bc it's just another variant of the Sm-g900v (Verizon) if you take out the battery and look at the back you will see 900v. But the SM-S902L is unlocked though and very much possible to root
[Galaxy S 5 Q&A, Help & Troubleshooting] lotto44:
My understanding is it's a locked bootloader as well. Any update? If it's the same as g900v then cf auto root has root software for it. Can you just use the root for the g900v on the s903vl?
[Galaxy S 5 Q&A, Help & Troubleshooting] Shaden Stewart:
I'm going to try and see if I have any success

---------- Post added at 05:51 AM ---------- Previous post was at 05:39 AM ----------

It does not work. I'm guessing whenever Odin flashes the file since the model is different from ours it won't work. But since the phones are the same except for the model numbers and all that do you think it would be possible to edit the CF auto root file for the g900v to make it compatible with the s903vl ?
[Google Pixel XL Guides, News, & Discussion] psychatog64:
Has any one tried to see if flashing an old firmware like v after being on new to see if depixel will still work I know chase mentioned he doesn't think it will but has any one actually tired it ?
[Google Pixel XL Guides, News, & Discussion] cam30era:
If you're on NMF26O, and you try to sideload last month's V, it will fail. It will not allow flashing an older version over a newer.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
I thought we can downgrade thought that's one or the points of having a unlocked bootloader can't even run the flash all or fastboot back to a older firmware?
[Google Pixel XL Guides, News, & Discussion] cam30era:
Well yes. If your bootloader is already unlocked, you can fastboot flash an earlier factory image.

I misunderstood your question. I thought you were asking about a device with a locked bootloader.
[Google Pixel XL Guides, News, & Discussion] psychatog64:
O yea no I'm unlocked already but was curious to see if any one that's unlocked already and is updated to newest firmware if they down graded to a older firmware to try and see if depixel will work that way still
[Sony Cross-Device General] rayman:
Dirtycow-based TA Dumper for Sony Xperia Devices. (v2.0)

Author:

Jens Andersen

Xda: rayman

Twitter: https://twitter.com/EnJens

GitHub: EnJens

Source can be found on https://github.com/EnJens/backupTA.

Must be built within AOSP (e.g. checkout to external/backupTA)

Changelog:

More devices supported. The dreaded "Permission denied" should be long gone

Stability improved

TA dump is now verified before pulling

An error message is correctly shown when the process fails.

Requirements:

Phone running a dirtycow capable OS (E.g. recent N builds won't work).

If you have already upgraded, downgrading (temporarily) should be possible.

It should work on all recent xperia phones, but there might be exceptions.

It works on Linux, Windows and Mac (OS X)

Instructions:

Ensure you have adb access (e.g. drivers installed, enabled etc)

Run backupTA.sh (linux) or backupTA.cmd (windows) in the root directory.

TA will be saved as TA-ModelNumber-Serial-Timestamp.img in

the backupTA.sh directory.

On failure, the TA file should be missing, but please check that the file is 2.097.152 bytes

Download:

backupTA.zip

Credits:

rayman

Bumble-Bee (Testing)

Myself5 (Testing and some scripts)

oshmoun (Testing)

Androxyde (Testing)

munjeni (checkta source)

Tested on:

Xperia Z1

Xperia ZL

Xperia Z2

Xperia Z3

Xperia Z5

Xperia Z5 Compact

Xperia E5

Xperia M5

Xperia M4 Aqua

Xperia C5

Xperia X

Xperia XA

Xperia XA Ultra

Xperia X Performance

Xperia X Compact

Xperia XZ

XDA:DevDB Information

Universal (Dirtycow-based) TA Backup, Tool/Utility for the OEM Cross Device Development

Contributors

rayman, rayman

Source Code: https://github.com/EnJens/backupTA

Version Information

Status: Stable

Created 2016-12-07

Last Updated 2020-07-27
[Sony Cross-Device General] rayman:
FAQ:

Q: Why is the backup different between reboots?

A: There is other data stored in the TA partition than just the TA Units. On some devices, the bootloader bootlog is stored there along with other pieces of data.
[Sony Cross-Device General] rayman:
How it works

A very quick primer on how backupTA works now the source is out:

Sony's devices are extremely locked down with SELinux, and even getting root (with dirtycow) leaves you with very little access to the system.

Other than true root (which is rather difficult to get, although not impossible), only the Sony TA daemon has access to the partition required. But the TA daemon has no access to write any files anywhere on the device where we can pull them...

The basic approach is:

* Overwrite run-as binary with a custom binary

* When executed it switches to root and sets platform_app permissions, which for some bizarre reason is allowed from run-as explicitly. (See note 1)

* Once it has these privileges, it has access to dirtycow /sbin/tad_static

* It overwrites tad_static with a special daemon that allows reading the entire TA partition over the tad socket already used by the system. (See note 2)

* The run-as replacement reads the TA dump over the tad socket and pipes it to stdout to write to a file. (See note 3)

Note 1:

Dirtycow cannot increase the size of any binaries on the system, so to make things actually work, this solution also overwrites screenrecord binary (which is significantly bigger). run-as then executes this after setting up root and does all the fancy things. On some devices the platform-app context with root does not allow reading or writing files anywhere. To get around this, it reads the replacement tad_static from stdin and writes the dump to stdout. The script that runs run-as handles the piping.

Note 2:

When tad_static is first executes during boot, it's cached by linux. For efficiency reasons and because it's on a read-only filesystem, it's executed from this cache in memory. When dirtycow replaces the binary on /sbin, it actually replaces the running binary's code in memory, forcing it to crash. Init automatically restarts it, but now it's the replaced binary running which allows us to dump what we need.

Note 3:

The tad socket is actually quite limited permission-wise too. Only a limited subset of selinux contexts are allowed to read/write to it and the same goes for users. Luckily, root user with some supplementary groups, and the platform_app selinux context does have access to it, so we abuse that fact to talk to the replaced TA daemon.
[Sony Cross-Device General] josephnero:
Awesome. was waiting for this.thanks
[Sony Cross-Device General] Myself5:
Second!
[Sony Cross-Device General] kistigun:
wow nice find! I'm a bit bumped out I allready unlocked my booloader but this is great news!
[Sony Cross-Device General] serajr:
Awesome... Congrats!!

XP F8131 output :good:

Picking 64-bit version
Running on F8131 on 64-bit platform
Pushing files
886 KB/s (9984 bytes in 0.010s)
743 KB/s (6088 bytes in 0.008s)
1072 KB/s (14280 bytes in 0.013s)
901 KB/s (10184 bytes in 0.011s)
122 KB/s (876 bytes in 0.006s)
Running scripts to dump ta to "TAIMG" on device
Overwriting run-as
Attempting to dirtycow
Done dirtycowing
Overwriting secondary payload (screenrecord)
Attempting to dirtycow
dirtycow failed
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Attempting exploit
Attempting to dirtycow
dirtycow failed
Waiting for result....
Bad reply received, failing...
Attempting exploit
Attempting to dirtycow
Attempting to dirtycow
dirtycow failed
Waiting for result....
Got a total of 2097152 bytes
Exploit successful!
Dumped TA as TA_F8131_CB512AD0TJ_06122016-2207.img
Pulling image
735 KB/s (2097152 bytes in 2.784s)
Cleaning up
TA Sucessfully pulled to TA_F8131_CB512AD0TJ_06122016-2207.img
****NOTE: Please verify filesize is 2MB ****
Pressione qualquer tecla para continuar. . .

Just a quick heads up. The first attempt failed because /data/local/tmp was not empty! It has two "flat..." files inside it (Stock fw).

Fix can be to change .sh and .cmd scripts to chmod each pushed file separately (instead of *), or even clear that folder.

Picking 64-bit version
Running on F8131 on 64-bit platform
Pushing files
180 KB/s (9984 bytes in 0.054s)
742 KB/s (6088 bytes in 0.008s)
1983 KB/s (14280 bytes in 0.007s)
1421 KB/s (10184 bytes in 0.006s)
213 KB/s (876 bytes in 0.004s)
[COLOR="DarkRed"]chmod: chmod '/data/local/tmp/flatland' to 100755: Operation not permitted
chmod: chmod '/data/local/tmp/flatland64' to 100755: Operation not permitted[/COLOR]
Running scripts to dump ta to "TAIMG" on device
...

Anyways... It did work like a charm! Respect!!
[Sony Cross-Device General] Sonic Dash:
So just to confirm, this fully backs up the TA partition including DRM keys on the Xperia XZ. So it's okay for me to now unlock the bootloader and restore everything with this? If so this is just what I've been waiting for!
[Sony Cross-Device General] alex.do:
Just to confirm, after TA (including DRMs) is backed up, I can unlock -> root -> then relock + restoring TA so I can have both root and DRMs working flawlessly? including OTA updates?
[Sony Cross-Device General] DannyWilde:
I don't think root with locked bootloader is possible. But if you got TA backup you can restore whenever you want and relock bootloader. Maybe important if you want to sell phone or if you need guarantee. [MENTION=962182]rayman[/MENTION]

Will it be possible to create. ftf to flash drm key just like in Z5 line?
[Sony Cross-Device General] Aaskereija:
Whats the difference?
[Sony Cross-Device General] DannyWilde:
Difference to what? Your in German "android-hilfe", right? :)
[Sony Cross-Device General] rayman:
Good point. I went lazy-mode and just chmod'ed it all and assumed everything there would be shell-user owned...I guess that doesn't always stand true. I'll fix it up.

In theory. I've verified it makes a 100% accurate copy of the TA Partition. I can't realistically guarantee anything else, but yes, it *should* work like that. That's kind of the point.

Probably not... The second you flash back the locked TA, signed boot images will be required again and signed boot images mean dm-verity, meaning verified /system partitions, so it wouldn't boot anymore without 100% stock firmware.

I don't see why not, but YMMV. It's certainly possible to extract the DRM key from the backup created by this tool and if Flashtool/bootloader allows flashing the data to a TA unit, it'll be possible.
[Sony Cross-Device General] Myself5:
Difference to what? As of now, there is no tool to backup the TA on Android Versions above 5.1.1 (last Version where iovyroot worked on), exept this one ;)

But shouldn't it just go on? I had the chmod failure during the final tests yesterday too, but I'm pretty sure it was just going on at that time.
[Sony Cross-Device General] Heesue:
How can I restore TA? I Backed up TA.
[Sony Cross-Device General] shoey63:
Unlock bootloader, flash TWRP, boot to TWRP, adb shell and use dd command to flash TA image back. Then power off and flash stock system, fotakernel and kernel with flashtool.
[Sony Cross-Device General] danilo_scala:
thanks great work friend, tested in xperia z5 premium
[Sony Cross-Device General] Heesue:
Thanks a lot! :D:D
[Sony Cross-Device General] drubio:
AWESOME!!!

Very Good Job Guys!

BIG THANKS
[Sony Cross-Device General] ggow:
Xperia X Compact

Seemed to work on Xperia X Compact:

Running 34.1.A.1.198 firmware

Really nice work :)

Output

Running on F5321 on 64-bit platform
Pushing files
[100%] /data/local/tmp/dirtycow
[100%] /data/local/tmp/run-as
[100%] /data/local/tmp/exploitta
[100%] /sdcard/dumpta
[100%] /data/local/tmp/backupTA.sh
Running scripts to dump ta to "TA_F5321_QV705K140B_20161207-1151.img" on device
Overwriting run-as
Attempting to dirtycow
Done dirtycowing
Overwriting secondary payload (screenrecord)
Attempting to dirtycow
dirtycow failed
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Attempting exploit
Attempting to dirtycow
dirtycow failed
Waiting for result....
Bad reply received, failing...
Attempting exploit
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Waiting for result....
Error connecting to unix socket: No such file or directory
Attempting exploit
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Waiting for result....
Error connecting to unix socket: No such file or directory
Attempting exploit
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Waiting for result....
Got a total of 2097152 bytes
Exploit successful!
Dumped TA as TA_F5321_QV705K140B_20161207-1151.img
Pulling image
[100%] /data/local/tmp/TA_F5321_QV705K140B_20161207-1151.img
Cleaning up
TA Sucessfully pulled to TA_F5321_QV705K140B_20161207-1151.img
****NOTE: Please verify filesize is 2MB ****
[Sony Cross-Device General] dhchris:
Hey [MENTION=4120742]munjeni[/MENTION],

nice to see you since you developed z1c roms.

I´ll try your tool, but, do you have a scriptfile (no windows - exe) for Linux/OSX - Systems?

Edit:

(Tried it in my parallels-Windows-System -> "Trim area dump is valid") - NICE !!! :good: Good job...

Now I´ll try to backup devicekeys
[Sony Cross-Device General] shoey63:
Can the tool be modified to do an md5sum check of the TA partition before creating the image?
[Sony Cross-Device General] munjeni:
Edit:

No need since v2 rel verifies trim area
[Sony Cross-Device General] rayman:
Version 2 Released

Version 2 is now released.

Changelog:

More devices supported. The dreaded "Permission denied" should be long gone

Stability improved

TA dump is now verified before pulling

An error message is correctly shown when the process fails.
[Sony Cross-Device General] darwusch:
Thanks, on my Xperia XA Ultra (F3211) it works now :)

Picking 64-bit version
Running on F3211 on 64-bit platform
Pushing files
Pushing files/dirtycow64 to /data/local/tmp/dirtycow
319 KB/s (9984 bytes in 0.030s)
Pushing files/run-as64 to /data/local/tmp/run-as
2972 KB/s (6088 bytes in 0.002s)
Pushing files/exploitta64 to /data/local/tmp/exploitta
3984 KB/s (14280 bytes in 0.003s)
Pushing files/dumpta64 to /data/local/tmp/dumpta
2486 KB/s (10184 bytes in 0.003s)
Pushing files/checkta64 to /data/local/tmp/checkta
3976 KB/s (10184 bytes in 0.002s)
pushing push files/backupTA.sh /data/local/tmp/backupTA.sh
447 KB/s (1094 bytes in 0.002s)
Running scripts to dump ta to "TA_F3211_WUJ01NB0DP_ma19-12-201623-1237.img" on device
Overwriting run-as
Attempting to dirtycow
Done dirtycowing
Overwriting secondary payload (screenrecord)
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Reading dumpta from stdin...
Read dumpta from stdin at 10184 bytes
Attempting exploit with buf of length 10184
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Waiting for result....
Bad reply received, failing...
Attempting exploit with buf of length 10184
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Attempting to dirtycow
Done dirtycowing
Waiting for result....
Got a total of 2097152 bytes
Exploit successful!
Dumped TA as TA_F3211_WUJ01NB0DP_ma19-12-201623-1237.img
adler32:0x42BFFFA9 calc_adler32:0x42BFFFA9
adler32:0x6A63D573 calc_adler32:0x6A63D573
adler32:0x2071DD10 calc_adler32:0x2071DD10
adler32:0xCF6754B5 calc_adler32:0xCF6754B5
adler32:0xBDE98BE9 calc_adler32:0xBDE98BE9
adler32:0xC3B50691 calc_adler32:0xC3B50691
adler32:0x43B2545C calc_adler32:0x43B2545C
Trim area dump is valid.
Pulling image
9061 KB/s (2097152 bytes in 0.226s)
Cleaning up
TA Successfully pulled to TA_F3211_WUJ01NB0DP_ma19-12-201623-1237.img
Press any key to continue . . .
[Sony Cross-Device General] BITS74:
Thanks Bro It works on Xperia Z3+ :good:

Can be added to the list of supported devices
[Sony Cross-Device General] porroni:
All good on Xperia M4 Aqua! Good job ^^ Now I can go ahead and unlock the bootloader!
[Sony Cross-Device General] s6182:
Must be root to convert ta.img to ta.zip

http://xdaforums.com/showthread.php?t=2292598

Does not give the ability to convert ta.img to ta.zip

Just ask me to connect my xperia
[Sony Cross-Device General] petrutms:
I made successfully TA Backup on my Xperia Z5P (Thank you, rayman!). I can now unlock the bootloader to root my phone, then to restore TA Backup? You can suggest me any tutorial in this regard, now that I already have TA Backup (simple way)? Thank you!
[Sony Cross-Device General] s6182:
+1 :confused:
[Sony Cross-Device General] STreeTNerD:
Yeah that would be good if someone could make a tutorial. Christmas wish and all that. ?
[Sony Cross-Device General] gregbradley:
The new version of flashtool is now Nougat compatable. It will also use this tool to take a TA backup AND RESTORE IT.

www.flashtool.net v 0.9.23.0
[Sony Cross-Device General] STreeTNerD:
When did he update it. Why is it same same version number?
[Sony Cross-Device General] gregbradley:
Today and its not the same version number

New version number is 0.9.23.0 old version number is 0.9.22.0
[Sony Cross-Device General] STreeTNerD:
That's mate. Can't wait to get home now, to flash my UK ftf. Might even unlock my bootloader tonight. Been on the fence about it. ?
[Sony Cross-Device General] s6182:
Flashtool flash ta.img but leaves the bootloader unlocked?

I want booloader unlock + ta + recovery + supersu

Can I unlock, recovery, root + ta
[Sony Cross-Device General] bhz21:
Quick question. (Sorry if it's a dumb one)

If I backup TA, unlock bootloader, root, restore TA, what will happen when nougat arrives for my device? (Xperia Z5 Premium)

Will I be able to update? If yes how? (OTA, flash ftf), and will I lose something? (Like root {or TA, idk :p})

Really appreciate any help. :o
[Sony Cross-Device General] rayman:
It's not possible. The second you relock bootloader by flashing TA back, boot image must be signed again which means /system will be protected by dm-verity so any changes to it will cause failure to boot.
[Sony Cross-Device General] bhz21:
Thanks for the reply. I see... So, if I just keep TA backed up in my PC for future use (and don't flash it to the phone) I can have root. Right?

Now, when Nougat arrives for my phone, can I update (directly, without recovering TA and relocking the bootloader), keep root and at a later moment (if I want to sell the phone or send it to warranty) flash TA back in Nougat and have a "untouched", locked bootloader phone?

Sorry, I know that's a lots of "if's" and questions but I'm just confused how the phone behaves in such modding conditions.

:)
[Sony Cross-Device General] YoLO13:
Extraction of DRM keys

Hi there,

I've used this tool to backup my TA and I just wanted to say thanks for producing this tool!

I've been trying to extract the DRM keys from this using the following tool:

http://xdaforums.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605

However, it hasn't been successful and keeps returning the same error.

Is there any way in which I could test the validity of the backup without unlocking the bootloader, because I really want to keep the DRM keys intact until I can extract them from a backup and flash them once rooted?

Thank you for your guys' help!!

------------------------------------------------------------------------------------------------------------------------

Edit: Figured out my mistake and the backups appear just fine!

Merry Christmas to you all!!
[Sony Cross-Device General] xrenoix:
great work [MENTION=962182]rayman[/MENTION] thank you so much

my device : xperia z5 premium 6.0.1 32.2A.5.11