Database Info

Help with downgrade?

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.

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.

[STOCK ROM] Stock Android 10 ROM

Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Will this work on the reteu devices (being from a different channel)?

FelixNevorsky said:
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS

takoa said:
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
Click to expand...
Click to collapse
My guess is that QSB is for Android 10 (it was called Q for some time). And PSB is 9.0 (aka Pie)

I mean the letters sbs and sb. thanks

takoa said:
I mean the letters sbs and sb. thanks
Click to expand...
Click to collapse
ummmm......Stable build.....maybe

Was Anyone able to root this version?

Wintershade said:
Will this work on the reteu devices (being from a different channel)?
Click to expand...
Click to collapse
Yes, it should. It's been already tested here on the forum with pretty good results. So yeah, I'd say it will. But if you're not in a hurry, maybe you can wait for a bit longer to get the official build for RETEU.

Channel Signification Firmware
Is a list exist for channel signification for https://mirrors.lolinet.com/firmware/moto/troika/official/
or a way to knows the signication ?
RETEU = Europe
RETUS = USA
RETCA = Canada
RETRU = ???
etc ...
Compatibility Variant / Firmware
Is exists a thumb rule for compatibility firmwares in between XT2013-1, XT2013-2, XT2013-3, XT2013-4.
Actually, I have a XT2013-4 device and I would like flash another firmware variant.
Thanks

RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.

arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards

arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks

Gypsy said:
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Click to expand...
Click to collapse
that is very good to know. thank you!

Gypsy said:
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
Click to expand...
Click to collapse
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time.. ?
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know.. ?
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?

zaqiezsbelelzsinski said:
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time..
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know..
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
Click to expand...
Click to collapse
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.

arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Click to expand...
Click to collapse
arsradu said:
@zaqiezsbelelzsinski
I can't and more to @arsradu's answers, but just in case you decide to unlock your bootloader for whatever reason, it voids your warranty., there's the link:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Good luck, if you have any difficulty, please ask!
Click to expand...
Click to collapse
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.[/QUOTE]

One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.

arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
Click to expand...
Click to collapse
Thank you for the feedback
Yes, I understand about the risk. Many years ago I always flashing my device (Nexus 5) while it was release update, but that was then ?. Now, Maybe I will be waiting till my device get update to android 10.
The problem is, there is no valid information from Motorola especially TROIKA XT2013-4 about update to android 10.
Thanks for your advice about flashing ROM..
Cheers ???

You could try to contact your local Motorola Support team. I don't think they will give you an actual ETA. But maybe they can tell you wether or not there will be an update to Android 10 for this particular model (XT2013-4). I think there should be. I see no reason why this particular model would be an exception. But you could double check that. Just in case.
Logic would suggest that there should be one soon. XT2013-1 and XT2013-2 already got the update. So it would make sense for the "-4" model to follow.
Sent from my motorola one action using Tapatalk

arsradu said:
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
Click to expand...
Click to collapse
@arsradu
I notice you have experience with security patches, tanks you to had shared!
IF I REALLY NEED TO DOWNGRADE MY SECURITY PATCH ! EVEN with all amounts of troubles, IS THERE A WAY doing it?
Thanks

Question Changing from Global Rom to EU solved(ish)

Hi guys,
So I got the chinese variant of the OnePlus 9 - LE2110. It came with a global Rom already installed. I'm currently on os 11.2.2.2 LE25DA.
I've been reading through the forums and I'm not sure what I need to download exactly to get this over to EU Rom. I think I also saw that I need to let this update first as it's prompting me to install 11.2.7.7. Things are changing so fast with this phone in terms of recent otas and root options that I'm concerned I'll use a dated method that could brick my phone.
Does someone know what file I need to flash on this and how? Also should I upgrade first. At the moment I'm downloading a zip of this but I'm not sure if this is correct :
11.2.6.6
OnePlus9Oxygen_22.E.09_GLO_0090_2105252341
Thanks in advance for any help or pointers

chinbags said:
Hi guys,
So I got the chinese variant of the OnePlus 9 - LE2110. It came with a global Rom already installed. I'm currently on os 11.2.2.2 LE25DA.
I've been reading through the forums and I'm not sure what I need to download exactly to get this over to EU Rom. I think I also saw that I need to let this update first as it's prompting me to install 11.2.7.7. Things are changing so fast with this phone in terms of recent otas and root options that I'm concerned I'll use a dated method that could brick my phone.
Does someone know what file I need to flash on this and how? Also should I upgrade first. At the moment I'm downloading a zip of this but I'm not sure if this is correct :
11.2.6.6
OnePlus9Oxygen_22.E.09_GLO_0090_2105252341
Thanks in advance for any help or pointers
Click to expand...
Click to collapse
Achieved it - as another user posted in another post. Set your device to EU before you update in the oxygen updater app.
But what was not mentioned is If you are just setting up, you also need to allow advanced settings in the updater. Otherwise I was getting a warning message telling me I have selected the wrong device.
Just updated using the updater with the device set to EU and I have BA version

Hey! I'm in the same spot as you were, but I updated it to 11.2.7.7.LE25DA. I also have the CN version. Do I have to wait to the next update to move from global to EU, or is there any option to change it now?
Thanks!

alex7171 said:
Hey! I'm in the same spot as you were, but I updated it to 11.2.7.7.LE25DA. I also have the CN version. Do I have to wait to the next update to move from global to EU, or is there any option to change it now?
Thanks!
Click to expand...
Click to collapse
That was my understanding. However I've been having reception issues that I did not have with a CN huaweii I had before this phone so I'm thinking it might be the EU rom I flashed, which would be odd as I'm in Ireland.
,
Anyway, even though I changed my phone from oneplus 9 (eu) to just oneplus 9 in the updater, I am prompted to download 11.2.7.7 - even though that's what I'm currently on.
Anyone know if this is just the global version of 11.2.7.7? This would mean I would not have to wait for the next update though.

chinbags said:
That was my understanding. However I've been having reception issues that I did not have with a CN huaweii I had before this phone so I'm thinking it might be the EU rom I flashed, which would be odd as I'm in Ireland.
Click to expand...
Click to collapse
Regarding the reception issues, bugs are always possible, or maybe the antenna isn't as strong as your previous phone. From https://www.kimovil.com/ I can see that your Chinese variant should be perfectly fine in Ireland. I would recommend that you reach out to oneplus support, what you've done so far is not breaching warranty restrictions.
Otherwise the "nuclear option" is to use an msm tool to reset your device, including the "modem" (or EFS?) partition which controls certain hardware-related functionality. This is because I'm quite certain they don't change when flashing any of the standard update images (not even a "full" update). Not sure an msm tool is available for your Chinese hardware variant. This is also becoming more risky and not sure how desperate you are.
chinbags said:
Anyway, even though I changed my phone from oneplus 9 (eu) to just oneplus 9 in the updater, I am prompted to download 11.2.7.7 - even though that's what I'm currently on.
Anyone know if this is just the global version of 11.2.7.7? This would mean I would not have to wait for the next update though.
Click to expand...
Click to collapse
You said yourself that you're running EU version but have set the app to check for "global", so I'm a bit confused by your confusion. If you want to stay on eu branch, then tell the app that your device is eu.

laasworld said:
Regarding the reception issues, bugs are always possible, or maybe the antenna isn't as strong as your previous phone. From https://www.kimovil.com/ I can see that your Chinese variant should be perfectly fine in Ireland. I would recommend that you reach out to oneplus support, what you've done so far is not breaching warranty restrictions.
Otherwise the "nuclear option" is to use an msm tool to reset your device, including the "modem" (or EFS?) partition which controls certain hardware-related functionality. This is because I'm quite certain they don't change when flashing any of the standard update images (not even a "full" update). Not sure an msm tool is available for your Chinese hardware variant. This is also becoming more risky and not sure how desperate you are.
You said yourself that you're running EU version but have set the app to check for "global", so I'm a bit confused by your confusion. If you want to stay on eu branch, then tell the app that your device is eu.
Click to expand...
Click to collapse

Cheers, thanks for all that info. I may just live with it, I don't think it's bad enough to warrant messing around with MSM tools. The reception issues seems to only happen when I'm travelling across the county and probably switching towers.
Sorry if my post is a little confusing. What I'm trying to say is I'm having reception issues while on EU rom. So I thought if I change back to global rom this might fix the reception issue. I thought I could only do this if there was an update available. I changed my phone to global on the update and it says there is an update available even though it's the same software version, that's all.
Do you think changing back to Global could fix it?

chinbags said:
Do you think changing back to Global could fix it?
Click to expand...
Click to collapse
I see, I highly doubt it, but it's a low-risk experiment and only a bit of fuss waiting for the download and update, so probably worth a shot. Not to mention the fuss to come back to eu version if it didn't help.
And to be clear about the app, I guess the app was then just telling you about the latest relevant image matching your preference, the "advanced mode" should probably be turned off once you've settled on the region of choice. It's only giving you persistent notifications, so it's not helpful and also quite distracting in the long term.

laasworld said:
I see, I highly doubt it, but it's a low-risk experiment and only a bit of fuss waiting for the download and update, so probably worth a shot. Not to mention the fuss to come back to eu version if it didn't help.
And to be clear about the app, I guess the app was then just telling you about the latest relevant image matching your preference, the "advanced mode" should probably be turned off once you've settled on the region of choice. It's only giving you persistent notifications, so it's not helpful and also quite distracting in the long term.
Click to expand...
Click to collapse
thanks, and yes regarding the app, I thought it was prompting me to install the same version of the software but for the global variant, this is not the case if you try it locally. I saw an option to flash it via the root method but this required twrp. Trying to install twrp at the moment but having an issue with the boot twrp.img command. anyway, if there's an easier way any pointers would be great but thanks for your help.
I'm also thinking if my connection issue persists I will get in touch with oneplus like you said - this is not an issue I should be having with this caliber of a phone.
If I get the global rom on, and make the same journey to test it, I will circle back here to let you know how I got on.
Cheers

What are the differences between the global and EU roms? Are there any benefits to using one over the other?

Superguy said:
What are the differences between the global and EU roms? Are there any benefits to using one over the other?
Click to expand...
Click to collapse
Not a lot, if any. On DA I'm getting the odd one plus notification from the updater or cloud services that I didn't get from EU. Otherwise it's the same rom. I'm testing the different variants to see if it makes any difference to signal strength (which it doesn't by the way).
I'm likely to revert back to EU rom because they say updates are quicker for it and 'should' be better in terms of gdpr issues. But they're basically the same (from what I can see).

So, just to be sure. Now that 11.2.8.8 has been released, I have to switch my phone in Oxygen Updater to EU version and full update? That's it?

Question Pixel 7 pro system firmware needed

I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.

Doesn't exist. Ideally, you would dump the firmware yourself from the phone.

Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?

Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?

kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.