General (TMO) Don't update Galaxy A32 5G - Samsung Galaxy A32 5G

Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions

TypicalGellert said:
Don't update to the new version with Bootloader V3 because Kernel Source of V2 is released which might be able to be used to unlock the bootloader, and to make custom roms or new TWRP versions
Click to expand...
Click to collapse
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.

neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.

neotheone11 said:
Thanks for the heads up. Quick question. Without root, how would one block Samsung's updates? I disabled automatic updates in Developer Options, however, that does not seem to be enough as the phone still prompts me to install the latest update.
Click to expand...
Click to collapse
I just keep them paused, I'm not sure if your able to disable it with adb

tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
Thank for the suggestion. Yes, that is what I meant when I said that I disabled automatic updates in the Developer Options. One of my Galaxy A32 phones kept pestering me to update despite the fact that I disabled the "automatic update" option so I was wondering if there was a better solution.
Do we know the IP addresses of the update servers? I searched online, but could not find the definitive answer.

tavella said:
I’m not 100% certain, but in Developer Settings, there is an option for ”Auto update system“. Under the option, there is text stating “Apply updates when the phone restarts.” I’m going to guess this is likely the setting you’re looking for.
I still haven’t seen the v3 update on my device. This might have to be enabled before the OTA is pushed out.
Click to expand...
Click to collapse
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked

financeledger said:
My 2nd A326U is on V3 ( T-mobile ) soon bootloader will be unlocked
Click to expand...
Click to collapse
I also have v3 (T-mobile) and am waiting for the same thing as you.

Hello guys. Where I can see bootloader version?
Thanks for answer.

Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.

Setting/about/software information/build number

scottyrick2 said:
Software version. Settings/About
5th digit from end is bootloader version. For example 3AUF7 is the ending on my version. 3 is the bootloader version.
Click to expand...
Click to collapse
Can you take screenshoot?

Ryan.XM said:
Can you take screenshoot?
Click to expand...
Click to collapse
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,

scottyrick2 said:
My Screensho is not working properly right now.
Here are Step-by-step directions to find your bootloader version.
1. open Settings on your phone
2. choose About
3. choose Software Information
4. look at the number under the Build Number section
5. the fifth character from the right is the bootloader version
Let me know if you have problems.
Best,
Click to expand...
Click to collapse
Ok thanks bro,

Here's what I did on my T-Mobile A326U Samsung Galaxy A32 5G
1. Open the Android 11 Settings on your phone
2. Choose About phone
3. Choose Software information
4. Look at the number under the Build number section
5. The fifth character from the right is the Bootloader version
Mine is apparently Bootloader version 6.

Related

DON'T upgrade to Nougat by OTA!

This has already discussed in other posts here BUT I continue to see A LOT of people waiting for Nougat OTA like Santa Claus should bring to them... (or, even worse, trying to push it in their phones... )
So, I make this post just to give more visibility to all...
I'll try to write it clear...
Don't update your Z to Nougat by OTA!
Is it clear enough? :laugh:
Now some explainations...
Over the the common generic motivations (difficulties when not in full stock conditions, risk to brick it during process, OTAs that are the Evil... ), there is a strong one in this case: Nougat OTA for Moto Z (silently...) upgrades your bootloader too, from v. 90.xx to v. 91.xx...
This isn't really needed (Nougat runs flawlessly on v.90.xx too... ) BUT it introduces some tighter rules on what you can and what you can't anymore boot on it, limiting hacking and upgrading (to developed third part ROMs...) possibilities...
One of this rules is that with v. 91.xx bootloader you can't anymore boot to MM ROM!
Considering that as of today it seems that bootloader can't be donwgraded (some have soft/hard bricked their Z trying to downgrade it...), Nougat upgrade by OTA is a one way process.
If you consider that stock Nougat seems to have some bugs and issues (and, as of today, no Xposed available...!) and that some (all?) third part Nougat ROMs requires "MM" (v. 90.xx) bootloader to work, it seems not to be a great idea leave that Motorola upgrades silently your bootloader...
So?
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
Considering we on the Moto Z droid don't have an unlockable bootloader and/or ability to root I don't see it effecting you negatively, other than an exploit that may be discovered for marshmallow that would allow for root. We are at the mercy of a kind developer taking on the task. I really miss my hotspot without a fee... But I can go back to my Moto X if it is necessary.
xterminater07 said:
I already did nougat via ota for my moto z droid... Does this affect anything? Also how do i flash a factory nougat on my moto z droid if i want to stsrt fresh?
Click to expand...
Click to collapse
I agree with dap... proposed solution can't be used since of unlocked bootloader, BUT if I had a Droid I would have remained sticky to first SW release as long as possible because of the higher probabilities of a flaw to hack and root it...
With Nougat and newer (even more "locked"...) bootloader it will be harder...
those are a lot of steps... is there a way to just hide the nag/update screen that pops up? it keeps wanting to update or ask for a time to update or reminds me to update etc
enetec said:
So, at present, the best method (IMHO...) to upgrade to Nougat is that one which is described in OP of this thread: you will have a full stock Nougat BUT with older bootloader and the possibility to easily return to MM or to whatever ROM you want...
Click to expand...
Click to collapse
Does the method you linked to even work with the VZW variant? It looks like it used to, but the Verizon stuff is all marked through and I'm not clear on the process.
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
aatjitra said:
hmmmfff... I have updated mine using OTA.. now I want to back to MM... but no way to do that...
Click to expand...
Click to collapse
Hello did you try to get down to MM? Thank you
regards
iron maiden said:
Hello did you try to get down to MM? Thank you
regards
Click to expand...
Click to collapse
No. I didn't.
I read in other thread that bootloader v91 won't work with MM.
Moto Z ( UAE ) no OTA yet
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
yanniclord said:
How can i disable the OTA Update app opening all the god damn time? I mean seriously, every time i lock the screen and turn it back on, it annoys me by saying i need to update to Android 7, I DON'T ****ING WANT TO! Can someone PLEASE tell me how to disable this?
Click to expand...
Click to collapse
You can't. The only thing you *can* do is tap the "Later" and then "Done" buttons. That will defer it for another 24 hours since it automatically fills in the phone's current time for the next check.
It's annoying, but it's only once a day.
EDIT: I thought you were referring to the VZW variant. If you're not and your phone is rooted, you might be able to disable or remove "Motorola Update Services". To do so, go to Settings > Apps > select "Show system" from menu (3 dots at top right) > scroll down and tap "Motorola Update Services"
I can't disable it on my VZW unit, but you might be able to. Or maybe you can remove the app via root (though I have no idea if that will cause further problems).
I too can confirm thr disabling motoservice in settings method. But you have to do it everytime you reboot your phone, it does t hurt me doing that.
I found a simple fix, get Titanium Backup and freeze that crap app, done.
yanniclord said:
I found a simple fix, get Titanium Backup and freeze that crap app, done.
Click to expand...
Click to collapse
There is another way for users with root eventually...
saif_khans said:
HI,
can anyone suggest which android 7 update is to be used for UAE users and how to install manually ?
Click to expand...
Click to collapse
Simply use the method linked in OP. It uses retmx sw.
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
sam564 said:
True, I updated via Ota and now I can not install custom roms, will in the future have a solution to this problem? Because we all know that by unlocking the bootloader we lose the warranty, but we do this because we want to have options to install on our devices.
Could any dev have managed to fix this in the future roms?
Click to expand...
Click to collapse
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Variants doesn't matter all moto z is using same kernel source (I have Chinese moto z)
Let me explain, I'm trying to port farm-root for moto z
Here's the source : https://github.com/freddierice/farm-root
If anyone knows how to deal with ndk and other Stuffs, can install TWRP with this version of farm-root
But I'm trying to make it easier and here's big barrier called SELinux
rczrider said:
Which variant do you have? @erfanoabdi suggested in another thread that they might have root figured out for the VZW variant in the next couple of days. No idea if what they're working on will be applicable to the Nougat.
Click to expand...
Click to collapse
Hope it happens. The phone (accidentally?) Downloaded the update and is now asking to install. I'm afraid one day it'll just automatically update on it's own.. I can't seem to find where the system update got downloaded to, otherwise I'd delete it

[HOW TO] Carrier Switch Galaxy S8/S8+ **SNAPDRAGON**

*READ FIRST*
This thread is now completely dedicated to the aspect of Carrier Switching on the Snapdragon model of the Galaxy S8/S8+, the current root progress can be seen here:
Current ROOT Progress for G950U/G955U Snapdragon
Please Note that if your device is network locked this WILL NOT unlock it for use on other carriers, however it will allow the switching of carriers and carrier specific features on network unlocked devices just by changing sim cards, the device will reboot and your done. As for those with a network locked device this thread still applies to you, if you are interested in a bloat free experience(that is faster and smoother than stock touchwiz), on your Galaxy S8/S8+​
Let's Begin!
Download the firmware for the unlocked S8/S8+ here:
G950U1UE1AQDC_XAA
Download the Prince Cosmy version of Odin here:
Odin_3.12.3_Modified
Enable developer options on your device:
Settings----->About Phone----->Click Build Number 7 times
Enable USB Debugging:
Settings----->Developer Options-----USB Debugging
Put your device into download mode: Volume Down + Bixby + Power
(accept the warning and connect your device to your computer)
Take the G950U1.zip you downloaded in step 1 and extract it, then place the BL,AP,CP,and CSC files into their corresponding places within Odin and press start
Once finished the device will boot back up and you will be free to disconnect it from your computer
You now have the unlocked, bloat free, firmware on your S8/S8+
CONTRIBUTORS
@Maltego for hosting files
@mweinbach for originally getting the unlocked firmware and for posting a tutorial on flashing it
@Acoustichayes for creating a dedicated root thread​
Delete
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
EDIT: installing now, needed the latest odin
Akumai said:
I've been getting protocol version errors trying to flash via odin 3.10 (the only one that I can download)
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=529152257862722617
Here is Odin 3.12.3
Persianhawkes said:
I have the s8+ version installing now. Will report back. Op make sure they uncheck Auto reboot and f. Reset time in odin first.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is for an s8....Not plus. Be careful.
suzook said:
This is for an s8....Not plus. Be careful.
Click to expand...
Click to collapse
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
I can't wait to give this a run this weekend
Persianhawkes said:
I know. I have the s8+ file. Flashed and booted up now I have to do some tinkering.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
suzook said:
Oh, ok. Didn't realize that. So does this overwrite the carrier info? Or is that untouched?
Click to expand...
Click to collapse
As of right now there is no way to overwrite carrier info, we are working on it though. That reserved comment is going to be where i put all that is known, been tried, etc with carrier switching just a little busy right now
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Triforce1001 said:
My build number is SM-G950A and my firmware is G950USQU1AQD9. I am quite familiar with the concept and process of rooting but I have never had an opportunity to actually get into it. I was wondering if my device is compatible with this firmware. If so I am fine with testing so long as there is a reliable way to restore my phone if something were to happen.
Click to expand...
Click to collapse
This is compatible with your device all US versions of the S8 and S8+ have the same model number. I have your stock firmware i just need to upload it to androidfilehost
If anyone feels like it joining I have created an IRC room we can all chat in and brainstorm things. It's #sgs8 on irc.freenode.net. Hasn't had many users since I created it but I lurk in there when I'm at home. I'd love some company. Let's get this thing rooted so we can shut all the haters up!
Glad to see more devs working on this
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Akumai said:
I went ahead and did the favors of doing some testing, in terms of restoral anyhow. From my experience, you do not have access to the usual desktop, and you have very few apps by default(none actually, just settings). I was able to revert to the original stock firmware via odin without a hitch. I did not try installing TWRP on this firmware however, but I can confirm the existence of OEM Unlock, which, by itself, claims to unlock the bootloader.
Click to expand...
Click to collapse
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
STF_TimelessGoD said:
I attempted to install TWRP on it but secure check fail boot i believe i will try again, but we only have the exynos twrp for the S8 to work with....
Unless someone can make a compatible version for Snapdragon?
Click to expand...
Click to collapse
Contact @ashyx he's very good with Samsung and TWRP
force70 said:
On no device that ive seen does OEM unlock in fact unlock the bootloader.
sent from my S8 plus, Note 7 or S7 Edge
Click to expand...
Click to collapse
it merely mentioned that it allows "the unlocking of the bootloader"
Akumai said:
it merely mentioned that it allows "the unlocking of the bootloader"
Click to expand...
Click to collapse
Thats not what that means is what im trying to say lol. That option on sammy phones has never really done much other than allow flashing in odin
What is of note is that i dont have that on my S8 which is new that option is always there.

[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

General Got my Edge S, unlocked bootloader and Magisk root

Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
HopelesRomantc91 said:
Basically the title. I received my Chinese Edge S today, so far I like it but I've barely used it. I thought I got a model with Gapps preloaded, but I was wrong (big surprise). I sideloaded Play Store, but haven't gotten much farther. Unlocking the bootloader was a little difficult, I had to factory reset, with the SIM card installed, to get "OEM Unlocking" to not be grayed out. But from there it was simple, I used the Motorola website to get the unlock code, ran it, no problem. I just followed the normal Magisk instructions: I installed the Magisk app, found the boot.img file inside the ROM download from the Lenovo Rescue and Smart Assistant, patched it with Magisk, flashed it via fastboot and I'm rooted. Once I hid Magisk, Google Pay seems to work fine (although it says NFC is not set up...I'll have to test it tomorrow for tap to pay to see if it works; when I go into NFC settings it says Google Pay is default). I'll let you all know how it goes. I also downloaded Google Assistant, but as I suspected it isn't working. I tried to sideload Gapps from Android 10, but it didn't work. I'll have to try TWRP later, or maybe wait until an Android 10 Gapps is available.
EDIT: Since I have root, is there a way install the Gapps? I found BiTGApps which has Android 11 support, but it only lists TWRP install method and there's currently no TWRP for this phone.
Click to expand...
Click to collapse
Wow, thanks for all this info. That is great that you were already able to root and get Magisk on there with minimal issues. This is pretty much what I do with my phones right out of the box. Regarding that link for Gapps, I read through the start of that thread and the package is definitely what we'll probably need for this phone. But, without a working recovery at this point, I don't think there is another way to install it.
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
CCivale said:
If you don't mind me asking, where did you purchase the phone? And where do you live?
Edit: Just saw your answer in the other thread.
Click to expand...
Click to collapse
It's worth noting that I cancelled my Giztop purchase and bought from Aliexpress instead. Can't remember if I actually said that or not.
there is twrp, it is experimental
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
I couldn't find it, can you link it?
Electimon said:
there is twrp, it is experimental
Click to expand...
Click to collapse
Can you link it?
syncrosys said:
That's awesome that you did that. I received my code from Moto, but I need to factory reset myself to get the OEM unlock slider to not be grayed out. I'm just waiting for the G100 Rom to be available and flash it then.
Until then. its a pretty sweet phone for the money.
Click to expand...
Click to collapse
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
ktitimbo said:
Any idea when the G100 ROM will be available?
Can you please describe the steps on how to flash the new ROM?
Click to expand...
Click to collapse
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
@HopelesRomantc91
Can you share the URL for unlock code request?
I couldn't unlock with global website...
I think I just used the global one here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/
Hello, I have patched boot img to my moto edge S 5g Chinese version and I have magisk root ok but if I restart the motorola it is lost and I have to reinstall boot parched, do you know why?
HopelesRomantc91 said:
I imagine it'll be available as soon as the phone itself is, just a matter of someone downloading the G100 ROM with RSA, then uploading it for the rest of us. I also imagine the process will simply be to download it, and rename it so RSA will flash it instead of the Chinese ROM for us, but that's really only speculation at this point. It may have a checksum that would make flashing a little more difficult, in which case it would be a matter of installing TWRP (once available) and then flashing that way.
Click to expand...
Click to collapse
Thanks for info . İs flashing g100 rom need root device or unlocking bootloader ?

Question What is the way that samsung devices download and upgrade os? So where does samsung device download firmware from when I click software update?

I will look foward to your reply.
Thank you!
Firmware download from here - https://www.sammobile.com/firmwares/
Upgrade guide here - https://forum.xda-developers.com/t/...m-s908e-ds-july-update-s908exxu2avf9.4415921/
(Big) thank you!
Try Frija for better speeds
Starwars8k said:
I will look foward to your reply.
Thank you!
Click to expand...
Click to collapse
That depends. If you have the unlocked version it comes directly from Samsung. If it is a carrier version, your carrier provides it. Both are the OTA method.
The non-automatic method is to download from sites like XDA, Samobile, etc.
Thank you!
Here are the steps to upgrade the operating system in your Samsung device:
Make sure the device is connected to the internet.
Open device settings.
Tap on “About Phone”.
You will see an update button, only if updates are available. Click on it.
Now install. The installation button may vary based on your OS. So, it is either “Install Now”, “Install System Software”, or “Reboot and Install”.
So, getting to the second part of your question, which is about firmware download when you click software update. Well, if the firmware on your device needs to be updated, they’ll show the download and install option, when you click software update. In case, there are no options for device firmware download, it typically means that your phone’s firmware is already up to date.
Read more

Categories

Resources