***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.
Related
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Instructions for sideloading the OTA images.
Use the latest OTA image from the above link instead of using Android N OTA.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting this in a new thread so more people see it.
Get the Android N Preview OTA from here.
Google has updated the OTA zips again for nexus 9.
We've updated the OTA packages on https://developer.android.com/preview/download-ota.html. This should fix the issue with adb sideload failing at 47%. Please try again with the new packages.
Click to expand...
Click to collapse
Quote taken from here
Note: Removed Marshmallow from the tittle because it has been report to work for lollipop brick as well.
Try this if sideloading a marshmallow OTA doesn't work. See here. (Also see this link for instructions on sideloading.)
My Nexus 9 that I purchased when the device was originally put up for sale, got an OTA to 6.0.1 a few weeks back. I had not activated OEM Unlock in settings, no developer mode so I also hadn't activated USB Debugging. Well, that legit OTA ended up soft bricking my device. From that moment on, all it would ever do was show the booting screen until the battery died.
I tried manually sideloading Google's official update to 6.0.1 to the device, no go. It kept failing during the process.
I tried (knowing it likely wouldn't work) playing around with Nexus Root Toolkit to see if maybe there was some magic in there that would work, no go.
After two straight weeks of trying, I could not get an update pushed to the device and last night had resigned myself to sending it into HTC for repair... something that they weren't sure yet whether or not would incur a cost FOR ME to repair, even though in a completely stock and pristine device, the OTA update is what hosed it.
This morning, I heard that Google released sideloadable Android N images for all supported Nexus devices that some were saying would work in this scenario. (https://plus.google.com/u/0/+ArtemRussakovskii/posts/K4oUnQymMqG)
And what do you know, that totally worked. It sideloaded to my Nexus 9 and its working again.
tl;dr If you got an OTA for your Nexus and it ruined the device, and nothing else works, try to update it to N. Worked for me.
Thanks to Artem and Lenny Fudenna for the heads up.
Click to expand...
Click to collapse
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
Thanks pal. You saved my Nexus 9 LTE after 4 months of soft brick.
This is because the N OTA is a full-block/full image OTA zip that doesn't check the system partition of it's current state. It will just blindly flash. This kind of OTA image is perfect for recovering locked bootloader devices because it is signed by Google, unlike their factory images which are not signed and gets flashed like any other custom ROM.
I hope Google will provide full-block OTAs for major version releases in the future to resolve instances like this. With the requirement of enabling OEM unlocking in the new Nexus devices, full-image OTAs like these would be required to recover from failed standard OTA updates. I imagine this can happen with the monthly security update OTAs like it did with you. For those who never had an OTA fail, they never knew they were dodging bullets all those times.
For those concerned that stolen devices can be re-purposed this way, fear not. Even with a factory reset (no more user data), after flashing this OTA to get my Nexus 9 working again, it asked me to authenticate with the last owner's credentials before letting me in. So this should still deter thieves if they get a hold of a full-image-OTA thinking they can just flash a factory image with a locked bootloader. Much safer than leaving the bootloader unlocked or keeping OEM unlocking enabled.
Another reason why it's a good idea vs the old Full Factory Image method: will not delete user data.
I seriously hope the Google Android team consider releasing full-image OTAs in the future as standard practice - at least for major Android releases (no need to do this for all the minor updates - kind of like reinstalling Windows and getting all the security updates).
Creating a full-image OTA shouldn't add much to their workflow. The OTA for Lollipop to Marshmallow, for example, would have to be a full-image OTA anyways. The only thing the Android team needs to do is to disable version checking so it can be side loaded no matter what state the system partition is in.
Also, if a user wants to keep their data partition intact, a full-image OTA for the major release is important. If Google only released a single full-image OTA for the original OS the device released with (example: Lollipop), and someone needs to recover from a bad OTA update when they're already in Marshmallow, the original Lollipop build may not work with the new data partition schema.
Of course you'd be thinking "I'll just be happy the device is not bricked", but if you can also solve the "I'm glad I didn't lose any data" dilemma without much effort, why wouldn't you?
Well, I have discovered an exception to this solution .
Yesterday I set my Nexus 9 to update to the Android N Preview but when I returned I had the robot with the exclamation mark and my machine would not boot . I went through all the processes to try and get a factory image of 6.0.1 installed but had not preset my bootloader to allow an unlock.
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
And I knew why it failed. It failed because it told me that the factory image I had downloaded from the correct URL was older than the version that had failed the OTA process.
Google does not give a version date for their Android N developer images so I had concluded that they must be up-to-date.
I now realise that their image was not up-to-date so I will now have to wait for Google to publish a newer version of their Developer N factory image that is the same age or newer than the failed OTA update from yesterday so that I can successfully ADB sideload the image without getting this error .
Just as well that I have some technical knowledge or I'd be sending my Nexus 9 back to HTC for something that was not my fault.
Overall - not impressed.
Herbiv4 said:
I eventually found this article and duly downloaded the Android N developer preview factory image and then tried to ADB sideload but the process failed.
Click to expand...
Click to collapse
You don't sideload a factory image, you sideload an "OTA zip" linked in the OP or again here
corkiejp said:
You don't sideload a factory image, you sideload an "OTA.zip" linked in the OP or again here
Click to expand...
Click to collapse
Just to clarify - I was up until 3:30am this morning having been through factory images, OTA zip files, the SDK for Android, the Wugfresh Nexus Root Kit, installing Linux Mint to try and get fastboot working when my Windows PC didn't seem to want to recognise my Nexus 9. I eventually sorted out the drivers included with the SDK because the Wugfresh drivers did not play nicely with my Nexus 9. Then I realised that as my bootloader was locked I could get nowhere with restoring 6.0.1. MMB29R.
After more googling I found this webpage and the link to the OTA .zip file plus the instructions of how to force the upgrade to the developer preview of Android N. Fantastic I thought.
I did in fact download the OTA .zip file from the right URL posted above and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA earlier the previous afternoon.
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
So apologies for using the wrong phrase - it wasn't a factory image - it was an OTA .zip file and my tablet did try to send over the .zip file but it failed owing to it's age relative to the files already on my Nexus 9.
Hope that this clarifies everything.
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Herbiv4 said:
I did in fact download the OTA .zip file from the right URL and tried to sideload that file but it failed because the download was older than the files that Google sent to my Nexus 9 OTA.
Click to expand...
Click to collapse
Thanks for clarifying, Google must have sent you an Android N OTA which included the latest patch. Hopefully they will provide new OTA zips with Preview 2 in April. Which should hopefully resolve your problem. As i haven't seen a link for the latest patch OTA yet.
Herbiv4 said:
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
You could setup a change detection on that page. I use it on the factory images page all the time.
Herbiv4 said:
The bottom line is - sideloading an OTA.zip file isn't as simple as it has been made out to be.
Click to expand...
Click to collapse
I remind you of the title of this thread "Marshmallow OTA update bricked ..." which should make this process still valid for those devices. Your findings are worth posting on the Android N thread.
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
{
"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"
}
corkiejp said:
MPA44I is Marshmallow Developer Preview. Is your device bricked that long? You should have RMA'd that while in Warranty.
Please check stock recovery to see if your device reports a different build version.
Click to expand...
Click to collapse
You mean this?
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
ignaciouy said:
my tablet is bricked at "6.0/MPA44I/217251", and I have bootloader locked, OS-n/a, tried to adb sideload the zip, and It doesn't work
Can anyone help me?
Click to expand...
Click to collapse
ignaciouy said:
That long because I tried everything, and nothing worked
I can't RMA because this was a gift in USA, and I live in Uruguay. So I can't send it to usa and get another back, I think I can't do that. + I can't afford it :/
Click to expand...
Click to collapse
What error did you get when trying to sideload the Android N zip?
corkiejp said:
What error did you get when trying to sideload the Android N zip?
Click to expand...
Click to collapse
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
ignaciouy said:
First of all, thanks for replying, this is what I get
I checked the md5 of the file and it's the same of the google download page
Click to expand...
Click to collapse
You maybe looking to perform a miracle here.
Other things to check: -
Your Cable
Versions of adb and fastboot on your PC (have you got the latest).
People have reported errors when using a faulty cable.
The stock recovery on your device maybe to old to apply the Android N OTA.
I tried 3 cables, and the same with all of them.
192:volantis-npc56x ignacio$ adb version
Android Debug Bridge version 1.0.32
Revision 09a0d98bebce-android
192:volantis-npc56x ignacio$
Isn't that the last one?
The stock recovery on your device maybe to old to apply the Android N OTA.
Click to expand...
Click to collapse
And what can I do? :-|||
Herbiv4 said:
So, as I said before, I now have to wait until Google to update their OTA .zip file to a version equal to or newer than the failed OTA file from yesterday.
As Google don't give publication dates to these files I will have to regularly check that web page until new files appear when they send out a further update .zip package.
Click to expand...
Click to collapse
corkiejp said:
You could setup a change detection on that page. I use it on the factory images page all the time.
Click to expand...
Click to collapse
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Nexus 9
"volantis" volantis-ota-NPC56X-2785955f.zip
MD5: 36d813350fd660ab751a434782f5523f
SHA-1: 2785955fd77310106d2fa9f02f93b595d77b8e72
Nexus 9G
"volantisg" volantisg-ota-NPC56X-d93e161c.zip
MD5: 1fb7d83cd065a962dbed49e72db97dc4
SHA-1: d93e161c15503dc641b654f6ef4c1611222bc9fd
Click to expand...
Click to collapse
corkiejp said:
I setup a change detection on the page and google has update the OTA zip for Nexus 9.
Click to expand...
Click to collapse
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Herbiv4 said:
Hello there Corkiejp, thanks very much for doing this. I downloaded this new OTA .zip file last night and used adb sideload as instructed. The transfer got to 47% on the PC side and on the Nexus 9 side the installation started briefly before suddenly rebooting so the install fails. When booting to recovery it shows the very latest version has registered but as the install has failed it cannot boot. I have done a factory reset and tried the process again but got the same result.
I'll have to wait for the next update and I'll try process again.
Otherwise, I'll have to ask HTC to fix this for me.
Click to expand...
Click to collapse
Get the recovery logs to see where it failed and post the results in this thread.
Hello, good evening I'm having the same Issue that herbiV4; it gets till 47% then reboot and shows the android in its back and *ningun comando" (No commands) if I try to reboot, it send me once again to the recovery menu like... It doesn't have a OS? Even when it "updated" the recovery menu I really REALLY need help, I already contacted with HTC and the told me to send it but I'm from Venezuela so that's absolutely impossible for me, the Nexus has been bricked for 4 months ;---;
This is what the ADB shows me in the pc.
And this is what the tablet shows exactly after it reboot post "No error" from adb
This is the Last log, I truly dont get the "error" thingy :/
Help :crying:
If your getting error's from this process, it maybe helpful to google, to report your recovery logs to this thread.
If your device is in this state we would really appreciate logs from more devices.
1) Power off your tablet.
2) Press and hold the Volume Down button. Then, while holding Volume Down, also press and hold the Power button until the tablet turns on. (Fastboot mode)
3) Press the Volume Down button once to highlight "Recovery." Press the Power button to start in recovery mode. You'll see an image of an Android robot with a red exclamation mark. (Recover mode)
4) Press and hold down the Power button. Then, while holding Power, press and release the Volume Up button once.
5) Use the Volume Up and Volume Down buttons to navigate to "View recovery logs", and press the Power button to select.
6) There might be multiple log files. Start from "/cache/recovery/last_log" to view the log contents. Look for lines like "Finding update package...", "Opening update package...", etc. These lines indicate that the log file is for the OTA.
7) Navigate towards the end of the log using the volume buttons and look for any errors.
We are specifically interested in knowing if the bricked devices show "fsync failed: I/O error". We are exploring options to recover devices with locked bootloaders that are bricked. We'll post an update here.
Click to expand...
Click to collapse
This process has been reported to work on a bricked lollipop device.
This process has been reported to work on a bricked lollipop device.
defmetal96 said:
Hi I know this is a long shot but do you know how to fix this ^^ abort error?
Currently stuck on LRX22L but it is not booting as the OTA update to LRX22L failed for no apparent reason, foolishly my bootloader is still locked and the OEM unlock option is not checked.
is there any salvation?
Click to expand...
Click to collapse
defmetal96 said:
Sideloaded the N preview and that finally did the trick.
For anyone else with this issue I think the N preview is the only escape at present if your tablet is locked and refusing OTA updates
Click to expand...
Click to collapse
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.
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
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
Hi again
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE! (if you do it right I doubt you will but just in case) BACK UP YOUR STUFF JUST IN CASE BEFORE YOU DO THIS AS YOU WILL WIPE YOUR USERDATA!
We now have access to RETUS Android 11!
Download this (retus android 11 firmware)
unzip all files to one folder somewhere
Code:
adb reboot bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
Code:
fastboot reboot fastboot
(reboots into fastbootd)
if you have twrp installed you should enter fastbootd and first things first flash stock recovery and reboot to it to continue flashing fastbootd commands doing something like this:
Code:
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot reboot fastboot
YOU SHOULD BE IN FASTBOOTD TO FLASH THE STUFF IN THIS NEXT SECTION
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot reboot bootloader
YOU SHOULD NOW BE BACK IN BOOTLOADER TO ISSUE THESE NEXT COMMANDS
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
And then use TWRP or magisk boot patching to root your device and enjoy Android 11!
You forgot to include the bootloader in your flashing instructions. I couldn't get this to boot, finally realizing that I forgot to flash the bootloader as I was just following your list. Boots now though and I am using the retus.
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
I feel like my Bluetooth audio might not be going so hot after this, maybe just my radio in the truck though. Any Bluetooth problems for you yet?
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
whoshotjr2006 said:
I didn't flash bootloader on mine and it booted just fine. I didn't want to take more risk than I already did flashing bootloader and having something go sideways or permanently changed. I deliberately left it out of the flashing instructions but if it worked for you that's good.
Thanks for your feedback though and a good reference for anyone that needs it.
Did you try out my twrp build?
Click to expand...
Click to collapse
Yes I did and so far so good. TOUCH WORKS!! Nicely done sir!
Do you need to be unlocked for this to work?
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
thebestofall007 said:
I'm having an audio issue where when someone answers a call, I cannot hear the person on the other end, even after turning call volume all the way up. I never had this with android 10.
Maybe a bad setting perhaps, but I don't know what that setting is...
Has anyone had this happen with this retca build?
Click to expand...
Click to collapse
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network.
{
"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"
}
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Onoitsu2 said:
knowing phones in general, but one-way audio is often caused by bad VoLTE on a network. View attachment 5454283
But beyond that you may have to re-flash your radio perhaps if it didn't do it right.
Click to expand...
Click to collapse
I think I had the one way audio problem after I restored my retca setup with twrp. Retca itself doesn't seem to have this problem after I do a fresh reflash of it to my phone. Retca also doesn't have that voLTE option you show in the screenshot.
This could be TWRP not restoring something, like the radio, properly.
Edited again, removed the question I had since I found the answers after some research
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
4xc7xy said:
A little off topic but also related to this topic:
By any chance does anyone have the file for RETUS? I would like to revert back to RETUS just because with RECTA, while it works as it should when it comes to normal usage and such, it also makes some apps in my phone not be "compatible" with other apps just because the main apps (Netflix and Hulu for example) are a U.S thing. For some reason cannot be downloaded on RECTA via the Play Store. I could just download apks and call it a day but having the RETUS rom file would help just guarantee that I could download most apps I use without apk file installations. Dummy me backed up everything RETUS related for the bootloader, recovery, and so on but never backed up the rom itself or somehow lost 500 braincells and deleted the thing. (Pov: Don't be a idiot like me, always double and even take the further step of triple checking that you got everything backed up before flashing regardless of it were to work fine or not.)
I would appreciate it if someone could send me it if they have access to it.
Thanks in advanced!
Click to expand...
Click to collapse
You should be able to find it here:
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Konner920 said:
can anyone grab the update they recently pushed to this firmware? I have it on my unlocked US power 2021 ill just sideload it in recovery
nvm it just released today for US
Click to expand...
Click to collapse
I keep getting "access denied" when I try to download this from moto updates tracker.
updated op to reflect retus a11 release
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
4xc7xy said:
Since i flashed the RECTA file when the steps where here awhile ago on my RETUS device, do I have to do all these steps to boot right back into RETUS or no?
Wondering because all I really did (anyone is free to call me an idiot lol) is just test if it booted, patched the img with magisk, tested it again to see if it would have root on it, and then flash it because it had the root lmao.
Click to expand...
Click to collapse
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
You can stay with retca or flash over to retus, i figured since we actually have our own firmware files now its probably a good thing to be on retus firmware again. Whichever works for you.
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
whoshotjr2006 said:
Your not an idiot bud, tinkering is a good thing. Everything is a good learning experience
Just make sure you back up all your stuff so you dont lose it, between all the crazy flashing stuff ive done tinkering with this device (rom builds and gsis) ive got my restore process down to about 30 mins now to get it back to how i like using it
If you stay on retca you may be able to use a magisk module to change your build.prop to have it think its on the retus version so you can download netflix and such from play store with no issues. I havent tried it but its worth a shot if you dont want to back up and restore again
Click to expand...
Click to collapse
Totally agree with that view, cause I know I tested mine in exactly the same way, it boots, cool. I flashed stock recovery, booted into it, to make sure I had 100% recovery potential, then flashed the test recovery, and went from there. That's 100% how we have to muddle through learning and risking things on devices.
I think my process is down to like 10-mins because I can just restore data partition from a backup. But also have the migrate-ng app backup as well I can utilize too as a "live" backup too (https://forum.xda-developers.com/t/...20-migrate-custom-rom-migration-tool.3862763/).
And yes for this Magisk module, you want to use MagiskHide Props Config, or similar modules for that exact task, then hop into terminal to set it up once installed, and it's easy to alter many things. That's how I forced mine to be landscape as the "watch" it is, among other system tweaks.
I installed the magiskHide props config and a terminal to edit it from my phone, all I have to do to trick my device into being a RETUS is editing the fingerprints, etc. I also took screenshots from a build.prop editor app to question if they're the ones I got to edit to RETUS id's, I'll attach them with this. Sorry for asking so many questions, I'm just still new at tinkering with android phones and such still.
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
mindmajick said:
Is there any way to use this zip to update a stock system without twrp? Thank you for any response.
Click to expand...
Click to collapse
That is rather impossible, but this zip also is not flashable via twrp, so you may want to hold off on doing anything to your device until you research the process properly.