Related
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Twinsen78 said:
Hi, i flash the pixel experience rom oreo 8.1 on my moto g 2015 but i dont liked, so i flashed the stock rom 6.0 via adb fastboot and some updates have appeared, i can do?
Click to expand...
Click to collapse
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
BenjyTec said:
While I don't know exactly how it is on Moto G3, it seems kind of a game of luck if you get OTA updates back. But necessary steps device independent often are:
- Flash stock ROM with a full wipe
- flash stock recovery
- relock the bootloader
- some devices include a flash counter, for example almost all Samsung devices. This counter has to be reset. Works different for every phone.
- for some devices, for example Sony, specific files MUST be backuped before a flash, otherwise there is no chance of getting OTA back.
But keep in mind that this device doesn't receive updates anymore since about last year. So maybe you just look for the most up to date stock ROM and flash it, which btw on my phone is Android Marshmallow, security patch level April 2017.
I hope this helps a little bit, even though I can't provide very detailed information. Let's hope someone more experienced helps further, or just search around in the web.
Click to expand...
Click to collapse
are only 3 security patch, i updated and not brick but thanks for the reply.
If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: PL2-4040-0-00WW-B01
It will be updated from: PL2-354N-0-00WW-B01, which is released October 2019 Security Update
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than PL2-354N-0-00WW-B01, update to 354N before proceed.
FYI, 354N is October 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install PL2-4040-0-00WW-B01-354N-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
https://www.androidfilehost.com/?w=files&flid=300345
reserved
Installed it on my TA-1043.
OS installed fine over adb sideload, everything seems to be working, and it shows "5" next to my wifi icon - guess it's cause it's 5GHz, also the mobile data icon is still not AOSP and some custom thing. Menus kinda feel stutter-ish. Screenshots were broken on first boot.
alternate download links like google drive?
The update wont install
version no. L2-354O-0-00WW-B01
Update: "Photo" mode in stock camera is broken, says "Action not support: 708". Pro mode works fine
how to use magisk?
i tryed to patch boot on magisk and boot from ADB, but phone going n bootloop and doesn't want up
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.
Getting error when the camera app is set to save photo to sd card.
---------- Post added at 03:24 PM ---------- Previous post was at 02:58 PM ----------
So right now for me on the Internal Stock... I cannot boot any TWRP of any kind or boot any patched magisk boot img. Has anyone been able to boot either TWRP or boot a patched boot img from magisk?
May I ask, can Nokia 6.1 plus use this rom?
joshclaudio said:
Hi. DRG is Nokia 6.1 Plus. This thread is for Nokia 6.1 (2018) which is PL2.
Click to expand...
Click to collapse
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.
kazekiri said:
The confusion is caused by the fact that the Nokia 6.1 Plus (DRG) forum on XDA was recently deleted and now redirects here.
Apparently XDA is working to restore the DRG forum but it will take some time. Until that is done you can expect to see a lot of confused DRG users here on the PL2 forum. Please help them out if you can.
Click to expand...
Click to collapse
Yeah, noticed that, too. I've been experiencing redirect problems since yesterday. Anyway, I installed Android 10 leaked internal build on my Nokia 6.1 Plus with a locked bootloader :silly: . Been using it for more than 48 hours and I have not faced any major issue, except for the not working microphone during calls (plugging in earphones can suffice, though).
solozeeh said:
Hi @hikari_calyx I'm currently on the DRG-354N-0-00WW-B01 stock build version with an unlocked bootloader. But the version on the post has PLC. Also, if after sideloading this rom I decide to go back to the October PIE update how hard will that be. Thanks.
Click to expand...
Click to collapse
Here's the link for the DRG version for anyone who needs it. (Since the DRG forum is currently down.)
Only install this if you are using a Nokia 6.1 Plus or X6 (DRG). DO NOT try to install on Nokia 6.1 2018 (PL2).
https://androidfilehost.com/?w=files&flid=300344
Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked
kaktyys71 said:
Hi hikari calyx! Please help me downgrade my Nokia 6.1 to Android 9. Bootloader locked
Click to expand...
Click to collapse
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.
Solannae said:
"If you don't have unlocked bootloader, you'll unable to roll back to stable build!"
Literally on top of the OP post. As every downgrade/restoration method needs an unlocked bootloader, you can either unlock yours (paid external service), or wait for an eventual OTA zip (not guaranteed, as stated by the OP) that will bring you back on Android 10 official Beta/Release in a couple of weeks.
Click to expand...
Click to collapse
Project Treble A/B? B slot don't help me?
I guess it ils worth a try. Reboot to bootloader, then "fastboot getvar all" to get active slot and "fastboot --set-active=[a/b, your inactive slot]
The thing is, with official OTA updates, once the update is over and everything went well, the previous slot is not necessarily in a bootable/usable state anymore. It is not the case with most custom roms/gsi as you either update directly on the current slot or on the other without modifying the active one, so you can switch between slots without issues.
kaktyys71 said:
Project Treble A/B? B slot don't help me?
Click to expand...
Click to collapse
If you switch inactive slot to active slot and reboot... it will ask to do a factory reset. Perform the factory reset and you should be back to the Pie version. Use the fastboot commands Solannae posted above.
---------- Post added at 11:58 PM ---------- Previous post was at 11:36 PM ----------
Battery draining fast on Internal Android 10.
The battery drain was due to the Adguard app. Everything is working normal again.
I have just installed December 2019 security patch via OTA and now I can't connect to any WiFi any more. It scans and detects networks, but it won't connect. It asks for the passphrase of networks which have already been stored, I enter it and then it says "could not save network" and "could not connect to network". Anyone with the same problem?
My idea to solve this was to boot into recovery and clear cache partition, but this option is simply missing in the recovery menu. Any idea how else cache partition can be cleared without root?
Maheshwara said:
I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.
Click to expand...
Click to collapse
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.
sd_shadow said:
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.
Click to expand...
Click to collapse
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Maheshwara said:
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Unfortunately there is no official way to get Moto firmware.
There has always been people who have access, that reupload firmware.
https://mirrors.lolinet.com/firmware/moto
Is currently the best updated site.
Hopefully a newer version is uploaded soon.
Otherwise you could contact moto support.
Is it still under warranty?
Sent from my mata using XDA Labs
This XDA post contains links to unbricking tools for Moto devices.
RSDLite does not work on Windows 10. If you have a Windows 7 machine, you might want to try that.
Otherwise, go here for a video for converting RSDLite XML files to Windows batch files
The download link is hard to find, so here http://rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
Make sure you download the SDK platform-tools from Google, I had problems when using the one included. Replace adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe from the firmware converter with the ones from the platform-tools package.
If you're not using Windows, make sure you have platform-tools installed and follow this guide to convert the XML file to a shell script yourself, of course adding #!/bin/bash to the first line of the script.
You may also need to edit the resulting batch/script file and replace the target "system" with "system_a" and fingers crossed it'll complete and you'll be golden.
@sd_shadow
I know nothing but the lolinet page for getting firmwares, too. That's where I got the too old image I already have from. I hope, that it will not last too long till a recent image appears there.
In the meantime, I contacted Moto support. My device is still under warranty. They will investigate further how to help me and then get in touch with me again. I hope, I will not need to send it in, because it is easy to solve the problem on my own - I need nothing but such a damn recent firmware.
@Lesking72
Good to know that RSD does not work with Windows 10... My desperation led me to try this. I prefer more platform independent ways of flashing, because my daily driver is Linux (with a Windows 10 VirtualBox which I only use if there is no way around). To transfer the support or flash file of the image to a linux flashing script is quite simple. Fastboot flashing commands are always the same - there is only a need to look which partition to assign which file to. All information about this can be found in the flash file. The main thing for me is, that now, I know where the problem is: I do not have a firmware which is new enough to flash it with bootloader locked. So no RSD, flashfile converters, Blankflash or what else will help me in my situation. I will have to wait for a factory image with a recent firmware. Damn! I can not do anything else! This is what is really annoying to me.
Even more annoying is that I can not even unlock the bootloader to solve the problem, because the "Allow OEM Unlock" flag in developer settings is inactive! At least I think so... Any idea how to find out if this flag is active or not via fastboot without voiding warranty? I can get the unlock data via fastboot and so request the unlock code, but what if when unlocking it says that it can not be unlocked because of this flag being inactive? Then I would have lost my warranty for nothing. Too risky...
I have also played around a bit with this Moto LSMA Tool. It does not even detect my intact Moto Z3 Play in fastboot mode!
@Maheshwara I was watching the rootjunky videos I linked in my previous post and for his device, it threw errors for some parts but still worked. It might be worth it to try flashing again, but replace the "system" target with "system_a"
I haven't tried to downgrade the firmware on my phone though, so I don't know if your issue is because of anti-downgrade features or it's just showing those errors.
@Lesking72
The Moto support has already confirmed me that my problems' reason is the anti-downgrade "feature". And I flashed the same partitions like in the image's flash file. I simply built fastboot commands of the information inside.
The only thing that could solve my problem is to get a recent factory image or find somebody with unlocked Z4 version with RETUS channel, bootloader still locked and recent software version, who could backup all the partitions for me.
I have just seen that there is at least a more recent image for Verizon version here: https://mirrors.lolinet.com/firmware/moto/foles/official/VZW/
That gives me a bit of hope that there will be soon one for the unlocked retail version, too. Or would it be a good idea to try if I can flash boot, vbmeta and dspso of the latest Verizon image to my device? If I am honest, I do not think so...
@Maheshwara If you tried flashing the newest version boot, vbmeta and dspso from the VZW image it would likely not work because your system partition etc. will be from the older unlocked version you tried to flash.
Even if that weren't the case I don't know if you'd be able to flash the VZW firmware without unlocking the bootloader (I figure it's signed differently to stop people from installing the retail firmware on a VZW phone which would make it not work on a retail phone with a locked bootloader)
The odd thing is that I have no OTA update available and when I connect to LMSA it says I'm on the latest version
Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk
I live in México, and i have the same moto z4 than you, 1980-3 US retail, and the ota has not arrived yet,
My last OTA is from october, do you know about other users with the same problem than you? MAHESHWARA
@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk
Maheshwara said:
@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Maybe you will receive the new fixed december OTA, do you know something about android 10?
Maheshwara said:
Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
@Maheshwara i get the OTA yesterday, my phone is with de december security patch, and working fine
https://ibb.co/mNHp69X
airecomprimido said:
Maybe you will receive the new fixed december OTA
Click to expand...
Click to collapse
Too late - my phone is already fully bricked! I will have to wait until a factory image with December patch version will appear somewhere. No other way to revive it... No boot, no OTA, but good to know that it seems to have been definitely rolled out now. So there's a bit of hope that the full factory image I need will be available soon.
Got the factory image version I needed this morning. After having flashed it my device got revived. So far so good, but WiFi connectivity was still broken. After having done a factory reset everything was fine.
But no good that a simple OTA security patch upgrade craps a device with necessity of a full reset.
Gesendet von meinem moto z4 mit Tapatalk
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
Hello, Can any smart person because I'm slow lol help me get the Recovery or the Boot.img for a Motorola Edge 2021, My version is 12 (S1RMS32.48-18-11-2-3). Thanks
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
ruq said:
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
Click to expand...
Click to collapse
I understand that yes but my problem is that I don't have a laptop or PC to run the program so I'm trying to find another way to get the firmware for my Edge 2021, And if I can't do that is there any custom ROM compatible with this device that I could use to patch it with magisk?
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
ruq said:
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
Click to expand...
Click to collapse
I already solved that problem I use another phone to flash the images
ruq said:
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
Click to expand...
Click to collapse
My firmware is android 12 so would it be alright if I install this android 11 image?
Imparel said:
My firmware is android 12 so would it be alright if I install this android 11 image?
Click to expand...
Click to collapse
An android DOWNGRADE might cause issues...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
Okay I understand, I'll just take my chances and hopefully I don't brick my device...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
I did try it but instead of fully flashing the img I just did fastboot boot so that it would only boot into it one time and it didn't work at all so my only chance of rooting my device is using a PC to get the firmware of my phone, And thanks for the help.