Related
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 rooted my phone last week because I wanted to use substratum to theme my notifications. Since then, I've run into a bunch of frustrating problems.
Current Model: OnePlus 7 Pro 12GB version, build xXx_NoLimits_7.7 on OOS 9.5.11-GM21AB
Problems:
Phone used to be 9.5.11-GM21AA but now it's 9.5.11-GM21AB - does this affect anything?
Substratum hasn't worked in stock+root, and 2 different ROMs I've tried
Favourite app of mine doesn't work properly and I think it's because I'm on build 9.5.11 and not 9.5.10
How I messed it up: Started by rooting and trying to install Renovate ICE Rom, installed the wrong file which converted me to 9.5.5-GM21AB. Then I updated to 9.5.11 but it remained AB. I tried several times to unroot, roll back and get to 9.5.10AA but it always kept itself at 9.5.11AB. Sometimes my wifi would break. I currently have xXx NoLimits Rom installed.
Desired outcome: I want to unroot and roll back to 9.5.10-GM21AA stock
Any help is greatly appreciated. Thank you!
MSM tool should fix it.
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
+1
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
zams85 said:
+1
Click to expand...
Click to collapse
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
bmcmr said:
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
Click to expand...
Click to collapse
Just download the full zip for 9510 and update via system update
virtyx said:
Just download the full zip for 9510 and update via system update
Click to expand...
Click to collapse
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
bmcmr said:
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
Click to expand...
Click to collapse
Correct
You will unrooted after the upgrade as itll flash completely stock.
Just re-roof after it and your good to go!
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
bmcmr said:
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
Click to expand...
Click to collapse
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Whats wrong with .10 ? .11 borked or something?
virtyx said:
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Click to expand...
Click to collapse
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
sarni84 said:
Whats wrong with .10 ? .11 borked or something?
Click to expand...
Click to collapse
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
bmcmr said:
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
Click to expand...
Click to collapse
I don't blame you, 9511 isn't as smooth as 9510.
also noticed 9510 had better battery life.
I might roll back myself
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?
Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.
sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.
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
.
Reserved
Placeholder thread for further development
Kernel development is fast underway. Those interested in helping test please let me know. The first thing I need to test is whether the builds Im making will work on ALL variations of the June release. Im just on the generic one and thats what I built for but anyone on a carrier build or the JP one that wants to verify boot and that things are working correctly that would be extremely helpful.
I have a rooted T-Mobile 6a if you're still looking for a tester.
Delete
ctfrommn said:
Delete
Click to expand...
Click to collapse
I can test. I'm on the Verizon build.
Give me some time.....stuff ended up not working as intended. Probably tomorrow, but thank you.
Sounds good, looking forward to it. Also yes I'm on the June build.
Every new device I get has a learning curve to building for it. This one is totally new to me but Ill get it sorted out soon enough one way or another.
Ideally I want to resurrect Velocity....baby steps though
Sounds like a winner to me...I'm all about AOSP1
I'll let you sink your teeth into it and will prolly jump in after the August update...have a feeling it'll be substantial. We share the same opinion...fast and dependable above all.
Ok, I think were finally cooking with gas.....looks like gone are the days of a simple boot.img flash and Ill need to migrate to using an anykernel zip format, which is fine and in a lot of ways simpler provided you have an app to flash them. Not sure if you can sideload these but Ill look into it further. I should have an actual test up yet today for anyone who can flash it.
ctfrommn said:
Every new device I get has a learning curve to building for it. This one is totally new to me but Ill get it sorted out soon enough one way or another.
Ideally I want to resurrect Velocity....baby steps though
Click to expand...
Click to collapse
Yeah, I'm getting back into it after years of not messing with my phones, my last real contribution to XDA was in 2019. This time I'm hoping to get into the development scene rather than just messing around, good luck! Lots if not everything has changed since my days.
I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.
ctfrommn said:
I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.
Click to expand...
Click to collapse
After flashing it with FKM, how would I go about getting Magisk flashed again? I haven't used FKM in quite a while.
JRJ442 said:
After flashing it with FKM, how would I go about getting Magisk flashed again? I haven't used FKM in quite a while.
Click to expand...
Click to collapse
If youre rooted now you will be after as well
Can we get a variant for a13 beta?
Look forward to trying this out
ctfrommn said:
I ran out of time to get anything super exciting done (this is a giant PITA) but there is a zip in the test folder that "should" work on all June builds but feel free and let me know if it doesnt.
At this point this is a optimized (slightly by my standards) stock build. Everything works normally and it does feel better.
No idea if this works via ADB sideload but kernel apps should all work, FKM does for sure.
Click to expand...
Click to collapse
Flashing with FKM results in boot loop for me, flashing stock boot.img didn't fix it. I'll just have to flash full stock firmware with wipe option disabled.
EDIT: Phone really did not like me using the flash-all.bat from firmware to flash it, refused to flash system partitions. Ended up using Android Flash Tool from Google and now the phone is back.
Thankfully the 6a is not my main phone so I can keep testing builds even if they bork the phone. Let me know if you need any logs.
What build are your on?
ctfrommn said:
What build are your on?
Click to expand...
Click to collapse
SD2A.220601.002
Interceptor777 said:
SD2A.220601.002
Click to expand...
Click to collapse
Very weird, works fine for me