Question Is it possible to lock or relock it after unlocking the bootloader? - OnePlus 11

Does anyone know, I still have a STOCK system, without unlocked bootloader (and without root).
I uploaded the boot files extracted from "payload.bin" (init_boot, boot, vendor_boot) to it and patched it in Magisk.
In theory, Magisk reported no bugs during patching.
And here's the key question: is it safe to try to boot (not flash) OP11?
Of course, after unlocking the bootloader.
If after booting without flash it turns out that some functions do not work (screen brightness, changing colors, PIN locks, etc.), just restart OP11 and everything should return to the state before "boot".
Is it possible to lock or relock the bootloader later so that banking applications, contactless payments, etc. work?
regards
f.

qriozum said:
Does anyone know, I still have a STOCK system, without unlocked bootloader (and without root).
I uploaded the boot files extracted from "payload.bin" (init_boot, boot, vendor_boot) to it and patched it in Magisk.
In theory, Magisk reported no bugs during patching.
And here's the key question: is it safe to try to boot (not flash) OP11?
Of course, after unlocking the bootloader.
If after booting without flash it turns out that some functions do not work (screen brightness, changing colors, PIN locks, etc.), just restart OP11 and everything should return to the state before "boot".
Is it possible to lock or relock the bootloader later so that banking applications, contactless payments, etc. work?
regards
f.
Click to expand...
Click to collapse
I don’t have an answer to your question, but thought I would share that I got my OP11 yesterday. I updated to the latest ÔTA version, A.07. I then unlocked the bootloader and rebooted without issue. I am now looking to root, but not sure exactly how to get the files you mentioned. Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.

azsl1326 said:
I don’t have an answer to your question, but thought I would share that I got my OP11 yesterday. I updated to the latest ÔTA version, A.07. I then unlocked the bootloader and rebooted without issue. I am now looking to root, but not sure exactly how to get the files you mentioned. Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.
Click to expand...
Click to collapse
It is unbelievable that you have unlocked a bootloader and you have no problem with the pin/impression/blockade.
Here, two users say that they have a problem: https://forum.xda-developers.com/t/screen-lock-setup-crashing-unlocked-bootloader-rooted.4554073/
What is your OP11 version you unlocked?

azsl1326 said:
Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.
Click to expand...
Click to collapse
I used dumper to unpack "payload.bin":
Releases · ssut/payload-dumper-go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
After starting it, "payload.bin" will unpack the commands and you will have system partition images in the subdirectory.
Here two methods of obtaining root on OP11
Root OnePlus 11 via Magisk Patched Init_Boot/Boot
In this comprehensive guide, we will show you the detailed steps to root your OnePlus 11 via Magisk patched boot.img.
www.droidwin.com

qriozum said:
It is unbelievable that you have unlocked a bootloader and you have no problem with the pin/impression/blockade.
Here, two users say that they have a problem: https://forum.xda-developers.com/t/screen-lock-setup-crashing-unlocked-bootloader-rooted.4554073/
What is your OP11 version you unlocked?
Click to expand...
Click to collapse
I did see that but have had zero issues. Here's the version I am running.

qriozum said:
I used dumper to unpack "payload.bin":
Releases · ssut/payload-dumper-go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
After starting it, "payload.bin" will unpack the commands and you will have system partition images in the subdirectory.
Here two methods of obtaining root on OP11
Root OnePlus 11 via Magisk Patched Init_Boot/Boot
In this comprehensive guide, we will show you the detailed steps to root your OnePlus 11 via Magisk patched boot.img.
www.droidwin.com
Click to expand...
Click to collapse
Thank you!!! Did you unpack the payload.bin file on your android device or on a computer?

azsl1326 said:
Thank you!!! Did you unpack the payload.bin file on your android device or on a computer?
Click to expand...
Click to collapse
Unpacked on the computer.
Your model is 2451, i.e. the American version.
If I associate it well, then for your model there is only an incremental OTA, there is no fullOTA.
But I can be wrong.

I just got my American version through Amazon and I'm confused do we patch boot.img or init_boot.img now for root. And as for Amazon they ended up screwing people with the presale I payed 799.99 with a 100 dollar gift card today it lists for 699.99 so they essentially forced people to buy a gift card they didn't need even on checkout they were both itemized separate. I did manage to get them to refund the extra 100 though which was fine but I didn't like being cheated. The funniest part was when Amazon asked me instead of refunding me to my card if I wanted a gift card instead

scottlam1 said:
I just got my American version through Amazon and I'm confused do we patch boot.img or init_boot.img now for root. And as for Amazon they ended up screwing people with the presale I payed 799.99 with a 100 dollar gift card today it lists for 699.99 so they essentially forced people to buy a gift card they didn't need even on checkout they were both itemized separate. I did manage to get them to refund the extra 100 though which was fine but I didn't like being cheated
Click to expand...
Click to collapse
Patch init_boot.img for root

CoinsClassic said:
Patch init_boot.img for root
Click to expand...
Click to collapse
So to test I can type fastboot boot init_boot.img

scottlam1 said:
So to test I can type fastboot boot init_boot.img
Click to expand...
Click to collapse
This is not working, init_boot.img cannot be booted directly. So you can just flash it using "fastboot flash init_boot your_init_boot.img".

@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!

Swap_File said:
@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!
Click to expand...
Click to collapse
init_boot.img · qssi-user-13-TP1A.220905.001-1673015136383-release-keys--US · Android Dumps / oneplus / op594dl1 · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
CPH2451

Swap_File said:
@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!
Click to expand...
Click to collapse
It's still factory sealed I'm just reading and learning now being cautious because I don't have msm to save my ass anymore.

CoinsClassic said:
init_boot.img · qssi-user-13-TP1A.220905.001-1673015136383-release-keys--US · Android Dumps / oneplus / op594dl1 · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
CPH2451
Click to expand...
Click to collapse
This prob isn't answered yet but if we patch init boot how would ota survival work on magisk because it patches boot img in other slot. Is that something the magisk dev might have to implement in the future. I know the dev works for Google but they still let him keep the magisk project

scottlam1 said:
This prob isn't answered yet but if we patch init boot how would ota survival work on magisk because it patches boot img in other slot. Is that something the magisk dev might have to implement in the future. I know the dev works for Google but they still let him keep the magisk project
Click to expand...
Click to collapse
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.

CoinsClassic said:
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.
Click to expand...
Click to collapse
Ok I use the public magisk on my 8t never played around with the canary builds

CoinsClassic said:
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.
Click to expand...
Click to collapse
Friend, you really unlocked the European model, then you root and you have a screen lock/pin/fingerprint?
Automatic screen brightness?
Changing color mode also works?
I inquire, because as a colleague above I try to be careful, I don't have enough money to buy another copy.
In the neighboring thread of two users, he claims that the European version (2449) after the very unlocking of the bootloader allows them to set the PIN/screen lock - so no banking applications will work :/

qriozum said:
Friend, you really unlocked the European model, then you root and you have a screen lock/pin/fingerprint?
Automatic screen brightness?
Changing color mode also works?
I inquire, because as a colleague above I try to be careful, I don't have enough money to buy another copy.
In the neighboring thread of two users, he claims that the European version (2449) after the very unlocking of the bootloader allows them to set the PIN/screen lock - so no banking applications will work :/
Click to expand...
Click to collapse
I am the owner of this thread It's true, I cannot set any lock screen password/pin/fingerprint, etc.
I may need to try relocking and unlocking bl few more times, according to some users that should do the trick.

CoinsClassic said:
I am the owner of this thread It's true, I cannot set any lock screen password/pin/fingerprint, etc.
I may need to try relocking and unlocking bl few more times, according to some users that should do the trick.
Click to expand...
Click to collapse
Got an odd question does your camera glass have almost like a particle affect to it around the camera lenses but not on the lenses that's clear I hope I didn't get a defective phone would be a pain in ass to have to return

Related

Need Rooted patched image after 10.0.7 aka 10.0.3

Just Updated to 10.0.7 via full ota update lost root access
mytechtb said:
Just Updated to 10.0.7 via full ota update lost root access
Click to expand...
Click to collapse
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.
Kirahvi said:
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.
Click to expand...
Click to collapse
I'd like to agree with u on that second part but it keeps telling me path not found sadly...not sure what I'm doing wrong got the image in c drive in my atform tools and still happening read the instructions 10 plus times myself. I've actually had to do the same process on my xiaomi a2 lite and worked easily but not this time for OnePlus
rob420p said:
I'd like to agree with u on that second part but it keeps telling me path not found sadly...not sure what I'm doing wrong got the image in c drive in my atform tools and still happening read the instructions 10 plus times myself. I've actually had to do the same process on my xiaomi a2 lite and worked easily but not this time for OnePlus
Click to expand...
Click to collapse
Do you have some data plan with your carrier? Just boot a patched boot.img from the previous OOS version. WiFi will not work but you can still use LTE to direct install magisk then reboot.
Kirahvi said:
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.
Click to expand...
Click to collapse
so cold time FYI i did downloaded the ota file and patched it with magisk and flashed through the cmd...but i didnt worked at all even i cant able to boot my device until i flash stock boot
morback said:
Do you have some data plan with your carrier? Just boot a patched boot.img from the previous OOS version. WiFi will not work but you can still use LTE to direct install magisk then reboot.
Click to expand...
Click to collapse
Thanks I'll give it a try that way I have unlimited data luckily
mytechtb said:
so cold time FYI i did downloaded the ota file and patched it with magisk and flashed through the cmd...but i didnt worked at all even i cant able to boot my device until i flash stock boot
Click to expand...
Click to collapse
Did you remember to tick the "Preserve AVB 2.0/dm-verity" when patching the boot image in magisk?
This method work for me https://www.reddit.com/r/oneplus/co...twrp/?utm_medium=android_app&utm_source=share
One plus 7t pro McLaren 10.0.6 update to 10.0.0.7 without lose root privileges

all about official firmware and where to find it

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.

Question I'm very overwhelmed please help

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
/boot​This 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
/recovery​This 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.

Question How to root this phone?

HI
I got gifted a Moto G30 and I was wondering if is possible to root it. I've had previous phones that I'd rooted. I looked for a tutorial in this forum but i couldn't find nothing. Can someone help me?
Install the Magisk app
Fetch the boot.img from your stock rom (can be found on lolinet)
Patch it using the Magisk app
Unlock Bootloader (backup first)
Flash the patched boot.img to both boot_a and boot_b.
Kuntitled said:
Install the Magisk app
Fetch the boot.img from your stock rom (can be found on lolinet)
Patch it using the Magisk app
Unlock Bootloader (backup first)
Flash the patched boot.img to both boot_a and boot_b.
Click to expand...
Click to collapse
Can I root my G30 with that way if is the XT2129-2 version?
Can I root my phone with SuperSU instead?
Can I do this: unlock bootloader - flash TWRP - root with magisk via TWRP?
Evedammo said:
Can I root my G30 with that way if is the XT2129-2 version?
Click to expand...
Click to collapse
Yes. I have the XT2129-2 6/128GB variant and the instructions provided work as expected. Note well that subsequent updates will fail verification and will have to be installed manually from the point of root onwards.
Evedammo said:
Can I root my phone with SuperSU instead?
Click to expand...
Click to collapse
No, this device requires a systemless root at this point due to the way /system is mounted. You will also require Magisk's systemless hosts module if you wish to use AdAway or similar.
Evedammo said:
Can I do this: unlock bootloader - flash TWRP - root with magisk via TWRP?
Click to expand...
Click to collapse
There is no TWRP image available for this device yet. The closest match by SoC/config is Cebu but you are strongly advised not to attempt flashing a different device's TWRP as this may lead to a brick, dead kittens and rifts in the spacetime continuum, not to mention standing an ice-cube's chance in Hell of working. The reason I mention Cebu is that a future release for CapriP isn't altogether impossible. In the meantime, Magisk systemless root is your one and only friend.
One last caveat: Do not, under any circumstances, attempt to replace GSF/Play Store with MicroG on this device, including using Magisk modules. It is currently practically impossible to patch the framework for signature spoofing.
Chron0s said:
Yes. I have the XT2129-2 6/128GB variant and the instructions provided work as expected. Note well that subsequent updates will fail verification and will have to be installed manually from the point of root onwards.
No, this device requires a systemless root at this point due to the way /system is mounted. You will also require Magisk's systemless hosts module if you wish to use AdAway or similar.
There is no TWRP image available for this device yet. The closest match by SoC/config is Cebu but you are strongly advised not to attempt flashing a different device's TWRP as this may lead to a brick, dead kittens and rifts in the spacetime continuum, not to mention standing an ice-cube's chance in Hell of working. The reason I mention Cebu is that a future release for CapriP isn't altogether impossible. In the meantime, Magisk systemless root is your one and only friend.
One last caveat: Do not, under any circumstances, attempt to replace GSF/Play Store with MicroG on this device, including using Magisk modules. It is currently practically impossible to patch the framework for signature spoofing.
Click to expand...
Click to collapse
I've read there's a TWRP for this phone here https://www.getdroidtips.com/twrp-recovery-motorola-g30/
I haven't tested it yet bc I haven't rooted my phone
Evedammo said:
I've read there's a TWRP for this phone here https://www.getdroidtips.com/twrp-recovery-motorola-g30/
I haven't tested it yet bc I haven't rooted my phone
Click to expand...
Click to collapse
I wouldn't reccommend doing that.
Kuntitled said:
I wouldn't reccommend doing that.
Click to expand...
Click to collapse
Ok, i'll wait then until I see some thread here about TWRP for this model. Ty for the help, I'll root my phone without problem
Evedammo said:
I've read there's a TWRP for this phone here https://www.getdroidtips.com/twrp-recovery-motorola-g30/
Click to expand...
Click to collapse
Highly suspect:
"The Moto G30 features a 6.7-inch IPS LCD panel with support for HDR10. It has a resolution of 1080 x 2400 pixels and an aspect ratio of 20:9. The phone features the new Qualcomm Snapdragon 750G"
The XT2129-2 is 1600x720 and has a Snapdragon 662 chipset. Don't walk away, run.
sorry for the dumb question, just wanted to ask if the 4 GB version is rootable too.
Chron0s said:
Highly suspect:
"The Moto G30 features a 6.7-inch IPS LCD panel with support for HDR10. It has a resolution of 1080 x 2400 pixels and an aspect ratio of 20:9. The phone features the new Qualcomm Snapdragon 750G"
The XT2129-2 is 1600x720 and has a Snapdragon 662 chipset. Don't walk away, run.
Click to expand...
Click to collapse
why? I know the 662 has slightly lower performance than other chipset/phones on the same price range, but it should be good enough for everything except games (I don't play games on phones).
All variants are rootable using the Magisk systemless ramdisk method.
What I meant was run from that fake TWRP before you end up with an unrecoverable recovery flash. The specs for the "Moto G30" that site was advertising a TWRP for were completely wrong. There's nothing at all wrong with the G30; there's everything wrong with false information that can harm your device.
agreed, and thanks fo the clarification

Question Help me understand GIS for Xperia 10 III

I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.

Categories

Resources