Database Info

[Q] Root for the One Plus One?

This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.

adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.

EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!

Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central

CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.

I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk

dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.

From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.

Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?

dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.

cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?

You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk

it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.

The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.

tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.

I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.

Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.

Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?

Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

I want to root my pixel 2

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

TWRP on the P4a?

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

Question Is custom recovery possible/something that's being worked on?

Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!

TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.

jake.99x3 said:
I figure it would be helpful no?
Click to expand...
Click to collapse
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.

Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?

96carboard said:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Click to expand...
Click to collapse
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands

Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.

JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes

Yeah it would be nice to have for sure

Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.

JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.
old_fart said:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
Click to expand...
Click to collapse
The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.
Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.

HipKat said:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Click to expand...
Click to collapse
That's insane. And dangerous. When it messes up, good luck fixing it.

96carboard said:
That's insane. And dangerous. When it messes up, good luck fixing it.
Click to expand...
Click to collapse
Ummmm, what??

TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.
I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.

I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"

Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
You sure you've used it? TWRP is fully touch screen.

Beefheart said:
You sure you've used it? TWRP is fully touch screen.
Click to expand...
Click to collapse
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.

Renate said:
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Click to expand...
Click to collapse
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.

Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can

HipKat said:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
Click to expand...
Click to collapse
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?

Renate said:
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Click to expand...
Click to collapse
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.