Flashing from PK1 To G930U(PL2) - T-Mobile Samsung Galaxy S7 Questions & Answers

Hello! I just want to make sure before potentially bricking my device. I want to switch my T-Mobile S7's firmware to the latest U version, but I saw in another post that you might potentially brick your phone by doing this since the bootloader are on different version?
I don't care about wifi-calling etc, as I am planning to switch to a different carrier. I just have three questions I am not 100% sure yet, could someone shine some lights on these? Thanks
1) Would this trip knox?
2) Is it just as simple as flashing all the files(Including Bootloader) except for HOME_CSC?
3) Would to process be any different if I were flashing to Version version instead?

sup bro you should be fine i have been using the 930U version for sometime and its stable...
The last 4 characters of that version says 4APL2- the 4 represent the bootloader version
which is the latest, it will flash and will not trip knox as long as you follow the instructions accordingly. If you want to go back to 930T the bootloader must be version 4 or higher. GOOD LUCK

Related

Baseband/modem update files

Hey all, trying to update my brother in laws firmware on his s3. I'm familiar with all the different firmware versions on the sprint sgs4, but am completely lost when it comes to the verizon s3 firmware versions. Can someone point me in the right direction to the most current firmware? I've found this thread, but it appears the last time it was edited was back in June and I'm pretty sure there has been updates for you guys since. Also, Is there any issues I should be aware of? For example, with the new sprint firmware, we are advised not to take the current bootloader both because of knox security and the inability to downgrade bootloaders, so some devs have made available tar files to update modem only via odin. Any advice you guys may have would be great.
exeleon said:
Hey all, trying to update my brother in laws firmware on his s3. I'm familiar with all the different firmware versions on the sprint sgs4, but am completely lost when it comes to the verizon s3 firmware versions. Can someone point me in the right direction to the most current firmware? I've found this thread, but it appears the last time it was edited was back in June and I'm pretty sure there has been updates for you guys since. Also, Is there any issues I should be aware of? For example, with the new sprint firmware, we are advised not to take the current bootloader both because of knox security and the inability to downgrade bootloaders, so some devs have made available tar files to update modem only via odin. Any advice you guys may have would be great.
Click to expand...
Click to collapse
We are still officially on the mf1 firmware and that's the 4.1.2 update. No need to worry about the knox bootloader because it isn't 4.3, just flash it in recovery.
Sent from my SCH-I535 using Tapatalk 2

New Update - QH2

According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.

Delete .bin files from older firmware to downgrade to an older bootloader version?

Id like to downgrade my S7 from nougat to marshmallow. My current lowest factory reset option is nougat on bootloader version 3. Id like to downgrade to a downloaded stock firmware that uses version 1 of the bootloader.
my device is currently rooted and carrier unlocked
ive made a full backup of the nougat system, before ive done anything to it other than the rooting.
ive been reading around that some people were able to bypass the downgrade bootloader lock error in odin by first going into their desired downgraded firmware tar files and deleting any file that ends in .bin , and then successfully been able to flash the older firmware. what I want to know is if i decide to try this, and it still doesnt work in odin, or something still doesnt work properly - am i still able to fully restore from that backup ive just made? has anyone done this without issues? i hate the look and feel of nougat and oreo looks and feels the exact same...
i did make another thread about downgrading, but i didnt know nearly as much at the time. Been told downgrading is impossible and thats true, officially speaking. Id just like to know if anyone has been successful with this workaround.
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Beanvee7 said:
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Click to expand...
Click to collapse
model is sm-g930w8 but yes OEM unlocking is on, and so is usb debugging just to be on the safe side. It is running the very first version of nougat right now, 7.0. But the security patch is from feb 2018. Ive read that the bootloader itself is unlocked on this version of the phone though, its just that downgrade protection in the software that could get in the way, if what i read was correct? in the same place was where i read that deleting those bin files from the firmware i want to install would be a good workaround, it would make the bootloader not check it at all if i read it correctly.
i havent tried anything yet, ive been doing my research first to stay on the safe side. it might work without issues, but I want to be prepared for if issues do arise, what the correct next step should be to keep the device itself not bricked
Yea not 100% sure for the G930W8, it's the same SoC as the G930F but the firmware restrictions could be different since it's the Canada specific version
so, i decided to brave it and try it, since to read around you find alot of conflicting information... i was suspecting that odin would fail shortly after starting at sboot.bin if it was the bootloader thats the issue. but it didnt. it failed the very next step after that at param.bin.
anyone happen to know what param.bin means?
What files are you trying to flash? I have had the same problem, even though the bootloader is unlocked the device has efuses that prevent downgrade to older binary. I was using U2 binary and only managed to downgrade to nougat u2 binary version. Even when I skipped bootloader files, marshmallow would still give an error that system.img is version 0 where as device is v1

[HElP NEEDED] - SM-G903T - Advice on how to bring back life to my phone

Hey All,
Like many unfortunate souls out there I updated my device to Oreo via T-Mobile OTA and instantly my device slowed down with odd behavior. Given I have G930T model which cannot be rooted (be very honest I am confused between the models and why G930T can't be rooted), I am desperate to make this posting hoping someone can help me a bit.
My simple goals:
- Get stock Android on my device and have it running faster, all features working and extend my battery life.
- Keep my phone/app settings
- Not have T-Mobile bloatware.
My concerns:
- Will I lose features such as camera not working in a text message app, WiFi calling, etc.
- Is it better to go back to Nougat or install Oreo? (this is once I figure out all the jargon and many guides)
I refuse to upgrade to a newer device because of stupid software updates and I love this phone too much. This phone is causing me issues professionally such as speaker turning off in the middle of the call, call volume is too low, outgoing text messages failing, sluggish performance, freezing, and horrible battery life. Beside for battery issue, everything else started to happen after software updates.
My Device/Setup:
- Samsung Galaxy S7 - T-Mobile - G903T
- Current stock version R16NW.G930TUVU4CRF1
- macOS with Samsung USB cable
Before there is an outcry on why I didn't search for and find a previous thread that can easily explain, I did and found this amazing write up (it took me a while to even find this):
https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3846694
However, there are a few things that I use daily such as visual voicemail and WiFi calling in an office where I had a bad signal. I really hope this post gets me some specific pointers and not get removed from the site for posting this. I am a beginner so please be gentle.
Thanks!
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues https://www.reddit.com/r/Android/comments/5xzbo3/qualcomm_s7_engineering_boot_images_leaked_root/
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Beanvee7 said:
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues ...
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide ...
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Click to expand...
Click to collapse
Thanks for such a detail accurate answer I was looking for. Sorry for the late reply as work has been crazy. I will go through to install Samsung stock firmware and see if it improves performance and battery life. Will try to get G930U and see if I can go without WiFi calling. First, I am trying to do a backup using SmartSwitch (will dig around for more backup option if this one doesn't work). Will update here once I am finished and any lesson learned to help someone else in the future.

SM-G930A 6.0.1 unlocked running on T-Mobile flash to SM-G930T 8.0?

Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
leprkon said:
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
Click to expand...
Click to collapse
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
cooltt said:
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
Click to expand...
Click to collapse
Thanks for the reply! I appreciate the direction. You are right, US phones are a pain. And yes, the phone was originally an AT&T phone, but was unlocked.
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
cooltt said:
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Click to expand...
Click to collapse
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
leprkon said:
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
Click to expand...
Click to collapse
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Beanvee7 said:
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Click to expand...
Click to collapse
Thanks for the reply! I had tried flashing the 8.0 G930T variant last night with the latest version of Odin and the PrinceComsy version and got a Model Mismatch error. I read that the modified Odin3 v3.13.1_3B_PatcheD would let me flash the firmware and ignore the Model Mismatch error. However, I didn't go through with it because I was not sure if I would brick my phone and instead erred on the side of caution and made my post here. Would I be safe to flash the files from SM-G930T_1_20180625111401_xf3965l42p_fac onto my current device?
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Thanks for the assist! Everything worked like a charm!
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Great glad it all worked out
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Thanks
[email protected] said:
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Ok, so flash any unbranded Stock Rom for your device using this version of Odin which has been specifically modified to flash US devices. https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 PatcheD.zip is the file you want to download.
Then when you have checked the phone is working ok on undrnaded firmware you can go ahead and root the device using this method which is again for US Qualcomm devices. https://www.****************/2018/0...on-galaxy-s7-and-s7-edge-on-android-8-0-oreo/
Take you time and read instructions.
Click to expand...
Click to collapse
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
[email protected] said:
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
Click to expand...
Click to collapse
If I understand it correctly there is no unbranded firmware for the US, its all network specific but you can flash unbranded UK firmware and it will work fine, UK BTU is the one you want from sammobile.
Load into the modified version of Odin and flash.
This is what I found, and downloading.
[email protected] said:
This is what I found, and downloading.
Click to expand...
Click to collapse
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
cooltt said:
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
Click to expand...
Click to collapse
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
[email protected] said:
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
Click to expand...
Click to collapse
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
cooltt said:
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
Click to expand...
Click to collapse
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
[email protected] said:
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
Click to expand...
Click to collapse
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
cooltt said:
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
Click to expand...
Click to collapse
Thank you so much. You guys are amazingly patient, and informative. Thank you for educating me, and helping me achieve my goal.
I have tried a few times but can not flash the files. I have attached screenshots, and followed the instructions here. Do you see anything I should be doing differently?
I initially thought the code came as one tar file, which I could flash, but it was a zip file, which I had to unpack.

Categories

Resources