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)
Related
OK so I have the z3. Cool phone I might add. I use my hotspot A lot but after upgrading to 5.0.2 foolishly. I cannot use my data connection externally. Is there a a way to downgrade to 4.4.4 or b. A way to upgrade to a later version of android where this big may be fixed. I really need the hotspot to work as its my life line. I'd like to keep it stock for now if possible too. Thanks Guys
benjy105 said:
OK so I have the z3. Cool phone I might add. I use my hotspot A lot but after upgrading to 5.0.2 foolishly. I cannot use my data connection externally. Is there a a way to downgrade to 4.4.4 or b. A way to upgrade to a later version of android where this big may be fixed. I really need the hotspot to work as its my life line. I'd like to keep it stock for now if possible too. Thanks Guys
Click to expand...
Click to collapse
(I think you meant "in dire need of help" unless you're specifically looking for low quality answers )
Downgrade using xperifirm to get the rom, and flashtool to install it, using this guide (note: you'll have to choose a different rom to the one mentioned in that guide):
http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
OK that's great. What is xperifirm in regards to.the importance of getting the room. I have downloaded 4.4.4 from.another source before I started this thread. Will I not be able to.use thaT? What I mean is is it significant to the process??
benjy105 said:
OK that's great. What is xperifirm in regards to.the importance of getting the room. I have downloaded 4.4.4 from.another source before I started this thread. Will I not be able to.use thaT? What I mean is is it significant to the process??
Click to expand...
Click to collapse
No, nothing special about xperifirm; It's just the only place i've ever got a rom from so i know it's legit. as long as flashtool likes your 4.4.4 it should be fine.
So I've coklme across a new problem. When installing the flash program I tried the windows key and r and typed in the stuff needed but I'm not getting what it says on the instructions. Therefor unable to install allbthe drivers. Running Windows 8.1.
I'm lost nnow. Could it be zipped with the drivers pre installed?
benjy105 said:
So I've coklme across a new problem. When installing the flash program I tried the windows key and r and typed in the stuff needed but I'm not getting what it says on the instructions. Therefor unable to install allbthe drivers. Running Windows 8.1.
I'm lost nnow. Could it be zipped with the drivers pre installed?
Click to expand...
Click to collapse
Probably need to put a little more detail about what you expect to happen and what's actually happening. (I used windows 7 and it installed without problem, but I think I read that windows 8 required a little more love to get the drivers installed. )
Webern said:
Probably need to put a little more detail about what you expect to happen and what's actually happening. (I used windows 7 and it installed without problem, but I think I read that windows 8 required a little more love to get the drivers installed. )
Click to expand...
Click to collapse
First off it wouldn't download and install all the drivers. So I installed the Sony companion and then when I went to flash the tft file it said unable to extract.ini or such. May just be a bad roM. I'm not at the computer now but I'll try again tomorrow
benjy105 said:
First off it wouldn't download and install all the drivers. So I installed the Sony companion and then when I went to flash the tft file it said unable to extract.ini or such. May just be a bad roM. I'm not at the computer now but I'll try again tomorrow
Click to expand...
Click to collapse
You have installed the wrong program, Install flashtool from flashtool.net and flash the FTF (not tft) using that
The sony flashtool only works on unlocked bootloader phones, but the original developed here on XDA is far better and works on locked bootloaders as well.
It was an ftf file it just blooming autocorrected. Right I'm going to try again and I'll take shots too
Alright everyone, I'll just say I don't ever create a Q&A thread unless I've run out of options and unfortunately I have...
So my device never got an OTA and its the 22nd now so I've basically given up on that. As a result, I took matters into my own hands and unlocked the bootloader (which went fine).
FlashTool
Now the hard part is trying to use FlashTool to push an ftf file onto the device but unfortunately every time I try to use it every ftf file simply stalls after setting the max buffer size. Once it does this I have a look at the .flashtool\firmwares\prepared folder only to find a single .sin file there.
I have tried a number of things to try and get FlashTool to work including:
Using different USB Ports/Cables (I thought it might help lol.)
Using different ftf files
E6653_32.1.A.1.163_R4C_Australia_Generic
E6653_32.1.A.1.163_TH
E6653_Customized AU_1298-7277_32.1.A.1.163_R4C
Updating FlashTool to the latest (including patch)
Just pushing a single SIN item by excluding everything else
Fastboot AOSP
After FlashTool, I considered just using fastboot to push AOSP marshmallow to my phone using the following:
Code:
[FONT=Arial]fastboot flash boot boot.img[/FONT]
[FONT=Arial]fastboot flash system system.img[/FONT]
However, when I tried to push system.img it just stalled out on 'sending system.img' and never got beyond that.
Fastboot FTF
I have also tried extracting the core parts of the ftf file and using fastboot to push the .sin files onto the phone.. Didn't work =(
Sony Companion
I really should have started here but I didn't realise it was a thing until after unlocking my bootloader. But I have now tried the the Sony Companion method of updating the device but it won't work because 'contains modified sofwtare that cannot be updated'
Other stuff you need to know
More stuff you need to know:
FlashTool version: 0.9.19.10
Sony Z5 model: E6653
Bootloader status: ROOTED
Flashmode Driver: installed from FlashTool
Solved.
Installed flashtools and z5 driver on another pc and used flashtool to push firstly a Lollipop build onto the device. After confirmation of it working I put on the Marshmallow build and it booted up.
No Problems to report so far and working 100%. Only had to add another APN to get mobile data working.
Try reinstall Flashtools. Worked for me.
Haha yeah, I've tried that too but I'll give it another shot tonight just in case.
You can manually Flash the Marshmallow OTA Update file.Check out the guide here > http://rootmygalaxy.net/download-sony-xperia-z5-marshmallow-ftf-32-1-1-163-model-no-e6653/
Btw i haven't tried this method.
First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?
Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.
Hello everybody,
As you can see in the title I am searching to know how i can root my Sony Xperia XZ Premium G8141 47.1.A.12.34, that I have flashed thanks to this thread : https://forum.xda-developers.com/xz...shtool-0-9-t3736217/post75276892#post75276892
After Flashing the photo camera doesn't take pictures anymore (take green photos but video works) but I know that this is a DRM problem. I find a tutorial on XDAdevelopers that tell you how to root and fix the DRM on a Sony Xperia XZ Premium : https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
I Checked first if my Sony was compatible with this tutorial, read everything before doing stupid things and all seams to be ok. I downloaded the XperiFix, installed it and put my device on fast boot mode before I launched the program. But after the rooting process, when my device was rebooted, the camera problem was still present and my device wasn't rooted too.
So I want to know if anyone have the same problem or know how to fix that or have an alternative solution. Is it the flash tool that I used that isn't compatible with the Xperifix software or something else ?
MashNuke said:
Hello everybody,
As you can see in the title I am searching to know how i can root my Sony Xperia XZ Premium G8141 47.1.A.12.34, that I have flashed thanks to this thread : https://forum.xda-developers.com/xz...shtool-0-9-t3736217/post75276892#post75276892
After Flashing the photo camera doesn't take pictures anymore (take green photos but video works) but I know that this is a DRM problem. I find a tutorial on XDAdevelopers that tell you how to root and fix the DRM on a Sony Xperia XZ Premium : https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
I Checked first if my Sony was compatible with this tutorial, read everything before doing stupid things and all seams to be ok. I downloaded the XperiFix, installed it and put my device on fast boot mode before I launched the program. But after the rooting process, when my device was rebooted, the camera problem was still present and my device wasn't rooted too.
So I want to know if anyone have the same problem or know how to fix that or have an alternative solution. Is it the flash tool that I used that isn't compatible with the Xperifix software or something else ?
Click to expand...
Click to collapse
Well you unlocked your bootloader.
unlocking the bootloader will erase the TA partition which includes camera features (DRM), and now they are deleted along with whats left in TA partition.
now you can not go back to a natural device.
good news is if you follow the procedure properly on this link:
https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
(2. Use XperiFIX to get what you want)
then you should get your DRM fix patch, read the thread carefully, youre gonna have to do it all over again as you lost TA partition which you can never get back now.
So go do procedure 1 + 2 carefully, you will get it fixed and you will also have a rooted phone
if its not working try to flash a previous version FW that supports xperifix im not sure the one you have is supported but most likely it is, then redo the process in the thread and see if it works out.
hit the thanks if I was a help
madshark2009 said:
Well you unlocked your bootloader.
unlocking the bootloader will erase the TA partition which includes camera features (DRM), and now they are deleted along with whats left in TA partition.
now you can not go back to a natural device.
good news is if you follow the procedure properly on this link:
https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
(2. Use XperiFIX to get what you want)
then you should get your DRM fix patch, read the thread carefully, youre gonna have to do it all over again as you lost TA partition which you can never get back now.
So go do procedure 1 + 2 carefully, you will get it fixed and you will also have a rooted phone
if its not working try to flash a previous version FW that supports xperifix im not sure the one you have is supported but most likely it is, then redo the process in the thread and see if it works out.
hit the thanks if I was a help
Click to expand...
Click to collapse
Thanks for the help and for the very quick reply !
I'll try too flash a older version firmware for my device, but I didn't find links to download the right version for my actual firmware (G8141 47.1.A.12.34), so I want to no if it's a problem to take an other version (as exemple G8141 47.1.A.12.34 from XperiFirm) and flash it to my device ?
MashNuke said:
Thanks for the help and for the very quick reply !
I'll try too flash a older version firmware for my device, but I didn't find links to download the right version for my actual firmware (G8141 47.1.A.12.34), so I want to no if it's a problem to take an other version (as exemple G8141 47.1.A.12.34 from XperiFirm) and flash it to my device ?
Click to expand...
Click to collapse
i rechecked and i think the xperifix should work on any firmware so try it out
if you are unlocked just download the xperifix on that link and just run it as instructed and it should work
also check if you followed correctly:
https://www.youtube.com/watch?time_continue=8&v=XeYlIHnSuOM
also check if you installed the firmware that suits your device G1841/G1842 they are 2 different things
flash whats suited.
if that didnt work, you can download the firmware in the video using xperifirm and do the procedure again.
and to answer your question, i dont really understand you already have 47.1.A.12.34 why would you want to install it again? im not getting the question...
EDIT (2/5/2021):
Hmm, Newflasher just worked for me now and I'm not sure what could have changed between when I was having issues and when it worked. Other people have reported similar, transient issues with Newflasher where it works and then suddenly doesn't, and vice-versa.
I'll update this post if I'm able to isolate the issue from before.
ORIGNIAL POST:
Hello all,
I have a Xperia 5 ii ( XQ-AS62 ).
I've successfully unlocked the bootloader.
I have TWRP 3.4.0 installed, I followed this guide https://forum.xda-developers.com/t/guide-how-to-flash-twrp-on-the-xperia-5-ii.4188419/
I have no important data that needs to backed up. I'm free to wipe it (the data in system partition is corrupted anyway).
I would like to install stock Android 10 (or anything else, at this point).
I have downloaded the stock Android 10 firmware via XperiFirm 5.5.0.
The next step SHOULD be to download Newflasher, move 'newflasher.exe' into the folder containing the firmware (the folder containing the *.sin files), put my Xperia 5 ii into flash mode (hold volume down while plugging in USB-C cable), and run newflasher, at which point newflasher would flash any present *.sin files into the appropriate partitions.
I've attempted the above.
However, what I'm experiencing is that, when using Newflasher, I'm met with the error message:
No usb device with vid:0x0fce pid:0xb00b !
At which point the program exits.
This is not a unique problem, but I've not seen any actual solutions that I can use.
Threads on the topic (for other Xperia devices):
[Solved] - Full Wipe - Newsflasher -> no usb device vid:0x0fce pid:0xb00b
Hello, Device is rooted and BL is unlocked and on FW v47.2.A.10.45 Performed a wipe incl system and internal storage. (Dalvik/ART is included) Wanted to start over, and perform a full backup after this... I shouldn't have checked ''internal...
forum.xda-developers.com
No usb device with vid:0x0fce pid:0xb00b · Issue #5 · munjeni/newflasher
Hi there, I succsessfully downgraded using newflasher couple of days ago, then I accedentaly updated firmware (big fingers), so I tried downgrading again, but now I get ... Determining available fr...
github.com
https://www.reddit.com/r/SonyXperia/comments/i32207
https://www.reddit.com/r/SonyXperia/comments/887sk3
One of those threads mentions using Sony Emma. It looks like you need to be a Sony Partner to register to use that (is that true? Any of you used it before?)
My current system is borked (won't boot) so I don't think I can install/use Magisk.
Again, my goal is to get Android 10 (or anything else) installed.
I still am able to see the device when in fastboot, and TWRP seems fine, so there should be hope right?
I can confirm that my bootloader has remained unlocked.
Any suggestions?
Thanks much!
xperia companion should do the trick
flyl0 said:
xperia companion should do the trick
Click to expand...
Click to collapse
I managed to get Newflasher working but never found out why.
Would Xperia Companion still work even if there was no ROM on the device (such as if it were fully wiped)? When I tried to use Xperia Companion (before Newflasher ended up working for me) it didn't seem to recognize my device. I had no ROM loaded at the time (it was fully wiped).
could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?
barret95 said:
could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?
Click to expand...
Click to collapse
Are you still having issues? At one point, I got my own device into the state you described. I believe that when I got newflasher working (and again, I don't know why newflasher suddenly decided to work) I was able to flash the firmware and the phone booted with no issue. Is the newflasher tool telling you that it's flashing the images successfully?
barret95 said:
could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?
Click to expand...
Click to collapse
I want to downgrade to A10 since A11 is still too buggy. I have also AS52. Can you tell me where you find the firmware?
T3chDelicious said:
I want to downgrade to A10 since A11 is still too buggy. I have also AS52. Can you tell me where you find the firmware?
Click to expand...
Click to collapse
File on MEGA
mega.nz