Related
I've got one of these on order and was reading about the DRM keys needed for Bravia engine and the camera to work. Can I restore those keys with the TA backup program and still keep the bootloader unlocked? Really would put a damper on the flashing fun.
mas5acre said:
I've got one of these on order and was reading about the DRM keys needed for Bravia engine and the camera to work. Can I restore those keys with the TA backup program and still keep the bootloader unlocked? Really would put a damper on the flashing fun.
Click to expand...
Click to collapse
If you restore TA back up, it automatically relocks the phone.
dw1llow said:
If you restore TA back up, it automatically relocks the phone.
Click to expand...
Click to collapse
So theres no way to flash just the keys huh....That kinda kills the modding scene, if someone doesn't find/create a work around. Losing the Bravia engine kinda sucks but that only works with Sony's video player, but losing the camera...that sucks. Sure there are other camera apps but I doubt they would have the software implementation of steady shot.
mas5acre said:
So theres no way to flash just the keys huh....That kinda kills the modding scene, if someone doesn't find/create a work around.
Click to expand...
Click to collapse
Well, if you're going to install custom rom, you'll have to forgo all the software-emulated Sony-specific features, like the BE engine, Bionz, etc.
Oh, btw, when you relock the phone, you gotta have the stock rom installed, other wise it's going to hardbrick your phone.
dw1llow said:
Well, if you're going to install custom rom, you'll have to forgo all the software-emulated Sony-specific features, like the BE engine, Bionz, etc.
Oh, btw, when you relock the phone, you gotta have the stock rom installed, other wise it's going to hardbrick your phone.
Click to expand...
Click to collapse
I'll test some roms eventally....I just hate proprietary software on a mostly open platform like android. If I screw it up and don't have the original rom installed and it's hardbricked, can I still recover with a ta backup?
I thought ta both relocked the phone and installed the original rom.
As for the Bionz engine, I've read some bad things about photos taken with the z1 having grain. Maybe losing it isn't such a bad thing.
mas5acre said:
I'll test some roms eventally....I just hate proprietary software on a mostly open platform like android. If I screw it up and don't have the original rom installed and it's hardbricked, can I still recover with a ta backup?
I thought ta both relocked the phone and installed the original rom.
As for the Bionz engine, I've read some bad things about photos taken with the z1 having grain. Maybe losing it isn't such a bad thing.
Click to expand...
Click to collapse
TA is just a partition, so you need to flash stock ROM before restoring.
Yeah, me too. I've been using CM for like 2 years, so I don't know what it's going to be like using stock roms/kernels. But I'm pretty sure I'll hate it, cus there's nothing I hate more than being stuck with old android versions. I'm already dreading when my Z1 arrives, it will be running 4.2.2. Such a downgrade from CM10.2.
I backed up TA！
dw1llow said:
Well, if you're going to install custom rom, you'll have to forgo all the software-emulated Sony-specific features, like the BE engine, Bionz, etc.
Oh, btw, when you relock the phone, you gotta have the stock rom installed, other wise it's going to hardbrick your phone.
Click to expand...
Click to collapse
I don't have the Xperia Z1 in hand to confirm, but if the software is built anything like the Xperia Z then you most certainly won't brick your device by flashing locked TA while on a custom kernel. At worst you might stop it from booting (wrong signature on kernel), but all you need to do then is stick it in flash mode and install a signed kernel image using FlashTool or somthing. Worst case, stick it in fastboot mode and unlock again.
Looking forward to cyanogen 10.2 on Xperia z1!
First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.
xperia_loser said:
First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.
Click to expand...
Click to collapse
first thing first, do you have your original imei saved somwhere? one your phone box or on the e-mail you've got from sony for the unlocking code? (they require your imei for that code)
so there should be nothing illigal with reinjecting your own imei.
second thing, i have no idea how to do it...
First thing first
shteren said:
first thing first, do you have your original imei saved somwhere? one your phone box or on the e-mail you've got from sony for the unlocking code? (they require your imei for that code)
so there should be nothing illigal with reinjecting your own imei.
second thing, i have no idea how to do it...
Click to expand...
Click to collapse
I'm rather noob by not following the backing-up tricks before messing with its very inside mechanism, thus, I've lost the code on my device; however, I have the imei code written on the box.
The problem is "I have no idea how to do it either" :highfive:
I've been scrawling around with google help and my reading comprehensive but nothing gained so far.
I've called the service center of Sony in my country and been given addresses of service shops where I would visit in a couples of days.
Thank you for your care and hopefully help may come. :angel:
well, u've bricked ur device hard times..
What abt. TA Partition Backup?
U hv to relock the bootloader and for that u need ur TA partition (Do not use others)
I faced the same prob on my XZ lost baseband and and and
Restored TA partition and locked the bootloader, now my XZ is healthy with twins XZR and BB Q10 lol
Good Luck :silly:
Edit :
Read this -- My post about Bricked XZ
No TA back-up, it's totally doomed
shysparrow said:
well, u've bricked ur device hard times..
What abt. TA Partition Backup?
U hv to relock the bootloader and for that u need ur TA partition (Do not use others)
I faced the same prob on my XZ lost baseband and and and
Restored TA partition and locked the bootloader, now my XZ is healthy with twins XZR and BB Q10 lol
Good Luck :silly:
Edit :
Read this -- My post about Bricked XZ
Click to expand...
Click to collapse
Thank you so much, I've read that later on; however, it was silly of me not to have made any TA back-up :cyclops:
Thus, it's my fabulous brick now lolo=
I need your advice
I am not a good learner but... I've read more these days and found:
http://forum.xda-developers.com/showthread.php?t=2449244&page=4
Quote:
Originally Posted by iconoclastnet View Post
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.
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
Click to expand...
Click to collapse
This is the reply of gladiac and something came to my mind:
I've back up my TA by v9.9 (on my bricked phone of course) and receive a zip file in which I have TA.img
By such information above, we have the location for IMEI on hexa table of the file.
In my case of bricking my device by my fool and risky action, I thought of overiding the TA.img to inject my IMEI (now the text on the box and the back of my phone only, not in TA partition any more :crying in to TA.img? Will there be any further harm?
I dare not test it because I am still very vague about my exit if something might go wrong. If problems may arise after my tinkering of the TA.img and restoring the tinkered TA.img back, then, in such scenerio, will my reverting back to the very first TA.img (the not tinkered one) save my bricked phone at the least?
I really dont know if Backup TA can restore TA partition when the phone is in bad state.
It might be silly questions to you but please, I really need help.
Thank you for your appreciation.
xperia_loser said:
First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.
Click to expand...
Click to collapse
dude, i used the same pudding tw file and lost baseband and imei.but later i flashed with official android 4.1.2 ftf file which removed bootloop problems but still i dont have imei or baseband.i have flashed many c5502/c5503 roms and basebands but there was no use.i think the pudding ftf file could be the reason...
Easy fix
The same thing happened to me. Baseband and IMEI were unknown suddenly.
Then I did a factory reset, wiped all caches and flashed cm-11 followed by GAPPS & I got back network.
It was a pain to reinstall all apps and do all the same settings again though.
I remember seeing a stickie on the sp thread. That was a good guide to rooting etc.
http://forum.xda-developers.com/showthread.php?t=2100529
The same was appearing in more than one sub forum. Why can't we have such a stickie here?
I am waiting for my ZR.
Sent from my GT-S5570 using xda app-developers app
ajgo333 said:
dude, i used the same pudding tw file and lost baseband and imei.but later i flashed with official android 4.1.2 ftf file which removed bootloop problems but still i dont have imei or baseband.i have flashed many c5502/c5503 roms and basebands but there was no use.i think the pudding ftf file could be the reason...
Click to expand...
Click to collapse
Actually, I was on Beanstalk (CM based) first, which I can use normally with IMEI and baseband on. I lost them as my nephew touched the "plane" icon. So, the problem was on CM.
For the 'lost' wording, I dont think we lose IMEI and baseband but actually the phone fails to connect to IMEI and baseband data.
ayushag96 said:
The same thing happened to me. Baseband and IMEI were unknown suddenly.
Then I did a factory reset, wiped all caches and flashed cm-11 followed by GAPPS & I got back network.
It was a pain to reinstall all apps and do all the same settings again though.
Click to expand...
Click to collapse
I've tried that but bootloop occured.
On US ftf, no bootloop but wifi cannot be turned on.
On Beanstalk, everything's fine but no IMEI and baseband.
I am using my phone as a paperweight with wifi-connection and good gaming experience, lol
Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !
thewild said:
Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !
Click to expand...
Click to collapse
Why to take risk??bro it doesnt even take 5 min for a TA backup..
thewild said:
Hi all,
I made a backup of my TA partition some time ago and never took time ti unlock my bootloader.
I had to send my SP for repair, and they changed the "electronic card" (I believe this is the motherboard). The phone was working but it would not charge anymore, so I guess the power circuit was burned.
My question is : will my TA partition backup work on my new hardware ? I don't want to do it again if this is not necessary, I just want to move ahead and unlock my bootloader.
Thanks for your answers !
Click to expand...
Click to collapse
I would bet that "DRM" keys contained in a TA partition are unique and different for every device. otherwise, we would know what those keys are, and they would not have their said purpose. however, backing up the TA partition takes about few seconds, don't see why you wouldn't make a new backup and be on the safe side. you know, just in case...
I thought I had to be root to backup the TA ? So I have to first root, backup TA, unlock bootloader, re-root...
I think I'll do it, but I'm a bit lazy and I don't like to make unnecessary stuff.
thewild said:
I thought I had to be root to backup the TA ? So I have to first root, backup TA, unlock bootloader, re-root...
I think I'll do it, but I'm a bit lazy and I don't like to make unnecessary stuff.
Click to expand...
Click to collapse
DUDE?! RTFM! You made a whole UNNECESESSARY thread on this forum. :silly::silly::silly::silly:
Robin>Hood said:
DUDE?! RTFM! You made a whole UNNECESESSARY thread on this forum. :silly::silly::silly::silly:
Click to expand...
Click to collapse
What do you mean ? Maybe YOU should RTFM ?
Quote from http://forum.xda-developers.com/showthread.php?t=2292598 (backup TA 9.9) :
Q: Do I need root for this?
A: Yes, you do need root for this to work. I would advice to use @DooMLoRD's excellent Easy Rooting Toolkit for this, when not already rooted.
So yes, there are a lot of steps to backup the TA. Since I'm on .254, rooting is not just one click away, I have to flash kernel, root, reflash kernel.
If someone told me "your backup is fine because the key is linked to that stuff or that stuff and not to the motherboard, so go ahead" I would have avoided unnecessary hastle AND many people would have learned something in the process, like what the TA partition keys are linked to.
Nothing unnecessary, except maybe for your post, right ?
thewild said:
What do you mean ? Maybe YOU should RTFM ?
Click to expand...
Click to collapse
Dude THINK!
The post you link to says to ASK questions about backup TA in that thread, I believe it even has been answered before. :victory:
If you would have used your brain logic would have told you the encryption is unique, you can't just copy the TA partition of one device to another come on, its so simple.
Besides that? Why even bother to unlock the bootloader if you dont want to go through the hassle of installing new / other roms? You know what this website is about? Not about being lazy and stupid but about being inventive and curious. And of course people need to share their information, like I said before, people should take the time to READ, not be LAZY.
So don't be lazy. There's enough fat people in the world Enjoy your phone!:highfive:
Okay guys.. As members, both should know better.
First of all. If you go to this thread: http://forum.xda-developers.com/showthread.php?t=2292598 and read a bit you would know that making a TA backup is VERY IMPORTANT TO DO!
Also read a bit futher. Root is required to use this tool..
And a extra detail YOU CAN NOT I REPEAT CAN NOT USE THE TA BACKUP OF SOMEONE ELSE TO RESTORE YOURS BECAUSE IT WILL HARD BRICK YOUR DEVICE
As stated in the Q&A of that thread:
DevShaft said:
\
Q: Can I use someone else's backup?
A: No, this will hard-brick your device.
Click to expand...
Click to collapse
It is important to read the entire OP/thread to prevent this kind of questions Also read the replies.. They can answer questions for you
Also as an answer to your question:
NO you have an entire new internal system so the files are diffrent. If you havent unlock your bootloader yet make a backup first before doing so and remove the one you already have. I think you will hardbrick your device when you restore your TA backup from before the repair
I know better ^^
OK take it easy guys, it was a simple question meant to have a simple answer.
I should have asked my question in the "backup TA" thread, that's true, but I don't think it was a stupid question.
mrjraider said:
Also as an answer to your question:
NO you have an entire new internal system so the files are diffrent. If you havent unlock your bootloader yet make a backup first before doing so and remove the one you already have. I think you will hardbrick your device when you restore your TA backup from before the repair
Click to expand...
Click to collapse
Thanks, that's the answer I was looking for.
I know TA partitions are unique, the question was whether an electronic card replacement necessarily meant a new TA partition. Does it mean everything changed, from IMEI to hardware keys ? Well, the answer seems to be "yes", but I don't think it was SO obvious.
Thanks again for the answer.
Yes a new motherboard means also a new IMEI..
Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.
pfhastie said:
Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.
Click to expand...
Click to collapse
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.
St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
why would u answer the question without understanding what he wrote ? and the fact remains that u admitted that u didnt read it all the way so its pointless to reply jus like u may be saying its pointless for me to reply to your post and not answer the question
Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.
pfhastie said:
Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.
Click to expand...
Click to collapse
no know not of any other ways but sony and flashtool atm
1: Use backup-TA ONLY. You won't be reinstating it and getting back Bravia while you are using a custom ROM though You restore this backup only if you want to go back to stock and restore Bravia/send phone in for service.
2: You need the code from the Sony service. However just because you got the code, doesn't mean you used the code so won't wreck your warranty on its own. You restore the TA backup before your send away under warranty and then they don't even know you ever unlocked in the first place
Don't flash any .ftf to relock your bootloader, thats what you make the TA backup for. Any other method to relock bootloader will show relocked instead of never unlocked status you need for warranty. TA is only thing that will restore Bravia also.
pfhastie said:
Hi there
I will try and keep this as short as I can./QUOTE]
Click to expand...
Click to collapse
nlooooo said:
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.
Click to expand...
Click to collapse
Doh man, usually I understand everything but it seems I have to read more carefully..... And I shouldn't try to read something while talking to a friend. It won't happen again
Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?
pfhastie said:
Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?
Click to expand...
Click to collapse
As far as I know you need the code. Every phone gets an unique code created from your Imei
OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!
pfhastie said:
OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!
Click to expand...
Click to collapse
What if you flash Darklords pre rooted and deodexed rom?
http://forum.xda-developers.com/showthread.php?t=2647459
Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.
pfhastie said:
Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.
Click to expand...
Click to collapse
don't bank on the devs coming up with a new root method for 4.3, currently there isn't a need for one since we can all root on 4.1 then unoffically upgrade with a pre-rooted firmware, this is a relitevly simple procedure and can be done within an hour
It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.
pfhastie said:
It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.
Click to expand...
Click to collapse
+1 on what @matt4321 said in the previous post. Downgrade to 4.1.2, root, and then backup your TA partition with Backup-TA, flash CWM v8, and unlock bootloader if so desired.
If you want to be on 4.3, once you're unlocked, and after flashing any Official 4.3 FTF, you can then flash a kernel that can be found in EXR leaked 4.3 thread which comes with CWM already included, and finally proceed to flash SuperSU in recovery.
The minute one of the Official 4.3 FTF's came out I flashed it and tried the kernel I just mentioned; it's been working fine, probably even better than the official stock kernel (even though it is based on a stock kernel, only with CWM, that's why you need to be unlocked), given that I don't have a single one of the bugs that people are reporting exist on the Official 4.3 Roms. Battery is at 40% and I am already at almost 35 hours on a single charge.
If you already have the FTF files, this procedure doesn't take more than 40 minutes, if you're comfortable with and know what you're doing.
I hear you and will very likely give it a shot as soon as I can find the time (if only this was my only concern). At this stage, I'd be inclined to use Doomlord's Rooted&Deodexed ROM as it doesn't require unlocking the bootloader, but it is still a long way around to get root for the 4.3 version I am already using.
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!
Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
pfhastie said:
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
Click to expand...
Click to collapse
Regarding odexing/deodexing, read this.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
Click to expand...
Click to collapse
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.
Antiga Prime said:
Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
Regarding odexing/deodexing, read this.
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.
Click to expand...
Click to collapse
Oh, I get you. Still, bit of a faff, isn't it? These devices will be old before they can be utilised perfectly.
Custom ROMS still have a way to go unless stock based. Although the stock 4.3 isn't flawless, its better for me than the 4.3/4.4 custom's running on a 4.1 kernel. Every i've tried comes with the proviso that you will suffer blue screens of death at random until Sony releases the 4.3 kernel open source for them to merge. Some guys are hardcore though and putting up with reboots and crashes is a normal part of the game as it's not a bug - they are waiting for Sony. There's also another huge issue (for me) of the speakerphone never working correctly at the Sony volumes. They have to turn the volume of the whole ROM down to compensate and this makes it hard to hear in a noisy environment, a frustrating bug for me which has hung around since 4.1. You can max the volume up with a file which someone did, but it breaks the speakerphone then so you can only have one or the other.
In a lot of ways I am one of those guys though, I do like to experiment and am comfortable with the processes but I always find what I flash causes me some frustration before long so I go back to stock. If I had the knowledge to help fix problems it would be a different story and i'd stick with custom but as I can't I don't really see the point until 4.3 sources come out and its all a bit more stable.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!
Click to expand...
Click to collapse
Hi guys,
I want to root my device using the guide posted on this forum, but I'm not sure how I would go about restoring it to factory state to regain my warranty in case I need to send the phone for repairs. I previously had a One M7 and the whole process of rooting and flashing stuff was child's play, but it seems much more difficult with the xperia, espeically there seem to be nowere near as much guides and resources.
Has any of you done what I'm asking about? Is it even possible? This question is literally the only thing holding me back from rooting the phone, as the uselessness of my SD card is starting to seriously annoy me and the fact that we were promised the lollipop update in February and it's still not here nearly halfway through March.
Use Sony PC Companion to flash back to completely stock.
seklerek said:
Hi guys,
I want to root my device using the guide posted on this forum, but I'm not sure how I would go about restoring it to factory state to regain my warranty in case I need to send the phone for repairs. I previously had a One M7 and the whole process of rooting and flashing stuff was child's play, but it seems much more difficult with the xperia, espeically there seem to be nowere near as much guides and resources.
Has any of you done what I'm asking about? Is it even possible? This question is literally the only thing holding me back from rooting the phone, as the uselessness of my SD card is starting to seriously annoy me and the fact that we were promised the lollipop update in February and it's still not here nearly halfway through March.
Click to expand...
Click to collapse
Firstly downgrade to a rootable firmware(ftf) using Flashtool. Then root. Backup TA partition (most important step). After this, even if you unlock bootloader, your TA partition is safe. After that if you want to restore warranty you may go back to the rootable firmware using Flashtool and then root and restore the TA partition. Viola you have your warranty back. Restoring the TA partition locks the bootloader and gives back the DRM keys and so you get your warranty.you may even flash the firmware all over to unroot (just to be on the safe side)
DO NOT UNLOCK BOOTLOADER BEFORE BACKING UP TA PARTITION OF YOU CARE ABOUT WARRANTY
Sent from my D5833 using XDA Free mobile app