Definitely not, should be between 650-700 Mb for stock rom.Is it normal that my full backup takes only 1mb of storage?
Hmm. I must try to change to .tar backup..Definitely not, should be between 650-700 Mb for stock rom.
Updated to v2, now recovery displays correct model information.Would it be possible to get a how-to to remove the Xperia TX\GX tag on the recovery? Or add an \V ?![]()
This happened to me too, can I ask how you were able to get out of the bootloop? I'm a noob with Xperia, and I didn't really find any solution other than to flash an ftf, which is what I ended up doing. Twice. I tried to restore from both internal and external, using the default (blob) backup format. My next experiment is going to be to try it with a .tar backup and see if that works, but I might not get to that for a day or two.for me,i start the phone, when i have the logo "Sony", I press the touch vol+ and when the phone vibrate, I release the touch et it's good ^^
but i have a problem with the restore, i make my restore and after i bootloop ? :/
Try flashing reboot fix from CWM itself.This happened to me too, can I ask how you were able to get out of the bootloop? I'm a noob with Xperia, and I didn't really find any solution other than to flash an ftf, which is what I ended up doing. Twice. I tried to restore from both internal and external, using the default (blob) backup format. My next experiment is going to be to try it with a .tar backup and see if that works, but I might not get to that for a day or two.
Running Xperia V LT25i with SuperSport ICS rom [9.0.1.D.0.10] with the matching kernel, stock except for unsecure/debuggable.
Changed the restore format to .tar, flashed the reboot fix, restored my backup and bootlooped again.Try flashing reboot fix from CWM itself.
I misunderstood (I read reboot instead of bootlop). Reboot fix is not helping at all.Changed the restore format to .tar, flashed the reboot fix, restored my backup and bootlooped again.![]()
You are right, but Cyanogen is not possible on locked bootloader. Furthermore Siyah and other available stock kernels include the original CWM in which is based this, so for now there is no workaround for those issues that you remark.this recovery is just outdated, cyanogenmod has a much newer recovery included, backups and restores work fine there and the date is also right, I got a backup with year 1970 with this version which is also included in the advanced stock kernel...
I would recommend flashing a kernel with recovery included, siyah or some of the modded stock kernels. maybe it works then, I don't wanna test because I stay with cm10.
I have a V, so my kernel options are pretty limited at this point. However, replacing CWM with TWRP did the trick - backup, restore, no problems. Thanks everyone for your help.this recovery is just outdated, cyanogenmod has a much newer recovery included, backups and restores work fine there and the date is also right, I got a backup with year 1970 with this version which is also included in the advanced stock kernel...
I would recommend flashing a kernel with recovery included, siyah or some of the modded stock kernels. maybe it works then, I don't wanna test because I stay with cm10.
Gesendet von meinem Xperia T mit Tapatalk 2
in theory if you flash a stock rom via flashtool your phone should be back to stock like state. if flash a stock rom via recovery etc then you wont get updates from sonyIf I wipe all data and 're-flash my phone I should be able to get OTA updates back I hope ? Or is it broken for good
Sent from my LT30a using xda app-developers app
You can flash only FTF's via flashtool (Corect me if wrong)@shingers5
So just to clarify:
1) There are 2 ways to install a ROM a) via flashtool and b) via recovery
2) These methods are somewhat different - (how?)
3) doing so via recovery means that OTA updates are broken
Is that right?
Look at here.thanks Greg, if that is the case, then why do ppl say that after installing CLOCKWORKMOD recovery OTA updates fail?
If the ROM in use is either from OTA or from an FTF, then are we saying that it is only if you then go on to load a ZIP ROM via CWM that you break OTA updates - up until that point having CWM installed will not have broken OTA updates?