Related
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
Pretty self explanatory. I have the update pending for 8.0 but I've heard mixed reviews of the Oreo updates. So please, if anyone can be honest and tell me weather to proceed, or should I wait and why. Thanks you.
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
liriolebron said:
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
Click to expand...
Click to collapse
What's the best way to check if it's Verizon? And I don't need to root or anything honestly. I'm asking if the bugs with 8.0 are worth updating at the current state.
I recommend unlocking bootloader first and then update
So by unlocking the bootloader, I won't run into problems taking official updates?
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
No. If you modify system (root, Magisk, custom ROMs/kernels, TWRP recovery, etc) then you won't be able to take official OTA updates. But you can take them just fine with an unlocked bootloader.
Also, I'm on stock 8.1 and have no issues to speak of. I say go for it.
Sent from my Pixel XL using Tapatalk
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
FYI If phone is a Verizon version an on 7.1.1 you are able to unlock it. If you update beyond 7.1.1 without unlocking you will Never be able to unlock it. If it's a Google version no worries.
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
asj0422 said:
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
Click to expand...
Click to collapse
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Sent from my Pixel XL using Tapatalk
borxnx said:
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Click to expand...
Click to collapse
He's right though. Unlocking will lead to security issues and may take away the ability to use important apps. If he prioritizes functionality, then it's best to keep it locked but if he wants to tinker, it'll come with compromises.
Since he just bought it, I don't see why he couldn't just warranty it if an update goes wrong, which is extremely rare. From what I've seen from people with bricked devices, the majority of them were unlocked and tried to update using non-conventional ways.
Bootloaders are locked from factory for a reason, not for inconvenience.
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Ndmand said:
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
Click to expand...
Click to collapse
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
bita said:
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Click to expand...
Click to collapse
Thank You,
This is exactly what I need. I interpret "OEM relocked" to mean that after flashing, you system was relocked, and you didn't have to separately relock your bootloader. I appreciate your help.
Ndmand
Tarima said:
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
Click to expand...
Click to collapse
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Ndmand said:
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Click to expand...
Click to collapse
No problem. Yes, once you root with superSU, your system partition will be flagged permanently as modified even if you unroot. That's why you need to flash a virgin system backup image. This is also why I root with Magisk, as it makes taking OTA much easier. You may want to consider that as well when you root again.
I don't quite understand Magisk yet, but I will look into it. Thanks for making this doable and understandable.
Ndmand
Do a RUU and update ota , no need to relock bootloader, you will lose data if you do RUU
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
oxineitor said:
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
Click to expand...
Click to collapse
U.S Unlocked has not yet received OTA. To go to Oreo you'll have to run the RUU.
Take the RUU posted by santod on this page:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page254
Newbie Here
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Yank1llaz said:
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Click to expand...
Click to collapse
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Tarima said:
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Click to expand...
Click to collapse
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
andybones said:
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
Click to expand...
Click to collapse
Unless you're rooted with Magisk systemless root, you can't take OTA from a rooted state until you restore a stock system image, which I'm thinking might undo the SIM unlock procedure the OP had to do on his Sprint device.
---------- Post added at 02:43 AM ---------- Previous post was at 02:35 AM ----------
Yank1llaz said:
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
Click to expand...
Click to collapse
That's what I was saying, there will 99% for sure be no other updates for this phone, so that's a non-issue. And if there is, you can run an RUU, return to stock, take the update, then do the sim unlock procedure again.
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Tarima said:
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Click to expand...
Click to collapse
Process for those. Sorry for being such a pain in the behind.
Yank1llaz said:
Process for those. Sorry for being such a pain in the behind.
Click to expand...
Click to collapse
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Tarima said:
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Click to expand...
Click to collapse
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Yank1llaz said:
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Click to expand...
Click to collapse
Sorry not sure about that, you'll have to ask in the appropriate forum.
Hi Boys and Girls hope you are all safe and well?
New to the Pixel Series and currently have a 6 Pro, I'm a converted Samsung user after years and years since the s2 I think.... I'm loving the pixel thus far even with the bugs but I have a question about Rooting and flashing custom roms I think I know the answer but need it clarifying...
If I root/flash a rom can I revert back to stock without it braking anything or voiding warranty?
As you will know on Samsung once you root Knox breaks and you can't use banking apps, g pay etc even if you flash a factory image and remove root? Is this the case with Pixels? I miss flashing the excellent ROM's created on here and my last 2 Samsungs S10+ and S20 FE 5G I never rooted as I use g-pay and banking apps.
Thanks in advance for any anybody taking the time to answer me.
Hi!
Yes, you can put Pixel phones back completely to the 100% stock with no indication it had even been rooted, and with the correct actions there is no disadvantage to having the phone rooted except:
A minority of banking apps can't be fooled that the phone isn't rooted and therefore might not work, or might not work completely. I don't have such a problem, my banking apps are fooled although if I want to set up my Chase app to work with my fingerprint, I need to set it up while not rooted. GPay works fine when you fool it.
When you're rooted you have to manually update the Android OS (each month if you want every update).
As you probably know, in order to root, you'll have to unlock the bootloader, which will factory reset your phone.
Also, if you're on the November update and want to use a custom kernel, you'll have to disable verity and verification (most or all custom kernels for the December update don't need that anymore).
If you want to run a custom kernel, I recommended not disabling verity and verification, and update to the December build or newer when they're out so you can use a fixed kernel that doesn't require that anymore.
If you did disable verity and verification, you'll have to factory reset the phone afterwards for the phone to be usable.
You'll need to use Magisk Canary 23016 (or the latest Canary build if there's a newer one by the time you root). Magisk Beta and Stable haven't been updated recently enough for the latest changes necessary for Android 12 and this phone, and Canary build 23015 and older still needed verity and verification disabled.
m1ckbr1t said:
If I root/flash a rom can I revert back to stock without it braking anything or voiding warranty?
Click to expand...
Click to collapse
Yes, you can remove root and always go back to stock whenever you wish without banking apps being affected. It will all work the same just as it was received from the factory.
Google seems to be extremely generous with how they warranty their phones. They will allow you to unlock the bootloader, and even root, but they do require you to undo all of that back to stock if you are deemed to be approved for an RMA if something were to go wrong with your phone.
I always had the same fear with Apple devices when I'd jailbreak them, but I'd always undo everything before I needed help from their store and I was fine.
roirraW edor ehT said:
Hi!
Yes, you can put Pixel phones back completely to the 100% stock with no indication it had even been rooted, and with the correct actions there is no disadvantage to having the phone rooted except:
A minority of banking apps can't be fooled that the phone isn't rooted and therefore might not work, or might not work completely. I don't have such a problem, my banking apps are fooled although if I want to set up my Chase app to work with my fingerprint, I need to set it up while not rooted. GPay works fine when you fool it.
When you're rooted you have to manually update the Android OS (each month if you want every update).
As you probably know, in order to root, you'll have to unlock the bootloader, which will factory reset your phone.
Also, if you're on the November update and want to use a custom kernel, you'll have to disable verity and verification (most or all custom kernels for the December update don't need that anymore).
If you want to run a custom kernel, I recommended not disabling verity and verification, and update to the December build or newer when they're out so you can use a fixed kernel that doesn't require that anymore.
If you did disable verity and verification, you'll have to factory reset the phone afterwards for the phone to be usable.
You'll need to use Magisk Canary 23016 (or the latest Canary build if there's a newer one by the time you root). Magisk Beta and Stable haven't been updated recently enough for the latest changes necessary for Android 12 and this phone, and Canary build 23015 and older still needed verity and verification disabled.
Click to expand...
Click to collapse
Gonna jump in here. I also just got my 6 Pro and I'm waiting until the January update to root. Am I going to have to completely re-setup my phone or is there a way to back up everything outside of a normal backup? I'm using lawn chair as a launcher and I have that backed up.
Zach Alt said:
Gonna jump in here. I also just got my 6 Pro and I'm waiting until the January update to root. Am I going to have to completely re-setup my phone or is there a way to back up everything outside of a normal backup? I'm using lawn chair as a launcher and I have that backed up.
Click to expand...
Click to collapse
More or less, you'll have to set your phone up from scratch, except you can restore your Google cloud backup. Plenty of apps don't use Google's automatic cloud backup but some do.
A very select few apps have their own backup process you can manually do within the app (Nova Launcher Prime, some music apps, etc).
You can theoretically use some non-root apps or manually with ADB to backup apps, but in my experience, it just doesn't work satisfactorily or completely.
At least you have some time before the January update to experiment with that if you want.
You could try such an app or manually use ADB to backup an app, uninstall it, and then restore the app and app data using the same method and see if it did a satisfactory job for your purposes.
I can't really recommend a non-root app for this as I've never been happy with non-root restore results, not once you're rooted, I recommend Swift Backup (I use it to backup 100% to my preferred spare cloud space so I don't use precious infernal storage, and I have it scheduled to automatically do every night if the battery is over 50% - only for apps that have been updated since the previous backup.
Backup and restore to and from cloud is much slower, but I use 400GB of my internal storage for music files, and it's nice knowing if I had to do an emergency factory reset that I wouldn't lose that backup.
I paid for the lifetime features of Swift Backup.
I hear folks still use Titanium Backup as well, and I still did for years, but I decided to try Swift's features.
Good luck when you root!
Hey @roirraW "edor" ehT and @RetroTech07 many thanks for your detailed answers really appreciated as always the XDA guys and gals are so helpful.
I'll be doing my homework this weekend and having a play.
m1ckbr1t said:
Hey @roirraW "edor" ehT and @RetroTech07 many thanks for your detailed answers really appreciated as always the XDA guys and gals are so helpful.
I'll be doing my homework this weekend and having a play.
Click to expand...
Click to collapse
You bet, happy to help. Please don't hesitate to ask anything else. There are also folks active in this section who are a lot more knowledgeable than me.
Zach Alt said:
Gonna jump in here. I also just got my 6 Pro and I'm waiting until the January update to root. Am I going to have to completely re-setup my phone or is there a way to back up everything outside of a normal backup? I'm using lawn chair as a launcher and I have that backed up.
Click to expand...
Click to collapse
Just to expand a bit on the sage advice of @roirraW "edor" ehT , the only reason you will need to wipe everything is because you have to unlock your bootloader, if you haven't already. Rooting itself does not require having to wipe (unless of course Google has some more shenanigans up its sleeve) , but unlocking the bootloader (which is required to root) does wipe your phone. So if you wanted to you could unlock your bootloader now (wipe and re-setup) and then when the January update comes out you can just root without having to set up again. Kind of a set me up now or set me up later thing.
And of course when updating in the future just do it by one of the several methods that don't end up wiping your data.
EDIT: Of course, wiping now would mean you would be likely stuck on the November build until the January one comes out given they have taken down and stopped the December updates (assuming you are on the November build now).
Lughnasadh said:
Just to expand a bit on the sage advice of @roirraW "edor" ehT , the only reason you will need to wipe everything is because you have to unlock your bootloader, if you haven't already. Rooting itself does not require having to wipe (unless of course Google has some more shenanigans up its sleeve) , but unlocking the bootloader (which is required to root) does wipe your phone. So if you wanted to you could unlock your bootloader now (wipe and re-setup) and then when the January update comes out you can just root without having to set up again. Kind of a set me up now or set me up later thing.
And of course when updating in the future just do it by one of the several methods that don't end up wiping your data.
Click to expand...
Click to collapse
That's excellent advice. I know I would rather unlock, wipe, and (re)set things up now in the same situation, and then once I would root on January's update, I could spend my now free time implementing root apps.
roirraW edor ehT said:
That's excellent advice. I know I would rather unlock, wipe, and (re)set things up now in the same situation, and then once I would root on January's update, I could spend my now free time implementing root apps.
Click to expand...
Click to collapse
Yeah, especially since he said he just got his phone so he may not be too invested in his setup just yet. For me (and my neurotic mind ) I would just be dreading having to setup up again and would rather just rip the Band-Aid off now .
EDIT: Editing my original post to include that if he wiped now he would likely be stuck on the November build until the January one comes out since they stopped the December updates (assuming he's on the Nov. build now).
Lughnasadh said:
Yeah, especially since he said he just got his phone so he may not be too invested in his setup just yet. For me (and my neurotic mind ) I would just be dreading having to setup up again and would rather just rip the Band-Aid off now .
EDIT: Editing my original post to include that if he wiped now he would likely be stuck on the November build until the January one comes out since they stopped the December updates (assuming he's on the Nov. build now).
Click to expand...
Click to collapse
I'm currently on the November build, so I'm stuck here until the January update no matter what right?
Zach Alt said:
I'm currently on the November build, so I'm stuck here until the January update no matter what right?
Click to expand...
Click to collapse
Yes, if you are on November you are stuck there until the January ones come out unless you update to December via images that a person or two (think @roirraW "edor" ehT is one of them) has uploaded for people's convenience.
Lughnasadh said:
Yes, if you are on November you are stuck there until the January ones come out unless you update to December via images that a person or two (think @roirraW "edor" ehT is one of them) has uploaded for people's convenience.
Click to expand...
Click to collapse
I think I'll give Google the benefit of the doubt and just unlock now and wait to root after the January update drops. Thank you both for your time in replying!
Zach Alt said:
I think I'll give Google the benefit of the doubt and just unlock now and wait to root after the January update drops. Thank you both for your time in replying!
Click to expand...
Click to collapse
You are welcome. If you decide to unlock now you could also just go ahead and root now if you wanted to. You'll just have to re-root (no big deal) when the January update comes out but you won't have to wipe as long as you update by a method that preserves your data in January.
Just make sure you use Canary Magisk 23016.
Lughnasadh said:
You are welcome. If you decide to unlock now you could also just go ahead and root now if you wanted to. You'll just have to re-root (no big deal) when the January update comes out but you won't have to wipe as long as you update by a method that preserves your data in January.
Just make sure you use Canary Magisk 23016.
Click to expand...
Click to collapse
Well I am of course having trouble, I sent you a PM if you get a chance.
Zach Alt said:
Well I am of course having trouble, I sent you a PM if you get a chance.
Click to expand...
Click to collapse
I don't know specifically how @Lughnasadh feels about PM tech support, but a lot of us generally discourage it. I just plain block PMs unless I've "friended" someone.
One of the reasons is that whatever problem you're having, the solution can probably benefit someone else who reads this or finds it in a search. But as I said, I can't speak for @Lughnasadh.
If you haven't already, you can use the filters at the top of the P6P section for just the How To Guides, and you'll find full root instructions that should help as well.
roirraW edor ehT said:
I don't know specifically how @Lughnasadh feels about PM tech support, but a lot of us generally discourage it. I just plain block PMs unless I've "friended" someone.
One of the reasons is that whatever problem you're having, the solution can probably benefit someone else who reads this or finds it in a search. But as I said, I can't speak for @Lughnasadh.
If you haven't already, you can use the filters at the top of the P6P section for just the How To Guides, and you'll find full root instructions that should help as well.
Click to expand...
Click to collapse
Thanks for this. I usually ignore PMs but decided to help this time and looks like he got things going.
But completely agree with you. Search, ask in the threads if needed and everyone will benefit. As a last resort, ask first before PMing someone.
Just saw this, got ya, sorry guys. So I will ask my question here, now that I have root, can I factory reset my phone to get back to the setup menu and not lose root? I understand I'll have to add magisk again.
Zach Alt said:
Just saw this, got ya, sorry guys. So I will ask my question here, now that I have root, can I factory reset my phone to get back to the setup menu and not lose root? I understand I'll have to add magisk again.
Click to expand...
Click to collapse
Well...I also discourage folks from factory resetting through the OS or recovery unless a phone is completely stock, but if the only change is the kernel (boot.img) that you modified with Magisk, then it should be fine.
Flashing entire official stock image files (which includes a -w switch to wipe the phone) would also work, albeit you'd have to flash the Magisk'd boot.img again, besides re-installing the Magisk app as you said.
Factory resetting while not 100% stock has sometimes at least temporarily bricked some folks' phones in the past, but I'm pretty sure people in your same situation in this section have reported doing so and it was fine.
IGNORE THIS POST - I blame lack of sleep
roirraW edor ehT said:
Well...I also discourage folks from factory resetting through the OS or recovery unless a phone is completely stock, but if the only change is the kernel (boot.img) that you modified with Magisk, then it should be fine.
Flashing entire official stock image files (which includes a -w switch to wipe the phone) would also work, albeit you'd have to flash the Magisk'd boot.img again, besides re-installing the Magisk app as you said.
Factory resetting while not 100% stock has sometimes at least temporarily bricked some folks' phones in the past, but I'm pretty sure people in your same situation in this section have reported doing so and it was fine.
Click to expand...
Click to collapse
I believe you mean "relocking the bootloader". Factory reset, aka data wipe, should never brick a device, regardless whether the firmware is custom, modified, or stock. It simply wipes user data.
Attempting to lock the bootloader with custom firmware on the other hand is a BAD idea and could indeed result in a brick...although I believe there are protections currently in place to prevent bootloader from locking if anything is modified.