Related
Hello!
I recently purchased a Mate 9 through an operator that sells unlocked phones in my country.
The firmware version on the phone currently is MHA-L09C106B120 which is pretty old, but the software update section of the settings menu says there aren't any updates available.
I found a newer version MHA-L09C106B160 on this site: http://hwmt.ru/oth/HWFF/info/view.php?find_model=mha
Question: seeing as how the newer firmware refers to apparently my same localized version of the phone (L09C106), can I force it to update to it somehow, without rooting or unlocking bootloader? Additionally, is there anyway to do this without an external sdcard? (I currently have one on order but it will take many days to get here)
Thanks!
Not necessary in the update. In my case under the overflow menu you will see download option if this is a full rom.
Hi, thanks! Sorry I'm a bit lost here. The overflow menu of what app?
Also in the site I mentioned, the new firmware is listed as OTA, not full. Does that mean I can't update to it?
Thanks again
You could update it, I can imagine by the number of cust es of the Costa Rica ice.
The overflow menu of what app?
Click to expand...
Click to collapse
In Settings > System update
Thanks. I ended up rebranding to C636 to get newer updates.
Hello everybody,
Firstly, apologies about all text, no links.. But i'm new to the site and don't have enough posts to link yet.
So, i'm new to the Mate 9 (had Samsungs for quite a few years now... Overpriced battery sucking hogs that never last to 18 months withou massive issues) and I really haven't gotten into the custon side of/flashing etc since my original galaxy (dunut, before the s!) /HTC Desire, sgs3 days.... So i'm probably quite out of touch... But still capable to learn and especially follow a good guide!
Now, my thing is... I want to stay stock as I use Android pay quite a lot... Yet with my experience with optus they are ATROCIOUS at updates, every with volume sale items like the Galaxy s4, 5 &6 so I can only imagine that i'll never get an update with the mate 9.
I purchased my phone outright, but second hand.... So I don't think I'll have a warranty anyway.
So far I have gathered that I can only debrand if I unlock the bootloader (and pay remains broken even if it gets relocked with an original rom) so for me, at least for the time being, that's out.
My next option is to side load firmware from the SD card... I just want to keep up to date. There is some screen sensitivity issues that the newest firmware apparently addresses.. Not to mention camera updates and battery usage updates (already VERY impressed with the battery though, especially after my S6- Awful phone)
Trouble is, I can't get any update to complete! - They get to 5% and then fail!
The firmware models I've tried have slightly different numbers to what's on my Optus Mate 9... But I can't find any exact matches, so I'm kind of expecting this to be the cause of my failed updates, even when I've downloaded from the different sites following the guides.
Currently i'm running with this;
Model: MHA-L09
Build: MHA-L09C34B122
EMUI: 5.0
Android: 7.0
and I have tried these three updates from the Huawei... Note 2 full and one OTA. Also note the firmware/region differences... But it's as close as I can find.
2017.04.25 MHA L09BC346B181 FULL-MF
2017.04.25 MHA L09BC346B181 OTA-MF
2017.04.24 MHA L09BC34B170 FULL-MF
I've also followed these two guides (and another one with a B170 update), downloading the updates from each respective site in case the firmware was something different than what I could find. Note also that one tells you to put the dload folder into the device memory.. Which won't work, so I just did it in SD which enables the phone to recognise the update file.
(links not allowed sorry, removed and replaced with text, can probably google to see what I did, always fails on step 1)
From get droid tips, upgrade to B170 & B181
from stechguide, upgrade it B181
Not to mention having followed all the guides I could find on this forum.
I'm sorry if I've missed a discussion that already deals with this (or similar) or if it's really bleedingly obvious. I'm just at a bit of a loss here!
Thanks in advance.
Sorry,
This is for Australian firmware. Optus.
Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.
Thanks for that,
I'd obviously misunderstood what's available already... Figured since I don't have the 10x zoom available like the latest release, I was behind.
ante0 said:
Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.
Click to expand...
Click to collapse
Yes, new users are led the wrong way by reading these guides.
The dload method probably worked with older devices so the Mate 9 articles seem to be created by copy and paste and replacing the older devices name with "Mate 9". Voila! There's your new shiny article about the Mate 9 and people klick it.
Yeah. I got sucked in. Noob mistake.
Sorry for polluting the board with my stupidity!
Very out of touch with behind the scenes android.
Thanks for taking the time guys
Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.
Saw that. Figured I'm just stuck as is for now. I'll check out what you're referring to!
Leighm0 said:
Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.
Click to expand...
Click to collapse
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Texan1 said:
should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
IMHO yes you should. Don't let FF/FH turn into an obsession, just enjoy your phone.
Sent from my MHA-L29 using XDA Labs
Texan1 said:
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.
By the way, when you unlock bootloader on mate 9, then flash a full firmware (either the update and rebrand guide, Firmware finder or funky) your bootloader gets locked again. So no real harm done.
Leighm0 said:
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.
Click to expand...
Click to collapse
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?
Texan1 said:
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?
Click to expand...
Click to collapse
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.
Leighm0 said:
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.
Click to expand...
Click to collapse
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?
Good question... Wondering that myself.
Sent from my MHA-L09 using XDA Free mobile app
Texan1 said:
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?
Click to expand...
Click to collapse
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..
Leighm0 said:
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..
Click to expand...
Click to collapse
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.
Texan1 said:
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.
Click to expand...
Click to collapse
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!
Leighm0 said:
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!
Click to expand...
Click to collapse
Iirc they go by IMEI.
I just purchased two Dual-sim S7's from the same store on the same day in Hong Kong. One of them is running Nougat out of the box, while the other one is still on Marshmallow, with no updates available via OTA.
I've tried the following but none have allowed it to find an update:
Search for updates with and without a SIM card in the phone
Factory Reset from settings
Wipe cache partition/data/factory reset from Recovery
The Nougat phone shows:
"The latest updates have already been installed.
Current version:
G930FXXU1DQD8/
G930FOZS1DQD8/
G930FXXU1DQC8"
The Marshmallow phone shows:
"The latest updates have already been installed.
Current version:
G930FXXU1BPKF/
G930F0ZS1BPKF/
G930FXXU1DQQC8"
It seems 7.0 for this model was released at least 3 months ago and I'm surprised the Marshmallow phone still can't update to Nougat. Does anyone have any idea why Nougat is still not available for that phone, or can anyone point me in the right direction as to updating it to 7.0? Thank you in advanced.
I don't feel comfortable with the process of flashing firmware but if it comes to that scenario, I'll do it.
rcheung28 said:
I just purchased two Dual-sim S7's from the same store on the same day in Hong Kong. One of them is running Nougat out of the box, while the other one is still on Marshmallow, with no updates available via OTA.
I've tried the following but none have allowed it to find an update:
Search for updates with and without a SIM card in the phone
Factory Reset from settings
Wipe cache partition/data/factory reset from Recovery
The Nougat phone shows:
"The latest updates have already been installed.
Current version:
G930FXXU1DQD8/
G930FOZS1DQD8/
G930FXXU1DQC8"
The Marshmallow phone shows:
"The latest updates have already been installed.
Current version:
G930FXXU1BPKF/
G930F0ZS1BPKF/
G930FXXU1DQQC8"
It seems 7.0 for this model was released at least 3 months ago and I'm surprised the Marshmallow phone still can't update to Nougat. Does anyone have any idea why Nougat is still not available for that phone, or can anyone point me in the right direction as to updating it to 7.0? Thank you in advanced.
I don't feel comfortable with the process of flashing firmware but if it comes to that scenario, I'll do it.
Click to expand...
Click to collapse
Check in download mode which model it says it is, download the firmware from updato and flash with ODIN
Instructions all over the forum
*Detection* said:
Check in download mode which model it says it is, download the firmware from updato and flash with ODIN
Instructions all over the forum
Click to expand...
Click to collapse
I do want both phones to run the exact same firmware. Would it be safe to assume that I can flash G930FXXU1DQD8(Same firmware as the Nougat unit) to the Marshmallow phone?
rcheung28 said:
I do want both phones to run the exact same firmware. Would it be safe to assume that I can flash G930FXXU1DQD8(Same firmware as the Nougat unit) to the Marshmallow phone?
Click to expand...
Click to collapse
Like I say, check in download mode to ensure they are both the same models
Firmware model numbers, boxes, stickers etc can all be faked and often are, download mode cannot be faked
As long as they are both the same, yes you can flash the same firmware on both
Samsung Smart Switch might be able to update the MM one too
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Lol, 11 will never be "fixed".
If the bootloader was updated you're boned.
Apparently on the OTA updates on at least some devices it's not being updated, you can rollback.
The 5th digit from the end of the boot loader version and the firmware are the significant digits. If the boot loader version is the same or less than the firmware, you can rollback. In this case it's a 2.
Not sure that this Samsung rule applies to Motorola updates.
RETIEF said:
Not sure that this Samsung rule applies to Motorola updates.
Click to expand...
Click to collapse
No idea, it may be a Samsung idiosyncrasy.
A very annoying one...
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
Check the software channel from Settings>Telephone information (or similar), which software channel do you have? If it is timit you are on the tim software channel (and the updates depends on the carrier, but actually seems in line with reteu, the european standar), if you are on reteu this is really strange. I don't know why they miss the boot animation but the firmware is right.
Yes the software channel is timit, but in android 10 it showed the boot animation for reteu channel. And i dont know why now it shows an edge logo animation that has nothing to do with this model. It looks like they put something from another model in the update. Look at the attached photo.
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
You can always just root phone and change the boot animation files. They're in system/media/bootanimation.zip
Just download android 10 firmware get this file from system.img and put it on your phone
the.real.p3y0t3 said:
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
Click to expand...
Click to collapse
Hello and sorry for asking a newbie question here but I don't want this to go sideways...
I have a new XT2113-2 (TM) that is yet to be boot loader unlocked/rooted/etc. I don't want to do that until I am sure. I got this variant of the phone so I could unlock the bootloader, root, TWRP, etc and was afraid the "global" variant -3 might not work with USA 5G. The phone came with Android 11 installed (and has since auto-installed at least one security update). It shows the build as RZKS31.Q3-45-16-3-11 and the baseband ends with Kiev_TMO_CUST. I am using it on ATT (via Red Pocket) since TM service just sucks where I live. And I do get the 5G icon on it now.
But ideally, I want to get this to the original TM Android 10, which I think is shown here as the file XT2113-2_KIEV_TMO_10_QZKS30.Q4-40-95-6_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip as I hope it will undo some of the "security" crap Google has added to Android with each successive release.
So I need to be sure of the following:
1. Can I downgrade from 11 to 10?
2. Is there some reason to NOT use the firmware mentioned above? Should I use retail US (RETUS) instead? I am not sure the differences (it would be great if that would permit me to use this phone on Red Pocket Verizon but the IMEI now shows as incompatible on Verizon).
3. Must I unlock the boot loader to downgrade? I know I must to do other stuff and I have the unlock code on hand and ready to put it if needed. If I must unlock the boot loader to downgrade, will I have to re-unlock it afterwards? And, if so, will I have to go through the same process of getting a code or will the code I have now work?
4. How do I flash to do the downgrade? I have the Lenovo Rescue/Smart Assistant installed on my PC and was able to download the stock firmware (I assume it matches what is on there now) and stashed it aside. But is there some other tool needed?
5. Once I achieve downgrade, what is the best way to avoid having the thing auto-update to Android 11?
Thanks for your help with these questions.
Z flip 4 is supposed to get OneUI 5.0 with A13 in November, but it just received the November security patch without A13. Do you think that A13 will get delayed for our phone?
I read here that beta 2 was released recently. Usually they will issue beta 3 before it will be final. So yes, I can see the A13 can be delayed till December.
But that's no biggie really. Not that much changed from A12 to A13 anyway.
Beta 4 ZVK3 is under testing at the moment
I am still stuck in beta 1 ZVK9. I manually load this one, after that, keep looking for beta 2, 3 and 4 now. No luck. For those if you are still in A12, maybe be patient. Google Pay won't work in beta software, I don't see other issues.
johnny8910 said:
Beta 4 ZVK3 is under testing at the moment
Click to expand...
Click to collapse
Oh, good to know.
I guess my part regarding delay is irrelevant then.
What about performance? Any significant variances against A12? How's the battery life?
starche_old said:
What about performance? Any significant variances against A12? How's the battery life?
Click to expand...
Click to collapse
No massive changes, but does seem snappier. Ram Memory management is improved over A11 in my opinion.
Battery life for me is exactly the same.
Has anyone managed to get the firmware file or the fetch the ota update file, for the US model, for the stable release yet?
I too, curiously any one (service/model) combination in US get official A13 update?
I have F721U1 directly purchased from samsung.com. I am with US mobile service (VZW MVNO). I manually apply A13 beta 1. Phone runs fine and does not hit any issues as I am aware in my usage pattern.
However, Gpay won't work with beta SW. Keep googling without any luck for official download Link. Tired for read all different web site post update screen and news announcement. None of them has download link.
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Maybe a couple days more.....
https://www.sammobile.com/news/galaxy-z-flip-4-fold-4-android-13-update-stable-released/
krusir said:
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Click to expand...
Click to collapse
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Thank you. I will try it when I find download link.
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
SM-F721B A13 CSC SLK is official
Download from Samfirm
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Flashed One UI 5 yesterday. From the SM-F721B EUX to SM-F721B SRI, dirty flash.
Worked fine, it feels a little more smooth but I was expecting more changes tbh.
EUX upgrade live today for me.
One day later for me. Also EUX.
acytoo said:
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Click to expand...
Click to collapse
The only difference between the two is the carrier (U) firmware has carrier specific features, not apps, that aren't in the unlocked (U1) firmware. For example, people who have AT&T as their carrier, such as myself, can get AT&T's 5G+ an I have no idea what AT&T's 5G+ even is. Also the U1 version isn't the Google Fi version, I'm guessing when you buy a Google Fi Z flip they use the unlocked variant and just put a sim card inside of it.
krusir said:
Thank you. I will try it when I find download link.
Click to expand...
Click to collapse
In case you haven't found it yet, and one UI 5 is out, you can use samloader, which is a terminal/command line tool that allow you to download firmware straight from Samsung's servers. On Linux it is as simple as running pip install git+https://github.com/samloader/samloader.git and on windows I don't know what to do as I don't primarily use it. The only Idea I have is to download python for windows, clone the repository and copy the files to the same directory of python.exe.
The command to download the firmware using samloader - samloader -m SM-F721U -r TMB -v F721USQU1BVK3/F721UOYN1BVK3/F721USQU1BVK3/F721USQU1BVK3 -o <name of file, e.g. flip4-oneui5.zip or SM-F721U-OneUI5.zip>