the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
LodeUnknown said:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
Click to expand...
Click to collapse
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
*Detection* said:
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
Click to expand...
Click to collapse
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
LodeUnknown said:
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
Click to expand...
Click to collapse
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
*Detection* said:
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
Click to expand...
Click to collapse
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
LodeUnknown said:
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
Click to expand...
Click to collapse
If your phone is a US model S7 (snapdragon) you cannot flash custom ROMs
My instructions are for ODIN (version 3.12.7 for Nougat)
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
LodeUnknown said:
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
Click to expand...
Click to collapse
You cannot flash a custom ROM to a snapdragon phone using any method, it has a locked bootloader
ODIN is for stock ROMs only (and TWRP recovery which you cannot use on snapdragon either)
You can use ODIN on any S7 for stock ROMs
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
LodeUnknown said:
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
Click to expand...
Click to collapse
Yes, only Exynos has an unlocked bootloader (See the snapdragon vs exynos custom ROM dev forums)
Yes you could still use a US carrier as long as the phone is SIM unlocked (carphone warehouse phones are all unlocked), I have no idea of the limitations / implications, but some people here already do that, and the G930W8 (Canada) is Exynos
No idea about warranty, but if you bought it from say the UK and had it shipped, you'd have to discuss with Samsung if they would accept it into a US service centre or if you'd have to ship it back to the UK, no idea about that, no doubt there are places in the US that you could buy a Exynos from
Hit Samsung up on twitter and ask them
Related
I recently had my Orange Galaxy S2 i9100P unlocked by the local phone shop.
The unlocking worked fine, but I have now noticed that it has been rooted too.
It has a superuser app installed, which he said he didn't realise it had installed.
Not sure that I want it to be rooted when I sell it as it might put off potential buyers.
So I called the shop and asked if it has to be rooted to unlock it and he said that it does.
He said that the other way to unlocked it is to use a code but that system is currently down (the website that gives out codes) and it would cost £26 instead of the £10 that I paid to have it unlocked using root. I asked him if I could unroot it by flashing with the standard Orange firmware (using Keis) and he said yes I could and that would unroot it. When asked that if this would then lock it again he said that no it shouldn't, but he didn't seem too sure about what he was saying.
So some specific questions:-
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
MrModbus said:
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
Click to expand...
Click to collapse
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Just trying to be helpful.
Tiash420 said:
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
Click to expand...
Click to collapse
Ah OK.
Tiash420 said:
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
Click to expand...
Click to collapse
How do you mean? Are you saying that there is another appliocation that is running that is performing the unlock and that needs root to do its stuff?
Tiash420 said:
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
Click to expand...
Click to collapse
That is an option. But Last time I looked (a few years back) I couldn't find any i9100P specific unbranded firmware. There was i9100 firmware, but that didn't support the i9100P NFC chip.
Tiash420 said:
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Click to expand...
Click to collapse
My app is just called "superuser" and is at v3.1.3. I suppse that I could try the temp unroot and see what happens.
Yes, I'm saying there might be some app keeping the unlock alive. Cause that's how I unlocked my iPhone 4, quite a lot of times. :3
And you should search again for unofficial rom.
And also try the temporary unroot button.
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
MrModbus said:
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
Click to expand...
Click to collapse
Flash a custom recovery through Odin and then backup your current Rom. And then find flashable-zip official firmwares and then flash and see results. If anything goes wrong revert back to the old firmware.
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
MrModbus said:
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
Click to expand...
Click to collapse
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
My current details are:-
PDA: I9100PXXLSS
PHONE: I9100PBVLS2
CSC: I9100PPORALS6
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
MrModbus said:
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
Click to expand...
Click to collapse
Vodafone firmware is Vodafone branded, so i won't use it as its probably highly customized by vodafone. The France version should not have a branding. You can check your modem version in Android: "Settings-->about Phone". If you get you right, you want to sell a branded phone as unbranded and potentially next owner may not know. sounds not very good
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
MrModbus said:
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
Click to expand...
Click to collapse
I suppose its hard to say, because no one but the shop owner exactly knows what method was used to unlock the phone. Thats the reason why there is no guarantee that the unlock survives a firmware flash. If you just want to get rid of unwanted apps, you can use "Titanium Backup" to uninstall whatever you want. I would never use a non rooted phone again, so may be the new owner is happy that its already rooted
LS.xD said:
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Click to expand...
Click to collapse
Yeah this works, if you really wanna get rid off the orange BS. Just uninstall all the BS with Titanium Backup and then simply unroot. :3 And the device fresh and unlocked and not rooted without the BS. :3 And everybody's happy, right?
Solved
Used patched version of odin to flash the samsung unlocked firmware (G955U1) from the firmware servers. No more Verizon Splashscreen and spay/bixby work fine
I've been using android devices all my life and have rooted every single device I've owned in the past (probably 4-5 devices). I know the risks and I know how to flash my device and such but I got my S8+ from verizon about 3 months ago before the international unlocked version was released. I only bought it from verizon because their phones are carrier unlocked by default. I use google's project fi.
Verizon is somewhat good with bloatware I can disable or uninstall all of their applications and I haven't found my device to be slowed or burdened by their addons so I never felt the need to root my device which was nice but I got the Bixby update today and I cannot use it unless I update my system software. Tried to update it and it attempts to connect via verizon and ultimately fails saying it cannot connect to the update server. I expected this -- I think it's due to me not using verizon and not having the phone registered with their service.
Want to use Bixby and also would like to flash a stock updated (latest stock version) ROM as I don't care for any new features or custom ROMs because this phone is perfect as it is so far.
Phone software/model specs:
model is SAMSUNG-SM-G955U
kernel version 4.4.16 march 11th, 2017
sev 8.1
android 7.0
aspv march 1st, 2017
knox 2.8
If I follow my usual rooting route properly is it safe to root my phone? Asking because S8+ root is relatively new. I won't ever sell the phone so I don't care if the warranty goes void or something like that.
Essentially looking to turn my Verizon version into a completely US unlocked phone with a stock clean ROM. Is there any possible way I can perform this and still be able to use Samsung Pay? Not a necessity but I do enjoy it.
No root is out
joshclouds said:
No root is out
Click to expand...
Click to collapse
Alright, If I flash the newest version of the samsung firmware onto my device (force update it) will SPay and Bixby still work? And my Knox will be fine?
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
joshclouds said:
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
Click to expand...
Click to collapse
I have the S8+ G955U. It's verzion and has the ****ty verzion startup screen and sound it's just annoying. I really want to use Bixby voice as I just got the update from samsung but it says I have to have the newest samsung firmware to use it. I cannot update my phone normally because I don't use verizon I use google fi. So I want to try to flash the standard US carrier unlocked firmware onto my phone from sammobile (not the verizon variant). Is this safe?
the firmware list I'm choosing from: (spaces added so because account is not old enough to post links)
www . sammobile . com/firmwares/galaxy-s8/SM-G955U/
Which one on that list should I use? Obviously I'd choose the first one which is the Verizon firmware but I really would like to just have pure Samsung unlocked stock firmware so I don't have verizon apps & the verizon startup screen.
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
joshclouds said:
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
Click to expand...
Click to collapse
If you could get that thread for me that'd be perfect. Thanks for the help. Really wishing I waited the extra 3 weeks and bought the unlocked version instead.
Updating because I was able to solve it myself. I used a patched version of Odin to bypass the model mismatch error and flashed a new system image and csc (G955U1 model image) that wasn't for my G955U Verizon model.
Bixby works, KNOX is fine, SPay is solid. Verizon splash screen is gone and the phone (from the settings point of view) has no carrier and is fully unlocked and void of bloatware.
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.
Hey all,
I bought a new OnePlus 8 5g T-mobile phone for my wife. She's on the RedPocket annual GMSA/ATT plan. I've stopped the auto OO11 update and I've gone into *#*#4636#*#* and selected "LTE Only" for the connection type (like I did with my old OP6) but it doesn't stick after a reboot.
My real question is:
Since 4G LTE seems to work properly with the T-Mobile stock OS, what are the reasons for converting over to the international version?
Will 4G still work after I update it to OO11.x? I don't mind it having the T-Mobile boot or bloat. I have mostly disabled/uninstalled the apps she doesn't need.
Thanks!!!
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware, and even if you don't really "care" about it, every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
FoxyDrew said:
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware. And even if you don't really "care" every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
Click to expand...
Click to collapse
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
chuddler said:
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
Click to expand...
Click to collapse
np man, that guide is very complicated for no reason, converting to global is rather simple, but it's a 3 step process. This all assumes you can unlock your bootloader though.
1.) MSM back to stock T-Mobile Android 10 firmware. Specifically this one. This will re-lock your BL if its unlocked.
2.) Let that boot up, go into settings to enable OEM unlocking, and then unlock the bootloader.
3.) Once the bootloader is unlocked, flash THIS global Android 10 ROM via fastboot. There's a flash-all.bat file to make it simple. Once you've finished this step your essentially done, and on global firmware, you just need to...
4.) Boot the phone up and take the OTA update in settings to Android 11. There will be 2 OTAs to take, one FULL OTA to Android 11, than an incremental one to the latest Android 11 build
Optionally afterwards you can re-lock your bootloader, or keep it unlocked and root if that's what you/she wants.
If you're not familiar with MSM tool, and the drivers it needs, check out this thread.
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.