TA Backup not working - Xperia SP Q&A, Help & Troubleshooting

Hello.
I am unable to backup my device TA-partition. I have followed all the instructions as described here.
I have made sure my device is rooted and USB Debugging enabled but I get the following error:
Code:
Waiting for USB Debugging...OK
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
dd: can't open '/sdcard/backupTA.img': No such file or directory
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup does not match TA Partition. Please try again.
*** Backup unsuccessful. ***
Backup-TA: v9.11
PC: Windows 7 x64
Device Firmware: Stock .205
Can someone please help?

I had similar problem but I already had an old TA backup. Couldn't backup/restore on stock rom. I flashed cm12.1 and it restored successfully, then I flashed stock rom. So try flashing other rom which works on Locked bootloader and try to backup on that rom. for example this rom cm12.0

krek4 said:
I had similar problem but I already had an old TA backup. Couldn't backup/restore on stock rom. I flashed cm12.1 and it restored successfully, then I flashed stock rom. So try flashing other rom which works on Locked bootloader and try to backup on that rom. for example this rom cm12.0
Click to expand...
Click to collapse
Ok so something unfortunate happened. I decided to flash CM12 as you suggested. But in TWRP I don't know what but I did something wrong while wiping which soft bricked my phone. I was unable to get into recovery. The phone was stuck at the Sony Logo screen. Fortunately I was able to do a System Repair using Xperia companion and now the phone is back to normal.
Unexpectedly now I am able to backup the TA partition. Maybe factory reset does the trick.
Code:
Waiting for USB Debugging...OK
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.783153 seconds, 2.6MB/s
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
PULL BACKUP FROM SDCARD
=======================================
3978 KB/s (2097152 bytes in 0.514s)
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
PACKAGE BACKUP
=======================================
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Scanning
Creating archive ..\backup\TA-backup-20160430.184625.zip
Compressing TA.blk
Compressing TA.img
Compressing TA.md5
Compressing TA.serial
Compressing TA.timestamp
Compressing TA.version
Everything is Ok
*** Backup successful. ***

Good for you :good:

Related

Flash nandroid backup image from PC?

Hi,
I've made a backup of my phone with cwm. The backup consists of the following files :
cache.img
data.img
datadata.img
nandroid.md5
system.img
Is there a way to restore this from the PC (like with odin or heimdall)?
Thanks.
nobody? ^^
you can restore it thru CWM i dont think anyone has tried it thru Odin but if i was to try it (which would be very risky) i would flash the nandroid.md5
BUT I DO NOT RECOMMEND IT

want to get cm11- help please

Okay, I restored my z1 to .534, rooted it, backuped ta, unlocked bootloader.
Now I dont have a working camera.
I want to get to cm11 and have the camera working.
I dont know where to go from here, any help is appreciated. Thanks
Why. 534? Restore TA, flash the .290.ftf, unlock bl. Then go on, as in the cm11-thread described...
Getting really scared/frustrated please someone help. Many panics. I backed up a TA and when I try to restore it I get this.
Can I just get back to .290 with working camera or anything that works. Someone please help.
Files: 6
Size: 2097244
Compressed: 169438
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
COMPARE TA PARTITION WITH BACKUP
=======================================
OK
=======================================
BACKUP CURRENT TA PARTITION
=======================================
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.260349 seconds, 7.7MB/s
=======================================
PUSH BACKUP TO SDCARD
=======================================
2572 KB/s (2097152 bytes in 0.796s)
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup has gone corrupted while pushing. Please try again.
*** Restore unsuccessful. ***
Press any key to continue . . .
Why you just don't read carefully and listening when someone saying to you what to do? Did you backup TA and Unlocked Bootloader so tell me why the hell you try to relock it again? Just because the camera don't working? Flash via Flashtool the Stock .290 FTF and everything will be fine or follow the instruction on CM11 thread to update to .290. Camera will be back again and you will have the CM11 Rom on your phone. If you start messing up you can brick you phone.
Camera wont work on unlock bootloader on versions prior to .290. All you need to do is to put the cm11.zip into your sdcard then follow the instructions in the cm11 thread

【E1】 xperia E1 - Androxyde flashtool hints

It is possible to flash stuff with ft in flashmode in win8.1-64. (lights off)
fastboot mode is not so good I believe. (blue light)
PC companion still overflashed (no light) the E1 after messing with ft. I left the bootloader untouched = locked.
overall, I like ODIN & Galaxy better for flashing.
you do need ft ! after ONANDROID restore, you easily get into FC loop. PC 'companion' will let you down. Only FT in flashmode will soft-unbrick your E1 !
though ergonomics in ft is kinda messy. anyway.
General BACKUP hints on E1
conclusion : no nandroid on E1 ! very bad !
solution: we must manually use dd for read write partns !
since E1 does not have CWM or ASR for nandroid backupping, we use ONANDROID after towelroot.
no E1 patch file developed yet, so only SYS and USER partition backup poss.
its nice to have a NANDROID on E1. But its bad that it cannot be restored by NANDROID MANAGER, because that relies on CWM for restore, which is non existant on E1.
hotboot fail
hotbooting E1 stock .elf or .Image kernels fails.
maybe its not proper "boot.img" format
sudo fastboot boot ./kernel_S1-SW-LIVE-B578-PID1-0005-MMC.elf ./kernel_S1-SW-LIVE-B578-PID1-0005-MMC.elf.ramdisk
creating boot image...
creating boot image - 11247616 bytes
downloading 'boot.img'...
OKAY [ 0.347s]
booting...
FAILED (status read failed (No such device))
finished. total time: 6.707s

Nasty OPTIONS in FLASHTOOL latest versions.

I used v9.22.2 last night...
I downloaded. 266 firmware from Xperiablog.com
1. Then i did USB debugging On
2. Unknown sources ON
3. Installed ADB and Fastboot drivers.
4. Installed Flashtool and then installed fastboot, flashmode, z3+ drivers.
5. Restartded PC.
6. Flashed FTF. 266
________________
7. I didnt tick at the bottom Disable Final Verification.
8. In the TA exclude i didnt tick any options.
9. In the wipe option i checked them all.
10. In simlock TA i didn't check any option.
--------------------------
11. Then i started the flash process.
12. A text comes saying that
"FSC found do you want to use this FSC?"
13. I clicked at NO and continued Flashing process.
14. The flash was going smothly but in the log it is writing something to my TA partition 1 and TA partition 2.
------------------------------------
These are the steps i followed,, in flashtool, i used flashtool blog from xperiablog to do this.. But i hav huge doubt in my mind.
As the flashed FTF wasn't mine,
--------------------------------------
1. did i did something wrong by not checking TA Exclude option while Flashing?
2. And by saying NO to the FSC found in the FTF.?
3. Did i damaged my DRM keys and TA partition?
-------------------------------------
NOW I CANT SEE ANY DRM KEYS AND FOTA PARTITION INFO IN THE DEVICE HIDDEN SETTING MENU, which can be seen by pressing *#*#7378743#*#*
Please help i am little fuc###d up right now.
First thing is the Secret menu code is *#*#7378423#*#* (not *#*#7378743#*#*). then select: Service Tests > Security.
Second thing is you did not done any wrong. The steps you followed is correct.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
If you did not unlock the bootloader, you will not loose the DRM Keys.
I did flash . 266 to backup my TA and DRM keys.
By IOVYTOOL I successfully did backup of my TA image. But I don't know how to backup DRM keys.. I am not getting any posts here @ XDA which tells me how to backup DRM keys.
Any help would be great from your side regarding this!!
Also when I flashed stock ftf . 266 to my device there is an option which says
"FSC Script found, Do You Want To use FSC Script?"
And I clicked at NO and continued the flashing process. In some posts about other Xperia Series some senior member were saying to Allow yes for that FSC Script and on some posts some were saying to NO for that FSC SCRIPT.
So I am litteraly confused right now about my NO to the FSC Script.
Will you please explain this FSC thing to me?
Also the FTF that I downloaded wasn't my self baked from Xperiafirm. Earlier I had Xperia L and at that time some senior devs warned me to Exclude Custom.TA and other TA stuffs if the FTF wasn't created by Self. They said when downloading ftf from Xperia firm by Self the Xperiafirm includes TA files of that connected device in that ftf file and if that FTF will be flashed on some other Device then Exclude TA option must be checked because it will damage your TA partition and DRM keys.
Will you enlighten me about this TA thing to me?
I am not expert to explain this, but, I did everything as you did and successfully flashed .266 FTF file, took backup of TA Partition. Afterwards, BL unlocked, bloatware removed, again after some time Flashed .266, restored TA backup and successfully relocked the BL.
I also clicked on NO for FSC script whicle flashing FTF Files. I never clicked on any Exclusion while flashing.
for backing up TA partition, open command prompt in PC -> change the directory to IOVYTOOL folder -> run the command for backup. TA Partition backup also stored in the same folder. Restoring is also the same, flash .266 FTF File, open CMD Prompt -> change directory to IOVYTOOL folder -> run the command for restore, thats it.

Can someone send me the backup image or bin of NVDATA,persist,proinfo,protect1,protect2, NVRAM and nvcfg?

I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!
chakrabortyshubham66 said:
I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!
Click to expand...
Click to collapse
No one will provide NVRAM or protected system data.
Is there any alternative way by which you can fix this issue?
Please PM me so that I can coordinate on this thing.
If you wiped those things without making a backup, you're fked. Those files are tailored specifically unique for every device.
bruh you want having someone else's IMEI and SN !!!!
chakrabortyshubham66 said:
I Flashed the stock using SP flash Tool and i don't have backup of the partition.
and now i want the file so i can edit it and paste my imei and baseband.
NVDATA, NVRAM and nvcfg
mine boots to recovery and it says unable to mount /nvdata (Permission Denied).
PLZ HELP!
Click to expand...
Click to collapse
try flashing older ROMs like MIUI 12.5 or 13 Global ones via SP flash tool. I were flashed my stolen Redmi 9 many times via SP and never faced issue. also make sure you have right DA and auth file among right rom

Categories

Resources