Related
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
-My boot loader was unlocked prior to doing these steps
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
YrrchSebor said:
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
Click to expand...
Click to collapse
Great job. You know technically these same instructions should work for ANY of the v10 variants ..verizon...at&t etc....including the ones that up till now didn't have root at all.
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
It requires an unlocked boot loader.
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
famewolf said:
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
Click to expand...
Click to collapse
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
will this factory reset my phone?
CrimsonSaber5G said:
will this factory reset my phone?
Click to expand...
Click to collapse
Nope. Unlocking your bootloader will but this won't in itself.
Sent from my LG-H901 using XDA-Developers mobile app
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
CrimsonSaber5G said:
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
Click to expand...
Click to collapse
No, it means it's unlockable, but you have to actively unlock it. There should be a thread here somewhere if you haven't done that yet, but it's just boot into bootloader and then 'fastboot oem unlock'
Edit: in case you need it there are great instructions in the v20 thread that I linked in the first post.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
je2854 said:
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
Click to expand...
Click to collapse
I think it's considered a very serious vulnerability that must and will be patched soon. They can't have root access so easily obtained on any device.
Amd4life said:
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
Click to expand...
Click to collapse
You're welcome, and thanks for confirming. That one step where the screen goes weirdly backlit with the Tmo splash screen is a bit nerve-wracking, and so is writing recovery this way, but I was comforted by the fact that you can just tell it to to write to the recovery partition rather than having to know the more technical name/location(not sure if this was possible a few years back?)
Anyway, if I did brick I was gonna go straight to the store and buy a ZTE Zmax Pro for $180 haha.
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
YrrchSebor said:
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
Click to expand...
Click to collapse
No. The shell has limited access...it has just enough permissions to write recovery and access some things on boot...you need to get it a recovery where you can then flash a zip to install superuser.
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
AnonVendetta said:
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Click to expand...
Click to collapse
There is a 20l KDZ floating around in some other threads. Not sure if there is or will be a systemless root, never even done it myself [emoji4]
Sent from my LG-H901 using XDA-Developers mobile app
joesee said:
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
Click to expand...
Click to collapse
The Volte silence bug is fixed in 20l, as many have reported. I had updated officially to 20l and was stock unrooted prior to this. But for people who are rooted on 20j or earlier, I believe Eliminator has released a pre-rooted update, so maybe you'd wanna do that instead.
Sent from my LG-H901 using XDA-Developers mobile app
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?
Someone's bound to hose up their phone. Wondering where factory images are?
Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk
me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.
There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.
https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
statustray said:
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
Click to expand...
Click to collapse
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
KittyRgnarok said:
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
Click to expand...
Click to collapse
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
statustray said:
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
Click to expand...
Click to collapse
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
KittyRgnarok said:
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
Click to expand...
Click to collapse
mike.s said:
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
Click to expand...
Click to collapse
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
statustray said:
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
Click to expand...
Click to collapse
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
KittyRgnarok said:
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
Click to expand...
Click to collapse
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
statustray said:
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
Click to expand...
Click to collapse
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
statustray said:
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
Click to expand...
Click to collapse
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
KittyRgnarok said:
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
Click to expand...
Click to collapse
You must've been posting as I was typing my message to you. I'm just now seeing that you provided some steps. Yes, I had figured that out and got it done. Life's good now.
I am doing some searching trying to figure out tethering, that's the last piece of the equation for now... hehehe..... On the old vzw unlimited data plan and I don't want to switch over to their new plans. If I can get this going, then my better half will be super happy, and then I will look into getting me a Google Pixel (but the XL version).
KittyRgnarok said:
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
Click to expand...
Click to collapse
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
statustray said:
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
Click to expand...
Click to collapse
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Hi everyone
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
S7sadly said:
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
Click to expand...
Click to collapse
Same files.
Thank you
KittyRgnarok said:
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Click to expand...
Click to collapse
Thanks for the heads up on the Pixel 2 issues. I will probably stay with stock like on my better half's phone, and just want to root and tether. Now the burn ins, that kind of worries me. Hmmmm... decisons, decision... hehe...
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
KittyRgnarok said:
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
Click to expand...
Click to collapse
Thanks for that information. I did not realize that. And sorry for the delay in responding. I didn't get on xda yesterday as I got back home late last night. I will certainly look for that magisk module you mentioned.
Oh and by the way, I just got me a Google Pixel XL today
Now I need to work the same magic on this one. I've already got it activated at the VZW Store near where I live. *Woohoo*
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
12paq said:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
Click to expand...
Click to collapse
LMAO. Give it up. We're going to be on 11. Good night
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
digger16309 said:
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
Click to expand...
Click to collapse
Good luck my friend. Stay on 10
We don't even have kernel source yet..
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Thanks! As I said TWRP has not been needed and I was just curious.
However I did enjoy your insecure condescending attitude. It made me LMAO.
Again, thanks! ??
dmb219 said:
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Click to expand...
Click to collapse
I know, it looks like TWRP has been doing a long slow death spiral.
We have TWRP on Android 10 for the Pixel C tablet. But of course among other things, there's no A/B partitions and Google abandoned support for the device a while ago.
Might be a while, pixel 3+ devices haven't had a 100% working TWRP for a long time.
They can still sideload ROMs and patch boot images with adb/fastboot
I'll miss this moving on from my 2xl. Nice to flash and update things without needing a PC
Golf c said:
Good luck my friend. Stay on 10
Click to expand...
Click to collapse
I will until there is EdXposed for 11 + module updates.
digger16309 said:
I will until there is EdXposed for 11 + module updates.
Click to expand...
Click to collapse
Yucky
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
dpaine88 said:
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
Click to expand...
Click to collapse
Just unlocked my Pixel4a using the standard ADB commands. Will say that OEM Unlocking stayed grayed out, until I connected to my WiFi (No SIM) and let the phone connect to the mother-ship.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
renzyyy said:
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
Click to expand...
Click to collapse
If I get around to it this weekend, I may just do a rom dump to extract the boot.img. Haven't done it in a while. I'm still waiting for some screen protectors to arrive before I mess with my phone.
Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
I can't find them either.
Isn't Android 11 going to make it more difficult to hide root anymore? I am tempted to root, but heard (or read) somewhere that with android 11 that it may not be worth it as any app (or something like that) will be able to see and not work.
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
edufur said:
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
Click to expand...
Click to collapse
Curious about adguard. I just tried it and won't install with chrome as browser.
Sent from my OnePlus 5T using XDA Labs