Mod was already available for the Pixel2.
If you don't know what Edge Sense Plus is, you can check it here: https://forum.xda-developers.com/pixel-2/themes/root-custom-active-edge-actions-edge-t3732368
Just curious but do we know it can be rooted?
krabman said:
Just curious but do we know it can be rooted?
Click to expand...
Click to collapse
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Will get pixel 3xl by November 8 9. I am willing to test it for you.
ill have mine by 18th or 19th ill help out if still needed.
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
j to the 4n said:
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
WisdomWolf said:
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
Click to expand...
Click to collapse
Doing this would be extremely unwise without a copy of the stock boot image. I would advise you to wait till the factory images come out. Which should be soon. If you bootloop, highly likely, you will have a unusable phone until the factory images get posted.
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Sent from my Pixel 2 XL using Tapatalk
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
WisdomWolf said:
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Click to expand...
Click to collapse
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
I have mine. I'm willing to test whatever/whenever it's safe to do so.
I did enable the "OEM Unlocking" in the developer settings. It didn't come with a USB-C to USB -A cable, so I cannot connect it to a PC anyway.
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Golf c said:
Your phone comes with a boot image.
Click to expand...
Click to collapse
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
lensgrabber said:
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
Click to expand...
Click to collapse
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
sd_matto said:
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
Click to expand...
Click to collapse
There is no "standalone" boot image yet. It comes with factory image. Which should be out soon. The boot image is in your device. You can patch the boot image with Magisk Manager or sideload the Magisk zip. I would not do either of those until you have the factory image. If you bootloop, your device will be useless without factory images
mattj949 said:
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
Click to expand...
Click to collapse
Did you use the "unlock_critical" version of the command or just "unlock"?
Golf c said:
You can patch the boot image with Magisk Manager.
Click to expand...
Click to collapse
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
sd_matto said:
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
Click to expand...
Click to collapse
No 2 the boot image in the device. Unlock bootloader.
Download Magisk Manager apk. Im about ready to unlock mine right now. In Magisk Manager select patch boot image file. It will save a copy to your device. Transfer to PC.
Fastboot flash boot image. You will bootloop im sure. AVB has changed with crosshatch.
DO NOT attempt this without factory image.
I will be doing this when factory image comes out.
nirenshah said:
Did you use the "unlock_critical" version of the command or just "unlock"?
Click to expand...
Click to collapse
Just "unlock" the other one is not valid for this one. Sorry, I should have mentioned that!
My apologies gentlemen. You do need a separate copy of the the boot image from the factory image to patch in Magisk Manager. Sorry for the wrong info. Actually it makes sense doesn't it.
Golf c said:
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
Click to expand...
Click to collapse
I got my Pixel 3XL last night. Excited to get things going on the Pixel 3XL, coming from a Nexus 6P.
I was sad that the factory image isn't immediately available on google's site for this phone, and I don't want to brick it trying to install Magisk without a factory image to fall back onto.
In any case, woot, woot! Phone looks great and I'm going to transfer over my line today.
Cheers,
B.D.
Related
Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running
The real question is kernel source. Not much reason to unlock the bootloader without that.
Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?
I have the update waiting to be installed.
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?
So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app
canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.
In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk
Thanks buddy! It worked
i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize
I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.
Rooted Verizon Pixel 2: "There's an internal problem with your device. Contact ..."
I rooted my Verizon Pixel 2 running 8.1 and whenever I boot it up and I'm on the lock screen, I get this error: ""There's an internal problem with your device. Contact your manufacturer for details" Anyone know how to get rid of it?
I found this for a Nexus6p, but I'm not sure it'd work for a Google Pixel 2 (Verizon): https://forum.xda-developers.com/showpost.php?p=64289509&postcount=8
You have to re flash the stock boot image and dtbo image.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
On both slots.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
---------- Post added at 01:30 AM ---------- Previous post was at 01:21 AM ----------
iamnotreallyhere said:
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
Click to expand...
Click to collapse
Also you may not have to reflash the stock boot image just dtbo. If you are using a custom kernel make sure to flash that dtbo.
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Lightn1ng said:
On both slots.
Click to expand...
Click to collapse
I did this. Curious though.. @Shadow/Walker doesn't mention doing it...is it important?
I downgraded to Magisk 15.1 because of this issue. 15.2 doesn't bring this error.
upperbladez said:
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Click to expand...
Click to collapse
Glad you figured it out! I was going to say it's in the second zip file within the first zip file. Also I don't think there is a way to brick unless you lock your boot loader. As long as you can fastboot and have an unlocked bootloader you should be able to recover from anything. Never ever ever lock your bootloader ever again
Just ignore the message, it's just a security warning because of what Magisk is patching to enable systemless mods on the vendor partition. I doesn't affect anything.
Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch
Doubtful being that the article's date is from May...
jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!
Fake News...
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk
bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?
Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated
TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.
I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.
Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs
I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Factory images are up
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse
I think I can still cancel my order but I''m hopeful it wont come to that.
Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time
Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
My understanding is it won't work on Android 10.
androiddiego said:
My understanding is it won't work on Android 10.
Click to expand...
Click to collapse
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
It sounds like they'll get there, just not quickly. If you read that link closely, this seems to apply to all phones shipped with android 10. So jumping to another phone is not necessarily a solution.
does anyone with a Moto G Stylus have a working stock recovery?
fronto said:
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
Click to expand...
Click to collapse
Did u unlock the bootloader
Sent from my moto g stylus using Tapatalk
When you go into recovery hit the + and - volume buttons together and it will pop up.
Yes their is recovery software. It's rescue mode.
fronto said:
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/mcp/service
twrp
why do you need a recovery when you can unlock the bootloader and use the factory recovery to flash what ever you want and they have a nice recovery option using the rescue and smart assistant software for pc mac or lin. i fail to see why you would want a custom recovery.
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
DMedina559 said:
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
Click to expand...
Click to collapse
How did you root? Are there instructions somewhere for Android 10 root?
cyrusalmighty said:
How did you root? Are there instructions somewhere for Android 10 root?
Click to expand...
Click to collapse
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
DMedina559 said:
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
Click to expand...
Click to collapse
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
I haven't kept up with the android modding scene for years so I'm kinda out of the loop, but the general rule of thumb is to not do ota updates unless you're flashing full images with fastboot or using an OEM recovery software (Lenovo\Moto have one here)
As for the patch, I got the boot.img from the recovery software I linked above and installed magisk manager on my phone to patch the img which I then moved to my laptop to flash in fastboot
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
Hi,
First download Rescue and Smart Assistant from Motorola website, make sure activate the developer options and usb debugging and download your phone's software with Rescue and Smart Assistant (it will find it automatically), find boot.img from inside the downloaded zip file and copy it to your phone, download Magisk Manager to your phone, and patch the boot.img with Magisk Manager, copy patched boot.img to your computer and flash it with adb.
If you have a desire to get TWRP, you should write to Telegram @mauronofrio and raise some donate to develop TWRP for this device.
Root Moto g stylus
fronto said:
does anyone with a Moto G Stylus have a working stock recovery?
Click to expand...
Click to collapse
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Luiszipatla said:
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Click to expand...
Click to collapse
Same issue, I've had the same provoking anger problem with this phone and previously a Moto e5 plus. It's rooted yet no Magisk module seems to work. This phone I can't even get lucky patcher to work. Android 10 sucks, I miss the good old days of Android 6 and 7.
Anyone else notice the modules not working at all but it's rooted?
Also to do a backup, adb backup and adb restore are your friends.
Rooted you can clone the device at least with adb commands. Slower but it's an exact copy at least.
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
vache said:
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
Click to expand...
Click to collapse
Going to flash the patched boot IMG once the firmware is done. Is there an app to catch the log or an adb command?