Related
So I used the disconnect internet trick and got Tango to install on my phone. Problem is, it stopped with the 3 updates and did not install (or find) the Samsung one that I know was supposed to be installed (for firmware), so my firmware is now 2103.11.10.1 instead of what it is supposed to be.
Does anyone know a way to force the OEM firmware to be sent to Zune. The internet disconnect trick isn't work now, so I'm stuck. Also, my backups aren't showing up, even though during the update process it said it was creating a backup (for all the OS updates it installed all the way up to 8773).
If there is no way to get the OEM firmware to be pushed, does anyone know how to get the Focus Flash to stock? I know I have a backup on my computer, but Zune isn't recognizing it (I had forced 8107 on my phone, and Zune made a backup of that ROM).
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
b4malevolent said:
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
Click to expand...
Click to collapse
Someone at wpcentral posted this for their Focus Flash:
Look like Firmware Update, Radio Software, BootLoader
Firmware Revision 2103.12.05.04
Hardware Revision Number 23.1.0.8
Radio Software Version: 2103.12.5.4
Radio Hardware Version: 0.0.0.6
BootLoader Version 6.5.17.0
Chip SOC Version 0.74.21.1
So there must be one out there (plus, everyone else has been receiving firmware updates, like Nokia, so I can't see Samsung not making one).
Since you used the debrand trick to update to 8107, you'll most likely have to reset your phone to get the Samsung update. I did the same thing & then did the cab send method to update to 8773. Didn't have any problems. Kept trying to get the Samsung update via the disconnect trick. No luck. As soon as I reset my phone, it popped right up. I'm installing it now. Good luck.
Steve
As it looks like theres no way using a Developer unlocked Mobile to run Apps or now that Samsung have blocked the Interop Unlock - even when you restore.
Is it possible to download a Previous update and "update" the phone that way. An update that doesnt have the block and so it doesnt affect the data on the phone?
Thanks in Advance.
"Updating" to an older version is not possible, no. It might be possible to spoof the current version to an old one, if the phone is interop-unlocked, and then "upgrade" to a firmware release that's actually older than your current one... but even that might not actually work, if the updater checks the checksums of the "old" files. It wouldn't work with OS updates for sure; those contain differential (rather than canonical) patches.
Installing an old, stock ROM with the old firmware does work. However, while this is possible with Samsung gen1 phones, I don't believe anybody has found a way to do it with gen2 phones yet.
Finally, restoring a phone backup (as made by Zune when updating, or as made using the Easy Backup tool which just spoofs the update process), definitely does restore both your unlocks and your ability to unlock - that is, it restores the registry (where the unlocks are controlled from) and it restores the firmware (where the ability to unlock is implemented). If this didn't work for you, it's due to one of two things:
A) Your backup (more properly called a "restore point") was created at a time when your phone already had relocked and lost the ability to unlock.
A.1) You can use an older restore point, if you kept them (which I strongly recommend); just move it back to %LOCALAPPDATA%\Microsoft\Windows Phone Update.
A.2) Before you ask, no, you can't use somebody else's restore point; they have device-specific encryption that we haven't broken yet.
B) Your restore worked, but trying to interop-unlock again failed because you updated your Diagnostics app from the Marketplace.
B.1) You can undo this by first uninstalling Diagnostics from the app list, then re-installing it using the phone dialer.
The other option is to use the stock flash tool and just update to Mango from stock.
I have the files for the Samsung Focus v1.3
I can upload them, but if you use it on another device, or on v1.4 it might brick your phone.
Just say if wanted.
I have used it a number of times, because of screwing up my phone and it not being able to boot up, even after formatting.
You will just need to put the phone into download mode, and it takes about two minutes.
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
Hi all,
I've given this phone to my parents but with every Android update it keeps getting slower and slower.
I've tried removing as much bloatware as possible, also only basic apps are installed. But the phone is sluggish, lagging and barely usable.
When receiving a call, the screen goes black for a couple of seconds, starts ringing and after other 4-5 seconds it shows the name of the person calling.
Such a shame though, as it used to be a nice compact snappy experience for basic users.
Was thinking to buy another phone, but wanted to ask first if it is possible to downgrade. I've red that downgrading is blocked by Odin due to baseband firmware (is this true?).
Please, if anyone has a solution, let me know.
Also, if it is not possible to downgrade to stock 7.0, is there way to install a custom (nearly stock) Rom based on 7.0 firmware.
Is it possible to Root and TWRP on the latest 9.0?
Thanks in advance
P.S.: I hate this from Samsung, updating phones to make them slower (also no way to disable update notification)... no more Samsung for me I guess!
I tried to install android 7 and 8. It failed. Versions 9.0 (update 09.2020) were successful. Need root.