Related
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?
abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b
michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/
I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?
abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!
CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools
Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms.
First of all, there seem to be multiple regions that have different firmware’s, and there seem to be different software channels per region or per region per provider. ( for instance vfeu vs reteu )
The phone model is XT2041-X where the X can stand for 1 to 4
The development name / moto name is called: Sofiar ( XT2041-1/3)
the development name for the US name is: Sofia ( xt2041-4 )
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Manual selection of firmware sources:
So far, every source on the internet points to the lolinet mirror
see https://mirrors.lolinet.com/firmware/moto/sofiar/official/
US version: https://mirrors.lolinet.com/firmware/moto/sofia/official/
a 2nd source would be the moto updates tracker, but I expect that everything you find here Will appear on lolinet
US: https://t.me/s/MotoUpdatesTracker?q=#sofia
The rest of the world: https://t.me/s/MotoUpdatesTracker?q=#sofiar
so far I have not been able to find any other sources. I hope this helps a bit in downloading / finding the stock firmware for your phone.
If you find any other / better source, please let me know, I'll add it to this first post.
Thanks
I successfully updated mine and regained root.
I will post manual update guide later.
A side note: the following must be flashed in fastbootd (fastboot reboot fastbootd or adb reboot fastboot)
boot.img, recovery.img, vbmeta.img, super, dtbo.img
@mingkee Pls can you share manual update guide? THX
endva3 said:
@mingkee Pls can you share manual update guide? THX
Click to expand...
Click to collapse
There's a simple method using LMSA rescue method, but make sure you backup your phone because your phone will be wiped during the process.
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
quangtran1 said:
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
Click to expand...
Click to collapse
You may have patched unmatched build number.
Solution: flash full ROM
LMSA rescue is the simplest method but it will wipe the phone
Thanks! That was what I ended up doing.
Is it possible to change fw xt2041-3 (PAHF0004PL) to XT2041-3 (PAHF0006GB)? I'm on the PL version (andoid security January 2020) and the GB version is May 2020. If possible, the bootloader must be unlocked? Can it be changed via any tool (mototool) or via adb commands?
Anyone have the boot.img for QPMS30.80-51-3?
I cant download the latest May update from their server. Some reason the link to download expired a few days after. So if anyone has another link or can just hook it up with the boot.img please
I couldnt get it with the rescue app either it was a lower version.
EDIT
Found it here
https://forum.xda-developers.com/showpost.php?p=82865201&postcount=73
Some lessons learned
pjottrr said:
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Click to expand...
Click to collapse
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Mikael1013 said:
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Click to expand...
Click to collapse
Switching from a carrier rom to an unlocked version won't SIM unlock a phone (at least not to my knowledge), if that's your objective. But if you're looking to switch the retail flavor rom, try RETUS, specifically XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
rlrevell said:
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Click to expand...
Click to collapse
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
TNS201 said:
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
Click to expand...
Click to collapse
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
CodyF86 said:
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
Click to expand...
Click to collapse
Do you have stock boot IMG by any chance? Thx in advance
freddienuxx said:
Do you have stock boot IMG by any chance? Thx in advance
Click to expand...
Click to collapse
sofia_80-51-3boot.img
CodyF86 said:
sofia_80-51-3boot.img
Click to expand...
Click to collapse
Thx man
rlrevell said:
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
Click to expand...
Click to collapse
yea when you are in bootloader with phone attached to the PC it should work
It worked on my pixel 2 xl and this phone
Does anybody have this file available? (Sorry for the spaces, I can't post a link...). The download link has expired.
t.me /motoupdatestracker/ 2752
filename: SOFIA_RETAIL_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What's the difference between that and RETUS on lolinet? Is there any? Reason I'm asking is that I don't have any radios after that OTA (Google Fi) and flashing the boot.img from RETUS QPMS-30.80-51-5.
I tried unsuccessfully to install TWRP on a Xiaomi Redmi Note 8 Pro.
These are the steps I took:
Unlock the bootloader with MiUnlock.
Downloaded Fastboot.
Copied this CFW TWRP inside the Fastboot folder.
Downloaded these two files and copied inside the Fastboot folder.
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
And the result is that it no longer turns on. It also fails neither to enter the Fastboot screen, nor in that of recovery.
Windows no longer sees the device, so I can't interact in any way even with the folders inside the phone memory. Finally it is not even seen by Xiaomi Flash Tool (wanting to try to reinstall the official ROM).
The phone, immediately after unlocking it with the Xiaomi tool, had MIUI 12. I don't know which Android mounted (my fault), but I proceeded the same, without doing a downgrade, since in a discussion here on the forum it seemed that it could work same, even without downgrading to Android 9.
Is there any way to fix?
Maybe using Linux, you might be able to interact with the phone memory even if it is turned off / bricked?
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Only if you have flashed it with a CFW
Angry Unlocker said:
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
I had the same problem
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Thanks for your answers!
kingsemperor said:
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
Click to expand...
Click to collapse
I am not quite clear what you mean exactly, but I, before proceeding with trying to flash a custom ROM, I had connected my original Xiaomi account to the device in question and also had requested the unlocking of the bootloader through the appropriate Xiaomi software (and I finally waited the time indicated by them, before proceeding). So on my Note 8 Pro there was actually the original / official MIUI updated to the latest version and I didn't need to proceed with a payment of any kind following that tutorial.
chumpokemon said:
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Click to expand...
Click to collapse
Thanks for your suggestion, but I have already solved it by following precisely that video.
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Perike said:
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Click to expand...
Click to collapse
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
chumpokemon said:
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
Click to expand...
Click to collapse
Flashed successfully, but the result is a reboot and This Miui version cant be installed on this device...
Angry Unlocker said:
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Why does it say "this video is private" ?
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/bootThis is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recoveryThis is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[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
Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.
Has anyone got a factory image of the moto g30? To flash and get rid of stupid android 12! Doesn't matter particularly if its not android 11, I'll be able to upgrade. I take it flashing an old image mean's it'll include moto's software and stuff. Would rather not have a rooted device as I don't want to miss out on features.
You people and your unwillingness to get used to change. lol
But anyway, you can go back to A11 granted you unlock your bootloader and flash the firmware while you make sure it matches your software channel.
The firmware can be found on lolinet.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Thanks for your quick reply, honestly wouldn't have though it would be such a big deal but its stressing me tf out! How would one know which software channel one is?
Ed_Silver said:
Thanks for your quick reply, honestly wouldn't have though it would be such a big deal but its stressing me tf out! How would one know which software channel one is?
Click to expand...
Click to collapse
Actually dont worry about that, worked it out
I saw on another thread that some people were struggling to unlock the bootloader... do you know how to circumvent that?
I had no issues when just following unlock instructions, and anyway, with a locked bootloader you CAN'T mess anything up (though you can delete all user data, which you'd do when manually flashing an image anyway)
Ah I hope I don't run into any problems! Have you got a link to your instructions? Otherwise I'll use
but with the g30 image ive downloaded
So my platform tools doesn't include a "flash-all.sh" and the "fastboot flashing unlock" command seems to do nothing except wait for the device. Any help would be greatly appreciated!
Ed_Silver said:
So my platform tools doesn't include a "flash-all.sh" and the "fastboot flashing unlock" command seems to do nothing except wait for the device. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Just follow Motorolas official guide. It's easy enough for you to understand.