I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Gordster said:
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Click to expand...
Click to collapse
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thank you sd_shadow. I appreciate your very detailed response and answer. I will try your methods and hopefully be able to return to Android 10. Android 11 seems to currently have a lot of bugs at least with the Moto G Power phone. Wish I had stayed on Android 10.
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thanks a lot sd_shadow
I tried Flash Option 2 using LMSA. Replaced all the Android 11 ROM files in the default download directory folder with official Android 10 ROM files, and then used the rescue option to flash the Android 10 files to the Moto g Power. Everything worked perfectly. I now have Android 10 back on my phone. I keep getting the notification that there is an Android 11 update available but just have to ignore this. Thanks again for your help.
Gord
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
darko454 said:
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
Click to expand...
Click to collapse
Seems that lmsa doesn't work for some software channels, or if the baseband and the channel don't match.
What does getvar all say?
Code:
fastboot getvar all
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
JackDHopper said:
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:View attachment 5375851
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
Click to expand...
Click to collapse
Magisk Hide should be able to hide the bootloader status
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
It''s a game of cat and mouse, google introduces new security measures, magisk devs get to working a way around it... There is even a module now that lets you pass full safetynet with xposed and microg.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
jhford said:
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
Click to expand...
Click to collapse
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
jhford said:
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
Click to expand...
Click to collapse
Yeah you should be able to
Beetle84 said:
Yeah you should be able to
Click to expand...
Click to collapse
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
jhford said:
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
Click to expand...
Click to collapse
No idea, i havent flashed anything on my g8 in a while
does this work with moto g power 2021, android 11 aint working for me either, always get the systen ui has stopped error and certain apps stop working
this is my model number just to make sure
Hi all!! I been trying to downgrade my moto g power 2021 to Android 10 from 11 and I been reading in this thread. At first I tried the second method of flashing that sd_shadow suggested and it seems after 32% a message that says "flash single partian, flash failed" pops up.
Then I tried the first method. I tried making the flashall.bat file and put it in the sdk tools directory as the steps said in the fast boot forum. It didn't work when I double clicked so then I put my supposed firmware zip files (that I got from the lolinet website above) inside the sdk tool directory (unzipped) and Android 10 actually installed. I skipped all the steps after factory reset so I can go into devmode and turn off automatic updates. However when I tried turning on my WiFi, the phone would crash and restart and it would do that everytime it tried to connect to the WiFi. Even after I factory reset my device again the same problem persisted. I managed to use lmsa to go back to 11. What can I do to fix this downgrade issue?
After 1.5 full days of many attempts to downgrade from A11 to A10, fastbootd is the answer! I used Motorola-XML-To-Batch-Script-master with stock firmware from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat and boom! back to stock 10!
I go into further details here: https://forum.xda-developers.com/t/how-to-downgrade-android-11-to-10.4283809/post-86614163
Related
Hello,
I currently have an H932 with a corrupt LAF on pie. I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon. If anyone could help to get the .up file for my h912. The link below is instructions on how to get this URL or .up file.
https://www.the***********.com/how-to-capture-ota-update-url-android/
Thanks,
zapzapdew
Same here,. hopefully someone that has not yet updated, or has just started the h932 root process can capture the ota before continuing the steps
Repairing LAF Partition with LG Bridge
zapzapdew said:
Hello,
I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon.
Click to expand...
Click to collapse
I face similar issue when I reset my phone (also h932) and then TWRP deleted and replaced by stock recovery. I tried to install twrp again via lafsploit method no luck. my phone not detected on my PC. so I decide to download LG Bridge and perform an update (I assume that your phone can boot android). If your phone is already running 30d pie then click update error recovery (see image below). If you still on older version you can update to recent version without update error recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
immns said:
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
Click to expand...
Click to collapse
May I ask did your phone bootloader unlocked when update using LG bridge. Actually I try before using update error recovery but no luck. After download firmware when install update on stock recovery, it hang on 5% then restart. My phone is bootloader unlocked when I try. Is it necessary has to be on locked bootloader. Thank you.
hendavi said:
May I ask did your phone bootloader unlocked ..... Thank you.
Click to expand...
Click to collapse
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
hendavi said:
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
Click to expand...
Click to collapse
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I don't know what laf do I have now, probably is stock laf because after flash pie stock rom I forget to flash RCTD Remover and Disable DM-Verity zip.
Unable to flash TWRP because my phone cannot go to download mode. Thanks anyway.
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
could you solve your problem ???? The same happens to me, if you could answer thank you very much.
lost download mode and twrp, also root.
I would like to know if there is any way}, thanks
Reposting this here for visibility:
Hello all. So I am having a similar issue. I was already running a stock rom and I flashed the stock laf from the stock H932 thread. However, I noticed that the latest laf version from that thread doesn't match the latest firmware. I'm not sure if that was the cause but I lost my download mode abilities and twrp recovery (booting into recovery shows "no command". My bootloader is still unlocked and the device will boot into the stock system but download mode freezes whenever accessed meaning I can't use either oreo or pie LGUP to repair it. It shows Unknown B79 and says Unknown / E / L / RO at the bottom. Does anyone have an idea on if there is anything I can do to restore download mode? I noticed I have Would it cause problems to relock the bootloader at this point, as I would like to relock it with the coming changes to safetynet. Thank you for any help.
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie, you should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
TheDannemand said:
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie you, should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
Click to expand...
Click to collapse
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
tbxn said:
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
Click to expand...
Click to collapse
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
TheDannemand said:
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
Click to expand...
Click to collapse
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
tbxn said:
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
Click to expand...
Click to collapse
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there, Upgrade mode should work.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge Recovery mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Edit: Capturing the OTA does NOT require root, that much I remember. I seem to recall you just search through logcat file immediately after starting the OTA download. But again, I haven't done it myself.
TheDannemand said:
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge repair mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Click to expand...
Click to collapse
Yea, I tried LG Bridge but I ran into the same problem as LGUP. When the phone reboots to enter download mode it freezes in download mode. It does the same thing when I manually enter download mode. I tried different ports, cords, pcs etc. all the same outcome.
However, I may be able to get ahold of another H932 so that I can possibly try my hand at capturing the ota link. I have to be more careful with this one, haha. It was never rooted or bootloader unlocked and I have no intention of doing that. Does it still need to be rolled back to nougat to rewrite the partitions if it was always stock? If so, then I would flash Nougat_h93210c_00_1017.kdz in Partition DL mode selecting all partitions, then flash Oreo_h93220h_00_0416.kdz (in Partition DL mode selecting all partitions again?) and then capture the update url when I get it via adb, correct?
The H932 handset that lost twrp and download mode was last flashed with one of the latest twrp flashable roms based on the kdz and not the actual stock kdz so I hope it still has a chance of working, but at the very least hopefully I can capture the ota url for some other's benefit.
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
TheDannemand said:
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
Click to expand...
Click to collapse
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
tbxn said:
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
Click to expand...
Click to collapse
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
TheDannemand said:
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
Click to expand...
Click to collapse
OK, so I flashed the stock phone and got to the point of running logcat. Nothing showed up in the logcat so I used the Take Bug Report method. I found two different ota file urls in the log. One of them was repeated more often so I think that is the correct one. However, I am unsure as to how I should proceed now. Do I need an .up file in order to use fota on the phone with no download mode? Did I perhaps grab the wrong zips? The zips appear to contain all the ota partition files. Trying to use the zip results in a "Windows cannot find WPDAPI.exe" error and an MTP is not running error. Granted this is the LGUP version that i just used to flash the stock phone successfully.
Moto G Power 2021
XT2117
borneo
Firmware
Rescue and Smart Assistant (LMSA)
https://mirrors.lolinet.com/firmware/moto/borneo/official/
https://t.me/s/MotoUpdatesTracker
[Index] Motorola Stock Firmware
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Moto G Play
XT2093
Moto G Stylus
XT2115
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
gutter_chris said:
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
Click to expand...
Click to collapse
Sometimes there's a time delay for the allow oem unlocking, it may take a few days, be sure to connect to wifi or lte after factory reset.
You certainly can try LMSA, but reflashing the firmware is unlikely to speed up the process.
sd_shadow said:
Sometimes there's a time delay for the allow oem unlocking, it may take a few days.
Click to expand...
Click to collapse
Yeah, I had read that somewhere yesterday. Thanks for confirming that. I will wait patiently first.
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
TheTrueJayTwenty said:
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
Click to expand...
Click to collapse
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
sd_shadow said:
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
Click to expand...
Click to collapse
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
TheTrueJayTwenty said:
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
Click to expand...
Click to collapse
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
sd_shadow said:
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
Click to expand...
Click to collapse
I have it on Wi-Fi right now, hopefully its just delayed. I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them. Very strange way to do business if you ask me.
TheTrueJayTwenty said:
I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them.
Click to expand...
Click to collapse
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
MuffinGod said:
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
Click to expand...
Click to collapse
So I may have figured it out, I did a factory reset, on setup I declined everything. I removed everything I could via adb that had anything to do with sprint, boost, and carrier. I then went into the apps list on the device clicked show system apps, went through the apps I couldn't disable under advanced I denied the app permission to modify system settings. As for the TOS the keeps popping up you can try turning on airplane mode you can still use Wi-Fi, I've had hit or miss luck with this one. But Wi-Fi is still working as of now... Hopefully someone can get the bootloader unlocked on the boost model.
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
MuffinGod said:
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
Click to expand...
Click to collapse
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
TheTrueJayTwenty said:
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
Click to expand...
Click to collapse
Yeah boost varient. Mine was grayed out for a couple of days and then it wasn't.
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
MuffinGod said:
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
Click to expand...
Click to collapse
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
Hmm... I followed steps correctly (I think) flashed img and rebooted. Downloaded root checker and confirmed had root. I downloaded a system app Uninstaller, granted root permissions and tried to uninstall carrier device manager. The app requested a reboot. Reboot completed anf now I don't have root access and the carrier app is still installed. Any ideas what I did wrong?
Re-flashed and have root again. Trying to delete system apps through root explorer results in a failure. Is there a system write protection on this phone I need to disable?
Is it safe to try:
adb shell reboot disemmcwp
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.***
From the Pixel Images page:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This applies to ALL Tensor devices, regardless of whether or not you're rooted!
What this means: Once Android 13 Stable boots, it updates an anti-rollback counter in the device hardware to prevent rolling back the bootloader. This will prevent previous versions of the bootloader from starting.
Why this is a problem: The OTA only updates one slot, then reboots into that slot. It does not update both slots at once. If there is a boot failure after updating to Android 13, the device may attempt to "recycle" back to the old slot. If this other slot has a previous version of the bootloader, the bootloader will not start, rendering the device a brick.
How do I make sure this doesn't happen to me? If you updated via OTA, simply sideload the OTA again. Since you are currently on the Android 13 slot, this will overwrite your old Android 12 slot with the new bootloader.
If you have an unlocked bootloader and prefer to update using the factory image, you can flash the bootloader to both slots:
fastboot flash bootloader --slot=all <bootloader image> It's highly recommended you do this BEFORE updating, but if you didn't, do it as soon as possible.
I've updated several times since the August 2022 update, am I still at risk?
If you've updated via OTA at least once the initial Android 13 update, you should be fine. Instructions to check bootloader versions are further down this post.
The initial Android 13 release bootloader version is slider-1.2-8739948. As long as your bootloader is equal to or higher than this, you should be fine.
What if I was on the Android 13 Beta? Same as above - the beta did not incorporate the anti-rollback, and the beta bootloaders are still considered "old".
Will the new bootloader prevent me from flashing and running Android 12? The short answer is YES, for now. Contrary to what the warning above says, you CAN flash Android 12 on the Android 13 bootloader, and though it will boot, it will not run properly. See this post.
How do I check my current bootloader version?
Spoiler: Use these commands in an ADB command line:
Code:
adb reboot bootloader #Reboots device to bootloader.
fastboot getvar current-slot #Outputs current slot, should also be visible on the device screen: "Boot slot"
fastboot getvar version-bootloader #Outputs current slot's bootloader version, should also be visible on device screen "Bootloader version"
fastboot --set-active=a or b #Use this to switch to the inactive slot - if current slot is A, set to B or vice versa.
fastboot getvar current-slot
fastboot getvar version-bootloader
fastboot --set-active=b or a (set to original slot) #Set active slot back to what it was before. If you started on slot A, make sure you switch back to slot A.
fastboot getvar current-slot
fastboot continue #Commands device to resume boot, same function as selecting "Start" in the bootloader menu.
#So as an example:
fastboot getvar current-sot
>current-slot: a
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=b
>Setting current slot to 'b'
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=a
>Setting current slot to 'a'
fastboot continue
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
AlphaSteam said:
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
Click to expand...
Click to collapse
No. That's is the recommended method according to Google.
"To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:
Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image."
Can we run A13 system on an A12 bootloader?
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
kylechen said:
Can we run A13 system on an A12 bootloader?
Click to expand...
Click to collapse
Hasn't been tested yet. If you want, you can try by using the same --force argument; just be aware that if it doesn't work, you may need to wipe data.
kylechen said:
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Click to expand...
Click to collapse
Don't know, doubt it.
kylechen said:
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
Click to expand...
Click to collapse
This seems like something you could research yourself. I highly doubt it - many OEMs implement some form of anti-rollback on their devices to prevent downgrading to previous firmwares. Samsung is especially notorious for this.
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
Android is open source, and that means it is potentially vulnerable to "downgrade attacks." Essentially, an attacker downgrades the software to an older version that has known exploits. This is particularly dangerous in open source software like Android because the act of fixing an exploit reveals it to everyone.
Click to expand...
Click to collapse
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
tom1807 said:
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
Click to expand...
Click to collapse
Not as a daily driver.
V0latyle said:
Not as a daily driver.
Click to expand...
Click to collapse
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
The whole point of this thread is that if only one slot is updated and the device switches/is switched to the Android 12 slot after updating and running Android 13, it will brick.
The side effects of running 12 on the 13 bootloader have been established. See the OP. WebView and DRM Apex constantly crash.
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Lughnasadh said:
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Click to expand...
Click to collapse
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
roirraW edor ehT said:
harassing my fellow moderators LOL!,
Click to expand...
Click to collapse
Beat you to it bet you won't find the Easter egg
roirraW edor ehT said:
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
Click to expand...
Click to collapse
Ah, ok. Makes sense now. I had thought you stayed on it for a while and used it. Thanks...
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Nightf0x_007 said:
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Click to expand...
Click to collapse
Do you mean Android Flash Tool? If so, no, it doesn't flash to both slots. However, the latest version of the Pixel Flasher does.
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
eagledipesh said:
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
Click to expand...
Click to collapse
Sideload the OTA again. It always installs to the inactive slot.
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Sui77 said:
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Click to expand...
Click to collapse
Should be able to, yes.
Thanks for posting this. I manually flashed the OTA update from Google' site and there is no warning listed there (I just double checked to see if it was added since I flashed). I knew you wouldn't be able to roll back to the old bootloader, but I had no idea the recommendation was to flash both bootloaders.
EDIT - actually after looking at the warning on the factory image page (and not seeing it on the OTA image page), I have to wonder if the OTA image flashing process actually flashed both bootloaders. I would think Google would add the same warning to the OTA image site if this was a potential problem.
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.