Related
Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred
RealFred2 said:
Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred
Click to expand...
Click to collapse
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.
gavster26 said:
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.
Click to expand...
Click to collapse
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)
RealFred2 said:
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)
Click to expand...
Click to collapse
If thats the firmware you want then by all means flash that bro. The nandroid backup from your wifes phone will be just the same. the backup will be on her sdcard in the file /clockworkmod/backups/ just copy it and paste it to your sdcard. restore it then flash the kernel.
There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i
c4cyro said:
There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i
Click to expand...
Click to collapse
Thanks, c4cyro; I managed to relock with flashtool (it had not worked when I had tried before, but suddenly it did); even so, I can't load from pc companion. Did you also unroot your phone? I've seen elsewhere that that can have something to do with it. I'd like to do this just because so far I haven't been able to (and I hate not being able to do stuff, even when I'm a noob).
Thanks again,
Fred
no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567
c4cyro said:
no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567
Click to expand...
Click to collapse
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred
RealFred2 said:
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred
Click to expand...
Click to collapse
maybe. does it recognise that it's a tipo or it just says that there's no software available?
c4cyro said:
maybe. does it recognise that it's a tipo or it just says that there's no software available?
Click to expand...
Click to collapse
It picks it up as Tipo Dual (listed as St21i2 instead of St21a2 bc the Gimlo .3 firmware -- which is the right one for the dual -- is the "i" version).
I've just found this firmware, which seems to be stock, so I'm going to try this:
1) try out this firmware (http://forum.xda-developers.com/showthread.php?t=2044944; 11.0.A.6.5 stock) and see what it is and how it works;
2) then install the base stock for the Tipo Dual for Gimlo (which for the dual is );
3) then install the Gimlo firmware and ROM, and see if I can get it to work the way I want (going mostly stock except for the loader, which I really like the one I'm using on Gimlo);
Will report back on how things turn out and what I end up sticking with!
Thanks again for your help, it's good to feel like I'm not hopping about on one foot on my own.
Fred
All the best!!
Hey everyone, I just unlocked my bootloader, only THEN to read that after doing so, I lose something called 'DRM keys'. And now my phone is refusing to boot (soft brick). I fear re-installing the android OS will permanently make me lose these keys, as I never had the chance to back them up. Is there any way I can still get these keys back??? AND ANY WAY TO GET MY PHONE WORKING?
PLEASE respond ASAP, I need to make calls with this phone for my job.
Ok I see your phone is on bootloop... you have to flash stock firmware if you don't know what file was removed/modified who knows haha
Download the latest FTF file for your device, check here Xperia E Official Thread [ROMS, MODS, ROOT, FTFS, HOW TO]
You have to flash that file with FlashTool, if you don't know how to use this, check here [TUTORIAL] HOW TO FLASH STOCK ROMs WITH FLASHTOOL is for XZ but it's the same procedure for XE and all sony devices...
Finally DRM Keys...
Some time ago, we talked about the importance of backing up the TA partition on Sony Xperia devices. Doing so on Sony Xperia devices saves your DRM keys. Why is this important? These keys are required in order to use a few proprietary software bits such as Bravia Engine in the Gallery app and OTA updates.
Click to expand...
Click to collapse
Source: XDA Portal
Hope you can get back your device, have a good day / night!
http://forum.xda-developers.com/showthread.php?t=2631456
Sent from a bad phone
Reflash stock FTF - that always works.
Oh, wait... MatsPunt's guide tells you to do exactly that... whoops.
I firstly rooted my phone, then unlocked bootloader.
after unlocking of bootloader, my phone doesn't boot again. (blocked on the boot animation)
then I flashed Extened stock kernel v5, installed kitkat, phone couldn't turn on wifi.
I format system and all datas, i tried to install jb, wifi came back, but can't connect. (only save id and password)
Now I flashed back CM11 from son fxp website, all works except wifi...
what should i do for get back wifi? please help me... :crying:
Anyone can help me please...
:crying:
hebarakisun said:
I firstly rooted my phone, then unlocked bootloader.
after unlocking of bootloader, my phone doesn't boot again. (blocked on the boot animation)
then I flashed Extened stock kernel v5, installed kitkat, phone couldn't turn on wifi.
I format system and all datas, i tried to install jb, wifi came back, but can't connect. (only save id and password)
Now I flashed back CM11 from son fxp website, all works except wifi...
what should i do for get back wifi? please help me... :crying:
Click to expand...
Click to collapse
hebarakisun said:
Anyone can help me please...
:crying:
Click to expand...
Click to collapse
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Hnk1 said:
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Click to expand...
Click to collapse
Thank you so much for your reponse..
I see that I must get back stock rom on my phone.
on the download page, there was 2 links, FTF file, part1 and part2,
please can you explain me how to flash it via flashtool?
My phone is unlocked bootloader.
hebarakisun said:
Thank you so much for your reponse..
I see that I must get back stock rom on my phone.
on the download page, there was 2 links, FTF file, part1 and part2,
please can you explain me how to flash it via flashtool?
My phone is unlocked bootloader.
Click to expand...
Click to collapse
I am glad I could be of any help!
Well, you can use any 15.3.A.1.17 ftf file depending on the region. Usually you do not have any problems apart from supported languages on your phone if you flash some other FTF file apart from your region.
Basically, you will need to download both the files and then you will need to extract them both to find one FTF file. from the link i shared. However, you can flash any FTF file with latest version x.x.17. Make sure you flash FTF made for your own device or you may permanently brick your phone for good. The link I am sharing below is for Xperia L
Here is a place where all the FTF files are compiled together by @Joel16
FIND IT HERE
The guide to flash an FTF file is as follows :
Look here
Remember the guide i sent you is for another device but as long as you flash Xperia L (taoshan) FTF file, it would be fine. Also, you would need to flash everything including kernel.
Good Luck and tell me if you need anything more at all!
Hnk1 said:
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Click to expand...
Click to collapse
I see that you helped the OP get through Wifi problem , but I am also having same problems , maybe more.
I clean installed many different ROMs , including Flashing the 15.3.A.1.17 Stock ROM.
I tried even different KK kernels and JB kernels(for Stock ROM) , but no luck.
Plus I have also tried flashing a kernel through Flashtool and reflashing it from recovery , but my Wifi doesn't work and after a hell lot of reboot cycles , I sometimes manage to get it on , which eventually turns off after crashing the phone after some indefinite time.
Please help.
coolhz said:
I see that you helped the OP get through Wifi problem , but I am also having same problems , maybe more.
I clean installed many different ROMs , including Flashing the 15.3.A.1.17 Stock ROM.
I tried even different KK kernels and JB kernels(for Stock ROM) , but no luck.
Plus I have also tried flashing a kernel through Flashtool and reflashing it from recovery , but my Wifi doesn't work and after a hell lot of reboot cycles , I sometimes manage to get it on , which eventually turns off after crashing the phone after some indefinite time.
Please help.
Click to expand...
Click to collapse
First of all, how did you unlock your bootloader?
Secondly, when you are flashing an FTF, have you flashed any FTF for a different variant ?
Like if you have c2105 and you flashed c2104 ?
What about your WiFi bug, tell me details about how it started and what kind of error do you get. The more the details, the more you are helping yourself out .
Lastly, is your device in warranty and can you claim it for an exchange if you relock your bootloader?
Hnk1 said:
First of all, how did you unlock your bootloader?
Secondly, when you are flashing an FTF, have you flashed any FTF for a different variant ?
Like if you have c2105 and you flashed c2104 ?
What about your WiFi bug, tell me details about how it started and what kind of error do you get. The more the details, the more you are helping yourself out .
Lastly, is your device in warranty and can you claim it for an exchange if you relock your bootloader?
Click to expand...
Click to collapse
Bootloader was unlocked through Flashtool from Androxyde.
Wifi problem started when I was using something like FXP 325 , that would be a couple of months ago , but then it was minor , just a reboot would do.
But now I have tried many ROMs(of course clean installed) , kernels(with essentials wiped) , also stock ROMs (.26 ,.12 ,.14 ,.17) all show wifi problems.
By that I know that its a user specific issue. My warranty is over , but I will have no problem paying a bit with relocked bootloader if repairs are needed.
But if there's a way I can fix it at home , please tell. And yeah , I always flash C2104 files as mine is C2104.
coolhz said:
Bootloader was unlocked through Flashtool from Androxyde.
Wifi problem started when I was using something like FXP 325 , that would be a couple of months ago , but then it was minor , just a reboot would do.
But now I have tried many ROMs(of course clean installed) , kernels(with essentials wiped) , also stock ROMs (.26 ,.12 ,.14 ,.17) all show wifi problems.
By that I know that its a user specific issue. My warranty is over , but I will have no problem paying a bit with relocked bootloader if repairs are needed.
But if there's a way I can fix it at home , please tell. And yeah , I always flash C2104 files as mine is C2104.
Click to expand...
Click to collapse
I think you should boot into recovery and do a full wipe including internal/ dalvik/everything including SD card. Don't just factory reset but do a complete wipe. (Twrp has that option. In other recoveries usually you have to do it individually.) So go in recovery and wipe everything you can see that could be wiped.
If that doesn't work,
I suggest you relock your bootlader and see if that helps.
Also try to relock bootloader and unlock it via Sony official way. See that works for you or not.
Seems like a software issue most probably because I'm afraid you didn't backup TA while unlocking bootloader and sometimes the keys are lost and it causes some problems like WiFi. Also, the reason is more likely because of the fact that you didn't do it officially. it could be hardware as well but that's very rare. I would suggest that only give it to someone who knows hardware quite well.
Update me what happens!
Hnk1 said:
I think you should boot into recovery and do a full wipe including internal/ dalvik/everything including SD card. Don't just factory reset but do a complete wipe. (Twrp has that option. In other recoveries usually you have to do it individually.) So go in recovery and wipe everything you can see that could be wiped.
If that doesn't work,
I suggest you relock your bootlader and see if that helps.
Also try to relock bootloader and unlock it via Sony official way. See that works for you or not.
Seems like a software issue most probably because I'm afraid you didn't backup TA while unlocking bootloader and sometimes the keys are lost and it causes some problems like WiFi. Also, the reason is more likely because of the fact that you didn't do it officially. it could be hardware as well but that's very rare. I would suggest that only give it to someone who knows hardware quite well.
Update me what happens!
Click to expand...
Click to collapse
nothing worked , issue still persists , also I would like to tell that Bluetooth also doesn't work along with Wifi.
I cleaned everthing , went back to stock , locked bootloader also. but no luck.
coolhz said:
nothing worked , issue still persists , also I would like to tell that Bluetooth also doesn't work along with Wifi.
I cleaned everthing , went back to stock , locked bootloader also. but no luck.
Click to expand...
Click to collapse
Well, I would say that this happened due to unlocking your bootloader without a TA backup. I am afraid there isnot much you can do as every device has a specific TA code and I am not sure if someone would be interested to share TA backup with you. Even if they do, I am not sure if it would be helpful.
I would share you with all the options you have got :
Go to question/answer and ask for TA backup from someone, this wouldnot work mostly and I would tell you to do everything with caution and on your own risk but that all that could help you out for now at home really. Try someone else TA and see if it is accepted and the WIFI starts to work again. (But use it as a last resort)
If I may add, if you can get a Jtag guy, he might be able to fix your device for a cost but I am not sure of that either.
Another option for you would be asking an expert to repair your phone and telling him all about TA/ unlocking bootloader. If he understands what you are talking about, it just means he knows what you want him to do. If he doesnot, it probably is a bad idea to pay him. You can add it could be a hardware issue as well just in case. However, some times those people use different sort of cables tools to flash FTF so maybe that could be helpful. You can say, you would only pay if WIFI and bluetooth starts to work again! (Second best option ??? )
I honestly do not know how to solve issues related to TA I also suggest write in Xperia Z1 / Z / Z2 forums about your problem as I remember that many of them had many issues due to unlocking bootloader. Sometimes unrooting solves the problem as well. I think that forum users be able to help you much better! Make sure you add all the details about how it happened, what you did and which device are you using and how everything you tried so far hasnot worked. Make sure you mention all tips you got and those that didnot work for you!
Good Luck!
Hnk1 said:
Well, I would say that this happened due to unlocking your bootloader without a TA backup. I am afraid there isnot much you can do as every device has a specific TA code and I am not sure if someone would be interested to share TA backup with you. Even if they do, I am not sure if it would be helpful.
I would share you with all the options you have got :
Go to question/answer and ask for TA backup from someone, this wouldnot work mostly and I would tell you to do everything with caution and on your own risk but that all that could help you out for now at home really. Try someone else TA and see if it is accepted and the WIFI starts to work again. (But use it as a last resort)
If I may add, if you can get a Jtag guy, he might be able to fix your device for a cost but I am not sure of that either.
Another option for you would be asking an expert to repair your phone and telling him all about TA/ unlocking bootloader. If he understands what you are talking about, it just means he knows what you want him to do. If he doesnot, it probably is a bad idea to pay him. You can add it could be a hardware issue as well just in case. However, some times those people use different sort of cables tools to flash FTF so maybe that could be helpful. You can say, you would only pay if WIFI and bluetooth starts to work again! (Second best option ??? )
I honestly do not know how to solve issues related to TA I also suggest write in Xperia Z1 / Z / Z2 forums about your problem as I remember that many of them had many issues due to unlocking bootloader. Sometimes unrooting solves the problem as well. I think that forum users be able to help you much better! Make sure you add all the details about how it happened, what you did and which device are you using and how everything you tried so far hasnot worked. Make sure you mention all tips you got and those that didnot work for you!
Good Luck!
Click to expand...
Click to collapse
bro I think I got it , I absent mindedly relocked bootloader through Flashtool , as I was going back to stock after months . I do have my TA backup.And I will restore it and see what happens. Thanks you just made me remeber that
I've seen lots of complains about new Flashtools versions, regarding FSC scripts and various kind of bricks that make the RIL break without any apparent reason, so I've decided to explain it. I'm the author of the FSC script for the M2, and I sent it to Androxyde so that he included it in the latest compilations of Flashtools some months ago. I'm going to explain as short as I can what it does:
A FSC script is a Flashing Template used by the 0.9.19 flashtools engine, which is actually designated to flash Xperias of seventh and eighth generation, this means, Z3+ (Z4) and newer. This happens because of some modifications to the S1 protocol made by Sony, starting in those devices. Provided that, to use the new flashing engine, I saw myself in the need of creating one for our devices. You can find it in C:\Users\<Your-User>\.flashTool\devices\D230X\default.fsc. This script comes pre-installed from Flashtools 0.9.19.8. If you open it, you can see it's actually a series of steps, predefined, like opening TA partition 2, set flashing status, closing it, etc.
The problem here is that, this script was created from a USB Log generated by using Emma to flash a 18.3.1.C.1.17 firmware, which means this script is for KitKat, not Lollipop.
This means that, for example, the upload of the sin images is not done in the same exact order as it was intended to be (instead of uploading first the TAs, it uploads the dbi and appsboot, etc), and, as in KitKat there was no Apps_log, Flashtools will skip it flash even though you told it to flash the sin, and lastly, in case it messes up something, it makes a backup of your TA state before starting to flash, and then restore it back when all flashes finishes.
Being that said, I personally consider that using a KitKat FSC to flash a Lollipop FTF is, at least, DANGEROUS. So, I'd definetly recommend you to delete it if you don't plan to use it, or be really careful and click always on NO when the program prompts if we want to use it.
TL;DR: Go to C:\Users\<Your-User>\.flashTool\devices\D230X\ and delete the default.fsc to avoid any brick / compatibility conflict.
Lucky, I had never had bootloop after flashing Stock ROM, sir. I always click YES, because i dont know about FSC script. Hmm during this time I have chosen wrong choice. Nice info, sir.
Glad i hardly updated flashtool, and have the 0.9.19.0 version
linuxct said:
You can find it in C:\Users\<Your-User>\.flashTool\devices\D230X\script.fsc.
Click to expand...
Click to collapse
You refer to a script.fsc file but in my case there is a default.fsc file, is this the same script?
If I understand correctly this script can only be used safely to flash a KK FTF and in all other cases it is dangerous to use?
BlackSheepToo said:
You refer to a script.fsc file but in my case there is a default.fsc file, is this the same script?
If I understand correctly this script can only be used safely to flash a KK FTF and in all other cases it is dangerous to use?
Click to expand...
Click to collapse
I think that is the script, as I deleted that before flashing and everything went well with no script popups.
BlackSheepToo said:
You refer to a script.fsc file but in my case there is a default.fsc file, is this the same script?
Click to expand...
Click to collapse
Yeah, I'm sorry for the confusion. I deleted it some months ago when I noticed something was going wrong, and it wasn't until the day I wrote that post when I realized what was actually going on here.
BlackSheepToo said:
If I understand correctly this script can only be used safely to flash a KK FTF and in all other cases it is dangerous to use?
Click to expand...
Click to collapse
Correct. If you want to flash 18.3.1.C.1.17 you can use it. If you use it in Lollipop, you'll be in risk of a brick.
----
I'm almost back on business guys, my last exam is on friday :victory:. I'll try to solve some of your requests today, and the ones I can't attend will be solved right when I finally finish, hopefully.
Is it saver to use the M2 script when flashing a KK FTF or does FlashTool also backup and restore the TA state by default?
Btw succes with you exam! :good:
BlackSheepToo said:
Is it saver to use the M2 script when flashing a KK FTF or does FlashTool also backup and restore the TA state by default?
Btw succes with you exam! :good:
Click to expand...
Click to collapse
I've no idea since I didn't try that, but I guess it'll make the backups anyway
And thanks!
So in other words do NOT upgrade from 0.9.18.6 as I always suggested. That guy took a great tool and made a bricking mess.
Miche1asso said:
So in other words do NOT upgrade from 0.9.18.6 as I always suggested. That guy took a great tool and made a bricking mess.
Click to expand...
Click to collapse
That's OK till you get a 2015 or newer device then you have to use the latest version of flashtool. I'm still on 9.18.6 myself it works flawlessly. Till I get my shiny new Xperia upgrade in July then I'll have to update to the latest version providing whatever device I get is listed as compatible with it.
[email protected] said:
That's OK till you get a 2015 or newer device then you have to use the latest version of flashtool. I'm still on 9.18.6 myself it works flawlessly. Till I get my shiny new Xperia upgrade in July then I'll have to update to the latest version providing whatever device I get is listed as compatible with it.
Click to expand...
Click to collapse
Sure, I meant when using it with the Xperia M2. But I am not looking forward to use Flashtool with newer devices. Tools like that should be monkey proof.
aidy.lucas said:
That's OK till you get a 2015 or newer device then you have to use the latest version of flashtool. I'm still on 9.18.6 myself it works flawlessly. Till I get my shiny new Xperia upgrade in July then I'll have to update to the latest version providing whatever device I get is listed as compatible with it.
Click to expand...
Click to collapse
Hi everybody including @aidy.lucas, I'm trying to get Z5 style by following linuxct's Tutorial.
Please guide me which FlashTool version is appropriate for me lest I brick my phone and, where to get it.
I'm on Stock Rom on latest 5.1.1 Lollipop built 18.6.A.0.182.
I have Locked Bootloader.
I'm rooted.
The Unborn said:
Hi everybody including @aidy.lucas, I'm trying to get Z5 style by following linuxct's Tutorial.
Please guide me which FlashTool version is appropriate for me lest I brick my phone and, where to get it.
I'm on Stock Rom on latest 5.1.1 Lollipop built 18.6.A.0.182.
I have Locked Bootloader.
I'm rooted.
Click to expand...
Click to collapse
I think that the latest version of Flashtool works ok, but if you want to be safe use 0.9.18.6 version it's in Flashtool download page or just Google it
Good Luck!
Sent from my XPERIA M2
Thx for the warning.
Regards!
Enviado desde mi Xperia M2 Aqua usando Tapatalk
@linuxct so this mean old flashtool without that FSC things and newer device is not compatible? We can't flash newer devices without fsc? Are you guys sure its changes in s1 protocol? Or maybe changes is only in newer jars from sony? I have some old unfinished works when I made xflasher in pure C and which depends on libusb instead of the gordongate, maybe somebody try to see if it will work without fsc?
@Androxyde?
munjeni said:
@linuxct so this mean old flashtool without that FSC things and newer device is not compatible? We can't flash newer devices without fsc?
Click to expand...
Click to collapse
Yep, it's not possible, but Flashtool comes bundled with most of them already (check them here)..
So, Androxyde's approach to this was, at first instance using the new behaviour of always requesting the FSC to flash the device (using the second version of the flash engine), starting from Flashtool 0.19.0 until 0.19.something (can't recall right now). In between those two versions, it was when I created the FSC script, and sent it to Androxyde so he could add it to Flashtools, and so Xperia M2 users could use future versions of Flashtools... But, starting from that version I can't recall, it had the two behaviours, when a FSC was found, it asked the user whether to use it or not, using then the old flashing engine.
munjeni said:
Are you guys sure its changes in s1 protocol? Or maybe changes is only in newer jars from sony? I have some old unfinished works when I made xflasher in pure C and which depends on libusb instead of the gordongate, maybe somebody try to see if it will work without fsc?
Click to expand...
Click to collapse
I remember when all this madness started Androxyde mentioned S1 protocol somewhere, but don't quote me on that please, it was quite a long time ago, and atm I'm not sure anymore where he mentioned it
I'd personally try your approach, but I don't own any Xperia devices anymore, sadly...
I am still on old xperia z1c and have no idea whats going on, found fsc word today Will be great if somebody provide changes to s1 protocol (if there is realy any changes), probably there is loader.sin changes probably? Thats realy shame if so ny decided to change a way for well known and well used flashtool old flashing behavior
linuxct said:
Yep, it's not possible, but Flashtool comes bundled with most of them already (check them here)..
Click to expand...
Click to collapse
But whats going on when there is no fsc? Is there any error? Interrupt? Please more details
munjeni said:
But whats going on when there is no fsc? Is there any error? Interrupt? Please more details
Click to expand...
Click to collapse
If there's no FSC and the Xperia is an old gen device, it'll just flash the device using the old flashing engine, which is the case of the Xperia M2.
If it's a new gen device, which requires using the second version of the flashing engine, it'll most likely fail, requesting it most likely.
From what I remember, when you connect the device in flash mode it reads the device info. Probably, that's where it checks if it's a new or old gen device, but, I'm not sure...
fsc things
Hi all
FSC is just a feature of my own. Nothing to see with S1 protocol.
If ever you open a .fsc file, you will see it is nothing more than a set of instructions which drive the flash session.
How to generate an accurate fsc ? do a device repair using Xperia Companion while doing a USB traffic capture using SImple USB Logger (Windows only). The capture logfile can then be parsed by Flashtool to generate the fsc file. For Flashtool to be able to guess sin file names, flashed sin file used by Xperia Companion have to be accessible to the usb log parser process so that a header comparison is done to guess file name.
Why I used fsc approach : it is the best way to flash the exact same way as Xperia companion does (file and ta flash order, some specific setloader commands too)
How is fsc searched : first it searches in FLASHTOOLDATA/mydevices then in FLASHTOOLDATA/devices
Because devices folder is a git repo synced with github at each flashtool startup, any modification in devices folder will be erased so I created a mydevices folder for local customizations. items in mydevices will always have the priority over devices folder.
For the search mechanism in 0.23.1.0 :
example for F8331 39.2.A.0.374 firmware :
first search for mydevices/F83XX/F8331_39.2.A.0.374.fsc
then for mydevices/F83XX/39.2.A.0.374.fsc
then for mydevices/F83XX/39.2.A.0.fsc
then for mydevices/F83XX/39.2.A.fsc
then for mydevices/F83XX/39.2.fsc
then for mydevices/F83XX/39.fsc
if nothing found in mydevices then it does the same search in devices/F83XX/
so if the fsc is the same for all 39.2.XXX.XXX.XXX firmwares, 39.2.fsc can match
FSC can be included into ftf at ftf creation. In such case, the bundled fsc (considered as trusted) will be used without asking anything to the user (the recomended way according to me)
Hello guys,
im using a Xperia XZs 32GB non Dual and i tried to build AOSP which still fails on my cloud instance.
In the meantime i unlocked the bootloader and after that, i noticed the non working camera i.e. green pictures caused by the DRM stuff.
So i tried this fix with kernel combined with the TWRP img and flashed it. After that im stuck at the Sony logo.
Is there any ROM i can flash now? ( i don't have windows and those usb-passthrough, adb stuffs with kvm is a poor experience)
or does some dev here already build successfully the AOSP images that i can flash to unbrick this mess?
regarding my build problems, i also posted in the sony dev forum [link]https://talk.sonymobile.com/t5/General-Discussion/Xperia-XZs-AOSP-7-x-build-not-working/m-p/1229197#M922[\link]
Thanks for any Help guys
EDIT: If someone ****ed up like me, i could restore it with the Xflasher tool from the thread here on XDA.
All you can do is flash the stock rom in flashtool
pikeylfc said:
All you can do is flash the stock rom in flashtool
Click to expand...
Click to collapse
i installed windows 7 x64 on a spare harddisk and tried the latest and 2 previous versions of flashtool.
The newest one and the previous one went to "not responding" and the oldest one hang's on the last step including the specific XZs files for flashtool which i downloaded from another thread here.
Are already usable and with flashtool flashable files for the XZs out there?
I am able to boot to fastboot and to rescue state. I have also TWRP on it.
This sony flashtool doesn't work for this device or maybe cause of the unlocked Bootloader.
EDIT: is this legit? it looks sketchy: G8231_1308-6105_41.2.A.0.235-R4D_Customized_IT.ftf (i cannot post links, but its from android.gl and hosted on alafile which you have to pay for cause of 3gb filesize)