I am a newbie to GSM, so bear with me
T-Mobile is offering me an OTA update to M919UVUFOK3 every 24 hours. Is it too late already to keep EFuses from blowing, since KNOX came with the MK2 on my motherboard? In which case have I got nothing to lose by accepting the OTA update? This would be the most stable, OR
Should I root the MK2, install TWRP, and upgrade via ODIN? I'm not sure if they have OK3 for modded firmware yet, at the moment, all I want to do is upgrade to the latest, most stable firmware / kernel / modem I can while keeping as many E-Fuses intact (knox bit, anything that keeps me from being able to downgrade, root, install a custom ROM, or ressurect my device if it becomes hard-bricked.
Here's what I know about my S4
About Device:
Model Number
SGH-M919
Android Version
4.3
Baseband version
M919UVUEMK2
Kernel version
3.4.0-2015522
[email protected] #1
Sat Nov 16 14:22:56 KST 2013
Build number
JSS15J.M919UVUEMK2
SELinux status
Enforcing
SEPF_SGH-M919_4.3_0010
Secure boot status
Type: Samsung
Here's what I have observed about my phone so far:
* T-Mobile finally gave me a SIM card that works
* Full eMMC dump using RIFF (anything available upon request)
* KNOX is installed
* ODEX information was found on this phone when I looked through partitions in a hex editor
* Found code amongst the boot loader partition in WinHEX, "BootLoader.Rollback.BlowFuse" <<< NOT Warm and Fuzzy feeling
So, in short, do I have nothing to lose by accepting the OTA update (I believe it is still rootable), OR should I root my current firmware and do everything by hand? OTA would ensure greatest stability, but I still want it to be MY phone. Any suggestions?
If anyone wants my full eMMC dump, *.pit file, anything let me know (as long as it's not something personal like a certificate or IMEI)
P.S. - What are these "Security Policy Updates" it constantly is asking me to enable? My friend said they are harmless (don't do any permanent castration on rollback capability). What do they do? Can they update the security - against me? (like changing the lock on my front door and stealing my house)
I'm a newbie, so if some questions sound stupid just bear with me. I just want the latest firmware, mostly stock but rooted, and not burn my bridges to go back and do anything I may learn about later. I could just keep delaying the update, but 4.4.4 ran faster on my last phone and I like it, but want to be able to keep my options open.
Thanks
If this is a stupid question, I'm a newbie just point me in the right direction.
I know how to root, I know how to use odin, I just need to know if MK2 is already too far to not trip the KNOX thing. I'm not sure if KNOX is actually installed, but I have a good bet it is, as it's listed under "Device Administrators".
It may sound a tad crazy, but everytime they fry one of these on my (originally $700) phone, they may as well have literally violated me, raped me, as if they're willing to go THAT far to control how I use... um, what is it called when you purchase something? I mean when you buy something, who's property does that become? Oh yeah, it's MY property. In Django Unchained, although his character is evil (and I'm talking electronics no offense intended), Calvin Candie said exactly how I feel about eFuses, controlling what I can and can't do with items I purchase.
"This CPU here, is MY property... and I can choose to do... with MY PROPERTY... WHATEVER I so desire!"
I'm just asking what would be the best course of action as I'm torn between stability and "Keeping my Rights". For those who do not know what an eFuse is, it's literally a fuse that's 20nm wide embedded in the snapdragon CPU itself. It's the way they can make it impossible to downgrade or reset the KNOX bits. When a KNOX bit is set, a higher voltage is applied to this fuse and it is purposely overloaded, breaking the link and setting it to a "1". If we had the RSA private key to sign our bootloader, it would be no problem. Here's some info on eFuses
https://en.wikipedia.org/wiki/EFUSE
http://paris.utdallas.edu/ssiri08/Tonti_SSIRI_eFuse_V2.pdf
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
hi all. I cannot find for the life of me the stock firmware I need. I am on Android 11. Do I need to downgrade to 10 for the OEM unlock option in development
Yes, people report that the US firmware is more tightly vendor-locked. I can only suggest the "go back in time" trick: https://fixwithme.com/samsung-oem-unlock-not-showing-fix
I followed that exactly and when I set it back to to a date prior to August 18th 2018 it always reset itself back to September of 2019 I don't know why but I don't think I'm going to be able to successfully root and unlock the bootloader this phone sucks
Daytoncarecenter521 said:
I followed that exactly and when I set it back to to a date prior to August 18th 2018 it always reset itself back to September of 2019 I don't know why but I don't think I'm going to be able to successfully root and unlock the bootloader this phone sucks
Click to expand...
Click to collapse
Probably they have been acknowledged of this trick and patched it in the latest update. They love to patch every possible backdoor into freedom of use of your own devices you've paid money for. After all, money themselves don't worth much in the today's world. Are you sure you've disabled all the auto-updates?
yeah I've done everything I'm a very experienced phone modifier but this weak phone for whatever reason is difficult. it's not like this phone is anything special
The last security update I see is June 1, 2022, which is to install Android 13, which I don't really want. Since there is a a new wifi calling exploit found, is there a way to get the security updates without installing A13 or does Goolge have the deck stacked and I'm essentially forced to upgrade? I live in a rural area and without wifi calling, I have no service.
I think your best bet would be to install a security patch via Magisk if you can find one. Also, maybe a kernel would offer what your looking for?
graysky said:
Since there is a a new wifi calling exploit found
Click to expand...
Click to collapse
First of all the exploit was fixed with the latest update a few days ago! The exploit was discovered, fixed and published by Google. That's the usual way a chip manufacturer deals with it and there' no reason why it should be unsecure to use the latest firmware. BTW: No device was attacked.
Security patch level June '22? You want the latest patch level without installing the corresponding firmware? For what purpose? A new security patch = updated firmware and without an updated firmware you don't have any patches. That's it.
Edit: Some background information. Your installed patch level is set in your boot.img. In theory you'll need a patched boot.img with another patch level (unlocked bootloader required => all data gets wiped!). But your device isn't then more secure than before!!
So it's clear in my head, the OS is firmware and the latest security patches rely on the latest OS to function, correct?
graysky said:
So it's clear in my head, the OS is firmware and the latest security patches rely on the latest OS to function, correct?
Click to expand...
Click to collapse
yes
WoKoschekk said:
yes
Click to expand...
Click to collapse
Thanks!
Interesting. I installed all the available updates and the is no March update, which I thought was needed to fix the exploit. The most recent update is from Feb 5, 2023. This is a 6A phone.