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
Related
I currently am using my V10 on at&t.
When I first got the phone I did the temporary unlock so I could use the phone out of the box until I was eligible for a "Permanent Unlock".
I used the permanent unlock and it was successful.
After the allotted time for the temporary unlock ran out, T-Mobile locked my phone again rendering it unusable as far as calls/texts.
I saved a backup with TWRP and wiped it and It worked again.
The problem is when I restore my backup it is still locked.
Any help is appreciated! Restarting from scratch on this phone would be a huge pain.
Since you already did the permanent unlock, your IMEI is whitelisted in T-Mobile's database.
Clear data for the Device Unlock app, run it, and do Permanent Unlock. It will unlock the phone again.
You might need to have a T-Mobile SIM card in the phone when you do it.
siraltus said:
Since you already did the permanent unlock, your IMEI is whitelisted in T-Mobile's database.
Clear data for the Device Unlock app, run it, and do Permanent Unlock. It will unlock the phone again.
You might need to have a T-Mobile SIM card in the phone when you do it.
Click to expand...
Click to collapse
Thank you for the reply! I also forgot to mention that I am running this debloated rom:
http://forum.xda-developers.com/tmo...-lg-v10-h901-10c-debranded-debloated-t3277305
The T-Mobile unlock application is on the rom but does not function properly. I assume this is because most of the services that are used by the app are disabled in the rom.
Is there any place I could download the T-Mobile services or maybe even just reinstall the device unlock application.
Once again thank you for the reply!
johnfroedge said:
Thank you for the reply! I also forgot to mention that I am running this debloated rom:
http://forum.xda-developers.com/tmo...-lg-v10-h901-10c-debranded-debloated-t3277305
The T-Mobile unlock application is on the rom but does not function properly. I assume this is because most of the services that are used by the app are disabled in the rom.
Is there any place I could download the T-Mobile services or maybe even just reinstall the device unlock application.
Once again thank you for the reply!
Click to expand...
Click to collapse
Yes, you're running my ROM. Did you read the first post in the ROM thread?
I clearly wrote there that the Device Unlock app does not work on my ROM (and is not even included in it).
You must flash back to full stock and unlock there, then flash my ROM again.
siraltus said:
Yes, you're running my ROM. Did you read the first post in the ROM thread?
I clearly wrote there that the Device Unlock app does not work on my ROM (and is not even included in it).
You must flash back to full stock and unlock there, then flash my ROM again.
Click to expand...
Click to collapse
Sorry for not noticing ha:laugh:. Great job by the way!
I will give it a go. Is there any way I can restore the majority of what I have on my phone(apps/settings) without the phone relocking.
I assume that no matter what, if I restore the phone with the backup I made it will be locked again.
In T-mobile's database this phone is unlocked.
johnfroedge said:
Sorry for not noticing ha:laugh:. Great job by the way!
I will give it a go. Is there any way I can restore the majority of what I have on my phone(apps/settings) without the phone relocking.
I assume that no matter what, if I restore the phone with the backup I made it will be locked again.
In T-mobile's database this phone is unlocked.
Click to expand...
Click to collapse
SIM lock status is not stored in the Android OS. It's stored in the baseband processor, which is a separate chip with its own proprietary OS that Android can talk to in a very limited and specific way via the RIL (Radio Interface Layer).
The SIM lock status is NOT stored in your TWRP backup. You can backup and restore at will.
Once the phone is permanently SIM-unlocked, it should stay that way forever, unless the permanent unlock did not stick. After you do a permanent unlock in the Device Unlock app, you must reboot the phone and wait for the toast notification saying "device is permanently unlocked." If it worked, the Device Unlock app will disappear from your app drawer (it disables itself). If you still see it, the unlock did not stick and you have to open the app and do it again.
siraltus said:
SIM lock status is not stored in the Android OS. It's stored in the baseband processor, which is a separate chip with its own proprietary OS that Android can talk to in a very limited and specific way via the RIL (Radio Interface Layer).
The SIM lock status is NOT stored in your TWRP backup. You can backup and restore at will.
Once the phone is permanently SIM-unlocked, it should stay that way forever, unless the permanent unlock did not stick. After you do a permanent unlock in the Device Unlock app, you must reboot the phone and wait for the toast notification saying "device is permanently unlocked." If it worked, the Device Unlock app will disappear from your app drawer (it disables itself). If you still see it, the unlock did not stick and you have to open the app and do it again.
Click to expand...
Click to collapse
Any suggestions for when I recieve a message like this? I assume it is not a problem.
{
"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"
}
johnfroedge said:
Any suggestions for when I recieve a message like this? I assume it is not a problem.
View attachment 3631869
Click to expand...
Click to collapse
Yes, that means the app failed to unlock the phone because it's already permanently unlocked. There's nothing for you to do there.
siraltus said:
Yes, that means the app failed to unlock the phone because it's already permanently unlocked. There's nothing for you to do there.
Click to expand...
Click to collapse
Thanks! I got it working again!
need help
johnfroedge said:
Thanks! I got it working again!
Click to expand...
Click to collapse
Pls what did you do to get it to work again? My galaxy core prime is network dead and I get the same unlock failed unlock approved crap.
Unlock t-mobile LG v10
Did anyone figure out how to get this unlocked? I am in the same situation and would love to collaborate with anyone on getting this unlocked.
In a similar situation with a LG K20 Plus unlocked third party. Restored a TWRP backup of Lineage OS 14.1 from stock OS. All was well I thought and then i noticed i lost UNLOCK + 1) IMEI 2) BASEBAND 3) SERIAL NUMBER. I restored IMEI, BASEBAND and working on SERIAL. Cannot get the Unlock back. Flashed back to stock to repair all and got all done but UNLOCK. Doesn't make sense.. I have tried a number of things but no success. I since flashed back to LineageOS thinking i might get the UNLOCK back but all i get now is a code input prompt like you get on LineageOS and most importantly code based unlock phones.. ATT,SPRINT,CRICKET etc. I got the same thing on Stock as well.. odd eh? Anyone have some suggestions?
Will post some screenshots soon.
Figured it out.. Flashed back to stock but a build newer than what i flashed before. Then I simply used the built in MetroPCS unlock app and it worked. lol... Flashed my custom stuff back and nothing lost at all. Got serial # back as well.
BOOTLOADER UNLOCK IS REQUIRED FOR THIS TO WORK
STEPS
1. <Mod Edit: Link removed for promoting paid service.>
2. flash stock ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip Firmware in RSD Lite or use my RSD lite for mac or linux use the servicefile.xml in the firmware to keep your data and apps.
2. download and run the batch file in XT1625-Remove-Amazon-Ads-only-keep-apps.zip tool. Just click on the remove-amazon-ads.bat and follow the directions.
3. once device reboots your good to take ota updates or adb sideload the latest ota update
NOTE
ads will not be restored on the device after a ota update until Amazon decides to push something to the device that affects the one app i deleted from the oem.img that displays the ads.
enjoy
Rootjunky out.
RSDLITE NOT WORKING ON WINDOWS 10 CHECK THIS OUT
https://youtu.be/njXQYn53SPc
Donate if you like my work thanks
Wow. Nice. Speechless. You're one awesome person! Thanks for your time and effort. It's very much appreciated.
Hey TOMSGT...thanks for the post. It worked for me, however I'm not receiving the latest OTA update which is called MPJ24.139-48
Apparently from the logs it's to improve call stability.
How can I continue to get updates? Thanks.
pacattack81 said:
Hey TOMSGT...thanks for the post. It worked for me, however I'm not receiving the latest OTA update which is called MPJ24.139-48
Apparently from the logs it's to improve call stability.
How can I continue to get updates? Thanks.
Click to expand...
Click to collapse
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Tomsgt said:
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Click to expand...
Click to collapse
Thanks. I'll keep my eyes posted for the update. My dad just got his phone updated so I wondered. Now I'd only they could fix the phones camera. My pictures come out pretty bad.
Thanks!
Tomsgt said:
That update isn't being pushed to all device yet just keep checking or you can adb sideload the ota I link in this thread from stock recovery.
Click to expand...
Click to collapse
Do you think being rooted will effect getting updates? On my nexus 5 after I rooted and installed twrp I wasn't able to get updates anymore.
pacattack81 said:
Do you think being rooted will effect getting updates? On my nexus 5 after I rooted and installed twrp I wasn't able to get updates anymore.
Click to expand...
Click to collapse
Yes root and twrp will cause ota update to fail to install.
Tomsgt said:
Yes root and twrp will cause ota update to fail to install.
Click to expand...
Click to collapse
Other than the update you provided how do I continue to sideload updates? Where there be a place updates will keep getting posted at? Also, when you say sideload the update you provided what do you mean? Can I flash the zip in TWRP or is there another method?
Thanks.
pacattack81 said:
Other than the update you provided how do I continue to sideload updates? Where there be a place updates will keep getting posted at? Also, when you say sideload the update you provided what do you mean? Can I flash the zip in TWRP or is there another method?
Thanks.
Click to expand...
Click to collapse
Well I will keep posting Amazon ota updates on my site as I get them.
Adb sideload is done on stock Android recovery by selecting apply update from adb or apply update from sdcard.
Tomsgt said:
Well I will keep posting Amazon ota updates on my site as I get them.
Adb sideload is done on stock Android recovery by selecting apply update from adb or apply update from sdcard.
Click to expand...
Click to collapse
Since I'm now using TWRP recovery how do I sideload the update? Can I flash the zip in TWRP?
Thank you for the good work.
I already followed your previous instruction on removing amazon. And, now, here you have a newer slightly different way. Can you please help me understand a few things?
1) what are oem.img and ads-removed-only-oem.img? Obviously, they are different from the stock firmware - ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which is bigger than 1GB. oem.img is only 128MB and ads-removed-only-oem.img is 540MB. Is it correct that you started from the stock firmware, and removed all of the Amazon additions, and you ended up with oem.img or ads-removed-only-oem.img? So, your script is not about deleting all the Amazon stuff, but about flashing an image that you came up with after removing all the Amazoz stuff?
2) The reason you need to unlock the bootloader on this instruction is to put the stock firmware on it, right? So, if you were to start from a fresh out of the box Amazon phone, then can you skip step 1 and 2?
3) What are the differences between oem.img and ads-removed-only-oem.img, that keeps OTA working vs not working?
TIA.
chonghak said:
Thank you for the good work.
I already followed your previous instruction on removing amazon. And, now, here you have a newer slightly different way. Can you please help me understand a few things?
1) what are oem.img and ads-removed-only-oem.img? Obviously, they are different from the stock firmware - ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which is bigger than 1GB. oem.img is only 128MB and ads-removed-only-oem.img is 540MB. Is it correct that you started from the stock firmware, and removed all of the Amazon additions, and you ended up with oem.img or ads-removed-only-oem.img? So, your script is not about deleting all the Amazon stuff, but about flashing an image that you came up with after removing all the Amazoz stuff?
2) The reason you need to unlock the bootloader on this instruction is to put the stock firmware on it, right? So, if you were to start from a fresh out of the box Amazon phone, then can you skip step 1 and 2?
3) What are the differences between oem.img and ads-removed-only-oem.img, that keeps OTA working vs not working?
TIA.
Click to expand...
Click to collapse
1. Ads remove only oem.img is just that the stock Amazon OEM.img but I deleted the lock screen ad app from it. This file isn't signed by Motorola and requires a unlocked bootloader to flash.
2. Bootloader I unlock has nothing to do with flashing stock firmware you can do that even with a locked bootloader it's about the edited OEM.img
3. The reason that ota updates still work with the ads removed only OEM.img is because Amazon doesn't check to see if that deleted file is there or not when updating and so the ota update still works.
Hello Tomsgt, thanks for all the help you provide. I already unlocked the bootloader, installed TWRP, installed xposed, removed the unlocked bootloader message, rooted it and have set it up the phone the way I want it, my question is, can I remove the ads on the lock screen with your tutorial without losing everything I've done already. I want to keep the Amazon apps since I do use them since I'm a Prime member I do find them useful but I really thought that the ads will not get to me and bother me but I was wrong, will I have to restart everything if I do that. Another question is that I just received and update MPJ24.139-49 https://goo.gl/photos/7bezpWNyQA4Sdgbb8 (I have MPJ24.139-48 installed) but since I''m rooted and have TWRP I can't update, if you need the update zip, where will I find it or how can I pull the zip. Thanks in advance.
Confirmed this works!
I did as instructed and spammed the check updates. Nothing... until I stuck in a sim (coincidence?)
{
"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"
}
markazali said:
Confirmed this works!
I did as instructed and spammed the check updates. Nothing... until I stuck in a sim (coincidence?)
Click to expand...
Click to collapse
boom there you go
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
munkyvirus said:
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
Click to expand...
Click to collapse
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Ultim8gamr said:
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Click to expand...
Click to collapse
thats seems to be what everyone is reporting yes. which really sucks too
munkyvirus said:
Can't seem to unlock the bootloader, Moto's site says its ineligible for bootloader unlock.
Click to expand...
Click to collapse
Ultim8gamr said:
I'm getting the same error on Amazon ad edition Moto G4 16gb model. Did Amazon reach out to moto to put a stop to this?
Click to expand...
Click to collapse
Doesn't look to be unlockable anymore. I already unlocked mine, but tried re-submitting the request, got an error saying it no longer qualifies.
However, Motorola's list of unlockable devices now says to contact Amazon CS for the Amazon models, so maybe Amazon is setting up their own system to allow BL unlock? Not sure, but at this point, it's better to spend the extra $25 to get the factory-direct version of the phone.
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
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
{
"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"
}
abdulmajed1 said:
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
Click to expand...
Click to collapse
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Device not boot
Click to expand...
Click to collapse
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Click to expand...
Click to collapse
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
No kidding? I wasn't aware of that!
Doesn't help in this situation, sadly.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
I've tried sideloading the latests ota file but then the process got aborted.
it showed: failed to verify whole file signature.
I've tried both latest stable ota " Androd 12 " and beta as well
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
I'm not able to reach oem unlocking option since it cannot boot
abdulmajed1 said:
I'm not able to reach oem unlocking option since it cannot boot
Click to expand...
Click to collapse
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Lughnasadh said:
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Click to expand...
Click to collapse
already tried sideloading different ota versions, different ports and cables as well. There's no point
Have you tried the Android Flash Tool?
I don't know if it would work since I believe locking the bootloader also disables OEM Unlocking, but it's worth a try.
hello guys
I fixed the pixel
ู:
The problem was mostly from the laptop
I used an Bugjaeger Mobile ADB - USB OTG app and install beta update from adb update recovery
thanks
***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.