Can I fix my sound problem/ bug on my s7 when I flash a custom Rom? - Samsung Galaxy S7 Questions and Answers

Hello,
For some days I had a thread where my audio suddenly cut off or some weird noises appeared.
https://youtu.be/a1TaBH11bTI
What I´ve seen the problem is not uncommon and it is software related. So I wanted to ask you about your experience, could you fix the problem by flashing a custom Rom?

Stop making dupe threads, mods have already closed one
http://forum.xda-developers.com/showthread.php?t=3673744

*Detection* said:
Stop making dupe threads, mods have already closed one
http://forum.xda-developers.com/showthread.php?t=3673744
Click to expand...
Click to collapse
It is different because I think it software related and I want to know if it is possible to fix it throught different Roms.
My prior thread was different I didn´t know why it happend.

No, it's exactly the same, with the exact same problem and exact same video

*Detection* said:
No, it's exactly the same, with the exact same problem and exact same video
Click to expand...
Click to collapse
Because my problem is not solved

alecander said:
Because my problem is not solved
Click to expand...
Click to collapse
So what? Making multiple threads isn't going to fix it, make 1 thread and wait for an answer

Happens to me whenever my phones swaps from WiFi to LTE or vice versa. Otherwise if it is a software issue it's most likely a bootloader/modem mismatch. Have you been jumping between 6.x and 7.x Android? Because if you use a 6.x bootloader/modem with a 7.x android or the other way around, it will break vibration and other aspects of the software.

Beanvee7 said:
Happens to me whenever my phones swaps from WiFi to LTE or vice versa. Otherwise if it is a software issue it's most likely a bootloader/modem mismatch. Have you been jumping between 6.x and 7.x Android? Because if you use a 6.x bootloader/modem with a 7.x android or the other way around, it will break vibration and other aspects of the software.
Click to expand...
Click to collapse
No, I stayed on android 6 never updated or downgraded but what do you mean with modem? or bootloader/modem. Maybe I should add that I rooted the phone to gain twrp and root. And vibration and other stuff works well besides this sound problem

There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.

Beanvee7 said:
There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.
Click to expand...
Click to collapse
And that is how you fix your problem? Update the bootloader and modem? But after the flash I can still keep twrp or do I need to do the process anew?

Beanvee7 said:
There are 4 firmware components, the OS/ROM, the bootloader, the modem, and the carrier config. When you change the OS/ROM, you should be changing the rest to match.
If you've stayed on android 6 you should be okay, however it's not a bad idea to go to updato.com, download the most recent 6.0.1 stock firmware for your country/carrier and flash the bootloader (BL) and modem (CP) files. There's a guide on updato.com showing the step by step process, just make sure you don't do a full flash. Only the bootloader and modem.
Since the bootloader is essentially the backbone of your phone, it's always beneficial to have it up to date with your version of android (Don't use a 7.x bootloader on 6.x). Modem updates also help with your phones signal and data performance.
You should find most ROM guides say always update the bootloader and modem before installing the ROM.
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?record=163A32D2CBDF11E69215FA163EE8F90B
So thats the version with the correct AP, CP and CSC when I flash the modem and bootloader everything should be fine I hope.

Yea my problems were fixed doing this, and if you only flash BL and CP you won't lose any data or TWRP.
I can't guarantee it will fix it, but it's a good start.

Beanvee7 said:
Yea my problems were fixed doing this, and if you only flash BL and CP you won't lose any data or TWRP.
I can't guarantee it will fix it, but it's a good start.
Click to expand...
Click to collapse
I flashed it but the sound problem remains it didn't make that aggressive sound cut off and noises like in my video but the sound still cuts off

Related

[STOCK][LATEST] OFFICIAL SM-G935U's G935UUEU4APL4 Firmware for the T-Mobile Variant

Hi there XDA,
First of all, I don't claim to be a developer nor I am here to plagiarize/steal/uncredit those developers and providers.
Therefore, this post is to provide you with the latest UNLOCKED SM-G935U Stock Firmware for
users running the T-MOBILE variant (SM-G935T)
There were many comments on threads as to when the firmware would update, and finally is here!
Note: I DO NOT TAKE CREDIT FOR THIS, I DID NOT CREATE THIS OR STOLE FROM ANYBODY. THE INFORMATION PROVIDED LINKS DIRECTLY TO SAMSUNG's OFFICIAL FIRMWARE WEBSITE "SAMMOBILE".
Note to the Community: This latest version is confirmed to have ISSUES with ROOT. After successful root and/or XPOSED, Wi-Fi connection, overall lag, and heating issues are present. So it is up to you if you decide to root or not.
Note to Admin/Moderators: IF YOU FEEL THIS THREAD IS NOT APPROPIATE OR IF YOU WANT TO ELIMINATE THIS THREAD, FEEL FREE TO DO IT. My intention is just to provide the community with this update for the SM-G935U (T-MOBILE) Firmware as quick as possible for those in need and for those pioneering fellas.
As soon as I am done setting up, I will surely provide you with any insight/features added to this update.
Happy developing...
RECENT UPDATES ON ROOT PERFORMANCE/STABILITY [Jan.30.2017]: This 4APL4 Variant INDEED works with the root method by @Mastajeff, I can't find any issues at all. I personally believe that this Firmware version without root works even better for whatever your needs.
*** BASED ON PERSONAL USE AND RECENT DOWNGRADE TO STOCK G935U###4API3, I ENDED UP HAVING BETTER PERFORMANCE, BATTERY LIFE, AND STABILITY WITHOUT ROOT. I JUST WENT ON TO DISABLE COUPLE SYSTEM APPS WITH EZ DISABLER. I NOTICED BETTER RESULTS, PERFORMANCE, AND STABILITY USING ROOT ON THE PREVIOUS #4API3 FIRMWARE VERSION. (THIS IS JUST MY OPINION BASED ON RECENT UPDATE I DID, BUT IT IS ALWAYS YOUR CHOICE TO WORK ON)
Official SM-G935U (T-Mobile) Variant "G935UUEU4APL4"
Model SM-G935U
Country USA (T-Mobile)
Version Android 6.0.1
Changelist 9978521
Build date Fri, 09 Dec 2016 14:00:30 +0000
Security Patch Level 2016-12-01
Product code TMB
PDA G935UUEU4APL4
CSC G935UOYM4APL4
Official SamMobile SM-G935U TMB Firmware website: http://www.sammobile.com/firmwares/download/118886/G935UUEU4APL4_G935UOYM4APL4_TMB/
What is the difference with features of this G935UUEU4APL4 Frimware and G935TUVU4APK1
Thanks purotijuana for the post - Great Catch!
Have you personally flashed this version?
What is the difference with features of this G935UUEU4APL4 Frimware and G935TUVU4APK1?
I am on previous U firmware API3. Is there a way to upgrade to this without losing data?
Thanks,
Hello my friend, of course you can upgrade without losing data.
But I have a quick note for you, if you have a micro sd card will make everything better.
But if you don't, just upgrade using latest Odin version v3.12 by flashing THE BL, AP, CP......AND MOST IMPORTANT THE CSC FILE....Don't flash the HOME_CSC. You won't lose anything at all my friend.
Hello my friend, of course you can upgrade without losing data.
But I have a quick note for you, if you have a micro sd card will make everything better.
But if you don't, just upgrade using latest Odin version v3.12 by flashing THE BL, AP, CP......AND MOST IMPORTANT THE CSC FILE....Don't flash the HOME_CSC. You won't lose anything at all my friend.
Can anyone who's flashed this confirm if the modem works with band 12, or if we still need to use the TMO apk3 modem?
DOMF said:
Can anyone who's flashed this confirm if the modem works with band 12, or if we still need to use the TMO apk3 modem?
Click to expand...
Click to collapse
As a matter of fact, T-Mobile's SM-G935T also released an APL4 Firmware update.
So we are better off flashing the latest CP File from SM-G935T into the G935U APL4 Firmware.
*will provide links to all downloads*
serendipityguy said:
Thanks purotijuana for the post - Great Catch!
Have you personally flashed this version?
What is the difference with features of this G935UUEU4APL4 Firmware and G935TUVU4APK1?
Click to expand...
Click to collapse
Hello there pal,
I've sucessfully flashed this update and the VERY FIRST THING I NOTICED is a SMOOTHER UI. During the setup I noticed an increase in speed and touch response.
Samsung Pay comes in by default and it can't be disabled by default. Other than that, the ONLY down I noticed....AND I MIGHT BE WRONG GUYS BUT....I am actually surprised to notice significant battery drain
Have you personally went on to flash this update??
APL4
purotijuana said:
Hello there pal,
I've sucessfully flashed this update and the VERY FIRST THING I NOTICED is a SMOOTHER UI. During the setup I noticed an increase in speed and touch response.
Samsung Pay comes in by default and it can't be disabled by default. Other than that, the ONLY down I noticed....AND I MIGHT BE WRONG GUYS BUT....I am actually surprised to notice significant battery drain
Have you personally went on to flash this update??
Click to expand...
Click to collapse
Has anyone else noticed big battery drain?
Jimmy4485 said:
Has anyone else noticed big battery drain?
Click to expand...
Click to collapse
Yes Jimmy, there is huge battery drain in this new update!
AndroidFileHost for faster download:
http://www.androidfilehost.com/?fid=385035244224411333
krishelnino said:
I am on previous U firmware API3. Is there a way to upgrade to this without losing data?
Thanks,
Click to expand...
Click to collapse
I was on API3 I went to setting and clicked on system update and it updated to APL4. If you are using G935T CP modem you might to flash the API3 modem in CP to get the update. and you should not loose any data.
purotijuana said:
Hello my friend, of course you can upgrade without losing data.
But I have a quick note for you, if you have a micro sd card will make everything better.
But if you don't, just upgrade using latest Odin version v3.12 by flashing THE BL, AP, CP......AND MOST IMPORTANT THE CSC FILE....Don't flash the HOME_CSC. You won't lose anything at all my friend.
Click to expand...
Click to collapse
i did exactly u said. and i didnt install home csc but i lost everything. how come it happened
quarkw said:
i did exactly u said. and i didnt install home csc but i lost everything. how come it happened
Click to expand...
Click to collapse
Perhaps quarkw something was not or was checked that caused the pit to partition your puppy with Odin. When you flash via Odin from one one rom to another there is always a chance of losing data.
Once you wipe cache in the recovery step (if you did this step) there were some other options that may have wipe the phone or your MicroSD card.
The files may actually be present and you may have lost root, if you had it. There are so many variables that could have happened.
It sucks to loose data, it does.
But look at it as a learning experience and make the time to perform the following steps next time.
If I were you, get root then get TI backup over at google play (get the paid version) to backup everything to your MicroSD that way you can always flash without losing data.
TIP: save your present contacts with their phone numbers, email address & address to Google Contacts, so whenever you flash and format, your contacts will be there automatically with you once you sign into your Google Account.
Perhaps I may write a tutorial on how to flash / backup rom & data APKs and such. It took me a while to learn the ropes too.
I'm pretty sure you flash the HOME CSC file if you DON'T want to lose all your data, thats what I've read else where here on xda
Quickvic30 said:
I'm pretty sure you flash the HOME CSC file if you DON'T want to lose all your data, thats what I've read else where here on xda
Click to expand...
Click to collapse
That's what I've read as well. CSC=wipes data Home_CSC=keeps data
A couple of things
newuser1984 said:
I was on API3 I went to setting and clicked on system update and it updated to APL4. If you are using G935T CP modem you might to flash the API3 modem in CP to get the update. and you should not loose any data.
Click to expand...
Click to collapse
Yes if you were using the G935T CP modem you do have to flash the API3 modem in the CP section of Odin to get the OTA update for APL4. I didn't lose any data doing this.
Also I could have sworn I could still use Wifi Calling on the API3 firmware. But I definitely can't on APL4. Can anyone confirm if you do have wifi calling with the API3 firmware with the US unlocked modem or API3 firmware with the T-Mobile APK1 CP modem?
NayrStrebor said:
Yes if you were using the G935T CP modem you do have to flash the API3 modem in the CP section of Odin to get the OTA update for APL4. I didn't lose any data doing this.
Also I could have sworn I could still use Wifi Calling on the API3 firmware. But I definitely can't on APL4. Can anyone confirm if you do have wifi calling with the API3 firmware with the US unlocked modem or API3 firmware with the T-Mobile APK1 CP modem?
Click to expand...
Click to collapse
I am on APL4 and wifi calling is working. I am using APK1 modem, it also worked on API3
newuser1984 said:
I am on APL4 and wifi calling is working. I am using APK1 modem, it also worked on API3
Click to expand...
Click to collapse
Where is wifi calling located in the settings?
Is there a battery drain?

Switch from SM-G930U Nougat to SM-G930T Oreo (T-Mobile) possible?

Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Edit: As indicated in the responses below, the solution is the latest Odin version (3.13.1), and I successfully converted. Good luck!
quasihellfish said:
Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Click to expand...
Click to collapse
You need to update your Odin. Oreo ROMs use a new compression format that your old Odin can't handle.
Ultima99 said:
You need to update your Odin. Oreo ROMs use a new compression format that your old Odin can't handle.
Click to expand...
Click to collapse
Update to what? I was using 3.12.7.
Edit: OK, looks like I found it. 3.13.1 is for Oreo, etc. Thanks for the heads-up.
Hi. I have the same Verizon s7 and have also got a 930u rom on it but I am desperate for Oreo. Have you managed to successfully flash the 930t oreo rom? And if so where did you download it from?
updated URL
james909 said:
Hi. I have the same Verizon s7 and have also got a 930u rom on it but I am desperate for Oreo. Have you managed to successfully flash the 930t oreo rom? And if so where did you download it from?
Click to expand...
Click to collapse
Yes, I was successful. You can get the firmware from Updato here: https://updato.com/firmware-archive-select-model?q=SM-G930T&exact=1&r=&v=Oreo(Android+8.0.0)&rpp=15
But ignore their update instructions, as they are outdated and meant for Nougat and below. You need Odin 3.13.1, from here: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789.
If you try with an older Odin version it will soft-brick your device (as I found). Otherwise flashing instructions are simple and the same as when you switched to 930U.
Great thanks. I will try it!
I can't get it to start. I've loaded up the firmware into odin, connected the phone in download mode and it won't start flashing. What could I be doing wrong and is it worth doing anyway?
james909 said:
I can't get it to start. I've loaded up the firmware into odin, connected the phone in download mode and it won't start flashing. What could I be doing wrong and is it worth doing anyway?
Click to expand...
Click to collapse
I can't tell you if it's worth it (I think it is). But you also need the Samsung USB drivers installed on your PC, and you need USB debugging turned on, etc. Make sure you have a working connection before flashing.
It worked. Thanks!
Does it has the whole bloatware thing???
I'm still gonna flash it, but I wanna know, cuz I'm not in my house right now, and also is it laggy???
Whicho_castillo said:
Does it has the whole bloatware thing???
I'm still gonna flash it, but I wanna know, cuz I'm not in my house right now, and also is it laggy???
Click to expand...
Click to collapse
Define "bloatware thing". There's like half a dozen T-mobile apps, plus a small handful of other "pre-installed" things like Whatsapp, etc. Virtually all of them can be disabled. The only one I've found that can't is the official T-mobile account app. But I just cleared the apps data, and never use it. I'm not logged in or anything, so it sits there idle.
Regarding "laggy", I can't really say. It works as well as Nougat did. And I think I can say the battery life is definitively better.
quasihellfish said:
Define "bloatware thing". There's like half a dozen T-mobile apps, plus a small handful of other "pre-installed" things like Whatsapp, etc. Virtually all of them can be disabled. The only one I've found that can't is the official T-mobile account app. But I just cleared the apps data, and never use it. I'm not logged in or anything, so it sits there idle.
Regarding "laggy", I can't really say. It works as well as Nougat did. And I think I can say the battery life is definitively better.
Click to expand...
Click to collapse
Thank for your response, at least I'll be using GoodLock
I have all the files over in the TMobile forum
Use the latest Odin
https://forum.xda-developers.com/tm.../sm-g930t-official-stock-oreo-update-t3810449
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
quasihellfish said:
Has anyone successfully (or have any info regarding) converted from a SM-G930U (7.0) to a SM-G930T (8.0)?
I have a completely stock, working S7 SM-G930U (that I previously converted from SM-G930V), updated to the latest Unlocked 7.0 version. I was eager to get Oreo, but didn't want to wait for 930U firmware so decided to just switch to the T-mobile version because I'm on a T-mobile MVNO. However, when I tried just flashing the G930T files with Odin it fails right after the "emmc_appsboot.mbn.lz4" step (whatever that is). This made the phone unbootable and would just boot loop.
I was able to successfully recover the phone by re-flashing the G930U files again after downloading from Updato. So the phone is working again, but I'm right back where I started.
So, my question is: Is there something different that I should be doing, or some other secret to go from U -> T, with the intent of getting Oreo? Would it work if I flashed the 7.0 version of 930T, then taken the OTA update?
Click to expand...
Click to collapse
U firmware is just firmware without carrier bloat. You can flash any carrier on an unlocked phone. I provided the link to my thread with the official TMobile Oreo stock files just get Odin. https://forum.xda-developers.com/tm.../sm-g930t-official-stock-oreo-update-t3810449
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Hi, there's bloatware and it's mildly annoying as is the t-mobile splash screen and sound effect. I'll switch bach to 930u when Oreo is available. You'll also have no data toggle swith in the shortcuts when you pull the screen down. However, I added mine using adb. You can also uninstall programs uing adb but I haven't. If anyone has the adb script for removing t-mobile apps I'd be greatful if they'd post it.
UmerBaig said:
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Click to expand...
Click to collapse
Call your network provider or carrier and see if they can change the settings or to make sure your data settings are set up right. Things like apn settings, network, etc.
---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------
james909 said:
Hi, there's bloatware and it's mildly annoying as is the t-mobile splash screen and sound effect. I'll switch bach to 930u when Oreo is available. You'll also have no data toggle swith in the shortcuts when you pull the screen down. However, I added mine using adb. You can also uninstall programs uing adb but I haven't. If anyone has the adb script for removing t-mobile apps I'd be greatful if they'd post it.
Click to expand...
Click to collapse
Once official Oreo is out for 930u I'm switching back also
UmerBaig said:
hello. I had flashed my smg930a with smg930U firmware. after that everytime I restarted my mobile, it showed error " no network connection " sometimes it picked up network after a restart and sometimes it picked up network after weeks. Tried flashing smg930a firmware again but the error remains same. Now i flashed it with smg930t firmware hoping the error will end but it shows "searching" and I've no network connection.
any help will be great.
Click to expand...
Click to collapse
What network SIM are you using? You kind of need to match the firmware with the carrier you are using, as it enable certain radios. That being said, the 930U should work universally. If it doesn't, then you probably didn't update or use the right APN settings to enable LTE. You'll have to do some online searching to look for the appropriate APN settings for your carrier, especially if you are using a firmware version that doesn't match your carrier.
I have Tmobile G930t.
Can i install G930FD indian rom in it?
Indian roms are for exynos processors i guess..
Pls advice
atin_garg said:
I have Tmobile G930t.
Can i install G930FD indian rom in it?
Click to expand...
Click to collapse
NO!
atin_garg said:
Indian roms are for exynos processors i guess.
Click to expand...
Click to collapse
Yes.
Can i Install this on My 930U its nougat and this to go on OREO ? is it possible ?
Thanks

Please help with switching firmwares, kind of a weird situation.

Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
finshan said:
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
Click to expand...
Click to collapse
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Youdoofus said:
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Click to expand...
Click to collapse
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
finshan said:
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
Click to expand...
Click to collapse
you cannot go backwards in bootloader revisions, but you can go backwards in android versions as long as theyre on the same BL revision(not likely, but who knows? I didnt look yet). Also, the worst thing that could happen if you try to flash an older BL version is that itll fail in Odin and will still allow the phone to boot normally (usually, and if it doesnt, its still fixable). The only issue with booting it after flashing new firmware with your current sim is that itll install the carrier specific stuff on the phone so long as the CSC needed for that is in the multi CSC pack you flashed on the phone, and if it does install the carrier crap you dont want, just factory reset it and reboot with the actual sim you want you use
no problem man, thats what we are here for

How To Guide F711U and F711U1 Firmware Links and Flashing Discussion Here

(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available

Question How to fix imei lost after flash stock rom

After flash Rom stock my phone lost imei how to fix it?
Please help
I have same problem. I'm stuck now on binary 2, can't downgrade firmware. I really don't know to fix.
I rooted my device before then I restored everything back to stock firmware/settings and now when updates comes my imei and baseband is gone.
Same issue any ideas?tried flashing every firmware for this phone but no luck seems to be hardware related
komninoskkomninos said:
Same issue any ideas?tried flashing every firmware for this phone but no luck seems to be hardware related
Click to expand...
Click to collapse
do you think if you downgrade android 11 to android 10 will the imei come back?
unfortunately it wont allow me to flash any older firmware only the latest one
You should try with this method https://forum.xda-developers.com/t/...oader-usb-vcom-and-cycling-rebooting.4322581/ the general procedure might suit for all MediaTek variants, I didn't check completely the thread, you should interchange some files for/from your model.
Probably, it requires at least the OEM unlock toggle to be switched.
Be warned that I didn´t try it on a Samsung Mediatek device because I had the Exynos/Qualcomm A10/20/30/50/70 variants, not the MediaTek, but with most of MediaTek Realme, Xiaomi, it works.
You can add also this tool to the job https://github.com/bkerler/mtkclient.
Definitely some firmwares erase the baseband becoming to null, in the theory that IMEI is not really lost, then returning to a working baseband they also have to come back, but if they have gone then returning the baseband only, it only will return the ability to make calls.
Alyandra said:
do you think if you downgrade android 11 to android 10 will the imei come back?
Click to expand...
Click to collapse
Yes Imei/Baseband works again downgrading to android 10 o the BUF9 FW

Categories

Resources