Related
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
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.
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
I got a Sprint LG G7 phone from the bay that has been unlocked and flashed to G710ULM Firmware running Android 8.
I want to update to Android 10 if possible. I've never 'hacked' into a phone but am very familiar w/ hacking gaming consoles and feel like I am in familiar territory. With that said, I've read many existing guides and tutorials but have some questions?
1) How do i create (or find) a backup to my current FW in case of errors, etc.
2) Will flashing a FW from another country (Korea, Canada, etc.) render the network services (w/ Sprint) I have useless? In fact, will updating ANY FW render my networking services useless?
3) Do I attempt to flash an updated FW of the original Sprint model (G710PM) or an updated version of the FW that is flashed on the device (G710ULM)
4) Do i need to do an intermediate step of flashing an Android 9 FW or can i go straight to Android 10.
I apologize if any of these questions are redundant to any currently existing guides or posts. I did my due diligence of looking everything up as best as possible before posting these questions. Any help is greatly appreciated.
War Destroyer said:
I got a Sprint LG G7 phone from the bay that has been unlocked and flashed to G710ULM Firmware running Android 8.
I want to update to Android 10 if possible. I've never 'hacked' into a phone but am very familiar w/ hacking gaming consoles and feel like I am in familiar territory. With that said, I've read many existing guides and tutorials but have some questions?
1) How do i create (or find) a backup to my current FW in case of errors, etc.
2) Will flashing a FW from another country (Korea, Canada, etc.) render the network services (w/ Sprint) I have useless? In fact, will updating ANY FW render my networking services useless?
3) Do I attempt to flash an updated FW of the original Sprint model (G710PM) or an updated version of the FW that is flashed on the device (G710ULM)
4) Do i need to do an intermediate step of flashing an Android 9 FW or can i go straight to Android 10.
I apologize if any of these questions are redundant to any currently existing guides or posts. I did my due diligence of looking everything up as best as possible before posting these questions. Any help is greatly appreciated.
Click to expand...
Click to collapse
I'm newbie, but i try answer you in my understanding, and of course, i take no responsibility if something unfortunate happens :angel:
1/ i dont know any way to backup whole phone, but you can flash current FW (G710ULM) again via cross flash.
2/ i dont use Sprint, but my network service is work properly with Android 10 eu, canada and ulm (lasted is Pie), you can try...
3/ yes, via cross flash (update: there is no KDZ or Dump available. Probably in the future there will be dumps of 710PM but for now there is no).
4/ no, you can flash any version, any model (except tmobile) by cross flash way.
Hi. I know this is an old post, but does op still have Sprint firmware backed up?
If you do, I would love to get it from you. I can't seem to boot off other ULM firmware and I think I need an up-to-date Sprint backup abl, laf, boot, and possibly more. If you don't, have fun with your device and have a good day.
I want to edit the hosts file of a moto edge (2021), however I also want it to continue to get OTA updates. So some (potentially dumb) questions:
Can you get OTA updates on an unlocked bootloader for motorola?
Can you get updates after rooting then unrooting the phone?
Will the hosts file changes made while rooted remain after unrooting?
Thank you for your time and help, much appreciated!
Hello, I have seen your publication and I want to give you an answer based on my experience with my Motorola phones, I am just going to try the custom rom that is available for this phone.
but I can clarify certain doubts
Regarding the updates, they continue to be received even if your device is unlocked, that is the answer to your first question,
second, once the phone is updated you can lose the root since in the updates they lose the modifications to some files like the boot.img.
and in the same way it depends on the update but if you can modify the host file.
But I am still going to recommend that you do not update the phone when you have it rooted, since in some update some changes are reverted and it may remain in the bootloop
I hope my answer helps you and I repeat this answer is based on experience with motorola phones