yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] Andrzej_Andrzej:
Thank you for your prompt reply, It is better now, I checked scripts folder but now I got this:

"Making ramdisk/stufs folder... done

Found android version equal or greater than Marshmallow.

Making ramdisk/init.ta.sh script... cp: can't stat 'binaries/init.ta.sh': No such file or directory

done

Error! Didn't found any file which contain string: service tad_static!

command ret: 1.

Your script didn't returned 0, please check your script!

Press any key to continue . . ."

Can you advise whta should I do now?

kind regards,

Andrzej_Andrzej

---------- Post added at 12:51 PM ---------- Previous post was at 12:39 PM ----------

And I forgot to add, in the instruction how to use ta_poc it says:

"How to use: Put your trim area backup (TA.img) in the same dir with .exe

Do the same with kernel, open DOUBLECLICKME.bat with text editor and change kernel name!"

Should I rename the name of the kernel , and to what ?

regards,
[Sony Cross-Device General] juanpirulo:
Extract poc_ta.zip and copy Ta.img boot.img/sin/elf and try in a new clean folder. You should only rename kernel when its done. if there is no errors script create new_boot.img which you will have to rename to boot.img
[Sony Cross-Device General] Andrzej_Andrzej:
Unfortunately stiil the same:

"Runing user script...

Making ramdisk/stufs folder... done

Found android version equal or greater than Marshmallow.

Making ramdisk/init.ta.sh script... done

Error! Didn't found any file which contain string: service tad_static!

command ret: 1.

Your script didn't returned 0, please check your script!

Press any key to continue . . ."
[Sony Cross-Device General] shoey63:
Do it again. Except this time put TA.img, kernel.sin (NOT FOTAKernel. sin)! and TWRP recovery image (name it to recovery.img) for your device into poc folder, and follow the prompts.
[Sony Cross-Device General] Andrzej_Andrzej:
Actually I do not have a file named kernel.sin - I have got a file Fotakernelxxxxx.sin

I downloaded this stock rom by xperifirm form Flashtool. My phone xperiaXA F3111 is operating on this stock rom now. Should I rename from fotakernelxxx.sin to kernelxxx.sin ?

regards,

---------- Post added at 03:51 PM ---------- Previous post was at 03:06 PM ----------

Actually I do not have a file named kernel.sin - I have got a file Fotakernelxxxxx.sin

I downloaded this stock rom by xperifirm form Flashtool. My phone xperiaXA F3111 is operating on this stock rom now. Should I rename from fotakernelxxx.sin to kernelxxx.sin ?

regards,

---------- Post added at 04:16 PM ---------- Previous post was at 03:51 PM ----------

OK, I placed boot.img, TA.img and recovery.img in ta_poc new folder.

It doesn't say about error now and processing everything to the very end I hope.

At some point it asks:

" Install Recovery:

- Install? (Say yes to install) [Y/n] "

What should I write Yes or No and where is it going to install that recovery ?

Additionally it says:

"No kernel dt, probably zImage allready have dt appended? Continuing anyway.

making new_boot.img

new_boot.img created.

Done. "

So is ot OK that No kernel dt ?
[Sony Cross-Device General] munjeni:
Yes it is ok!
[Sony Cross-Device General] Andrzej_Andrzej:
Dear Munjeni,

Thank you for your great tool and help. I would like to thank you to X-One, Juanpirulo, Shoey63 as well for their great help and patience. I am slowly getting there. I have a new_boot.img which I have to rename to boot.image ( I read it somewhere) and by ADB: fastboot flash boot boot.img I hope if I flash it my xperia xa will get up and running. Is there a risk after all of it that phone could be bricked ? And what then?

regards,

Andrzej_Andrzej
[Sony Cross-Device General] munjeni:
Before you proced find first original rom (FTF) which is excatly the same version like your one in case your phone not boot, so if phone not boot reflash only kernel using flashtool, for further questions about flash tool use search button, don't reguest help here about flash tool please, just search first since forum contain ton of posts related to flashtool! SO make everything ready (firmware "FTF", flashtool ...etc) before you flash new_boot.img, in case new_boot.img is not working for you.
[Sony Cross-Device General] Andrzej_Andrzej:
The problem is that xperi firm is downloading custom rom for my mobile provider but it is finally unpacked (in present version of the xperifirm it is impossible don't unpack at the and of downloading process). This stock rom contains Fotakernelxxx.sin. I found original custom rom which has got fotakernelxxx.sin and it is in FTF form prepared. So when my phone wouldn't boot should I connect to Flashtool and flash only Fotakernelxxx.sin from FTF folder, not all stock rom ?
[Sony Cross-Device General] munjeni:
Yes! But make sure it is the same rom version because of kernel version must match your kernel version!
[Sony Cross-Device General] mobiware:
By the way, when we use XperiFirm, do we need to download a firmware from our region necessarily? Some people say we do so that we get food signal and the modem works.
[Sony Cross-Device General] esps:
Just same model, can be diferent region (some region are debloat... in other case, USA region doesnt support to fingerprint sensor)...
[Sony Cross-Device General] Andrzej_Andrzej:
When I downloaded firware with xperifirm and it was unpacked or I found anyway the same firmware in FTF file and I unpacked it as well - I didn't find kernel.sin. There was only fotakernelxxxxx.sin. Despite this there was many files with .sin extension so the trouble is how to choose proper one which is actually a kernel.sin but has got a different file name. For a beginner this is abit difficult but this is important when we do some modifications so it would be good to know how to distinguish a proper one. Because it is I assume important and not a hit or miss type of guessing.
[Sony Cross-Device General] shoey63:
You have XA? Look for boot.sin
[Sony Cross-Device General] Andrzej_Andrzej:
Thank you for your help, I actually do not have boot.sin but boot_S1_SW_xxxxxxxxxxxMMC.sin

And one more question; you advised mi when I was doing ta_poc to put boot.img, recovery.img and TA.img in one folder in order to do new_boot.img. When ta_poc is doing it it asks: install recovery : say Yes or No ?

What is better to choose and what is implication of either choice, please ?

regards,
[Sony Cross-Device General] xRevengerZee:
Can someone please upload old version of poc i want to test something
[Sony Cross-Device General] Andrzej_Andrzej:
Has this new_boot.img (produced by ta_poc) flashing anything to do with adoptable storage ? I have many apps on it so after flashing this file (new_boot.img) will this adoptable storage and apps stay intact ? Or should I first move them back to internal memory ?
[Sony Cross-Device General] Andrzej_Andrzej:
It does not work.

Hi Munjeni,

It doesn't work. I flashed new_boot.img and got constant bootloop with first screen logo sony. Turning off and on endlessly. When ta_poc made new_boot.img I received no errors.

Please advise,

regards,
[Sony Cross-Device General] realtuxen:
1. do not look in the unpacked folder xperifirm makes, close xperifirm and let flashtool make the .ftf file. when its done creating the .ftf file use unzip/7zip/WinRAR to extract kernel.sin or in your case boot.sin from the .ftf file.

2. it depends if you want to incorporate a recovery in the boot.img, if you have a never phone you can also flash it to the (recovery) fotakernel location. basically the only difference is how you enter recovery when turning on the phone. some like to incorporate it in the kernel, some in recovery (fotakernel). with recovery you press power + vol down, if you incorporate it (answer yes) you need to press vol up or down at at certain point when the phone boots.

EDIT: make sure you have a recovery (TWRP) that is compatible, and if you already can boot it with power+vol down; answer no. although it is possible to have both.
[Sony Cross-Device General] Andrzej_Andrzej:
Thank you realtuxen,

regards,
[Sony Cross-Device General] Omega200:
There instructions are ok to follow? https://xdaforums.com/z4-tablet/general/guide-restore-drm-nogut-t3555042

I unlocked bl flashed supersu and now i just want to restore ta.
[Sony Cross-Device General] x_one:
Why don't just try?

And almost yes.. You don't need change name of kernel file.. You also can skip last step. Don't push anything to phone. If you prepare your new boot it will do it for you in the right way..
[Sony Cross-Device General] Omega200:
I tried but with no success. It just show me that i have no key
[Sony Cross-Device General] x_one:
Did you backuped your TA partition before unlocking bootloader?

You can't use tapoc without TA backup from your phone.
[Sony Cross-Device General] Omega200:
Yes, i backuped up, i tried with iovy, i got few times error from driver i guess, after that it worked but again i had no key in service menu. Whole day i tried to restore them but i'm giving up. I think my drivers screw up all the time.
[Sony Cross-Device General] x_one:
Do you have cell signal after boot with prepared image?

Take dmesg.log right after boot.
[Sony Cross-Device General] Omega200:
Yes, I have signal. I don't know how to take that....
[Sony Cross-Device General] x_one:
Check if you have /data/local/tmp/TA.img

And try this..
[Sony Cross-Device General] Andrzej_Andrzej:
Hi All

I did ta_poc and this time I used boot.img. New_boot.img made without errors but still bootloop constant on logo sony screen.

Please help.
[Sony Cross-Device General] Omega200:
I did that with no succes.
[Sony Cross-Device General] Andrzej_Andrzej:
Is this ta_poc not working on xperia xa ?
[Sony Cross-Device General] Omega200:
I don't know, i have z3+. In this morning i flashed again lp tried iovy, it said successfully but when i look in service menu i got error....
[Sony Cross-Device General] munjeni:
[MENTION=6709834]Omega200[/MENTION] Your TA.img must be dump from LOCKED bootloader!!! If you unlocked bootloader and done that TA dump than your TA.img is just nothing! By the way no body can help you without poc log and dmesg! Post it to http://www.pastebin.com

[MENTION=8176647]Andrzej_Andrzej[/MENTION] I have told you that no body can help you without log! We need your poc log and also as I told you earlier last_kmsg! Last time you posted kmsg two times instead of last_kmsg, I need last_kmsg and not kmsg! But please do not ask how you can get last_kmsg since I can't help you with it, just ask somebody in your device forum for how it can be done, hope this help.
[Sony Cross-Device General] munjeni:
Anybody from newer xperia devices give me s1_boot_info.log ??

Just put your device into bootloader mode and run RUNME.bat. I have managed to replace libusb driver, which depend for my xflasher tool, with standard flashtool usb driver so no need to install libusb anymore, need some logs from newer xperias related to the s1 protocol which seems is changed and diferent than one for xperia z1 - z3 line since it missing loader.sin, curently Androxyde seems not going to help me and I need to help byself, if I get it I will make xflasher for newer models too!
[Sony Cross-Device General] levone1:
[MENTION=4120742]munjeni[/MENTION] - quick question... At first, I remember poc offered hope that custom rom could have stock-quality camera, since TA could be mounted. It seems like maybe not the case anymore. If this is only working for stock, is it any different than other TA backups already available? I'm not trying to belittle all of your excellent work, I'm just curious from a technical standpoint. Or, is there still hope that this could work for custom roms? Thanks
[Sony Cross-Device General] munjeni:
It allready works for custom roms, but problem is nobody going to port stock camera for that use! :) I definitelly will not port camera, I had chance but got extreme versus support, you know that story I am sure, final result for my contribution to that android_7 and stock camera/kernel was 7 day temp ban, so thing is clear - you want stock qualitty camera? Than you must port stock camera to custom rom with help of my poc (to get drm back), poc can do nothing to camera quality without stock camera things! Poc is nothing other than camera related thing only! Poc without stock camera is uselless!
[Sony Cross-Device General] FakeMobile:
i have xperia xz with custom ROM (nougat ) , this is the log :

ret: 1
ret: 1
ret: 1
ret: 1
ret: 1
ret: 1

hope it help you
[Sony Cross-Device General] levone1:
I don't know much, but I've pokes around with LP camera port, to see if I could get some ideas of what to do, but it's over my head... If I can get framework jar to compile and run with modded smali files from LP port, could I get stock camera by simply porting 'semc camera ui' apk, or is there more required? What was it that you were trying to do?
[Sony Cross-Device General] munjeni:
Uhh, you need to port not only smali, you first need to port whole camera hall (booth kernel + android) and than all some needed things from stock jars! The most of hard things lives in hals since diferent api from old hals is no more compatible with newer hals, so in short you must to make first kernel hal backport, than androod hal, than jar/java stufs which is ton of work
[Sony Cross-Device General] munjeni:
Thanks! Seems vid and pid is diferent? Can you verify VID and PID in you PC device manager about usb when your phone is in bootloader mode? I have set it to default VID=0fce PID=adde
[Sony Cross-Device General] dr4go:
If it helps: I myself own the Xperia X Performance. My device manager shows the following for vid / pid:

USB\VID_0FCE&PID_0DDE&REV_0100
USB\VID_0FCE&PID_0DDE
[Sony Cross-Device General] munjeni:
Thats vid pid from fastboot mode... Not bootloader mode
[Sony Cross-Device General] dr4go:
Sorry, I thought fastboot mode would be the bootloader mode. ;) If you mean what flashtool calls the flashmode, here you go:

USB\VID_0FCE&PID_ADDE&REV_0318
USB\VID_0FCE&PID_ADDE
[Sony Cross-Device General] munjeni:
Thats it! Can you try my tool and give me output log? https://xdaforums.com/showpost.php?p=71991678&postcount=1376
[Sony Cross-Device General] munjeni:
Tad existed with status 1 which mean error. You need to look into:

1. is TA.img autocopied to the /data/local/tmp

2. ta log in /data/local/tmp

If above two things is ok than it is time for looking into logcat since tad_static outputs that log to the logcat. Hope this help
[Sony Cross-Device General] munjeni:
First of all please next time use http://www.pastebin.com to post logs instead of posting it directly here! Seccond thing, I have found that you have installed 32bit recovery on your device, why? I suggested many times... You need WORKING recovery first (mean you need to test recovery and confirm itself that that recovery booting on your phone), than you can use that recovery for poc. Third thing, I realy can't help you sorry, I simple have no free time to help you since your knownledge (needed basic phone stufs knownledge) is almost like novice, sorry, I simple have no free time to teach anybody sorry! Suggestion - please search xda and learn that basic thing called adb, just search for "how to use adb"
[Sony Cross-Device General] Andrzej_Andrzej:
1. I installed 32 bit recovery because I found it on xda here forum. This is recovery-XA-SS.img.

2. I must honestly admit that my knowledge is basic but I want to learn more.

3. In your first post you wrote down that everyone is invited.

4. My recovery even 32-bit is working which mean to me that I can enter TWRP every time with volume down and power button.

5. I must admit I am novice but I am not regarded myself a worse member than the others.

6. Instead of "insulting" me a bit please point me out where I can find useful information to learn more, expand my basic knowledge,

and remember that a long time ago probably that was a time that you were a novice as well.

kind regards,
[Sony Cross-Device General] juanpirulo:
[MENTION=4120742]munjeni[/MENTION] I tryed to poc the boot.img from lineageOS and this the error I ve got. cheers

cp: can't create 'TA.img': File exists

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

Trim Area PoC kernel image patcher by Munjeni @ 2017

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

hash:0xF744138D calc_hash:0xF744138D

hash:0xEA03DC75 calc_hash:0xEA03DC75

hash:0x5A7C4D66 calc_hash:0x5A7C4D66

hash:0x9A2DBCED calc_hash:0x9A2DBCED

device: D6603

serial number:

drm key:

Trim area dump is a valid.

Locked bootloader.

Deleting old folder ramdisk if exist...

command ret: 0.

New directory ramdisk created.

Created ouput folder "out"

opening C:\Users\JUANPIYROCIO\Desktop\LineageOS\ta_poc (1)\ta_poc\boot.img

C:\Users\JUANPIYROCIO\Desktop\LineageOS\ta_poc (1)\ta_poc\boot.img is Android image format.

Dumping to out...

BOARD_KERNEL_CMDLINE androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y buildvariant=userdebug

BOARD_KERNEL_BASE 00000000

BOARD_NAME

BOARD_PAGE_SIZE 2048

BOARD_KERNEL_OFFSET 00008000

BOARD_RAMDISK_OFFSET 02000000

BOARD_SECOND_OFFSET 00f00000

BOARD_TAGS_OFFSET 01e00000

BOARD_DT_SIZE 282624

Done.

No file exist out/boot.img.elf .

Gunziping...

setting up infflate...

infflating...

infflate returned: 0

gzpipe: ok.

unziped: ok.

Extracting ramdisk.cpio...

Runing user script...

Making ramdisk/stufs folder... done

Found android version equal or greater than Marshmallow.

Making ramdisk/init.ta.sh script... done

Found string in ramdisk/init.camera.rc@0750

patching ramdisk/init.camera.rc@0750

sed: unmatched '!'

installing ramdisk/stufs/TA.img

Found string in ramdisk/init.rc@0750

patching ramdisk/init.rc@0750

Found binary ramdisk/file_contexts.bin@0644

converting ramdisk/file_contexts.bin@0644 to plaintext file_contexts

patching file_contexts

converting plaintext file_contexts to binary ramdisk/file_contexts.bin@0644

General error, tell me about it on xda!

command ret: 1.

Your script didn't returned 0, please check your script!

Presione una tecla para continuar . . .

¿Desea terminar el trabajo por lotes (S/N)?
[Sony Cross-Device General] munjeni:
Can you post that non modified boot image?
[Sony Cross-Device General] juanpirulo:
here you have. this is the boot.img extract from lineage rom zip. cheers
[Sony Cross-Device General] munjeni:
3. Thats a true! Nobody say that you're not welcome

4. Thats a wrong recovery! Have no idea who made it 32bit

6. Have no free time teaching anybody with that basic things like ADB and thing, just search or open new thread. I told you that I need last_kmsg and also I told you that please do not ask how you can get it, I told you to ask somebody in your device forum to give you info how you can get that last_kmsg but you didn't done, and I said that can't help you without that log, now I saw that your adb knownledge is null and pointed you to search for "how to use adb", just search for it! I am ready to help with poc related things but sorry I can't help with very basic things, have no free time for it! You are welcome anyway but please do not ask me for that help, hope some body help you. Dont be a mad, nobody can earn skills in just two days, be patient please!
[Sony Cross-Device General] munjeni:
Thanks! Will check that tommorow!
[Sony Cross-Device General] dr4go:
Sorry for the late answer... wasn't online lately... here you go:

Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
Device path: \\?\usb#vid_0fce&pid_adde#5&32fa2635&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: Universal Serial Bus controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&32FA2635&0&2

ret: 1
[Sony Cross-Device General] munjeni:
Hi thanks for log! Huh seems s1 protocol is changed on newer xperias (as expected since newer device no more uses loader.sin) since s1 boot didn't sends first packet aka device info :( I realy will open an thread and explain how to sniff usb packets, will need that raw packets usb logs for further investigation, I asked androxide for some info but he didn't respond, seems I will need to learn byself
[Sony Cross-Device General] munjeni:
New version is out, its supported now!

Edit:

Forgot to tell about (sed: unmatched '!') , thats error! It fail to patch file! I have curently fixed it for your type of boot image but just to tell to all that if somebody found something like that in poc log thats definitelly an error, contact me with poc log!

Xflasher for z1 - z3 (z5??) finally finished, can be used with bat files the same way as a poc! :) Newer devices is not supported since changes in s1 protocol but hope somebody help me by providing usb sniff log as per my reguest on that thread, it will help me making support for new devices!
[Sony Cross-Device General] knop3x:
FYI I ran nougat_ta_poc on linux via wine ("wineconsole cmd") and it finished without any errors. I did not use any scripts.
[Sony Cross-Device General] gr8st:
Is this necessary? I just checked, owner/group=root and permissions are 777. TA.img is loading fine. I've tested by completely removing it and then I can't even boot to completion without it.
[Sony Cross-Device General] knop3x:
[MENTION=4120742]munjeni[/MENTION], [MENTION=357342]tobias.waldvogel[/MENTION]:

I have the same problem: If I use your tool (no scripts), then the rootkernel-tool (dm-verity off, ric off, TWRP, nothing else) I cannot go into recovery through the phone. The only way I found to boot into recovery is via "adb reboot recovery".

Although I have to say, I had a similar problem before, when I only used rootkernel. So I am not sure if this problem is because of this TA-POC.
[Sony Cross-Device General] Fauzi alaik:
What is tad? I cant find tad on group and owner on mixexplorer, and permission set to 777 right?
[Sony Cross-Device General] Emaulana:
Please make one for Sony Xperia ZL. Thanks in advance! Sorry, i mean for Sony Xperia ZL with Lollypop fw :)
[Sony Cross-Device General] x_one:
Install Terminal Emulator from google play.

When you run it type

su
cd /data/local/tmp
chmod 640 TA.img
chown tad:tad TA.img

Then you should have right permissions and owner.

You can check if it's OK typing

ls -la
[Sony Cross-Device General] munjeni:
New version is out, now roms before marchmalow is supported! Also updated dmesg_to_seinject tool, now no need to specify first argument like nougat_ta_poc since its now %2 which mean parameter got from the ta poc tool which now sends two parameters to the user script, first parameter is outputfolder (%1) and seccond parameter is basename of the ta poc tool (%2)
[Sony Cross-Device General] Emaulana:
Thanks a lot bro! :good::good::good:
[Sony Cross-Device General] munjeni:
Sorry new version again, fixed support for old devices, now tested on my z1c and it works! One good thing for older devices you no need to copy ta to the /data/local/tmp since it works ok!
[Sony Cross-Device General] fluffi444:
You are kidding, isn't it? Sorry for what? :o

There is so much potential in this and we are happy that you are on fire with this tool :good:
[Sony Cross-Device General] XDAample:
thanks for supporting Z1 series, anyway, Can't find DOUBLECLICKME_JB for before MM android version.:D
[Sony Cross-Device General] munjeni:
Again new version :D