yashsingh1/xdaforums huggingface dataset:
[LG Optimus G (International)] kimitza:
Your builds are getting better and better,but that damn wi-fi slugginesh is keeping me away. I wish you would have the time to work on an asylum from lg source:).

Sent from stock LG E975/smart phones,dumb people.
[LG Optimus G (International)] bangsti:
Asylum_CM10.2_20131030_e975.zip - is up on Asylum FTP Server and MediaFire

http://team-asylum.org/download/AsylumRoms/CM10.2/LG-E975/

http://www.mediafire.com/folder/k156yv5rlrccn/TeamAsylum

MD5:42F0D4A4A6DCEE3F50D4145A321EC6A4 *Asylum_CM10.2_20131030_e975.zip

Repo sync 16.00 CET

Changelog: http://10.2.cmxlog.com/?device=e975
[LG Optimus G (International)] Moepda:
E975 mod files 301013

UPDATE CM10.2 301013

Nothing different on mod files today 30 october

MOD FILES FOR USE ON E975 CM10.2 ASYLUM BUILDS 27/29/30 OCTOBER

MoEpDa Fleshable™ Files Mediafire

MoEpDa Fleshable™ Files FTP

+

Asylum build mirrors...

Mediafire Mirror

Bangsti FTP Mirror

+

MoEpDa TinyGapps only 30-38mb (Inc. latest multi dpi playstore 4.4.21 either normal or inverted) **UPDATED 221013**

TinyGapps

TinyGapps mirror

+

Flashable Lockrings for AOSP/AOKP/PA/CM Roms

Flashable Lockrings

Flashable Lockrings mirror

Please always appreciate and say thanks to BANGSTI for building this asylum rom & the kind use of his ftp hosting...
[LG Optimus G (International)] kimitza:
wow...you spoil us :)...now i'm at work...will try latest build tomorrow...and see if i can get a workaround with the wi-fi:)
[LG Optimus G (International)] davevinci:
Is ur wifi issue same with CM 10.2 builds? I was thinking you can use other wifi modules...
[LG Optimus G (International)] kimitza:
yep,since asylum is based on latest cm builds,it has the same bugs.

to make a comparison,the download speed on stock is about 8mb/s(on my belking N router),while on cm based roms is less than 300kbps.

Tests being made with real file download,not speedtest.
[Xperia Z1 Android Development] DooMLoRD:
there is a good reason why there is a script to do this...

the TA is VERY VERY DANGEROUS AREA... any minor mistake and you WILL BE LEFT with bricked device...

DO NOT TRY MANUAL WAY!

one small mistake in the partition layout (command typo) and you might wipe the bootloader or corrupt the partition table...

please i strongly advise that you DO NOT play with TA...

FYI this is the partition layout for the Z1:

root@android:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-21 17:03 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-21 17:03 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-21 17:03 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-21 17:03 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-21 17:03 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-21 17:03 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-21 17:03 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-21 17:03 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-21 17:03 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-21 17:03 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-21 17:03 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-21 17:03 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-21 17:03 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-21 17:03 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-21 17:03 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-21 17:03 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-21 17:03 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-21 17:03 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-21 17:03 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-21 17:03 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-21 17:03 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-21 17:03 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-21 17:03 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-21 17:03 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-21 17:03 userdata -> /dev/block/mmcblk0p25

thanks to [MENTION=2546099]yeeson[/MENTION] for fetching this info!
[Xperia Z1 Android Development] Rekoil:
Thanks for the info mate, though I do understand your point I would like to point out that running random scripts on sensitive areas is in my opinion much more dangerous than actually knowing what you are doing, and really isn't something that should be promoted in general (I understand why it is in this case). I personally trust myself not to make those kinds of mistakes much more than I do some random person on the internet. Especially when options aren't provided for operating systems other than Windows I feel that this guide is still needed.

We should be teaching people, not simply providing a solution (to something which someone who doesn't know what he is doing should even be tinkering with to be honest).

Had forgotten about the named symlinks, thanks for that! Updated tutorial.
[Xperia Z1 Android Development] bbkdhumm:
OMG !!! So many partitions. Is there a place where to find their purpose ?

One question please: waht does "TA" stand for ?

And finally: I agree... Such informations are HIGHLY dangerous in unexperienced hands. Sooooo easy to brick a phone...
[Xperia Z1 Android Development] Rekoil:
Aw come on guys, it's not that difficult of a guide to follow is it? Besides, how do you become experienced without ever trying? After all, this is a fairly technical forum.
[Xperia Z1 Android Development] bbkdhumm:
Did you never notice posts by novices having problems following guides?

Envoyé depuis mon GT-I9300 avec Tapatalk 4
[Xperia Z1 Android Development] peetr_:
I do agree with you completely.

When playing with partitions, manual way is the best way. And this is development forum. All possible info should be here. Noone should discourage you from posting any info, if you are warning the people that it's dangerous.
[Xperia Z1 Android Development] Mi|enko:
I seem to remember a time when people wouldn't host kernels or recoveries as update-able zips, because it didn't drive any knowledge into the users. Then, if something went wrong, they were ill equipped to deal with it. I'm all for automated tools, but see absolutely nothing wrong with sharing the manual know how.
[Xperia Z1 Android Development] jos_031:
Linux is best for all mods
[Xperia Z1 Android Development] Option58:
Although I appreciate your efforts in creating this thread. I advice users to use this automatic tool and full of safety checks. It worked for me. And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!

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

Greetings
[Xperia Z1 Android Development] Rekoil:
Yeah, great option for Mac and Linux users.

So does the manual method. In fact, I learned how to do it manually from studying that tool.
[Xperia Z1 Android Development] harfot:
No one will ever learn without trying new things.

You can even break a phone by flashing it with proven programs not reading instructions carefully, so I find it OK to give the opportunity for the users not using windows especially as you have given good warnings.
[Xperia Z1 Android Development] raimondomartire:
Anyone have noted that in 5.34 commercial&journalist version ta file it's cust-reset.ta and in central europa simlock.ta?
[Xperia Z1 Android Development] Planet X:
Do I have to make a new TA backup after I have updated to .534 ?
[Xperia Z1 Android Development] Desperanto86:
no
[Xperia Z1 Android Development] Shaky156:
@ OP why /platform/msm_sdcc.1/by-name/TA why not point directly the mmcblk0p1 TA partition?

e.g.

This:- dd if=/dev/block/mmcblk0p1 of=TA.img

Instead of:-dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img

I'm just nitpicking lol
[Xperia Z1 Android Development] Rekoil:
Both are fine, but in case a new phone comes to market that for some reason puts boot image at /dev/block/mmcblk0p1 and TA at /dev/block/mmcblk0p2 or something like that, I thought it was best to just point to the symlink instead, so as to definitely make it future proof.
[Xperia Z1 Android Development] maltloaf:
Thank you for this thread. I have backed up my TA for my new Z1 and stored it away.

malty
[Xperia Z1 Android Development] iconoclastnet:
How sure is that? I noticed that my TA did change with the update to .534 (based on md5sum). Can I freely mix-and-match my different TA backups (from the same device of course) with whatever (official) kernel version? Are they perhaps forward-compatible only (perhaps for downgrade prevention or something) and I should really keep the oldest one?
[Xperia Z1 Android Development] Desperanto86:
TA is CONSTANT like IMEI!
[Xperia Z1 Android Development] Michealtbh:
Is it possible to make a TA backup using a terminal emulator on a rooted Z1?
[Xperia Z1 Android Development] iconoclastnet:
Well, it's md5 seems to have changed, at least for me.

I took a backup of it first thing when the phone arrived, hadn't even put the sim card into it yet, rooted and backed up the TA partition and compared the md5 sum of the backup with the partition.

Then I poped in a sim card, did the usual setup stuff, played with the phone for a few days, did the ota of 518 -> 534, etc.

Before unlocking the boot loader I double checked the TA partition backup, and the md5 sums no longer matched. So I made another backup alongside the original, checking the md5 sums of the new backup, etc.

So, I have two TA backups made at different times from the same phone and they're different in some way. It may only be one bit, I haven't checked to see just how different they are, but they are different. At the time I assumed that it was related to the 534 upgrade, but that may have been just coincidental.

I have no doubt that they're unique to each device, but I'm not convinced that they're constant.

---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------

Yep. Just make sure to copy the resulting backup somewhere safe (off of the device) at some point afterward.
[Xperia Z1 Android Development] Desperanto86:
You have backuped full TA image, which contains many different information, but we need only DRM KEYS inside it! They are constant, I meaned that. This keys like digital sign. And they are depend from IMEI.
[Xperia Z1 Android Development] gregbradley:
Reading the guide from the ta backup tool it clearly stated that the ta is created at each bit and may not even be the same size on each boot but the important bits are preserved so just one backup will suffice
[Xperia Z1 Android Development] iconoclastnet:
Ah, ok. So the TA may change, but the parts that we care about won't. The backups that we're making also have some less important stuff in them as well, but effectively any good valid backup will work for the device it belongs to. Makes sense to me. Thanks for clearing that up!
[Xperia Z1 Android Development] shawnhalu:
Hi there, been in the samsung scene for quite awhile, so i am new to the sony one.

i do not understand abt the abd, but i have google it and it seem to be like cmd in windows? haha, but i do not know how to get access to it in windows.

how shld i start to back up the TA using your guide?

Do i have to Backup the TA everytime i updated the firmware to a newer one? as i read thru all the threads here seem like the TA changes abit after u update?
[Xperia Z1 Android Development] Rekoil:
You only need to back it up once, and if you don't know how to use adb in Windows you might be better off using the automated tool posted here instead.
[Xperia Z1 Android Development] shawnhalu:
ok but i wish to learn abt what u saying at 1st. so can u giv me some more info? if u have the time :)
[Xperia Z1 Android Development] Rekoil:
Sure, always happy to help! Have a look here for a quick little tutorial I just googled up on how to navigate your computer via the command line. You will also need to install the correct drivers for the Z1, available here and the ADB tool, available from the Android SDK, which you can get here, you will probably need to browse to where the ADB.exe application is installed for it to work. I think it is great that you want to learn, but please be very careful when you finally follow my guide, as you can (at least when restoring) actually cause a lot of damage to your phone if you do it incorrectly. Good luck!

Please click the thanks button if I've been helpful!
[Xperia Z1 Android Development] shawnhalu:
ok i try to read thru everything and get back to u :)
[Xperia Z1 Android Development] gladiac:
I just checked with vbindiff what contents actually change after the OTA upgrade. The first part is identical. This was to be expected since that part contains device specific information like the IMEI (0xB2D), SN#, ... . At 0x33D8 are OS version strings stored - which changed since the OTA. In my case that values changes from "1274-8313_14.1.G .1.518" to "1274-8313_14.1.G .1.534". That behaviour was also to be expected. After that, large parts of the files differ. Many of those differences ist just shifted (by some bytes) data. Other parts actually changed entirely. Not sure what is going on there. Be it as it may, i would only restore the newest TA-backup.

Cheers
[Xperia Z1 Android Development] shawnhalu:
ok i have read thru n roughly know how to do it. but just a question that is the only way to do it is with cmd?
[Xperia Z1 Android Development] Rekoil:
You're gonna have to be a little more specific than that. Which command are you talking about?
[Xperia Z1 Android Development] shawnhalu:
i mean i only can use command prompt to do it? with all the command?
[Xperia Z1 Android Development] Rekoil:
To do what, backup the TA? No, you can use the script here as well, but I thought you wanted to learn how to do it?
[Xperia Z1 Android Development] shawnhalu:
ya but i tot the adb stuff is using command prompt to do it? the script u gave is the auto one right.

i am trying to understand how adb works and how to do it.
[Xperia Z1 Android Development] colors:
Plz help guys. I have unlocked my bootloader, fixed the correct recovery, flashed doomkernel and after that flashed a custom rom. Rebooted phone and did my TA restore. Now the phone wont boot. I can connect to it thrue fastboot but what then? Any tips? Is it bricked? :S

(i have a backup on the phone, can i flash that .img anyway?)

EDIT: omg i was nervous there... Installed update_service_setup from sony and now the phone is back to normal! Lost recovery, root and everything but the phone starts! =)
[Xperia Z1 Android Development] Rekoil:
Yeah you can't run DooMKernel with a locked bootloader, which is what you get after restoring TA.
[Xperia Z1 Android Development] colors:
Okey, so thats why the phone went wierd. Tought i was doomed :P Will be more careful after this.. Stay on stock for a while, but i shouldnt mind root. But thats more complicated now when kingoapp and vroot cant root. 257. I dont have the energy to downgrade etc
[Xperia Z1 Android Development] Rodrigo Vilhena:
First Thank you very much for the post! I really appriciate that.

I have tried the automatic way, but did not worked to me so I used yours tutorial.

I just want to be sure I'm safe, I did on windows and in the and there is only one file TA.img, correct?

Just need to save that file and I'll be fine?

Thank you.
[Xperia Z1 Android Development] Rekoil:
Yes, if you followed the guide all should be well.
[Xperia Z1 Android Development] darknessmc:
if i loss everything, IMEI, DRM Keys, loader and hard-brick my device, can the service center of sony in my country restore my device on?
[Xperia Z1 Android Development] Rekoil:
No for two reasons.

One: they won't.

Two: the service center has no more information about the specific data on your phone than you do after you've wiped it.
[Xperia Z1 Android Development] BLiapis:
So by manually partitioning, anyone loaded linux or WinOs as dual/triple boot, and how is it working?
[Xperia Z1 Android Development] Rekoil:
I think you've misread the topic, this isn't about partitioning, but about manually backing up specifically the TA partition.

...besides, just being able to repartition the storage isn't enough to boot another operating system.
[Xperia Z1 Android Development] tdthd:
If I backup the partition ta in 534, the upgrade to 290 and open the bootloader. If you ever want to restore the backup, that version of the rom I have to?
[Xperia Z1 Android Development] Rekoil:
I presume you mean to say that if you want to restore, then you need to first flash .534? If that is what you are asking the answer is no, you just flash a stock ROM (any version), then follow the instructions in first post to restore the TA partition.
[Xperia Z1 Android Development] alex_hk90:
Just posting to say thank you for this - I'm on Linux so can't use the Backup TA scripts but this was quick and easy and seemed to work fine for my Sony Xperia Z1 Compact (rooted with bootloader locked). :)

The TA.img file for my phone was 2.00MB, does that sound about right?
[Xperia Z1 Android Development] Rekoil:
Yes, that is correct!
[Xperia Z1 Android Development] Ricky Divjakovski:
nice guide, better to make a tool to do it, my SamsungTool detects what block the EFS partition is at, and parses it to shell to backup the block, thus making it universal for eternity and i could add support sony devices TA partitions, will release a tool in a few days
[Xperia Z1 Android Development] Aust S5:
Thanks for the guide, in principle will the instructions also for for the z2? Trying to find a guide to backup TA with the z2 while on linux. I am fluent with adb fastboot etc just curious about the partitions, spose I could follow doomlords command to get the various partitions. z2 is rooted with the bootloader locked.
[Xperia Z1 Android Development] Rekoil:
Sorry I missed your post, I'm hoping you sorted it out, but for future reference and anyone else wondering the same thing, yes, it is generally the same for all Sony devices. Get root, adb in, dd ta partition, make sure you got a clean backup, store it on computer, go on your merry way.
[Xperia Z1 Android Development] Daedroza:
Hello,

I have used TA BACKUP MANAGER BEFORE,

It has created a *.zip which has TA.img file with various other files.

I am running ubuntu now a days, can I use this method? are other files required in the zip?? thank you!
[Xperia Z1 Android Development] boardlord:
Is this applicable to the Z3C?

For some reason or other my I cannot use the TA Backup script, it cannot find the TA partition if my Z3C.

However, using the commands in the OP I successfully backed up my *hopefully* TA partition. My question is, has anyone tried these command line instructions on a Z3C? Did I really get my TA partition using these instructions? I'll want to try CM12 once it's more mature, but I want to have my DRM keys just in case I have to send the phone in for warrabnty in the future :)
[Xperia Z1 Android Development] Me Gusta:
Sweet Jesus. This just saved my Xperia Z3 after Backup TA got corrupted files while transfering over and over..

Thanks OP!

Oh, and [MENTION=297867]boardlord[/MENTION] if it still matters, yes this works :D
[Xperia Z1 Android Development] micw:
Nice tutorial. I did it exactly the same way when I rooted my z3 tablet the 1st time because I did not want to rely on someone other's script and I wanted to understand how things works.

I'd recommend to do md5sum on the image after dowloading with adb again. Also store the md5 sum together with the image and verify it BEFORE you dd it to the partition! If you write a corrupt image to the partition, you will probably hard-brick the device.

It would also be a good idea to backup the partition before writing the old img to it.
[Xperia Z1 Android Development] Coudy:
Hi,

I have question. I'm on latest stock rooted rom on Xperia Z1C . When I check DRM keys in security menu, all keys are on and active, but when I flash another custom rom (not AOSP), and check DRM keys, then first 3 keys show Unknown error, but they are active. I have questions:

1. so are or are not that keys active ?

2. when I recovery TA keys on another rom, my phone goes to bootloop. I need reflash it again. How to avoid that ?

Thank you
[Xperia Z1 Android Development] AsureDawn:
Tutorial wasn't super useful on my XA (F3113), but at least got me going in the right direction.

Did `cat /proc/partitions`, found the one which matched the TA.img size and wrote the image to that partition. At that point, I checked the hash, rebooted, and was stuck in a bootloop (but at least it was booting). Ran device repair from Xperia Companion (which only runs if your device is locked--note that this will wipe everything and reinstall the original rom/bootloader), now boots fine.
[Android Q&A, Help & Troubleshooting] nijohnson:
Hi all,

So I am looking for a widget, and having trouble identifying if it exists. I'd like some thing that displays a message that I set. This message would change daily based on a small set of messages I input. Transparency is important too.

Any ideas?

Thanks,

NJ
[Galaxy S III Themes and Apps] TheDarkLegend:
any one give me a transparent status bar mod "looks like the s4" for i9300 leaked 4.2.2 PLEASE :)
[Galaxy S III Themes and Apps] jorse912:
Done
[Galaxy S III Themes and Apps] Blackwolf10:
install xposed and get wanam xposed it has that option and many more
[Galaxy S III Mini Q&A, Help & Troubleshooting] JackoMJ:
hi guys,

anyone an idea to disable (hack, apk, ...) the wifi popup notification whenever wifi is connected.

This drives me crazy ... :(

This notification is absolutely senseless, when connection is on i see it in the notification bar ...

I found a description but only for S III Verizon.

JackoMJ
[Galaxy S III Mini Q&A, Help & Troubleshooting] somin.n:
Hi! Try this:

- decompile secsettings.apk

- go to file "smali\com\android\settings\wifi\WifiStatusReceiver.smali"

- open in notepad++ and find this code:

.line 194
invoke-virtual {v3}, Landroid/widget/Toast;->getView()Landroid/view/View;

move-result-object v1

const v4, 0x102000b

invoke-virtual {v1, v4}, Landroid/view/View;->findViewById(I)Landroid/view/View;

move-result-object v1

check-cast v1, Landroid/widget/TextView;

.line 195
const/16 v4, 0x11

invoke-virtual {v1, v4}, Landroid/widget/TextView;->setGravity(I)V

.line 196
[COLOR="Red"]invoke-virtual {v3}, Landroid/widget/Toast;->show()V[/COLOR]

goto :goto_1a3

And change it to (just add # before it):

[COLOR="Red"]#invoke-virtual {v3}, Landroid/widget/Toast;->show()V[/COLOR]

Thats all - save, recompile, copy to phone, restart and hope :p
[Galaxy S III Mini Q&A, Help & Troubleshooting] JackoMJ:
Hi somin mf,

WHAT THE HELL IS GOING ON?

you are the best. Works perfect. No f****** popup any more.

How do you know or find this out because i think it´s not easy to make it. :confused:

JackoMJ
[Galaxy S III Mini Q&A, Help & Troubleshooting] somin.n:
Hehe, you are true, it is not so easy, maybe it was luck that I find it. How I find it?

- i was looking for wifi is connected to bla,bla,bla string in system apk's

- then I find its public id in public.xml file

- then I was looking for this id in *.smali files

- and then it was luck that I find proper line "invoke-virtual {XX}, Landroid/widget/Toast;->show()V", I just know that this line is making toast messages

There was some bad tests, but one of my try was working. And here is result ;)
[Galaxy S III Mini Q&A, Help & Troubleshooting] JackoMJ:
Thanks for your time and patience you spent on it.

Do you make every test like me (decompile, change, compile, copy to phone, reboot)?

Hope your Powerbutton won´t break ;)

Or is there a program you can simulate it on your pc without using your phone really?

That´s a very interesting question i think....

JackoMJ
[Galaxy S III Mini Q&A, Help & Troubleshooting] somin.n:
Yes one change and whole process with de/compile,restart,... in round. Don't know about pc sw to simulate it, but yes it would be great. And don't worry about my power button, sometimes I have to pull out my battery because of bootloop :laugh::victory: