Related
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)
Hi,
So in the past I used Xperifix to root my Xperia XZ Premium, and it worked a charm, but since then I have removed the root using Magisk in order to try and update my phone. At the time I didn't realise you can't update a rooted phone using the phone's automatic updater, or whatever it is lol. I tried to update it using Xperifix, but now Xperifix isn't working for me. I've contacted them for support but I've been waiting a few days for a reply, so I don't know when I'll be able to update my phone using Xperifix. I'm wondering if there's another way I can update it? I flashed my phone (whatever that means I'm not even sure myself) and it reset my phone, but reset it to version 7.1.1, and I don't know how to update it to the latest Android version without Xperifix.
Does anyone know how I can update my phone? I'm not used to rooting my phone so if you're going to use any tech talk please keep it basic ?
Thank you.
Jack_J18 said:
Hi,
So in the past I used Xperifix to root my Xperia XZ Premium, and it worked a charm, but since then I have removed the root using Magisk in order to try and update my phone. At the time I didn't realise you can't update a rooted phone using the phone's automatic updater, or whatever it is lol. I tried to update it using Xperifix, but now Xperifix isn't working for me. I've contacted them for support but I've been waiting a few days for a reply, so I don't know when I'll be able to update my phone using Xperifix. I'm wondering if there's another way I can update it? I flashed my phone (whatever that means I'm not even sure myself) and it reset my phone, but reset it to version 7.1.1, and I don't know how to update it to the latest Android version without Xperifix.
Does anyone know how I can update my phone? I'm not used to rooting my phone so if you're going to use any tech talk please keep it basic
Thank you.
Click to expand...
Click to collapse
The phone will still be unlocked, but perhaps your attempt to update it may have removed the recovery partition, but I'm surprised if it did. Usually OTA updates instantly fail on rooted phones and never get to do anything.
To get the latest firmware:
Download newflasher.
Install the Sony ADB drivers, to do this you will need to boot your Windows10 into safe mode and use 'driver signing disabled'
Read up on Xperiafirm, download the latest firmware for your region.
Put a copy of the Newflasher into the firmware download folder.
Unplug your phone from the PC.
Turn your phone off completely Power and Vol up (+) until it vibrates three times.
Run the newflasher and when prompted, plug your phone back in while holding the Volume up (+). Once the process has started you can let go.
Once you have the latest stock firmware on and running ok, try flashing with Xperiafix again.
Edit: you will need to download the very latest version of Xperiafix you CANNOT use and old version on the latest firmware. Sony have incorporated an anti-fix in the latest builds, using the old fix may well damge your phone.
Didgesteve said:
The phone will still be unlocked, but perhaps your attempt to update it may have removed the recovery partition, but I'm surprised if it did. Usually OTA updates instantly fail on rooted phones and never get to do anything.
To get the latest firmware:
Download newflasher.
Install the Sony ADB drivers, to do this you will need to boot your Windows10 into safe mode and use 'driver signing disabled'
Read up on Xperiafirm, download the latest firmware for your region.
Put a copy of the Newflasher into the firmware download folder.
Unplug your phone from the PC.
Turn your phone off completely Power and Vol up (+) until it vibrates three times.
Run the newflasher and when prompted, plug your phone back in while holding the Volume up (+). Once the process has started you can let go.
Once you have the latest stock firmware on and running ok, try flashing with Xperiafix again.
Edit: you will need to download the very latest version of Xperiafix you CANNOT use and old version on the latest firmware. Sony have incorporated an anti-fix in the latest builds, using the old fix may well damge your phone.
Click to expand...
Click to collapse
Thank you, I am trying this now. As for driver signing disabled, is that the same as driver signature enforcement? That's the only thing I was able to find on Google that was related to driver signing.
Thanks.
EDIT: I am not being prompted to plug my phone back in. It asks if I want to download GordanGate, which I've done, and afterwards it says "No usb device with vid". I've tried it with and without my phone plugged in.
EDIT 2: I didn't realise I had to put my phone into flash mode BEFORE running Newflasher. It's running now though.
EDIT 3: It worked, managed to update my phone. Thank you. Although Xperifix still isn't working. I'll see if I can find a solution. Thanks for all your help, much appreciated.
So iv had this device for quite some time now. Updating the phone through the internet doesnt do anything and goes into loop and restarts. So im stuck on this Android version for a long time.
Im a little bit of a newbie when it comes to firmware flashing rooting etc. I am on an Xperia XZ Premium G8141 with Build number 45.0.A.5.1
I already have the bootloader unlocked.
What would be the right steps for me to take in order to upgrade to Android Pie safely? Maybe even root the phone?
Stock Android Pie would be the best option for me i think
So i managed to Upgrade on my own to Android 8
Downloaded firmware from XperiFirm and flashed it on my device with newflasher
Still when i go to system updates it doesnt update. It downloads a 1.5 gb file then restarts and the update is still there.
Any solutions?
Your device is unlocked. OTA is broken. You must flash 9.0 manually. And no there is no way to re-lock the bootloader that I know of. If you would like me to tell you dee way to do that PM me or reply back here
lonewolfbtown said:
Your device is unlocked. OTA is broken. You must flash 9.0 manually. And no there is no way to re-lock the bootloader that I know of. If you would like me to tell you dee way to do that PM me or reply back here
Click to expand...
Click to collapse
i would like to know how yes. thanks
lets do that here and not over pm so maybe more people looking for something like that could find it also
i would like to have Android 9 Pie and also maybe give it a try to root it.
Iv never done that before and since its not my main device i would give it a go and install some custom apps and modifications.
Ok ? I'm at work right now but once I get home I'll write you up a guide here on how to get to pie, how to flash twrp, how to root phone, and how get xposed if that's what u want or existenze room working.
lonewolfbtown said:
Ok I'm at work right now but once I get home I'll write you up a guide here on how to get to pie, how to flash twrp, how to root phone, and how get xposed if that's what u want or existenze room working.
Click to expand...
Click to collapse
thats great! thanks alot for taking the time and patience to do this. much appreciated!
I just know how it feels to have ur thread go ignored. So I try to help anyone in any thread I see.
Do you want volte for T-mobile cause I can make that happen. Also do u have fastboot and adb drivers installed?
lonewolfbtown said:
I just know how it feels to have ur thread go ignored. So I try to help anyone in any thread I see.
Do you want volte for T-mobile cause I can make that happen. Also do u have fastboot and adb drivers installed?
Click to expand...
Click to collapse
im not sure what you mean with volte for T-mobile. If it has to do with networks im actually in Greece and we dont use T-Mobile here. I saw a Greek Android version up to 8.0.0. which i have installed right now
I have fastboot and adb drivers already installed, but the adb driver seems to be giving me some error and exclamation mark in device manager for some reason. The phone is recognised by Xperia Companion for example though
figure out that error. right click on the driver and look in details and report back. An xperia companion should most likely be useless at this point since u unlocked it
Well from a translation of Greek it says "not possible to start this device (code 10)"
Its the Sony sa0116 adb interface driver right? That's the one I could find
Sent from my iPhone using Tapatalk
First if your phone blows up, freezes, dies or boot loops it is not my fault. I will help if i can but if you blame me. I will not feel bad
First things first Here's what you need!!!
-flashtool- If you can find the xperia ftf downloader only more power to you. http://www.flashtool.net/index.php
-newflasher, This is the correct tool for flashing new firmware on the xz premium https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426
-twrp image: https://dl.twrp.me/maple/
-root aka magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-minimal adb. Not gonna link it. so easy to search. INSTALL THIS BEFORE EVERYTHING ELSE
Ok here we go to getting to 9.0 and root:
Getting your firmware
-First install flashtool after you download it.
-Once its installed you want to navigate your explorer to where it was installed, and find the drivers folder. Click the drivers exe and it will come up with many options. You want adb and fastboot. I think its the first two. Click install
-Drivers installed? OK moving on! Open flashtool and navigate to xperifirm. Should be on the toolbar. Another window will pop up with a bunch of xperia phones and years. Find your phone. click your region. In the right screen of the window it will show what firmware is available. Most recent pie version will end in .24. If unsure, GOOGLE THE FIRMWARE NUMBER.
-CLICK ON THAT FIRMWARE AND IT WILL BEGIN TO DOWNLOAD. after download it will unpack it
-Once it unpacks and finishes, close the download window. Close xperifirm. Dont touch flash tool. Leave THAT OPEN. Flashtool will then unpack the ftf (which is important that it does) and the bottom bar will have progress bar. It will be clear when it finishes or fails but you will see red letters if it did.
-Firmware unpacked? Great! Extract your newflash firmware. All items in the zip must go into the folder where your firmware was downloaded. Mine looks like this C:\Users\rocke\.flashTool. It will be in the download folder and it will have your unpacked firmware. Go into that folder and it will have a bunch of files from your ftf. Move your new flasher files in there. Make sure boot folder is emptied into the main folder where are the others are and new flasher. Delete boot folder.
Flashing time
-hold volume down and plug in phone to pc. Green light should come one.
-Open Newflasher.exe
-a few questions will appear. I dont type = yes on both questions cause its kinda pointless unless you need gordon gate drivers and u want to back up something that i think i dont need/
-WHoooooosh! Command lines will start popping up and your phone is being flashed. Let its do its thing
-Eventually it will tell you you can disconnect your phone after u close the window. Boom android 9
Give me the root captain!!!
root.....a dangerous but such a fun little thing
-first your twrp. Hold volume up and plug in phone. Blue Light will come on. the twrp image must go in the minimal adb folder. Other wise adb will think your crazy and say it doesnt exist.
-type this in minimal adb fastboot devices. it will show if a fastboot device is available. If not we have problem with drivers. If yes. Then we keep trucking on
-flash twrp. type this command in fastboot flash recovery twrp.img (rename image obviously) It will flash it to the phone.
-Reboot phone into recovery. Volume down and power button. Release at sony logo or it might be the unlocked bootloader warning. Cant remember. Either way release power button on that logo and keep holding volume down.
Boom your in twrp.
-if magisk wont move over to your sd card in twrp. its time to adb push
-adb push magisk.zip /sdcard
it will move the file.
-Find where you pushed it and install magisk. It will do its thing.
If you followed the instructions your phone should be rooted and you want need a drm fix to cover the holes of the BL unlock. If hit any snags message me or reply here
Thanks for taking the time to write this.
The first part of flashing Android 9 I already know how to do. As I mentioned I my second post in this thread I already upgraded from Android 7 to Android 8. My problem was that XperiFirm doesn't have Android 9 for my device and Android 8 is the latest I could find to download. I would have already flashed Android 9 otherwise
As for the rooting part I will have a look when I'm back at home
Sent from my iPhone using Tapatalk
Yes I understand that. If you want 9 u need to use xperiafirm and get a different region that has access to it. If you use Greece ftf that is still on oreo. Chance is you'll be on 8 for a long time
I'll try and find one with Android 9 then when I get the time to do that. Also pretty busy with work
Sent from my iPhone using Tapatalk
ce1 matches the europe basebands. that i know is for sure on 9.0
i think i will give a try to a custom Rom instead like this one :
https://forum.xda-developers.com/xz...tenz-pie-v3-5-0-beta-31-01-19-t3895452/page28
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