Develop Bugs

[A] Might be the answer for most of us regarding flashtool

So i check around the internet and found this. If you cant see the firmware content when selecting your ftf files. I found that by opening the ftf files using 7zip and deleting the for me it is the R800i_4.0.2.A.0.42_Generic_UK file inside then try to check whether the firmware content can be seen.
After deleting the file, the content can be seen. But i didnt try to flash it as i fear something might go wrong and hard bricked my phone. Anybody can test it out?
Idea from : lynxdog. ( I just played around the ftf folder to test it out whether can see the firmware content. )
Disclaimer :
Do it at your own risk.
I will not be held responsible for any damages caused to your smartphone. ( Test at your own risk )

AthrunIJ said:
So i check around the internet and found this. If you cant see the firmware content when selecting your ftf files. I found that by opening the ftf files using 7zip and deleting the for me it is the R800i_4.0.2.A.0.42_Generic_UK file inside then try to check whether the firmware content can be seen.
After deleting the file, the content can be seen. But i didnt try to flash it as i fear something might go wrong and hard bricked my phone. Anybody can test it out?
Idea from : lynxdog. ( I just played around the ftf folder to test it out whether can see the firmware content. )
Disclaimer :
Do it at your own risk.
I will not be held responsible for any damages caused to your smartphone. ( Test at your own risk )
Click to expand...
Click to collapse
As you have discovered the .ftf is simply a compressed file using a different file extension. The .sln files are also simply .img so you can use fastboot to flash these as required. I found that the UK generic 2.3.4 ftf file refused to decompress and be processed by flashtool so I manually extracted/unzipped the files and used fastboot to flash the kernel/system/userdata .sln to achieve what I wanted.

nurofenplus said:
As you have discovered the .ftf is simply a compressed file using a different file extension. The .sln files are also simply .img so you can use fastboot to flash these as required. I found that the UK generic 2.3.4 ftf file refused to decompress and be processed by flashtool so I manually extracted/unzipped the files and used fastboot to flash the kernel/system/userdata .sln to achieve what I wanted.
Click to expand...
Click to collapse
Same as the ICS Beta firmware i guess. As it came in a form of .img file instead of .ftf. file. So this firmware (uk generic 2.3.4) is only avail for unlock bootloader user. Bump!!!

sdojoin said:
Same as the ICS Beta firmware i guess. As it came in a form of .img file instead of .ftf. file. So this firmware (uk generic 2.3.4) is only avail for unlock bootloader user. Bump!!!
Click to expand...
Click to collapse
I'll check but it is a signed kernel and should flash just fine on a locked bootloader. I'll test it later this afternoon and confirm.

nurofenplus said:
I'll check but it is a signed kernel and should flash just fine on a locked bootloader. I'll test it later this afternoon and confirm.
Click to expand...
Click to collapse
If the .img file can be compile to be an .ftf file mybe u should try the Ics beta. If it can mybe it can flash on a locked bootloader as-well. If....

sdojoin said:
If the .img file can be compile to be an .ftf file mybe u should try the Ics beta. If it can mybe it can flash on a locked bootloader as-well. If....
Click to expand...
Click to collapse
The flashtool has an option under advance menu called bundle creation. I haven't used it but I'm guessing you point it at a folder with the collection of files (system, kernel etc...) and it does the rest.

nurofenplus said:
The flashtool has an option under advance menu called bundle creation. I haven't used it but I'm guessing you point it at a folder with the collection of files (system, kernel etc...) and it does the rest.
Click to expand...
Click to collapse
Ooo.. I haven't try it too.. Mybe i'll giv it a try when i get home. Thanks for the hint.

I think I'll try this myself as well!
Plus, I'm a locked user so I'm glad to try this out, I haven't thought about this idea. Lemme know how it goes for you, sdojoin!

Selim873 said:
I'm trying to download the beta but when I click the Accept button on the EULA, nothing happens, the reject button takes me back to the homepage obviously, but the accept button does nothing, does anybody have this mirrored?
Click to expand...
Click to collapse
I think the off. Beta link is dead after sony announce that play wont get any ics updte. Sory man..

sdojoin said:
I think the off. Beta link is dead after sony announce that play wont get any ics updte. Sory man..
Click to expand...
Click to collapse
That's okay, I found it though, but I have no idea how to work with the IMG files, as in, can't convert them into a group of .SIN_FILE_SET files to make them work with the Flash Tool bundle creator. So that won't work, because as far as I know, converting IMG to SIN isn't possible.

Selim873 said:
That's okay, I found it though, but I have no idea how to work with the IMG files, as in, can't convert them into a group of .SIN_FILE_SET files to make them work with the Flash Tool bundle creator. So that won't work, because as far as I know, converting IMG to SIN isn't possible.
Click to expand...
Click to collapse
Too many unknown words and language.... =.=, actually i post this to hlp some user who experience what i experience. the ftf files not showing firmware content and as a result cant flash it. so, basically, open the ftf files using 7zip or anything. then delete the file that has the same name as the ftf file itself. close the 'open archive' then voila working ftf file. then just follow the guide on using flashtool to flash. , learn it from many guys. And my utmost gratitude to the ppl who hlp.

AthrunIJ said:
Too many unknown words and language.... =.=, actually i post this to hlp some user who experience what i experience. the ftf files not showing firmware content and as a result cant flash it. so, basically, open the ftf files using 7zip or anything. then delete the file that has the same name as the ftf file itself. close the 'open archive' then voila working ftf file. then just follow the guide on using flashtool to flash. , learn it from many guys. And my utmost gratitude to the ppl who hlp.
Click to expand...
Click to collapse
Its already a diff discussion. Lol So it dont matter. If we cant flash this .ftf then just move on with a diff .ftf. No biggie.

The decrypt function in flashtool uses the temporary files that the official sony ericcson update tool creates in the background when upgrading your device. From these files flashtool extracts data and partition info etc... and generates the .sin files.
The bundle function then collects these files and creates a single .ftf file. So, I flashed the UK 2.3.3 and then relocked my bootloader (se update tool will not work with an unlocked bootloader). I then ran the sony update tool and let it download the latest 2.3.4 firmware and saved the files to another location.
Opened flashtool, ran the decrypt function using the folder I saved the se files to then the bundle function to create the ftf. I was able to successfully flash the new ftf file without issues. Anyway, probably a flashtool tutorial around somewhere.

Root xperia z1f

i am using z1f, SO-02F. I bought it from japan, it run 4.2.2 14.1.H.1.281 and now i want to root it without unlock bootloader to use Titanium backup and delete many docomo app. i dont want to install d5503 4.3 rom because it is many bugs. Thanks everyone

anyone can help me?

Hi! Just follow this guide... But start with step #10
http://forum.xda-developers.com/showthread.php?t=2642081
The first root from this device started with the jap version so you guys should find it easier to root than the global variant.

Riyal said:
Hi! Just follow this guide... But start with step #10
http://forum.xda-developers.com/showthread.php?t=2642081
The first root from this device started with the jap version so you guys should find it easier to root than the global variant.
Click to expand...
Click to collapse
tks u so much. i will try it now

Kid1412_92 said:
tks u so much. i will try it now
Click to expand...
Click to collapse
Ohh btw if you do that rooting method please do take note that after the procedure you would end up having a generic ROM and not the docomo ROM.

Riyal said:
Ohh btw if you do that rooting method please do take note that after the procedure you would end up having a generic ROM and not the docomo ROM.
Click to expand...
Click to collapse
Can i flash the docomo ROM replace generic rom in the final step
Gửi từ SO-02F của tôi bằng cách sử dụng Tapatalk

You would need to create a ROM dump then... The final step is flashing the file z1c-43-uk.system.flashable.zip in recovery which contains a UK generic ROM. Now what you need to do if you want a docomo version is
1. Download flashtool
2. Extract system.sin in ftf file of docomo
3. Extract ext4 image from system.sin using flashtool
4. Extract the contents of system.ext4 and replace the ones in the z1c-43-uk.system.flashable.zip
then flash the zip file you just modified. You should then get a rooted docomo ROM. Kinda hard to do if you don't know how but that's the only way for now sorry I could probably create one for you but that would be after a couple of days as I'm pretty busy this week.

Riyal said:
You would need to create a ROM dump then... The final step is flashing the file z1c-43-uk.system.flashable.zip in recovery which contains a UK generic ROM. Now what you need to do if you want a docomo version is
1. Download flashtool
2. Extract system.sin in ftf file of docomo
3. Extract ext4 image from system.sin using flashtool
4. Extract the contents of system.ext4 and replace the ones in the z1c-43-uk.system.flashable.zip
then flash the zip file you just modified. You should then get a rooted docomo ROM. Kinda hard to do if you don't know how but that's the only way for now sorry I could probably create one for you but that would be after a couple of days as I'm pretty busy this week.
Click to expand...
Click to collapse
tks u so much for help me, i will try it now and if this isnt work, i will ask u for help a next week :victory:
tks u ver two :laugh:

Ok here's a little more easier guide for you....
1. Download Docomo ftf
2. Extract the ftf using winrar, 7zip, winzip or any archiving tool.(I suggest 7zip though)
3. Get the system.sin
4. Open flashtool. http://www.flashtool.net/download.php
5. Navigate to Tools->Sin Editor
6. Select system.sin
7. Select Extract Data button
8. Flashtool should dump system.ext4 image
9. Download this application http://www.diskinternals.com/linux-reader/
10. Open application and open system.ext4
11. It upon opening it should show system files.
12. Extract everything and put it inside z1c-43-uk.system.flashable.zip
Special note: z1c-43-uk.system.flashable.zip has a tgz archive inside. You need to put all the system files you extracted inside the tgz file for it to work.
13. Flash your modified sz1c-43-uk.system.flashable.zip thru recovery
14. Done.

Riyal said:
Ok here's a little more easier guide for you....
...
12. Extract everything and put it inside z1c-43-uk.system.flashable.zip
Special note: z1c-43-uk.system.flashable.zip has a tgz archive inside. You need to put all the system files you extracted inside the tgz file for it to work.
13. Flash your modified sz1c-43-uk.system.flashable.zip thru recovery
14. Done.
Click to expand...
Click to collapse
If you do that in Windows then you lose all the file permissions information. I do not think it is really a good idea. It is much more reliable to mount the ext4 image in Linux with options "-o loop,ro" and then create the system.tgz natively using tar in Linux.
I have done that myself (with 142 DE-T ftf) and it worked just fine at first try.

LaizyJumper said:
If you do that in Windows then you lose all the file permissions information. I do not think it is really a good idea. It is much more reliable to mount the ext4 image in Linux with options "-o loop,ro" and then create the system.tgz natively using tar in Linux.
I have done that myself (with 142 DE-T ftf) and it worked just fine at first try.
Click to expand...
Click to collapse
Ahh you're right! Just looked at the script right now and it doesn't set permissions upon installation. I was assuming it would like any usual flashable zips.

have u rooted z1f docomo? i want to root it so i need to talk with u... im living in japan.. my all of social network nickname is bloodtear225. example facebook, skype, LINE, viber ect...

need help
Hi Riyal, I have tried to read all comment here and the link provided but m still confused on how to root Xperia Z1 f

How do I get to root on my Xperia T3 D5106 ???

Friends, I'm there one week direct non-stop trying to root on my Sony Xperia T3 (D5106) 18.1.A.2.25 version, do not know what else to do, I've tried all the tutorials xda forum .. all give error .. when I give in flash D5103 model, error appears here, my T3 only works on the D5106 model .. How do I get to root on my Xperia T3 D5106 ??? For God's sake = ( :crying:

You can follow the tutorials found in other threads like http://forum.xda-developers.com/xperia-t3/help/how-to-root-xperia-t3-18-1-2-25-t3007487 or http://help.howproblemsolution.com/1377446/tutorial-root-xperia-t3-firmware-18-1-a-2-25 that show how to root a D5103. It works altough your phone will complain at startup that you have the wrong version (but it still works). To circunvent this you must flash an ftf file for the D5106. If you don´t find one you can generate your own ftf with flashtool, that should be installed in c:\flashtool.
1) start flashtool and go to Devices/Check Updates. Double click on D510X then click on D5106 tab. If you find the brand of your phone, double click it and flashtool will start downloading. If you don´t find your brand, you can add it to the list in flashtool\devices\D510X\D5106\custlist.properties. In my case I added 1 line with "1286-6141=AMERICAS-LTE" without the quotes. You find this information about your phone in C:\program data\Sony\Sony PC Companion\<youremei>\default-capability.xml , almost at the end under <filesystem> <productnumber> and <cdf> <productnumber>.
Save custlist.properties and you will see your brand in flashtool. Be patient waiting for download - it will bring almost 1 GB.
2) when download is finished, flashtool will automatically decrypt the filesets and open the "Bundler". There you should mark the whole folder list and move it to the right to the "firmware content". Now you can click on "create" and your ftf will be generated in the firmwares folder.
If the process ends successfully you will have generated an ftf and a torrent file.
Follow the steps in the tutorial to flash the .14 firmware, run the rootkit to root your device and use your generated ftf to flash the .25 firmware. Flash only the Kernel and unmark the wipe Data in flashtool.
I hope this helps, since it worked for me. happy flashing

Hey @low-rider, your method worked perfectly on my D5106 Thanks:good:

anyone can help me to root my xperia t3?

What model T3 do you have?

low-rider said:
You can follow the tutorials found in other threads like http://forum.xda-developers.com/xperia-t3/help/how-to-root-xperia-t3-18-1-2-25-t3007487 or http://help.howproblemsolution.com/1377446/tutorial-root-xperia-t3-firmware-18-1-a-2-25 that show how to root a D5103. It works altough your phone will complain at startup that you have the wrong version (but it still works). To circunvent this you must flash an ftf file for the D5106. If you don´t find one you can generate your own ftf with flashtool, that should be installed in c:\flashtool.
1) start flashtool and go to Devices/Check Updates. Double click on D510X then click on D5106 tab. If you find the brand of your phone, double click it and flashtool will start downloading. If you don´t find your brand, you can add it to the list in flashtool\devices\D510X\D5106\custlist.properties. In my case I added 1 line with "1286-6141=AMERICAS-LTE" without the quotes. You find this information about your phone in C:\program data\Sony\Sony PC Companion\<youremei>\default-capability.xml , almost at the end under <filesystem> <productnumber> and <cdf> <productnumber>.
Save custlist.properties and you will see your brand in flashtool. Be patient waiting for download - it will bring almost 1 GB.
2) when download is finished, flashtool will automatically decrypt the filesets and open the "Bundler". There you should mark the whole folder list and move it to the right to the "firmware content". Now you can click on "create" and your ftf will be generated in the firmwares folder.
If the process ends successfully you will have generated an ftf and a torrent file.
Follow the steps in the tutorial to flash the .14 firmware, run the rootkit to root your device and use your generated ftf to flash the .25 firmware. Flash only the Kernel and unmark the wipe Data in flashtool.
I hope this helps, since it worked for me. happy flashing
Click to expand...
Click to collapse
hello my friend,
i have de Xperia T3 D5106, and the last Flash tool. i don't kwon how creted the tft file.
Which folder files i have to move to the firmware content? to them Created,
Please help me

MDC413I said:
hello my friend,
i have de Xperia T3 D5106, and the last Flash tool. i don't kwon how creted the tft file.
Which folder files i have to move to the firmware content? to them Created,
Please help me
Click to expand...
Click to collapse
"C:\Users\(username)\.flashTool\firmwares"

Already possible to flash/generate a FTF File

Hi,
i would like to know if there is any way to flash a ftf file yet?
With the latest Flashtool 0.9.23.2 you can already download the roms for XA1 but you cannot create a ftf file, because the device is not listed yet.
I found some ftf .files on the net but i can't flash them also with flashtool. the firmware is not listed. if i use a older version of flashtool, the firmware is listed,
but when i want flash the file, it's says no loader for the device has been found.
i have a branded firmware, and would like to flash a unbranded version of the firmware.
if i use xperia companion, i only can flash the same branded version.
i tried to trick the xperia companion, the software loading the firmware files in the background if using software repair.
i tried to replace the file with the ones downloaded with flashtool/xperifirm, but it won't work.
i

Yes. download newflasher tool from my signature

It is now. Since today or for some days, but I checked today. Already started creating ftfs for my forum.

Hello friends i can not flash stock firmware on G3223 is there a way? I have custom recovery but i erase system to have a clean installation but flasher from androxyde dosent work nor munjeni one. Any advise? I have the stock ftf Thanks

jotade said:
Hello friends i can not flash stock firmware on G3223 is there a way? I have custom recovery but i erase system to have a clean installation but flasher from androxyde dosent work nor munjeni one. Any advise? I have the stock ftf Thanks
Click to expand...
Click to collapse
Hello mate I have had that issue and it was resolved by using a fresh download of xperiafirm (via it built in button on flash tool) then click yes to use script!!

@jotade
You need add support for XA1 Ultra to Flashtool. Download this: https://drive.google.com/open?id=0B7UqjtcLWyHOMDhGTjlJLW15TlE, than unpack it. Start Flashtool and uncheck AutoSync (Devices -> Device Sync -> Auto Sync -> Off). After that copy unpacked G32XX folder into /Flashtool/devices folder.
Than You can create and flash the firmware on Your device.
There are modded by me XA1 .properties and .fsc files to match Ultra (second one has only name changed to match fws' name).

ch3mn3y said:
@jotade
You need add support for XA1 Ultra to Flashtool. Download this: https://drive.google.com/open?id=0B7UqjtcLWyHOMDhGTjlJLW15TlE, than unpack it. Start Flashtool and uncheck AutoSync (Devices -> Device Sync -> Auto Sync -> Off). After that copy unpacked G32XX folder into /Flashtool/devices folder.
Than You can create and flash the firmware on Your device.
There are modded by me XA1 .properties and .fsc files to match Ultra (second one has only name changed to match fws' name).
Click to expand...
Click to collapse
Thanks my friend but i already flash and root whitout doing that. Everything is great know. ROOT is the best

Hi guys, I've been poking around on here for the first time in many years..
Are you guys telling me that I can get a stock .ftf for my XA1 Ultra (G3221) via flash tool, if I first update flash tool into something that @munjeni maintains? Also, this new flashtool runs in x64 Ubuntu 16.04?
I would like to unpack the stock ftf, tweak it for root, repack it and flash it with flashtool - having first tried the stock ftf. I've done this before a while ago.
So far with the G3221 I unlocked the bootloader, and that's it. There are many adverts on this site on a smartphone, and it makes searching these forums difficult so I've struggled to find out what I need. Your guidance would be appreciated.

You can use both Flashtool (not sure if it supports Ultra already, but I attached, few post back, neede files to add support) and Xflasher. Both will flash the stock fine. Both works fine on Linux.
However You cannot flash modded stock using this apps. There is no way to repack it to .sins and than .ftf to make it seen and flashable by any of this 2 apps. It was possible with X10, but XA1 is not X10...
Only way to flash modded rom i use recovery. If Im right there is TWRP for XA1 Ultra already.
Sent using XT1562 - Resurrection Remix/Optimus Kernel

ERROR - Error flashing. Aborted
ch3mn3y said:
@jotade
You need add support for XA1 Ultra to Flashtool. Download this: url, than unpack it. Start Flashtool and uncheck AutoSync (Devices -> Device Sync -> Auto Sync -> Off). After that copy unpacked G32XX folder into /Flashtool/devices folder.
Than You can create and flash the firmware on Your device.
There are modded by me XA1 .properties and .fsc files to match Ultra (second one has only name changed to match fws' name).
Click to expand...
Click to collapse
Flashtool needs "loader.sin", but it isn't included in the folder you provided. Any idea what to do?

user845 said:
Flashtool needs "loader.sin", but it isn't included in the folder you provided. Any idea what to do?
Click to expand...
Click to collapse
It's not needed. It was with older devices, but not XA1.
ZUK Z2 Pro ✓ᵛᵉʳᶦᶠᶦᵉᵈ

*Solved* Android 9 update for other Countries.

Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.

Double that. I havent flashed pie too, requesting a little guide how to do it properly to have full stock firmware.

I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely

52.fsc
juandiazmora said:
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
Click to expand...
Click to collapse
Hi, I need help on the flashscript thingie.
Don't have a clue where to get it from.
Thanks in advance.

I'm with Customized CE1 in my H8314 and I'm still in Oreo. It would be possible do this steps with my same firmware without doing wipe? Only deleting the country restricion.
Regards

Why can't we just flash using the downloaded and unpacked firmware from Xperiafirm? Why this need to exclude some specific .ta files and disable final verification checks?

Quarzkopf said:
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Click to expand...
Click to collapse
@Quarzkopf I know this thread is a bit old but I ran into similar "Your device is corrupted..." error when trying to flash US customization to my UK Xperia 1 ii. I was wondering how you got resolved this to a clean flash without this error at the end? Wasn't clear from instructions. Much appreciate your help