I was trying to root my Verizon Galaxy S7 and sucessfuly did it using the SuperSU root.bat i found in:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
However when i noticed how performance was very affected by this it was an immediate regret, so i tried 3 different versions of Odin (v3.14.1, v3.12, and v3.12 (PrinceComsy)) to use the stock firmware provided in that thread to flash it, however in my las attempt (PrinceComsy) it failed and when i tried to go back (in shame and having failed) the phone wont boot and it says "Software Update Failed, Your device didn't update sucessfuly. Use the Version Software Update Assistant on a computer to repair your device and complete the update."
Edit: 7:16PM Got it to boot, no longer bricked but i still need to either get it back to stock or fix the horrible performance
Download stock firmware either from the samfirm tool, sammobile, or updato. Flash with Odin, make sure you select all four files (AP, CP, CSC, BP)
Most root methods for the USA models involve using an engineering bootloader, which comes with performance and battery impacts you can't get around because it's due to the bootloader. It's either root + performance impact, or stock no root.
Does anyone have a link to the fix/debloat scripts? The links on the thread no longer work. Thx Btw ^
Related
Hello,
I'm in a bit of a confusing situation. When nougat released for s6 last year i think, i flashed it through odin and after that samsung launched/introduced secure folder for nougat and i tried it. It wasn't working because my device status wasn't "official" anymore.
So now I'm thinking again to flash uk firmware (from sammobile) for galaxy s7 sm-g930f(not rooted & device status is OFFICIAL) via odin would this problem happen again if i flash it?
Thanks if anyone's interested to answer my query..!
If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.
Chances are if your device was Custom, then you have rooted it at some point / flashed custom, in that case KNOX will be tripped (0x1) and if secure folder relies on KNOX being valid (0x0) as a lot of Samsung stock apps do, it will not work any longer
Beanvee7 said:
If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.
Click to expand...
Click to collapse
I've always downloaded firmwares from sammobile.
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.
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
TheofficialJonerockit said:
So I have a Samsung j260AZ and it got stuck in firmware binary and will not accept any of the original firmware because of the Bit numbers below
B=5 K=5 S=5 <-- this was not the original numbers
So I Am trying to figure out how I can get the phone to accept the firmware.
I've tried 3 different odins (Comsy, 13.3, patched)
I have tried numerous ways to flash this phone and it just wont get back to normal.
HELL I even tried flashing the wrong firmware just to get firmware binary to leave and any kind of launcher to boot up but it wont accept any kind of firmware ...and I am not trying to go any higher in bit numbers. I tried to flash a unlocked version of bit security but that doesn't work either.
Anyways if anyone has any options I can do please let me know.
Click to expand...
Click to collapse
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Let me guess, you updated your device and now you want to go back to what you had?
Or, your device needed to have the stock firmware reflashed to repair the device to normal function and now you are trying to flash the stock firmware to repair the device but the firmware you are flashing is older than the firmware that was already on the device?
If either of these is the case for you, it is failing because you can't downgrade from a higher binary down to a lower binary, you can only keep the binary you have or flash up to the next binary, but once you go up to that next binary, once again, you can't go back to the binary that you had before.
In other words, if the firmware that was already on your device was a binary 6 or higher firmware, you can't flash the binary 5 firmware, you could flash a binary 7 over the binary 6, but once you had binary 7 installed, you could never go back to binary 6 or binary 5.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I read also
but I was just hoping that it wasn't true or that their was some way to intercept or clone its coding but install the real thing.
Well I guess I am gonna make this phone my test phone and see how badly I can screw it up by installing stuff and test software on it. LoL until it wont work anymore.
Has anyone tried Linux/Heimdall vs Windows/ODIN? I am just curious to try it myself as I gave up on Windows years ago. It also seems to me that since Android is a Google-based form of Linux, that a Linux user may have more success.. I will be attempting it myself as I cannot get my phone to update to Android Pie, or anything after the June 2019 version of Oreo and the security updates. Contacting Cricket nor Samsung is of any use as they are both reluctant to help anyone with any issue that doesn't include buying something (i.e. new warranty, new phone, new service upgrade, ect.), even though my phones are always purchased, not leased. Anyway.... I will be either flashing this old and busted thing or destroying it completely. Wish me luck.
Was trying to flash to combination rom so I can bypass frp then flash back to stock. Accidentally flashed to latest firmware G970U1UES4DTG1 which is actually G970U1 firmware.
Is it possible to flash to an earlier firmware? I was getting " please get the approval to use factory binary( pit) " then for some reason flashed to higher firmware without realizing it like an idiot.
I tried to load the combination files but I keep getting Fused 4 > binary 2. the firmware currently loaded is newer than the combination file so it wont let me go to it.
Will there be binary 4 combination files coming out? is there anyway I can unlock the bootloader without getting into the phone? or any way to enable USB debugging with my computer? Any help is appreciated.
Also doesn't help its AT&T and apparently they dont release their firmware files publicly
Hello
I've been reading forums and downloading files for days. Many of the links in the posts no longer work. Posts are 5 years and older. There are no new ones. At least not one that actually works. Downgrade I mean. That's why I wrote this question and I'm asking for help - how to really downgrade my Galaxy S6 G920F.
Thanks for the help.
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
I'm laughing because you write quite a lot in three days. Of course, this method does not work.
Is there anyone willing to help?
Totesnochill said:
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
Click to expand...
Click to collapse
That is assuming they have TWRP.
Also, the part you mention about "boot into download mode, connect to PC then boot to TWRP via fastboot" is not correct because Samsung is not compatible with fastboot, adb works but fastboot does not. Some Samsung devices technically have a "fastboot mode" but it isn't functional, it doesn't respond to fastboot commands, it's basically useless.
Also, you can't flash a firmware that has a lower binary than the currently installed firmware so if the binary of the downgraded firmware is lower than the binary of the currently installed firmware, the downgraded firmware can't be flashed.
Samsung is making it harder and harder to downgrade their devices.
OK. I'm afraid I'm missing the point of what's being said.
I know it is possible and there are also posts about it, but they are old, the links in them do not work. I'm asking for an expert who knows how to do this, philosophizing about what it would be like if it somehow doesn't really help me and I'm not interested either
I'm only interested in a positive thought, help and not brainstorming, if you understand me?
No offense