three questions about Nexus 6P - Nexus 6P Q&A, Help & Troubleshooting

hi guys,
please i have some questions i really need there answers:
1- (rooted phone) if i do a factory data reset will the root gone and the TWRP also ?
2- (rooted phone) is there a way to install an update if i got it ( like update security patches "monthly" ) on rooted phone without wipe data or loosing the root or TWRP?
3- (rooted phone) if i reinstall the factory image full,the root and TWRP will have gone or not ?
thanks a lot !

1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.

Face_Plant said:
1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.
Click to expand...
Click to collapse
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used

Chouiyekh said:
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used
Click to expand...
Click to collapse
If you are running Marshmallow or Nouget and used a version of SuperSU that is a year or less old it does system less root by default.
You can flash OTA updates on a rooted device with FlashFire without using a computer.

You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk

Why would factory reset remove systemless root? I expect factory reset to only reset what you're supposed to have changed since factory image. That is /data.

Systemless must be in /data if it's not in /system, right? I don't really know much about systemless, because I don't use Android pay, Snapchat or play children's games haha.
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Sent from my Nexus 6P using Tapatalk

HikingMoose said:
You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
thank you, i got it easily because i'm not a beginner i have some experience

HikingMoose said:
Systemless must be in /data if it's not in /system, right?
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Click to expand...
Click to collapse
You guessed right. Never thought of that, thought it was actually all done from boot partition.
Quoting Chainfire:
As the binaries should still be updatable, and we don't know the space we have available in the boot image itself, we're mounting a (writable) ext4 image with /su as mount point from /data, and modifying PATH accordingly. Interestingly, for reasons yet unknown to me, if the image is mounted r/o by init, later remounting it r/w causes a bunch of issues. So we're keeping it r/w (for root) for now.

Related

if i factory reset my phone, will it remove the root

will the root be gone if i factory reset my mytouch 4g?
Yes. Everything Will be wipe, superuser too.
Wrong. Actually, no. Not at all.
Factory reset wipes the /data partition, which holds user data.
Superuser resides on /system partition, which isn't wiped, and the fresh system after wipe will retain root access. Superuser app might be installed on /data, but the actual SU file will be on /system.
To remove root, you need to unroot - or flash non-rooted stock ROM.
Right, "factory" reset is a bit of a misnomer on Android.
There is no backup of the factory firmware if you have modified your system partition.
But if you flash a full RUU or PD15IMG.zip of the stock ROM, then yes you will lose root. However if you still have Radio S-OFF, you will still be able to flash unsigned images through the bootloader.
syedquadri said:
will the root be gone if i factory reset my mytouch 4g?
Click to expand...
Click to collapse
What ROM do you have? This all depends on the current ROM you have. If you did not update your ROM, then you will lose root. If you only updated your ROM and did NOT update your recovery, you could ruin your device potentially by selecting that option from within the phone or the stock recovery.
However, if you have a custom (probably rooted already) ROM and you have a recovery like clockworkmod recovery installed, then go ahead and wipe away. You can also clear just your cache, dalvik and many other stuff, the menu has a lot of options.

Encrypting the phone resulted in a bootloop

Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
jodvova said:
Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
Click to expand...
Click to collapse
Chances are very low. I had the same issue and the only way I was able to fix it was to use the Google factory image and completely wipe the phone. Then boot it before flashing anything including TWRP. It encrypts in about a minute. Setup the phone, and then flash TWRP, modified root boot image if you want, and the corresponding SU zip.
Sent from my Nexus 6P using Tapatalk

TWRP hangs on booting to recovery

Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.

H918 on 10k. Had root. Lost it. Need to roll back and reroot?

I'm not sure what happened, but my phone lost root and couldn't boot into system due to a problem with encryption. I had to do a reset. I'm now on 10k with no TWRP or root.
I assume I need to roll back to 10p or 10i stock and re-root. However, I can't find the programs and the stock 10i or 10p files.
EDIT: Apparently, the firmwares site doesn't like Firefox. It wasn't showing any of the firmwares for download. I had to use a different browser.
I was able to roll back to 10p. Install TWRP, and flash 10k with Magisk.
I don't want to have whatever happened to me again. Does anyone know why I lost lost TWRP and had to reset?
Sizzlechest said:
I was able to roll back to 10p. Install TWRP, and flash 10k with Magisk.
I don't want to have whatever happened to me again. Does anyone know why I lost lost TWRP and had to reset?
Click to expand...
Click to collapse
Did you flash anything recently that may have caused you to lose root? if I'm not mistaken, if you flash a boot image without flashing root after that will cause you to lose root and if you boot without root it will restore your backup recovery partition removing TWRP. I've actually dd'd my recovery partition over the backup so this doesn't happen, but I'm sure there are other ways to lose root...
dimm0k said:
Did you flash anything recently that may have caused you to lose root? if I'm not mistaken, if you flash a boot image without flashing root after that will cause you to lose root and if you boot without root it will restore your backup recovery partition removing TWRP. I've actually dd'd my recovery partition over the backup so this doesn't happen, but I'm sure there are other ways to lose root...
Click to expand...
Click to collapse
I suspect the person "fooling around" with my phone was in the SuperSU app. The only potentially destructive thing in there would be full unroot since you can remove TWRP from there. It's just a theory. Even if you dd the recovery partition, how would you get it back without TWRP or root?
Sizzlechest said:
I suspect the person "fooling around" with my phone was in the SuperSU app. The only potentially destructive thing in there would be full unroot since you can remove TWRP from there. It's just a theory. Even if you dd the recovery partition, how would you get it back without TWRP or root?
Click to expand...
Click to collapse
from what I've gathered, there are two recovery partitions, one is the main and then there is another that's a backup. when you install TWRP it always installs to the main one leaving the backup intact. when recovery gets reset, it pulls it from the backup... however if it didn't and the main is messed up then you might be screwed

Should I flash twrp?

I'm currently running magisk, I've been trying to do everything systemlessly but it's getting frustrating, failed boots, bugs, limitations... I want to stick with systemless so I can count on my warranty which I can get back with two commands. Now, my question is, how hard and risky is to get stock recovery and lock back the bootloader once twrp is installed. Another thing I'm concerned about is if OTA update kicks in, I uninstall magisk and update it and it fails, I'm stuck, can't get any data or backup. Twrp would help a ton and I'm pretty sure I can just flash the new OTA image from twrp. But how hard and risky is restoring factory phone image (system+bootloader+recovery) once lord twrp is installed?
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Daydreamaway said:
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Click to expand...
Click to collapse
That's great, and fastboot is always available no matter how corrupt the system is, right? What do you recommend for a full backup and what about allowing system modifications when twrp boots?

Categories

Resources