Related
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
US needs this terribly.
m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.
i could do with the Blue and Red boot logo now
Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?
Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?
Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.
So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.
Hi,
After I manually erased all the partitions on my Pixel (Sailfish) by using fastboot erase < name of the partition) on bootloader screen (please don't ask me why I did that :-| ) , I am not able to install Android 8.1 or any newer Android versios on that. I can install only Andorid 7.11 to 8.0 versions from google factory image site.
if I install 8. 1 or newer version, the device constantly reboots and sometimes stops in stock recovery or on the bootloader screen. I have tried pretty much everything with no sucess. Before erasing partitions, phone was working fine with Android 10 with December 2019 updates.
I will be ok and satisified if I can at least get Android 8.1 with July 2018 updates. Can someone please help me figure out what the heck is wrong with my device. There is no physical, or electrical damage on the device whatsoever.
Thanks.
JanuGerman said:
Hi,
After I manually erased all the partitions on my Pixel (Sailfish) by using fastboot erase < name of the partition) on bootloader screen (please don't ask me why I did that :-| ) , I am not able to install Android 8.1 or any newer Android versios on that. I can install only Andorid 7.11 to 8.0 versions from google factory image site.
if I install 8. 1 or newer version, the device constantly reboots and sometimes stops in stock recovery or on the bootloader screen. I have tried pretty much everything with no sucess. Before erasing partitions, phone was working fine with Android 10 with December 2019 updates.
I will be ok and satisified if I can at least get Android 8.1 with July 2018 updates. Can someone please help me figure out what the heck is wrong with my device. There is no physical, or electrical damage on the device whatsoever.
Thanks.
Click to expand...
Click to collapse
There is a difference and something strange, that I can't seem to grasp, between any version of Android 8.0 or prior and Android 8.1 or newer. some partition(s), checksum or a flag seems to be off...goddamnit!:crying:
JanuGerman said:
There is a difference and something strange, that I can't seem to grasp, between any version of Android 8.0 or prior and Android 8.1 or newer. some partition(s), checksum or a flag seems to be off...goddamnit!:crying:
Click to expand...
Click to collapse
Well, I was able to get a copy of persist.img from someone online and restore the /persist partition on my OG Pixel (Sailfish) and now I am able to boot into Android 10. if someone needs any help in this regard, I will be more than happy to help. Thanks. ciao
Hi all. I'm new to the Lenovo space, so please bear with me. After some searching, I can't quite seem to figure out what the model number of the P11 Plus is? Can anyone enlighten me?
Tab P11 Plus | 11" Family Tablet
Meet the Lenovo Tab P11 Plus, an Android tablet featuring an 11" 2K display and quad speakers for immersive multimedia, plus Google Kids Space and Entertainment Space for family fun and education.
www.lenovo.com
Knowing that, can this particular model's bootloader be unlocked and the OS rooted? Cheers.
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
molohov said:
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
Click to expand...
Click to collapse
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
I am thinking of buying this tab. Is it stock unlocked or is it not?
kanines said:
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
Click to expand...
Click to collapse
The answer is yes.
First, using Rescue and Smart Assist, DL the latest rom for this model this model. I used TB_J616F_S000046_220311_ROW.
Next go to C:\ProgramData\RSA\Download\RomFiles\TB_J616F_S000046_220311_ROW and you will find the boot.img files. Copy it to a folder on the tablet. Remember where.... duh.
Install Magisk 25.2 which is the version that I used. Follow Magisk instructions to "patch" the copied boot.img file. When complete, copy the patch boot image file back to your Adb/Fastboot folder, normally X:\platform-tools.
Put your tablet in fastboot mode and run: fastboot flash boot <name of patched boot.img file>.
So, there's no need to ask questions as there are a least a bizzion guides on the internet on how to do a "Magisk boot.img patch and flash".
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
every android ive unlocked bootloader, you click on the build number in settings 7 times, after aprox 3 it shows a count down until its unlocked, then it depends on the device im pretty sure, it was diff between my phone n table so it depends on ur device here is some resources
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
How To: Unlock Bootloader
How To Unlock Bootloader Galaxy A12. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
there is a diff between download mode and fastboot, just so u know, you need adb and fastboot from Androids SDK tools, you can find online, depending on ur computers OS. Also, ADB commands work with ur device on n plugged into the computer fastboot is for commands when ur in fastboot mode
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
I have the same issue!!! It seems a problem with the Fastboot mode.
19blacktiger77 said:
I have the same issue!!! It seems a problem with the Fastboot mode.
Click to expand...
Click to collapse
I solved!!!
I just had to download the latest version of ABD and Fastboot!
Hi. i rooted with this video.. it is in portuguese, but the codes are in english, 15 minutes and it´s done..
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
I've successfully rooted my Lenovo P11 Plus (J616F) tablet via the latest stock rom + Magisk 25.2, and it was much more painless than I'd thought it'd be. But I can't figure out how to get TWRP or any other custom recovery, and I'd be happy to hear if anyone has had any success with it...
HackVasant said:
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
Click to expand...
Click to collapse
Yes...
1.) Install USB drivers (I used this to detect fastboot mode: https://motorola-global-en-uk.custhelp.com/app/usb-drivers/)
>> NOTE: With your tablet in fastboot mode, you might have to go into device manager and manually update the drivers for your "unknown android device", pointing it to the usb drivers from the previous step)
2.) Install the lastest ADB and Fastboot software
3.) Unlock your bootloader!
3a.) Enable developer options -> Enable OEM unlocking
3b.) Enter fastboot mode (turn tablet off then hold power + volume up until just after it vibrates)
3c.) With your device connected to your PC, type fastboot flashing unlock in command prompt
4.) Look for the current latest stock rom TB-J616F_S240138_221026_ROW_SVC.ZIP
5.) Extract it somewhere on your PC, and copy boot.img to somewhere on your device
6.) Install Magisk v25.2 on your device
7.) Follow the rest of the installation instructions here: https://topjohnwu.github.io/Magisk/install.html
If all went well, after rebooting you might get a warning about your device being in "Orange State" and therefore cannot be trusted because the bootloader was unlocked... This is normal, and your instinct might be to run the command fastboot flashing lock to get rid of it, but THS IS A BAD IDEA because it could place your device into a "Red State" requiring you to unlock it again, effectively wiping your device
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
mingkee said:
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
Click to expand...
Click to collapse
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
SpectreCular said:
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Click to expand...
Click to collapse
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
mingkee said:
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
Click to expand...
Click to collapse
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
SpectreCular said:
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
Click to expand...
Click to collapse
Good!
I will make a backup on mine (I have Yoga 11 and practically they're the same) and unlock the bootloader and root it.
The reason why I root it so I can do adb on other device without laptop.
Actually, I have a lot of experience to root variety of machines, but what happened on Edge 2021 A12 puts me on hold on other Moto/Lenovo
I have Netflix and cable apps (Sling and Philo) and Discovery+.
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
SpectreCular said:
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
Click to expand...
Click to collapse
I have to make it clear. I have both P11 plus and Yoga 11
I have the P11 Plus J616F model and cannot get the device to unlock after many attempts with wiping device reinstalling firmware reinstalling device drivers. Does failed (unknown status code) after (bootloader) sysytem-fingerprint:Lenovo/TB-J616F/TB-J616F:12/SP1A.210812.0 mean anything to anyone. I can adb reboot recovery, from recovery I can use the keys to choose fastboot and tab goes into fastbootd and fastboot devices returns my device fashboot flashing unlock starts but ends with the failed message above. fastboot getvar all returns a bunch of information about the device but also stops with same failed message. If I choose reboot bootloader using the keys on my tab while in fastbootd tab reboots to FASTBOOT... shows up in device manager as you would expect but typing fastboot flashing unlock returns waiting for device. Any thoughts or ideas would be greatly appreciated.
Hello, Can any smart person because I'm slow lol help me get the Recovery or the Boot.img for a Motorola Edge 2021, My version is 12 (S1RMS32.48-18-11-2-3). Thanks
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
ruq said:
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
Click to expand...
Click to collapse
I understand that yes but my problem is that I don't have a laptop or PC to run the program so I'm trying to find another way to get the firmware for my Edge 2021, And if I can't do that is there any custom ROM compatible with this device that I could use to patch it with magisk?
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
ruq said:
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
Click to expand...
Click to collapse
I already solved that problem I use another phone to flash the images
ruq said:
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
Click to expand...
Click to collapse
My firmware is android 12 so would it be alright if I install this android 11 image?
Imparel said:
My firmware is android 12 so would it be alright if I install this android 11 image?
Click to expand...
Click to collapse
An android DOWNGRADE might cause issues...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
Okay I understand, I'll just take my chances and hopefully I don't brick my device...
ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
I did try it but instead of fully flashing the img I just did fastboot boot so that it would only boot into it one time and it didn't work at all so my only chance of rooting my device is using a PC to get the firmware of my phone, And thanks for the help.
Hi so today I Recieved a Motorola Moto G22 that I'd brought online.
Now upon booting the phone a number of things became apparent.
1) the stock image the phone comes with is seriously bad, from further inspection it appears google bloatware eats the ram.
2) upon thinking okay prehaps i should use a custom rom , however after many hours looking and trying diffrent things I've had no success.
So from trying many of the basic guides for unlocking motorola's bootloader, I've found an issue where i can't unlock it, when trying fastboot oem get_unlock_data
i get the following error " FAILED (remote: 'unknown command') " , I got this error with many other commands other guides suggested the only command that actually worked was "fastboot getvar all " which returned the varibles but with nothing really useful other than that the bootloader is locked.
so my question is : is it possible to unlock this thing and put better software on it?
software details which might help:
version: Moto G22 (XT2231-2} with android 12 RETGB 4GB ram 64GB space
I brought it to replace a sadly broken S9 which was working until the microphone stopped working for evering. (that and the buttons falling off)
Many Thanks in advance.
Josh
UPDATE: So after Many hours of trying to unlock I found a way to unlock the phone, however unlocking the bootloader triggers the dm-verity to loose it's mind.
for inromation if anyone is curious, I used MediaTekbootloaderunlock program which unlocked the bootloader.
So far Rooting this phone has not been anywhere near successful, i can tell they really don't want you changing the ROM.
Further Update: I have unfortunately Managed to Brick The G22 , Honestly I'd avoid this phone anyone who maybe thinking of getting this probably chose something else as the ROM it comes with is sluggish to say the least and (at least with my G22) would become unresponsive at random and lock up.
from what i can tell (and i'm no expert) they seem to really not want you to root this phone as the filesystem by default is read-only and by default you cant access certain directories either.
I`ve managed to get rid of Google bloatware on my Moto G22 using ADBAAppControl application. (https://adbappcontrol.com/en/) The phone has stock ROM and locked bootloader, as well.
janokv said:
I`ve managed to get rid of Google bloatware on my Moto G22 using ADBAAppControl application. (https://adbappcontrol.com/en/) The phone has stock ROM and locked bootloader, as well.
Click to expand...
Click to collapse
i wish i knew of this before i managed to brick mine, the hardware is good but the software is absolutely crap as far as i know.
HI GUYS I FOUND A WAY TO FLASH GSI IMAGE ON MOTO G22
now its better than moto edge 20
I WILL POST A TUTORIAL ON FLASHING ANY GSI ANDROID 12 ABOVE FOR THIS DEVICE
THERE ARE NO BUGS AS IHAVE FLASHED ON STOCK MOTO VENDOR
THE STEPS ARE PRETTY EASY IF YOU KNOW TO USE ANDROID SDK COMMANDS
THE FIRST STEP WILL BE TO DOWNLOAD LATEST ANDROID SDK (PLATFORM TOOLS)
THEN YOU HAVE TO DOWNLOAD THE GSI ANY GSI WILL WORK ABOVE ANDROID 12 FOR THIS I HAVE CHOSEN https://forum.xda-developers.com/t/gsi-unofficial-12-pixel-experience.4354695/
YOU COULD ALSO USE ANDROID 13 GSI BUT IT IS BIT LAGGY
AFTER DOWNLOAD IS DONE OPEN CMD ON YOUR PLATFORM TOOLS FOLDER AND USE THE COMMANDS GIVEN BELOW
fastboot devices
fastboot set_active a
fastboot flash product product_gsi.img
fastboot erase system
fastboot flash system system.img
after it is done reboot your phone
use the product image given here otherwise you will get error
you can get a message to format your device dont worry and just format it , also use fastbootd for the gsi flash
Now you will experiance some lag in system ui but dont worry just open settings select phh treble settings then misc features and there you will see the option force fps click on it and select [email protected] this will set the refresh rate to 90 and boom the phone will work smooth like a butter
gsi image
:note this will only work if have unlocked bootloader and use fastbootd to flash the gsi
Does this fix the stock UI lag? Even though it's on 90Hz I experience great lag. The app launches are slow and stutter. Does this image support fingerprint scanner, NFC tap to pay Google wallet, Netflix?
MAKEN7666 said:
gsi image
Click to expand...
Click to collapse
AndroSanDev said:
Does this fix the stock UI lag? Even though it's on 90Hz I experience great lag. The app launches are slow and stutter. Does this image support fingerprint scanner, NFC tap to pay Google wallet, Netflix?
Click to expand...
Click to collapse
yes the system ui wont lag after setting the refresh rate to 90 and everything is working perfect because it is stockk motorola vendor
the gsi is far better than the stock rom i got improvement in performance and increase in fps in games like mcpe and cod
Joshch96 said:
Hi so today I Recieved a Motorola Moto G22 that I'd brought online.
Now upon booting the phone a number of things became apparent.
1) the stock image the phone comes with is seriously bad, from further inspection it appears google bloatware eats the ram.
2) upon thinking okay prehaps i should use a custom rom , however after many hours looking and trying diffrent things I've had no success.
So from trying many of the basic guides for unlocking motorola's bootloader, I've found an issue where i can't unlock it, when trying fastboot oem get_unlock_data
i get the following error " FAILED (remote: 'unknown command') " , I got this error with many other commands other guides suggested the only command that actually worked was "fastboot getvar all " which returned the varibles but with nothing really useful other than that the bootloader is locked.
so my question is : is it possible to unlock this thing and put better software on it?
software details which might help:
version: Moto G22 (XT2231-2} with android 12 RETGB 4GB ram 64GB space
I brought it to replace a sadly broken S9 which was working until the microphone stopped working for evering. (that and the buttons falling off)
Many Thanks in advance.
Josh
Click to expand...
Click to collapse
You we’re getting unknown command error because you were using normal fast boot use fastbootd to open it enter fastboot select recovery after few sec you wil see no command then hold and press repeatedly volume up and power button after that the recovery will appear then select enter fastboot then give commands it will work
thanks for posting this tutorial I successfully installed android 13 pixel gsi on my Moto g22 it’s way much better than the stock rom
I'm getting this error
platform-tools> ./fastboot set_active a
(bootloader) version-bootloader:0x0923
(bootloader) unlocked:yes
fastboot: error: Device does not support slots
Arthursmithlik said:
You we’re getting unknown command error because you were using normal fast boot use fastbootd to open it enter fastboot select recovery after few sec you wil see no command then hold and press repeatedly volume up and power button after that the recovery will appear then select enter fastboot then give commands it will work
Click to expand...
Click to collapse
please explain how to unlock the bootloader, because I've done everything and I can't unlock it.
Vinniciusf said:
please explain how to unlock the bootloader, because I've done everything and I can't unlock it.
Click to expand...
Click to collapse
I managed to unlock the bootloader through this video (
) and I installed the pixel and I liked it
I was able to unlock bootloader and install Android 13 gsi. I had to delete and recreate partitions since the stock system partition size was not sufficient for gsi 13 build.
Its smooth and great but gsi images are bare minimal and the stock dialer app is not working properly. It doesnt show the inprogress call and hence cant end it.
Is there a way to download a stable custom gsi like maybe pixel experience and install it? I tried to download a img file from an unofficial source and sideload it but it fails. Also is there a working twrp build that I can flash for moto g22?
MAKEN7666 said:
:note isso só funcionará se tiver desbloqueado o bootloader e usar fastbootd para piscar o gsi
Click to expand...
Click to collapse
amigo, você poderia colocar o link de download desta versão de 12 pixels?
AndroSanDev said:
I was able to unlock bootloader and install Android 13 gsi. I had to delete and recreate partitions since the stock system partition size was not sufficient for gsi 13 build.
Its smooth and great but gsi images are bare minimal and the stock dialer app is not working properly. It doesnt show the inprogress call and hence cant end it.
Is there a way to download a stable custom gsi like maybe pixel experience and install it? I tried to download a img file from an unofficial source and sideload it but it fails. Also is there a working twrp build that I can flash for moto g22?
Click to expand...
Click to collapse
i tried setting refresh rate to 90 on gsi and its good now and you could easily resize the partition by just flashing the product image . currently iam working on twrp for this device i tried to patch magisk but failed . you could try the linage os gsi or phh treble they provide updates so i suggest phh treble