Is there anybody out there that successfully downgraded their device without having it rooted?
Need a step by step guide please.
its not possible anymore....i tried from A10 back to A9 at my Xperia 1 and no success at all
so stop wasting your time on it
Question of downgrade Android 12 to Android 11
Hello anyone, I am the new comer of the XDA. Nice to meet you here. Let move on to my questions. I have a HK version Xperia 1 III(XQ-BC72), and I love the device. However after I received and upgraded to Android 12(61.1.A.1.149), the nightmare...
forum.xda-developers.com
I managed to find a single mirror of an android 11 firmware file for Xperia 5 III by googling "XQ-BQ62 61.0.A.15.45 customized us ftf". This is the ONLY android 11 firmware I could find.
Extract contents into a directory mirroring the structure you'd see if downloading firmware from exafirm. You should have a standalone boot folder and all .sin files extracted into this directory (including unzipped partition .sin files). Delete ALL .ta files. Execute with newflasher.
I don't have time to walk thru every step but I can confirm I was able to downgrade from Android 12 to 11 using 61.0.A.15.45 ftf and newflasher without root. My bootloader is unlocked but honestly shouldn't need to be if using newflasher.
BIG THANKS to the kind soul who uploaded this ftf!!
This doesn't seem to work on XQ-BQ72 (Xperia 5 III) Android 12. Unless your steps had something specific while flashing via newflasher.
bhow11 said:
I managed to find a single mirror of an android 11 firmware file for Xperia 5 III by googling "XQ-BQ62 61.0.A.15.45 customized us ftf". This is the ONLY android 11 firmware I could find.
Extract contents into a directory mirroring the structure you'd see if downloading firmware from exafirm. You should have a standalone boot folder and all .sin files extracted into this directory (including unzipped partition .sin files). Delete ALL .ta files. Execute with newflasher.
I don't have time to walk thru every step but I can confirm I was able to downgrade from Android 12 to 11 using 61.0.A.15.45 ftf and newflasher without root. My bootloader is unlocked but honestly shouldn't need to be if using newflasher.
BIG THANKS to the kind soul who uploaded this ftf!!
Click to expand...
Click to collapse
anmolkakkar said:
This doesn't seem to work on XQ-BQ72 (Xperia 5 III) Android 12. Unless your steps had something specific while flashing via newflasher.
Click to expand...
Click to collapse
I have xq-bq62. I can only confirm this works for this model.
I am sure your unlocked bootloader helped in this case but I can't confirm as i tried the BQ72 firmwares also from that androidfilehost's user link but neither worked (mine is a locked bootloader, fyi). So I am assuming there is some tiny/unknown setting that worked in your favor.
anmolkakkar said:
I am sure your unlocked bootloader helped in this case but I can't confirm as i tried the BQ72 firmwares also from that androidfilehost's user link but neither worked (mine is a locked bootloader, fyi). So I am assuming there is some tiny/unknown setting that worked in your favor.
Click to expand...
Click to collapse
Were the firwmares .ftf? How you set up your working directory for newflasher is very important (based on my limited experience with sony devices...this is my first).
bhow11 said:
Were the firwmares .ftf? How you set up your working directory for newflasher is very important (based on my limited experience with sony devices...this is my first).
Click to expand...
Click to collapse
BQ72, from what I can tell, is the same as BQ62 except for what i'm guessing are a few changes in enabled network bands.
Also, newflasher shouldn't require a bootloader unlock. Only the offical sony flash tool would require that. Someone correct me if i'm wrong because like I said this is my first xperia device.
Yes, the firmwares were .ftf and I followed all the steps you mentioned in your post. Upon trying to flash with newflasher, it would return an error while flashing the partition blocks and would return FAIL FAIL in newflasher. None of the BQ72 Android 11 .ftf worked from the same user's file that you used for your BQ62.
anmolkakkar said:
Yes, the firmwares were .ftf and I followed all the steps you mentioned in your post. Upon trying to flash with newflasher, it would return an error while flashing the partition blocks and would return FAIL FAIL in newflasher. None of the BQ72 Android 11 .ftf worked from the same user's file that you used for your BQ62.
Click to expand...
Click to collapse
Try flashing the xq-bq72 android 11 firmware which is MUCH easier to find than my US variant (xq-bq62).
Newflasher again.
Exafirm - XQ-BQ72 61.0.A.15.45 (Android 11)
bhow11 said:
I managed to find a single mirror of an android 11 firmware file for Xperia 5 III by googling "XQ-BQ62 61.0.A.15.45 customized us ftf". This is the ONLY android 11 firmware I could find.
Extract contents into a directory mirroring the structure you'd see if downloading firmware from exafirm. You should have a standalone boot folder and all .sin files extracted into this directory (including unzipped partition .sin files). Delete ALL .ta files. Execute with newflasher.
I don't have time to walk thru every step but I can confirm I was able to downgrade from Android 12 to 11 using 61.0.A.15.45 ftf and newflasher without root. My bootloader is unlocked but honestly shouldn't need to be if using newflasher.
BIG THANKS to the kind soul who uploaded this ftf!!
Click to expand...
Click to collapse
After some technical difficulties, I've managed to copy these instructions pretty well. Newflasher seemed to have completed the process, yet my phone's firmware was still corrupt on a bootloop.
I had my bootloader unlocked as well. I've since locked it and restored back to Android 12 through Xperia Companion. I'm not sure what could have caused a problem.
Some points of interest:
1. I've kept all .sin files from the boot folder in that folder
2. All .sin files from the partition folder were moved to the parent folder where everything else should be (ex. Newflasher files)
3. Partition_delivery.xml was kept in the partition folder
4. The .ftf for Android 11 was also moved to the parent folder
I grabbed the most recent Android 12 files from XperiFirm (specifically 61.1.A.9.219). Is there a difference in those files that would make this rollback impossible?
Also running an XQ-BQ62.
raptor178 said:
After some technical difficulties, I've managed to copy these instructions pretty well. Newflasher seemed to have completed the process, yet my phone's firmware was still corrupt on a bootloop.
I had my bootloader unlocked as well. I've since locked it and restored back to Android 12 through Xperia Companion. I'm not sure what could have caused a problem.
Some points of interest:
1. I've kept all .sin files from the boot folder in that folder
2. All .sin files from the partition folder were moved to the parent folder where everything else should be (ex. Newflasher files)
3. Partition_delivery.xml was kept in the partition folder
4. The .ftf for Android 11 was also moved to the parent folder
I grabbed the most recent Android 12 files from XperiFirm (specifically 61.1.A.9.219). Is there a difference in those files that would make this rollback impossible?
Also running an XQ-BQ62.
Click to expand...
Click to collapse
I was running in to the same issues myself, the only available .ftf I could find for the XQ-BQ62 didn't work without modification (For reference, I was running the same 61.1.A.9.219 firmware) I attached my update.xml in case it differs from yours. What may have ended up making it work was zipping the contents of the partition folder to match bhow11's screenshot, I added the partition_delivery.xml to it as well. I'm unsure what exactly made this all work, but it does now.
I recently purchased the Sony Xperia 5 III and the first thing I had in mind was to unlock it since my 2012 HTC was probably the last phone I rooted, and my Xperia XZ3 wasn't as root-friendly with irreversible DRM loss and all.
When I got to the part about flashing the Xperifirm boot with Magisk, I wondered how my old 61.0x firmware would work with a new 61.1 boot. Nobody had asked this. I don't know if I was wrong but I also assumed there would be no way to backup my old firmware if the bootloader is locked. I didn't even know about A11/A12 (XZ3 had Android 9). So fearing a boot-loop I flashed the latest full firmware first. I fully regret it.
It's crazy how mad Android 12 makes me. All the love of Android is sucked out. I'm really sad too that this is a current trend. A12 kinda looks like early 2010s Windows Phone now.
Since my firmware is the Europe EEA will I never regain Android 11 except for a GSI or buying a brand new phone?
in my opinion downgrad never worked since Android 10 on my Xperia's
i tried many many hours at my Xperia 1 to go back to Android 9 but no succes
derin38 said:
I recently purchased the Sony Xperia 5 III and the first thing I had in mind was to unlock it since my 2012 HTC was probably the last phone I rooted, and my Xperia XZ3 wasn't as root-friendly with irreversible DRM loss and all.
When I got to the part about flashing the Xperifirm boot with Magisk, I wondered how my old 61.0x firmware would work with a new 61.1 boot. Nobody had asked this. I don't know if I was wrong but I also assumed there would be no way to backup my old firmware if the bootloader is locked. I didn't even know about A11/A12 (XZ3 had Android 9). So fearing a boot-loop I flashed the latest full firmware first. I fully regret it.
It's crazy how mad Android 12 makes me. All the love of Android is sucked out. I'm really sad too that this is a current trend. A12 kinda looks like early 2010s Windows Phone now.
Since my firmware is the Europe EEA will I never regain Android 11 except for a GSI or buying a brand new phone?
Click to expand...
Click to collapse
I tried from A13 to A11, but not succeeded. Also think about buying a brand new phone, damn
than the question....why u try downgrade.?
DanielMode said:
than the question....why u try downgrade.?
Click to expand...
Click to collapse
Due to ugly design, which starts from 40% bigger and not transparent security pattern screen.
u kidding me.....are u.!
u'll buy a new one just due the ugly OS design.
did u never try to get information about a new system before updating your system.?
DanielMode said:
u kidding me.....are u.!
u'll buy a new one just due the ugly OS design.
did u never try to get information about a new system before updating your system.?
Click to expand...
Click to collapse
I bought used phone. I'm scratching them a lot, so don't want to be upset of it. I haven't even asked which version they had, because I haven't knew that piece of **** loaded there!
Related
Hi, i've sony xperia xz premium and i want to flash a generic italian firmware. It's my first time in flashing a sony device and i searched a lot in internet, but i found nothing. I'm on locked bootloader, any help please?
You need flashtool to flash Sony devices. www.flashtool.net
But, it is not yet compatible with XZP.
There is another tool but no one know the safety of it so better wait.
Btw, you don't need to unlock the bootloader to flash official roms from other regions.
ninjy said:
You need flashtool to flash Sony devices. www.flashtool.net
But, it is not yet compatible with XZP.
There is another tool but no one know the safety of it so better wait.
Btw, you don't need to unlock the bootloader to flash official roms from other regions.
Click to expand...
Click to collapse
thank you man. I was reading about a file which is needed to use XZP with flashtool.
And, What about Xperia companion, SEUS and Emma? Are them good to de-brand?
Don't know those 2 other tools.
Personnaly I used on old version of that unsafe tool found on another thread here to unbrand, then to sleep well I did a software recovery using official Xperia companion.
Maybe it is total useless but who knows
ninjy said:
Don't know those 2 other tools.
Personnaly I used on old version of that unsafe tool found on another thread here to unbrand, then to sleep well I did a software recovery using official Xperia companion.
Maybe it is total useless but who knows
Click to expand...
Click to collapse
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Lorehaze said:
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Click to expand...
Click to collapse
Would there be any advantage with using a generic firmware for the same region, versus the carrier specific one?
So, does unlocking the bootloader and rooting cause you to stop getting OTA updates like on most phones?
Sent from my G8141 using Tapatalk
I feel your pain. You need newflasher and to follow the tutorial here
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16
- except make sure you put all the *.sin files in the newflasher directory and flash your phone.. Exclude everything else
The newflasher version that worked for me can be found here
https://mega.nz/#!MnhSlD7B!2NR5UVhaZH7D3mPXkXrUG3FfkSiavrSDVfKZ9UgE-Ik
laes443 said:
Would there be any advantage with using a generic firmware for the same region, versus the carrier specific one?
Click to expand...
Click to collapse
You don't have carrier bloatwares, but most of all, usually custom fw are released sooner because they don't need carriers approvals.
Jake_09 said:
So, does unlocking the bootloader and rooting cause you to stop getting OTA updates like on most phones?
Sent from my G8141 using Tapatalk
Click to expand...
Click to collapse
Don't remember about the bootloader but rooting it most probably make it fail to update.
Can't confirm, I usually flash new firm when they are released and don't wait for OTA stuff.
But the most annoying with Xperia phones since Z series, they have a "TA" partition, that contains DRM keys. They are used to unlock features like Bravia engine, special sound processing, ... And it seems also some camera features on XZP.
And when you unlock the bootloader, it wipes this partition and you lose your keys forever.
On Z5 there were two solution for this problem:
- Wait for a security breach that allow rooting Android, and gives you the hability to backup this partition. Then you can restore it after unlocked bootloader.
- Some people modded kernels to fake the presence of DRM keys.
In my opinion, for bootloader unlocking, wait that XZ1 are released (since they probably will have same specs as XZP) and more people getting involved to see what happens. Losing keys = losing Sony specific features you paid for.
By doing this, u won't lose any DRM key: obviously u need to remove all *.ta files (same from boot directory) in which those keys are contained.
I successfully flashed generic firmware over customized carrier firmware and in support app i got the same warranty message. No unlock no drm lost
@Jake_09 yes, carriers are often slowers in releasing firmware (i'm speaking about TIM carrier for Italy), in fact the rom which i found when i bought my phone was updated at april security patches. Now i got the last no brand update. I did the same as @ninjy with xperia companion after newflasher. Hope it helps!
Unlocking bootloader wipe TA partition, not flashing roms
cheetah2k said:
The newflasher version that worked for me can be found here
https://mega.nz/#!MnhSlD7B!2NR5UVhaZH7D3mPXkXrUG3FfkSiavrSDVfKZ9UgE-Ik
Click to expand...
Click to collapse
Heh, thanks for spreading my links :3.
Why we can't use flashtool? Maybe an old flashtool version can be used? I do not trust newflasher since virustotal reports it as a malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
pawnstar said:
Why we can't use flashtool? Maybe an old flashtool version can be used? I do not trust newflasher since virustotal reports it as a malware https://www.virustotal.com/sr/file/...57fcac8e88f48e8ab00a1cc61c9081d8f47/analysis/
Click to expand...
Click to collapse
That looks like a false positive since it's only 2-3 different AVs (at most) that are detecting it.
I'm going to flash to an unbranded/generic FW tonight and see how it goes!
Lorehaze said:
how to use this unsafe tool?
EDIT: for those who were lookin' for a solution, i used this unsafe tool: i just downloaded custom it firmware from xperiafirm, i pasted all the files (except all .ta files) in the same directory of the tool and i executed it. Now i'm restoring with xperia companion. All good! Thanks
Click to expand...
Click to collapse
Thanks man. Just a quick question - There's a *.ta file in the BOOT folder of the generic FW I downloaded, I definitely DON'T want to paste this as well correct?
laes443 said:
Thanks man. Just a quick question - There's a *.ta file in the BOOT folder of the generic FW I downloaded, I definitely DON'T want to paste this as well correct?
Click to expand...
Click to collapse
sure man, exclude all *.ta files, do the same for the files in boot folder.
Hope It helps
Lorehaze said:
sure man, exclude all *.ta files, do the same for the files in boot folder.
Hope It helps
Click to expand...
Click to collapse
It all worked out perfectly, just did a restore in Xperia Companion and now it's back using the generic FW, thanks
laes443 said:
It all worked out perfectly, just did a restore in Xperia Companion and now it's back using the generic FW, thanks
Click to expand...
Click to collapse
This doesnt mess with the bootloader or do anything to kill the DRM keys for the bravia engines?
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
Lorehaze said:
By doing this, u won't lose any DRM key: obviously u need to remove all *.ta files (same from boot directory) in which those keys are contained.
I successfully flashed generic firmware over customized carrier firmware and in support app i got the same warranty message. No unlock no drm lost
@Jake_09 yes, carriers are often slowers in releasing firmware (i'm speaking about TIM carrier for Italy), in fact the rom which i found when i bought my phone was updated at april security patches. Now i got the last no brand update. I did the same as @ninjy with xperia companion after newflasher. Hope it helps!
Click to expand...
Click to collapse
Cheers for this. I was worries about losing the features of the sony if I flashed a generic rom over the carrier specific one I have.
Not sure if this will do anything to improve the compatability between my car and the phone via bluetooth but worth a try.
svssolutions said:
This doesnt mess with the bootloader or do anything to kill the DRM keys for the bravia engines?
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
Cheers for this. I was worries about losing the features of the sony if I flashed a generic rom over the carrier specific one I have.
Not sure if this will do anything to improve the compatability between my car and the phone via bluetooth but worth a try.
Click to expand...
Click to collapse
This definitely didn't touch DRM at all. Just make sure you definitely don't use any of the *.TA files at all, even the one in the BOOT folder. I can still adjust my screen colour settings and they definitely work, sound settings, etc. Works great
Whats this talk about excluding .ta files? I just drop newflasher in fw folder and flash, works like a charm everytime.
What benefit do you get for excluding .ta?
It seems like there are a few people having trouble going back to stock and getting everything working.
As always, this requires an unlocked bootloader. If you don't have an unlocked bootloader then search google for a $5 service that does. It is what I did.
I flashed Project treble on my TA-1054. It worked great except it kept saying "insert SIM" when there was already a sim card inside, so I could not use it.
I tried to go back to stock but that firmware file on that google drive thread was corrupted, bad upload. Took me a few days to source this original firmware.
There is a tool called OST ( around 115MB), and a patch that comes with it (the smaller file less than 1MB)
The firmware is almost 2 GB
Download everything, including firmware.
1. Install the OST tool.
2. Replace the EXE file in the program files with the patch file you downloaded.
3. Delete the Onlineupdatetoolexe.config file. If you don't do this, the program will not start correctly.
4. Put phone into download mode ( either by powering it off, pluging into USB cable and immediately hold power and volume down. Or if you can boot into android with ADB debugging, just do a adb reboot bootloader.
5. Pick firmware file and click next.
THe first 2 times I tried this, It hanged at the last second. Third time was a charm. Give it time. Use a good USB cable.
I assume that this is the same way to flash other firmware files for other devices.
As soon as i get my hands on a android one firmware, I will flash it.
Or if anyone can guide me on how to extract the firmware on my TA-1045 USA version and flash it to my TA-1054 Chinese , let me know. Cheers.
Google drive folder with all the files I uploaded.
https://drive.google.com/open?id=1NbzO6lfSGacjM2wqrtBg3jMpljsZswne
Thanks bro...I am downloading it.
PL2-2380-0-00WW-B01.NBx.zip is global firmware name. firmware size is 4gb.
thanks! for extract is with nb0 tools FIH Mobile v3.4
https://drive.google.com/open?id=1cSgjrZUxIsN7oLbo7AP-RnILDZdswmB-
its android one firmware. I have no tool for flash...plz try and let me know
Flashing now. Will report back after flashing is done. thanks!!
Edit: Looks like the version I have for OST does not read NBX files. Will try to update that and report back. I have ntool but no working username password
I cannot flash the NBX file. I changed it to nb0 but OST LA says cannot read firmware. Is there any other way to flash?
EDIT: I went ahead and purchased a bunch of credits for NTOOL.
I will flash and see if it works!
It fails with the mdtp.img partition (no such partition) . I would think that it would just skip that partition but it did not. I will later try to extract and flash separately
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
stealthj said:
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
Click to expand...
Click to collapse
can u flash my chinese rom which is nbo format via ntool. I have have ntool but i dont have user name,password, i downloaded rom which u provide.my device still cant connect to mobile data.
NBX format only works on Ntool. but Ntool needs working user name and password to works. OST cant read or flash Nbx format.
if u get Ntool with working user id .. then plz flash my device also via remote mode like teamviewer.
Ntool Bricked my device. the only real restore you can do is by using ost with the stock chinese firmware. edit your apn. why is your data not working?
Global rom cant flash via ntool in Ta1054..showed error in partition. if it will be solved then china to global will be easy process..
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
safron35 said:
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
Click to expand...
Click to collapse
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
stealthj said:
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
Click to expand...
Click to collapse
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
TheImpulson said:
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
Click to expand...
Click to collapse
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
stealthj said:
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
Click to expand...
Click to collapse
How to flash it?
Edit: Also OnlineUpdaterTool in your 1st post asks for a password. What's the password?
nooby_pls said:
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Click to expand...
Click to collapse
I put the original chinese firmware on the first post.
There is an option to install google play store, but that would make your rom unable to receive updates.
I want to roll back to oreo but xperifirm deletes previous android versions and I cant download the 47.1.A.16.20 for my region Israel (customized IL)
is there a way I can download any oreo firmware from different regions and simply copy some files from the android Pie (customized IL) and place them with the oreo that is from a different region and make my device receive OTA from my region?
I also made a mistake and updated Xperia XZ to Android 9.0. I am looking for any tutorial how to back to proper Android Oreo or even 7.1 if I nowhere find out Oreo. I consider even selling this phone because 9.0 is so bad that using my phone is right now a nightmare. I have hope that another vendors will modified what Google has broken in Pie. Sound regulation, auto brightness, toggles and even status bar is all so bad that I cannot believe that it is genuine Android update, however I have seen on another phone this crappy update and I recognised that it is unfortunately true. I really urgently need old rom file or I will have to sell this amazing phone.
I fully second those comments. It can be worse, but this upgrade is a disgrace in creating inconveniences. How to rollback the Sony OS has become a must instead of a nicety. My plan for future is either not to upgrade for six months, or buy a working second hand unit with cracks and all just to test the new OS from Sony.
i roll back to oreo i alwasy take precuatiuons and download firmwares!!!!
Alexander Luna said:
i roll back to oreo i alwasy take precuatiuons and download firmwares!!!!
Click to expand...
Click to collapse
obviously I downloaded the firmware, but it was before my computer was broken and had to be formatted... which leads to my case now
Try Emma Sony official page
RedJHoN said:
Try Emma Sony official page
Click to expand...
Click to collapse
doesnt work on locked bootloader
https://drive.google.com/open?id=1BadirQ2PDjZnN9kdeew0CQGQdMkVUk8w
47.1.A.16.20 as flashable ftf file and seperate files to build your own ftf file
These files are branded T-Mobile Netherlands...
But, anything is better than nothing
Good luck
robertlouwen said:
https://drive.google.com/open?id=1BadirQ2PDjZnN9kdeew0CQGQdMkVUk8w
47.1.A.16.20 as flashable ftf file and seperate files to build your own ftf file
These files are branded T-Mobile Netherlands...
But, anything is better than nothing
Good luck
Click to expand...
Click to collapse
how do i make it my own Israel ftf?
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Good news! so you've manged to root Android 12? if so, what steps did you take?
beanbean50 said:
Good news! so you've manged to root Android 12? if so, what steps did you take?
Click to expand...
Click to collapse
Android 12? No, I'm on 11.
TarikVaineTree said:
Android 12? No, I'm on 11.
Click to expand...
Click to collapse
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
VerdandiAmine said:
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
Click to expand...
Click to collapse
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
beanbean50 said:
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
Click to expand...
Click to collapse
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
TarikVaineTree said:
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
Click to expand...
Click to collapse
I've finally managed to root Android 12 after weeks of trying.. Yippee..!
TarikVaineTree said:
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
Click to expand...
Click to collapse
Using phone info my correct CSC is VAU. The software I used to get firmware is Frija and I deployed it with Odin.
So flash the magisk patched boot.img file to AP via Odin as well as flash the firmware BL file to BL? Okay I will try this with VAU firmware and report back with what happens.
Im wondering if anyone has tried to use Xperia Companion (XC) to install firmware other than the latest available. XC uses firmware files located in the ...UpdateEngine\localstorage\US\ folder, so i thought i could swap them with files downloaded from Xperifirm. I even renamed Android12 binary files with Android11 filenames, but appears XC is too smart for me. Trying to Repair offline doesn't work either.
I ask because im now on Android12 and would like to go back to Android11, but im having no luck. Flashtool comes up with errors, Newflasher gives me the "Your device is corrupted" warning.
I'll get there eventually, i hope.
From what I understand you'd have to do a clean install and also unlock bootloader once you go up an Android level you can go back sorry I can't help you