Related
*READ FIRST*
This thread is now completely dedicated to the aspect of Carrier Switching on the Snapdragon model of the Galaxy S8/S8+, the current root progress can be seen here:
Current ROOT Progress for G950U/G955U Snapdragon
Please Note that if your device is network locked this WILL NOT unlock it for use on other carriers, however it will allow the switching of carriers and carrier specific features on network unlocked devices just by changing sim cards, the device will reboot and your done. As for those with a network locked device this thread still applies to you, if you are interested in a bloat free experience(that is faster and smoother than stock touchwiz), on your Galaxy S8/S8+
Let's Begin!
Download the firmware for the unlocked S8/S8+ here:
G950U1UE1AQDC_XAA
Download the Prince Cosmy version of Odin here:
Odin_3.12.3_Modified
Enable developer options on your device:
Settings----->About Phone----->Click Build Number 7 times
Enable USB Debugging:
Settings----->Developer Options-----USB Debugging
Put your device into download mode: Volume Down + Bixby + Power
(accept the warning and connect your device to your computer)
Take the G950U1.zip you downloaded in step 1 and extract it, then place the BL,AP,CP,and CSC files into their corresponding places within Odin and press start
Once finished the device will boot back up and you will be free to disconnect it from your computer
You now have the unlocked, bloat free, firmware on your S8/S8+
CONTRIBUTORS
@Maltego for hosting files
@mweinbach for originally getting the unlocked firmware and for posting a tutorial on flashing it
@Acoustichayes for creating a dedicated root thread
Delete
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
EDIT: installing now, needed the latest odin
Akumai said:
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=529152257862722617
Here is Odin 3.12.3
Persianhawkes said:
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is for an s8....Not plus. Be careful.
suzook said:
This is for an s8....Not plus. Be careful.
Click to expand...
Click to collapse
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
I can't wait to give this a run this weekend
Persianhawkes said:
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
suzook said:
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
Click to expand...
Click to collapse
As of right now there is no way to overwrite carrier info, we are working on it though. That reserved comment is going to be where i put all that is known, been tried, etc with carrier switching just a little busy right now
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
This is compatible with your device all US versions of the S8 and S8+ have the same model number. I have your stock firmware i just need to upload it to androidfilehost
If anyone feels like it joining I have created an IRC room we can all chat in and brainstorm things. It's #sgs8 on irc.freenode.net. Hasn't had many users since I created it but I lurk in there when I'm at home. I'd love some company. Let's get this thing rooted so we can shut all the haters up!
Glad to see more devs working on this
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
STF_TimelessGoD said:
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Click to expand...
Click to collapse
Contact @ashyx he's very good with Samsung and TWRP
force70 said:
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
Click to expand...
Click to collapse
it merely mentioned that it allows "the unlocking of the bootloader"
Akumai said:
it merely mentioned that it allows "the unlocking of the bootloader"
Click to expand...
Click to collapse
Thats not what that means is what im trying to say lol. That option on sammy phones has never really done much other than allow flashing in odin
What is of note is that i dont have that on my S8 which is new that option is always there.
S8 plus stuck in recovery with following message:
"Support SINGLE-SKU
Supported API: 3
dm-verity error
failed code : 0x02"
Is there a fix for this yet?
cheers
Matt
...? Elaborate?
What did you flash that lead to this?
dm-verity is what you usually get when you flash something incompatible, or when some insecure fw image is rejected.
Reflash the firmware using ODIN, and the latest FW package for your model / region. (in the AP box)
If you end up with DRK error afterwards, then you're boned. You need Samsung to help you out.
TL;DR: Careful when flashing stuff next time, always verify what you're flashing is for your device's model.
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Comarrid92 said:
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Click to expand...
Click to collapse
Took it back to Samsung and had to pay them £290 to fit a brand new board.
Out of warranty coz i rooted it.
only way out.
Gutted.
Matt
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
CoreyHUN said:
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
Click to expand...
Click to collapse
Wrong.
I did flash it, and it was rooted for about a week, but for some reason, i was bored, just potching around with my phone and decided to uncheck 'allow OEM' unlock, but forgot to re-check it before i restarted the phone...too late though...as Samsungs awesome security basically said...NO WAY...he's tinkering about with root triggered the efuse on the board and the ONLY way to fix that was a brand new board.
I'm not a newbie (hence my 371 thanks meter) when it comes to rooting phones....i've been on here since 2011 and rooted stacks of phones....HTC HD2, HTC Sensation, Desire HD, LG G2, LG G3, LG G4, HTC One-X, HTC One-x Plus, HTC Desire eye and a LOT more...Just made a silly mistake a week AFTER I rooted the phone.
I gotta be hnonest, I thought i'd miss root, but can hand on heart say....i'm not missing it one single bit.
My lovely Samsung still has 20 months warranty and i'm keeping it that way by not rooting.
LOVE my S8 Plus and to be honest, with Knox etc....I'd advise everyone not to root this EXPENSIVE beast of a phone!:good:
Matt
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
CoreyHUN said:
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
Click to expand...
Click to collapse
WRONG!
Hardware problems -> YES
Problems due to wrong use of your phone (i.e. root and phone won't do anything anymore): NO
And I do agree with Samsung: if you temper with the FW, and your phone doesn't do anything anymore -> IT'S YOUR OWN F...... FAULT ! ! !
Here's the nice big fat bill I got for repairing it.
Eeeuuurrreekkaaaaaa!
So after being presented with this error due to my own stupidity (trying to diagnose why MTP wasn't working on windows 10 and disabling Developer Options and not re-enabling OEM Unlock), I managed to get around it quite simply although at the cost of my data... BUT at least its not bricked.
The solution is simple;
1. Use SamFirm and download the latest firmware
2. Using Odin Load all the firmware options (BL, AP, CP and CSC) and in the options tab select all the checkboxes except "Flash Lock" and "T-Flash".
3. Press start and hold your breath.
Upon completion the phone may not reboot automatically so you will have to manually reboot using the Bixby, Volume Down and Power Buttons. Once rebooted you'll see it erasing the remaining userdata and finalising the re-partitioning process but a few minutes later you'll see the samsung logo and the welcome screen.
I hope this helps someone. Good Luck Peeps
I have the same problem guys but my odin isn't working the ID thing specifically the computer isn't recognising the phone.
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.
Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?
Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.
Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.
Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked
It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way
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.