Hi, I'm having a distorted sound while I'm playing videos or listening to music on speaker and headphones. I'm on stock MM, rooted and TWRP installed. I updated the system to 1 december patch and can't upgrate to Nougat because I'll lose the IMEI, that's what they told me so I hope someone can recommend me a fix or anything to avoid this bug because started to happen when I updated to this december version.
Greetings from Perú and thanks in advance.
Turn the volume down?
Or is it distorted even at low volume?
*Detection* said:
Turn the volume down?
Or is it distorted even at low volume?
Click to expand...
Click to collapse
Yeah, even at low volume and ringtones are affected tho. It's a 1 sec distortion but when I use *#0*# to test the speaker always sounds great so maybe it's something with this G930FXXU1BPLB firmware version.
When you updated to the december version was that via OTA or an Odin flash?
Also lose the IMEI? Who told you that? I've never heard of updating android erasing your IMEI, sounds like a miscommunication to me.
Beanvee7 said:
When you updated to the december version was that via OTA or an Odin flash?
Also lose the IMEI? Who told you that? I've never heard of updating android erasing your IMEI, sounds like a miscommunication to me.
Click to expand...
Click to collapse
I updated via Odin. Yeah, I lose the IMEI when I update to Nougat and I have to take the phone to a service center and they will change the IMEI in MM.
You flash all 4 firmware files (CP, BL, AP, CSC) at the same time?
Also that sounds very shady. A phone shouldn't lose it's IMEI phone updating, I have a feeling the phone was stolen, IMEI blocked, then resold, and they're using an IMEI hack to change it.
Is Xposed on the phone currently?
Beanvee7 said:
You flash all 4 firmware files (CP, BL, AP, CSC) at the same time?
Also that sounds very shady. A phone shouldn't lose it's IMEI phone updating, I have a feeling the phone was stolen, IMEI blocked, then resold, and they're using an IMEI hack to change it.
Is Xposed on the phone currently?
Click to expand...
Click to collapse
Yeah, a friend told me the same. This phone comes from another country and here they did that IMEI hack and that's why I lose it when I update to Nougat. I flashed all 4 files at the same time. Phone was working fine with november patch so I'm guessing I'll have to downgrade or update to another MM version and then go to the service center for IMEI hack to fix this distorted sound. I'm also have xposed installed but the sound stills there with or without xposed installed.
You could note down the IMEI that works, upgrade to Nougat, put Xposed back on, and use an Xposed module to set the IMEI back.
I assume an Xposed module is what's doing it right now on MM?
Beanvee7 said:
You could note down the IMEI that works, upgrade to Nougat, put Xposed back on, and use an Xposed module to set the IMEI back.
I assume an Xposed module is what's doing it right now on MM?
Click to expand...
Click to collapse
They gave me the phone just rooted and oem unlocked on developers settings, once I disabled It and a FRP error was showed on boot. So tooked to them and told me to not to disable It and not to update to Nougat because I will lose the IMEI.
You think that updating to Nougat via Odin and setting the IMEI that it's working on xposed will do the job?
In theory yes, but honestly if I were you I'd just be asking for a refund and buying a new phone. Way too much nonsense for a phone.
Do a full backup in TWRP with everything ticked, if anything goes wrong you can restore that and it'll be back to the way it was incl. IMEI - so you won't have to take it back to the centre.
Beanvee7 said:
In theory yes, but honestly if I were you I'd just be asking for a refund and buying a new phone. Way too much nonsense for a phone.
Do a full backup in TWRP with everything ticked, if anything goes wrong you can restore that and it'll be back to the way it was incl. IMEI - so you won't have to take it back to the centre.
Click to expand...
Click to collapse
'
Ok, thanks! Maybe You know a xposed module that could help me with it?
I'm only aware of one personally https://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
Probably just a software bug that could be resolved by downgrading to an earlier version of Nougat or MM (depending on which firmware you are on).
Beanvee7 said:
I'm only aware of one personally https://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
Click to expand...
Click to collapse
Thanks!
Revontheus said:
Probably just a software bug that could be resolved by downgrading to an earlier version of Nougat or MM (depending on which firmware you are on).
Click to expand...
Click to collapse
Yeah I'm on MM 1 december patch BTU, I'll try on XEU. Thanks!
ccalixtro said:
Yeah I'm on MM 1 december patch BTU, I'll try on XEU. Thanks!
Click to expand...
Click to collapse
I suggest trying the Global version of the firmware instead of region-specific ones , regardless, good luck and hope you solve the problem!
Revontheus said:
I suggest trying the Global version of the firmware instead of region-specific ones , regardless, good luck and hope you solve the problem!
Click to expand...
Click to collapse
What Code do I have to looking for? Thanks! By the way a friend if mine wants to exchange my g930f for his Nexus 6P.
ccalixtro said:
What Code do I have to looking for? Thanks! By the way a friend if mine wants to exchange my g930f for his Nexus 6P.
Click to expand...
Click to collapse
I wouldn't trade my S7 for the 6P, it's just not worth it really. I think Global versions are marked as Global in Samsung's repository
maybe backup the EFS and restore it after installing nougat(?)
Related
Hello.
Im trying to get back to 5.1.1 but Odin gives me FAIL everytime.
What should i do?
When during the flash odin give you fail?
Try to flash THIS firmware. It won't fail;
http://www.sammobile.com/firmwares/download/63682/G920FXXU3QOLH_G920FNEE3QOL2_NEE/
It's interesting to me. Has anyone tried?. Thank you.
Hi
May I please ask why you want to go back to 5.1.1 ?
The reason is, i have 5.1.1 and i am thinking of upgrading ,but if the feedback is result then i'd rather stay on Lollipop.
Thanks and sorry for my bad english
Because it was better with me in LP and because MM missing dozens of settings and functions that were present before.
forumber2 said:
Try to flash THIS firmware. It won't fail;
Click to expand...
Click to collapse
Does if matter if my model number is different? I live in the US and Verizon is my carrier, will this effect any of that if I flash it onto my phone?
Dreamfall31 said:
Does if matter if my model number is different? I live in the US and Verizon is my carrier, will this effect any of that if I flash it onto my phone?
Click to expand...
Click to collapse
Yeah, it matters.
What's your phone's model number?
forumber2 said:
Yeah, it matters.
What's your phone's model number?
Click to expand...
Click to collapse
SM-G920V
I've tried the firmwares on SamMobile for 5.1.1 and 5.0.2 that are listed under my model number, every time I try to flash it with odin3 it comes up as a fail.
Dreamfall31 said:
SM-G920V
I've tried the firmwares on SamMobile for 5.1.1 and 5.0.2 that are listed under my model number, every time I try to flash it with odin3 it comes up as a fail.
Click to expand...
Click to collapse
Verizon prevents downgrade on their bootloader.
You can't downgrade it, like iOS devices.
forumber2 said:
Verizon prevents downgrade on their bootloader.
You can't downgrade it, like iOS devices.
Click to expand...
Click to collapse
Ah that sucks...I dislike Verizon quite a bit.
LamBor68
I need to downgrade g920f XXV from 6.0.1 to 5.1.1, i try flash odin, but it is fail. help me! all everyone
faurionutz said:
Downgrade isn't possible anymore, even if you could it will brick your phone
Click to expand...
Click to collapse
thank you
faurionutz said:
Downgrade isn't possible anymore, even if you could it will brick your phone
Click to expand...
Click to collapse
Shut up. It is possible. I do it all the time. Just download the last 5.1.1 firmware below the 6.0.1 from sammobile and you are good to go.
faurionutz said:
If you don't read news then you will brick soon some phones
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
But it doesn't happen to me!
you can bypass or disable the security policies and then do the downgrade?
Thank you
Can anyone help me downgrade g920i 6.0.1 to 5.1.1 without flashing stock or without losing my data.?
AmazingAura01 said:
But it doesn't happen to me!
Click to expand...
Click to collapse
That pretty much depends on the version of the phone, for example Vodafone phones have a custom bootloader, so it can't be easily modified, and even if you successfully flashed another bootloader, most probably you'd trip knox, in the best case, or brick the phone... Bootloaders are always very tricky...
I'm not sure of the model number in that case, I think it's G920F/25F (S6/S6 Edge).
In my case I have a G925i, and would love to know if it can be downgraded from Android 6... I don't have the latest patch yet, I didn't want to install it because I want to eventually root this phone without tripping the blessed knox thing.... I recall that PingPongRoot can root the phone without tripping knox, but I'm not sure of the android version that it works with.
Sprokyshark said:
Can anyone help me downgrade g920i 6.0.1 to 5.1.1 without flashing stock or without losing my data.?
Click to expand...
Click to collapse
There shouldn't be, not as far as the User Data is, as long as you don't wipe the /data/media partition, which shouldn't be the case when you flash stock FW. What is lost however, is the applications, those are lost along with their internal data, like SMS, Contacts (if stored on the phone), MMS, Whatsapp chats (recent ones at least if you didn't backup the latest chats), email app (if you use the stock one), saved games (if local), etc.
so what is the solution?
Yeah man I figured it out. I'm back on 5.1.1 now when I was on my s3 flashing stock would erase the whole internal storage. And coz s6 doesn't have an SD card I thot my internal would be wiped
i have a galaxy s6 (SM-G920F)and it failed in an update and got stuck in a bootloop,i tried reflashing stock rom (6.0.1),ive tried smartswitch but nothing is working I cant get into recovery either,when I tried reflashing stock rom with odin it came up with sw rev check fail device 5 binary 4,any ideas what this means? as far as I can tell its a bootloader problem
god1980 said:
i have a galaxy s6 (SM-G920F)and it failed in an update and got stuck in a bootloop,i tried reflashing stock rom (6.0.1),ive tried smartswitch but nothing is working I cant get into recovery either,when I tried reflashing stock rom with odin it came up with sw rev check fail device 5 binary 4,any ideas what this means? as far as I can tell its a bootloader problem
Click to expand...
Click to collapse
Use smartswitch emergency recovery , samsung have put in place some issues with the Bootloader, moreso if you're on a newer bootloader then you cannot install a firmware which has a lower bootloader
sofir786 said:
Use smartswitch emergency recovery , samsung have put in place some issues with the Bootloader, moreso if you're on a newer bootloader then you cannot install a firmware which has a lower bootloader
Click to expand...
Click to collapse
ive tried smartswitch and it just says SM-G920F does not support initialization please contact customer services
same problem here, any luck finding a solution?
god1980 said:
ive tried smartswitch and it just says SM-G920F does not support initialization please contact customer services
Click to expand...
Click to collapse
When you downloaded your firmware for odin, was it the very newest update? Or an old one, I've noticed some older firmwares fail to flash due to being on a newer bootloader
bogdanserban said:
same problem here, any luck finding a solution?
Click to expand...
Click to collapse
I have same issue, all the stock software out there seem to be dated where can I new stock firmware? I have Samsung S 6 from tmobile SM-G920T1.
This is my problem:
device: galaxy s6 edge tmobile
system status: custom
sw rev. check fail. device:5, binary: 2
what should I do?
i solved same problem. Just flash full nougat 7.0 via odin, don't flash MM 6.0.1.
rezstrk said:
i solved same problem. Just flash full nougat 7.0 via odin, don't flash MM 6.0.1.
Click to expand...
Click to collapse
from where to download?
dohcvtec said:
from where to download?
Click to expand...
Click to collapse
here! have fun!
For 920F
https://drive.google.com/file/d/0B0b2ginGifb-U2VzdUtzRmJTYm8/view
rezstrk said:
here! have fun!
https://drive.google.com/file/d/0B0b2ginGifb-U2VzdUtzRmJTYm8/view
Click to expand...
Click to collapse
thanks. I'll get back to you and let you know what happened. thanks again!
dohcvtec said:
thanks. I'll get back to you and let you know what happened. thanks again!
Click to expand...
Click to collapse
I also had the same issue on SW REV DEVICE 5 BINARY 4
I downloaded the Nougat 7.0 United Kingdom/Ireland and flashed using Odin and now my S6 is up and running. You can try it too.
I had tried other versions with no success.
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
dohcvtec said:
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
Click to expand...
Click to collapse
Yo, did you get it fixed? My phone for tmobile cant get passed flashing
vandres1975 said:
Yo, did you get it fixed? My phone for tmobile cant get passed flashing
Click to expand...
Click to collapse
Hey, nope. Didn't manage to get passed it. Nothing so far. Really looking for some help on that issue but no luck so far. If I come up with a solution, I will post it here.
Dang that sucks, idk what I'm going to do to unbrick it.
dohcvtec said:
Hey, nope. Didn't manage to get passed it. Nothing so far. Really looking for some help on that issue but no luck so far. If I come up with a solution, I will post it here.
Click to expand...
Click to collapse
Hey, so I have the bootloader problem too and I think we have to wait for the nougat update for the type of phone you have. I have a galaxy s6 tmobile so I think I have to get nougat and flash that when it comes out for tmobile. You have to do the same I think but for now Im gonna send it to samsung and act dumb. Hopefully maybe they fix it and send it back. Do you think they will accept my phone though? It was rooted and had nemesis rom. for nougat port from s7 edge. Also current binary is: Samsung Official. System Status is: Custom. They can see knox is tripped since the counter is void: 1.
vandres1975 said:
Hey, so I have the bootloader problem too and I think we have to wait for the nougat update for the type of phone you have. I have a galaxy s6 tmobile so I think I have to get nougat and flash that when it comes out for tmobile. You have to do the same I think but for now Im gonna send it to samsung and act dumb. Hopefully maybe they fix it and send it back. Do you think they will accept my phone though? It was rooted and had nemesis rom. for nougat port from s7 edge. Also current binary is: Samsung Official. System Status is: Custom. They can see knox is tripped since the counter is void: 1.
Click to expand...
Click to collapse
Hey, it depends if you have warranty on the phone or not. If you have warranty, it will not cover your expenses because it's void after unlocking bootloader and rooting. If you don't have warranty and you are paying them anyways, they should have no trouble accepting it. Who would deny taking money. I hope they can fix it for you and I'm sorry we couldn't figure out how to. What you said about Nougat is true. I have checked that information as well. There is no Nougat for TMobile yet. We just have to wait. Again, in the mean time if I fix it, I will post my solution here.
dohcvtec said:
Hey, it depends if you have warranty on the phone or not. If you have warranty, it will not cover your expenses because it's void after unlocking bootloader and rooting. If you don't have warranty and you are paying them anyways, they should have no trouble accepting it. Who would deny taking money. I hope they can fix it for you and I'm sorry we couldn't figure out how to. What you said about Nougat is true. I have checked that information as well. There is no Nougat for TMobile yet. We just have to wait. Again, in the mean time if I fix it, I will post my solution here.
Click to expand...
Click to collapse
Alright.
dohcvtec said:
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
Click to expand...
Click to collapse
Try the first one from the top from here http://updato.com/firmware-archive-select-model?q=sm+g920t&exact=1
with Odin v3.12.3
Hi guys, I bought a Vodafone-branded unlocked S7 here in Ireland.
Never used it with Vodafone and I've never received any updates for it.
OTA, Smart switch and Updato they all say my device is up to date but I can see there are more recent firmwares for my CSC.
Here are my details:
PDA: G930FXXU1DQEI
CSC Version: G930FVFG1DQE3
BASEBAND Version: G930FXXU1BPJJ
CSC Code: VDI
Am I missing something or is it possible that under VDI there are more update channels and my phone is not supposed to receive the other updates?
It's working fine and everything, I'm only concerned about security patches to be honest.
Hope you can give me a hint.
Cheers guys.
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
*Detection* said:
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
Click to expand...
Click to collapse
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
alediaferia said:
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
Click to expand...
Click to collapse
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
*Detection* said:
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
Click to expand...
Click to collapse
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
alediaferia said:
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
Click to expand...
Click to collapse
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
*Detection* said:
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
Click to expand...
Click to collapse
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
alediaferia said:
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
Click to expand...
Click to collapse
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
*Detection* said:
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
Click to expand...
Click to collapse
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
alediaferia said:
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
Click to expand...
Click to collapse
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Aashish.007 said:
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Click to expand...
Click to collapse
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
I guess if the boot loader is unlocked then you're good to go.
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
And Stock firmware won't trip Knox.
For the sake of completeness, I have explained my solution in here: https://forum.xda-developers.com/galaxy-s7/help/wrong-modem-cp-version-t3743284
Thanks everyone for your help
Introduction:
Download official G965USQS4CSC8 (carrier) and G965U1UEU4CSC7 (unlocked) firmware for the SM-G965U and SM-G965U1 here. You can flash either onto a SM-G965U or SM-G965U1 using the patched Odin linked below. Flashing back and forth is safe because they are both on bootloader version 4.
Click to expand...
Click to collapse
Patch Level:
Carrier SM-G965U 04-01-19 (CSC8)
Unlocked SM-G965U1 03-01-19 (CSC7)
Click to expand...
Click to collapse
So, what is userdata?
A lot of people think this is carrier bloat only. However, userdata also contains the files necessary to activate carrier specific features. Without it, you may not be able utilize all of the carrier features that the phone is capable of providing. Please note that carrier userdata may not be available for your carrier.
Click to expand...
Click to collapse
SM-G965U1 (unlocked version) users read here:
Drawbacks of flashing carrier version G965USQS4CSC8 firmware on the unlocked phone (SM-G965U1):
CallerID no longer works unless you subscribe to carriers CallerID service.
Installs carrier bloat.
Benefits of flashing carrier version G965USQS4CSC8 firmware on the unlocked version phone (SM-G965U1):
Will enable all carrier specific features (video calling, etc, etc).
Click to expand...
Click to collapse
SM-G965U (carrier version) users read here:
Drawbacks of flashing unlocked version G965U1UEU4CSC7 firmware on the carrier version phone (SM-G965U):
Will disable all carrier specific features (video calling, etc, etc).
Benefits of flashing unlocked version G965U1UEU4CSC7 firmware on the carrier version phone (SM-G965U):
CallerID works without subscribing to carriers CallerID service.
Eliminates carrier bloat.
Click to expand...
Click to collapse
Installation Instructions:
Reboot to download mode:
Power off your Galaxy S9 Plus completely until it vibrates.
Press and hold the Volume Down + Bixby + Power buttons simultaneously. Release the buttons when you see the warning message.
Now just press Volume up button to continue.
Congratulations, you're now in download mode.
Connect your phone to your PC:
Start the patched Odin 3.13.1 that you downloaded from the provided link.
Plug the cord your phone came with into your phone and PC. Other cords may not work.
The Odin log will display a <ID:0/005> Added!! message once it connects.
Flash the firmware:
First, extract the compressed firmware to a folder on your PC.
In Odin, begin with the BL (bootloader) box, navigate to the firmware folder and select the file beginning with BL_.
Wait for each file to initialize and appear to the right of its corresponding box before attempting to proceed to the next step.
Now select the AP (Application Processor aka System) box, it should open the correct folder, then select the file beginning with AP_.
AP takes a while to initialize, don't worry.
Now select the CP (Core Processor aka modem) box, then select the file beginning with CP_.
Now select the CSC (Consumer Software Customization aka Carrier Settings) box, then select the file beginning with CSC_.
Choose HOME_CSC to not wipe your phone, or CSC_ (preferred option when switching between unlocked and carrier versions) to wipe your phone .
Optionally, select the userdata (User Data) box, then select the file beginning with USERDATA_.
Now, click start and wait for the magic.
Disconnect the cord when the phone reboots.
The phone should boot to recovery to automatically cleanup, then reboot again.
Click to expand...
Click to collapse
Downloads:
Download SM-G965U Firmware Here
Download SM-G965U1 Firmware Here
Download patched Odin Here
Click to expand...
Click to collapse
I v just one question. How do I restore a tripped knox after flashing or restore my flash count to zero?
Sent from my SM-G965F using Tapatalk
Got a non-Android File host mirror? They're slow or not working for me at all no matter what mirror of theirs I choose.
samson007 said:
I v just one question. How do I restore a tripped knox after flashing or restore my flash count to zero?
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Tripped knox is forever. There is a fuse that blows on the phone. That said, there are workarounds on rooted phones (you might as well stay rooted). Try looking for edits for the build.prop to restore functionality to Samsung Health and other affected apps. Dr Ketan still makes ROMs I believe and should have something for you.
NLA
NLA
Then I won't root. The only reason I want to root is because I need to use mod apps like Spotify but sadly all the ones v been downloading never worked. Can you help me out please. Thank you
rmarinella said:
Tripped knox is forever. There is a fuse that blows on the phone. That said, there are workarounds on rooted phones (you might as well stay rooted). Try looking for edits for the build.prop to restore functionality to Samsung Health and other affected apps. Dr Ketan still makes ROMs I believe and should have something for you.
Click to expand...
Click to collapse
Sent from my SM-G965F using Tapatalk
samson007 said:
Then I won't root. The only reason I want to root is because I need to use mod apps like Spotify but sadly all the ones v been downloading never worked. Can you help me out please. Thank you
Click to expand...
Click to collapse
I don't want to be rude, but your question was answered already. You can't untrip the know counter. It's an actual fuse, that physically becomes blown. This isn't a software setting, but an actual, physical fuse.
It goes back to the days of people using exploits, and in rare cases would damage their phone in the process, but the phone worked enough to relock the bootloader. Then the person would send their phone back and blame it on the manufacturer. So now Samsung decided to put in an actual fuse so that if you decide to unlock it, your warrenty is permanently void.
Bottom line, your out of luck. I know any unlock would have given a warning that it is PERMANENT and that it would VOID YOUR WARRENTY. Wether you read it and ignored the warning, or didn't bother to read it, it's on you for unlocking your bootloader.
todd3835 said:
I don't want to be rude, but your question was answered already. You can't untrip the know counter. It's an actual fuse, that physically becomes blown. This isn't a software setting, but an actual, physical fuse.
It goes back to the days of people using exploits, and in rare cases would damage their phone in the process, but the phone worked enough to relock the bootloader. Then the person would send their phone back and blame it on the manufacturer. So now Samsung decided to put in an actual fuse so that if you decide to unlock it, your warrenty is permanently void.
Bottom line, your out of luck. I know any unlock would have given a warning that it is PERMANENT and that it would VOID YOUR WARRENTY. Wether you read it and ignored the warning, or didn't bother to read it, it's on you for unlocking your bootloader.
Click to expand...
Click to collapse
Yea I remember those days... Well truth is I haven't rooted.. I was considering it until I read the warranty part... My point is, the reason I want it rooted is because I want to use some modded applications. I researched further and found out I could use some without even rooting. So i tried downloading Spotify mod app, but unfortunately it didn't work. I couldn't get recent application for it, what I kept getting was an outdated mod app. In all it didn't work. So am asking if there's a way to use mod apps without rooting the phone. Thank you
Sent from my SM-G965F using Tapatalk
samson007 said:
Yea I remember those days... Well truth is I haven't rooted.. I was considering it until I read the warranty part... My point is, the reason I want it rooted is because I want to use some modded applications. I researched further and found out I could use some without even rooting. So i tried downloading Spotify mod app, but unfortunately it didn't work. I couldn't get recent application for it, what I kept getting was an outdated mod app. In all it didn't work. So am asking if there's a way to use mod apps without rooting the phone. Thank you
Click to expand...
Click to collapse
You'll have to wait until someone mods the latest app. Or, you could just pay for Spotify. For the record, I used to use a modded Spotify, and they typically patch within a day or two of a modded apk being released. They may have finally switched to server side authentication which is why your likely not seeing an updated version. I stopped bothering because it's just a cat and mouse game. I didn't feel like Spotify was worth it, so I moved on.
I find Google Play Music is a better deal. I get add-free YouTube, and all the same music as Spotify, for the same price.
On a side note, I don't believe Xda allows modded apks that bypass paid features. There are sites that cater to such things, but I'm pretty sure it's a no-no here. They tend to support devs / companies as opposed to cheating them out of money.
Hi dude, I have 2 questions, I just buy S9+ 965U sprint unlock running U3ARH7 can I flash this 965U1's fw? and What is CSC in U1 fw? thanks
optimus207 said:
Hi dude, I have 2 questions, I just buy S9+ 965U sprint unlock running U3ARH7 can I flash this 965U1's fw? and What is CSC in U1 fw? thanks
Click to expand...
Click to collapse
Hi, you can flash the U1 firmware on the Sprint 965U. You need to use the patched Odin linked in the OP. The CSC file included is for multiple carriers. When flashing it will read your sim and setup accordingly.
Umm what's new? The "I" September patch Odin's have been out since mid September.
rmarinella said:
Introduction:
SM-G965U1 (unlocked version) users read here:
SM-G965U (carrier version) users read here:
Installation Instructions:
Downloads:
Click to expand...
Click to collapse
The thread provides detailed instructions and the most current firmware. The instructions are new to the thread and so are the links. Didn't realize I was required to explain what was new to you.
Uploading G965USQS3ARIB firmware now.
Hi, Q. If I install the ARIB version in my U1 under att, I still can use another carrier sim right?
I'm traveling to Argentina soon and I want to know that.
Thanks
Should be fine , your U1 is unlocked. The sim card in Argentina might not set up the APN for you regardless of what firmware you're on. Personally, I would use the U1 firmware though.
juannicolas said:
Hi, Q. If I install the ARIB version in my U1 under att, I still can use another carrier sim right?
I'm traveling to Argentina soon and I want to know that.
Thanks
Click to expand...
Click to collapse
I don't use the "B" revision firmwares, but there was at least one listed as a BOYD firmware. Since your already on U1 and loosing wifi-calling, HD voice, volte, etc, that might give you the best luck. Might be something to look into.
todd3835 said:
I don't use the "B" revision firmwares, but there was at least one listed as a BOYD firmware. Since your already on U1 and loosing wifi-calling, HD voice, volte, etc, that might give you the best luck. Might be something to look into.
Click to expand...
Click to collapse
Sorry, didn't understood your response. Is that an yes besides regaining the features of HDVoice, volte and Wifi Calling?
Thanks
juannicolas said:
Sorry, didn't understood your response. Is that an yes besides regaining the features of HDVoice, volte and Wifi Calling?
Thanks
Click to expand...
Click to collapse
You asked about sim swapping for traveling. The BYOD firmware makes for easier sim swapping. It's designed to populate the carrier settings when you insert a sim instead of needing to wipe your device.
As for ATT features, I believe those firmware are for the U firmware, so yes, you'd regain those features, but you'd get the ATT bloat. I don't mind the bloat personally. I just remove the junk I don't need.
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Frostyb said:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Click to expand...
Click to collapse
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
BloodyFruitDestroyer said:
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
Click to expand...
Click to collapse
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Frostyb said:
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Click to expand...
Click to collapse
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc
whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.
BloodyFruitDestroyer said:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
Click to expand...
Click to collapse
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Frostyb said:
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Click to expand...
Click to collapse
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
BloodyFruitDestroyer said:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
Click to expand...
Click to collapse
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Frostyb said:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Click to expand...
Click to collapse
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
BloodyFruitDestroyer said:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
Click to expand...
Click to collapse
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Frostyb said:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Click to expand...
Click to collapse
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
BloodyFruitDestroyer said:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
Click to expand...
Click to collapse
So the first image is of the current firmware that successfully flashed to my device via Odin.
The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.
What were your exact model and region again? Probably won't matter, please wait a minute
BloodyFruitDestroyer said:
What were your exact model and region again?
Click to expand...
Click to collapse
BloodyFruitDestroyer said:
What were your exact model and region again? Probably won't matter, please wait a minute
Click to expand...
Click to collapse
SM-G996B
Region is Ireland (CSC is MET)
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Hi there, I can help you out! I have some experience with Samsung.
So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.
It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Edit: It seems like someone more experienced appeared while I was writing this! Sweet!
BloodyFruitDestroyer said:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.
BloodyFruitDestroyer said:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Click to expand...
Click to collapse
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Frostyb said:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Click to expand...
Click to collapse
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.