Can no longer root my Nexus 6P - Android Q&A, Help & Troubleshooting

I recently installed Android 7.1.2 on my phone and since then I've been unable to root it. I've been able to successfully root it between firmware updates until the 7.1.2 upgrade.
I can install twrp-3.1.0 via fastboot, and when I boot into the twrp recovery, I use adb sideload to install SuperSU, because it seems by SD card has gotten encrypted (until the 7.1.2 update I had stored SuperSU on the SD card and installed it from there). Everything appears to work as expected according to the install messages on the phone's screen. But then when I reboot boot the phone, SuperSU reports that it isn't rooted.
Am I doing something wrong, or does 7.1.2 somehow prevent SuperSU from overwriting the necessary system files?

Related

Internal storage not recognized by the device

It's a long story, but I'll have to tell it so you can understand exactly what happened.
I was toying around with some system files and ended up in a bootloop. So I made a new kitkat ftf file that I flashed in flashtool, then I installed the advanced kernel for twrp and finally I installed a prerooted lollipop zip in recovery that I made with prf creator. When I first booted the device the su binary didn't work, so I had no root acces. I booted the tablet in fastboot and installed advanced kernel for twrp again (over lollipop), then I wiped everything and flashed the prerooted firmware again, plus the supersu zip to make sure it works.
This time root works and everything seems to be ok, except that the device doesn't recognize the internal storage.
I think it's mounted, but the system can't see it. Installing apps from Google Play works, I even installed dungeon hunter which required additional files (which are normally installed in android/obb) and it works fine. But if I try to download anything from the web it says "no SD card".
If I open the preinstalled file manager from Sony it shows that I have 5.3/11gb occupied, but if I press on it it's empty.
Same story on root explorer, with superuser access granted.
What could be the problem? How do I fix this?

[Q] Cannot install GooManager/TWRP Manager after installing CM7

Hi All, I just found this Nook Tablet 16GB still running the old 1.4.0, and decided to turn it into a CM tablet.
I followed this guide "Nook Tablet 1.4.3 complete root guide for 8or16gb to GB and JB" http://forum.xda-developers.com/showthread.php?t=2037368&highlight=compatible, but once I have CM7 installed with a SD CWM recovery, I'm not able to continue on installing a EMMC recovery and newer roms (they won't install via the CWM 5.x on the SD card).
Most guides I read online calls for using either Goo Manager to install a recovery, or TWRP Manager to install TWRP directly. When I try to install Goo Manager, Google Play tells me that its not compatible with my device, same thing with TWRP Manager, and Flashify as well. When I tried to side-load Goo Manager, it installs, but gives me an error right when I start the app, and seems to not be able to identify my device, and find any ROMs and recoveries for it. TWRP Manager can't even be sideloaded, as it gives me a parsing error before it can install.
Now I basically have CM7 running on the emmc, but still with a stock recovery.
Can someone show me how to get TWRP installed on the emmc so I can move up to CM11 or CM12?
Thanks!

root and ota updates - how to

as it is asked quite often, here's how you get ota with a modified stock rom.
For example, ota will fail if you have root (as it changes your boot partition slightly) or if you deleted some preinstalled apps (e.g. chrome browser). OTA script always checks the signatures of your running rom and the ota update. If they don't match, it will fail.
An unlocked bootloader does not prevent ota from working!!!
requirements: a backup of a 'clean' stock rom
So if you want to update perform the following steps (edit: you can find a second and easier method at the end of the post)
1. boot twrp
2. backup everything to be safe (boot, recovery, system, data) if something goes wrong
3. restore 'clean' stock boot partition and recovery partition
(4. if you changed something in 'system' restore system as well)
5. boot tablet
6. download and install ota - it should succeed
7. boot twrp and restore data again if needed
(8. root again with magisk)
good to know:
if you restore partitions, make sure they are from the same build! if not, tablet might not boot or ota will fail again.
if you are rooted, you can use the the backup of boot created by the magisk script (-->/data/stock_boot_<sha1>.img.gz)
if you don't have a backup, try to get hands on a stock rom and flash the required partitions manually (e.g. fastboot flash boot.img etc..)
good luck
(if anyone knows a better way, let me know and i will add it here)
edit: @MarkAllen provided this method which is far more simple (but which unfortunately has never worked for me by now).
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser and Magisk manager from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
MarkAllen said:
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
Click to expand...
Click to collapse
great to hear...
using the uninstaller alone has never worked for me...it always aborts...sometimes it complains that some files are missing or were changed, the recovery partition doesn't match the expected one, etc...
mostly i can't remember which things i've done to the rom/system.
but again, good to know that magisk uninstaller works, it definitely is less complicated and time consuming.

Installing zips from TWRP

Hello,
I just bought a new Honor 9 and I'm trying to root it.
I unlocked the bootloader and installed TWRP.
The procedure says I need to install the Magisk apk and then reboot into TWRP and install the Magisk zip.
When I launch the recovery and look for the zip to install (that I previously I copied on sdcard when I first booted the phone) I just see a bunch of folders with random names (encrypted I guess). Moreover I can't find the zip file where I was supposed to find it.
Am I missing something?
Thanks
DDeleted said:
Hello,
I just bought a new Honor 9 and I'm trying to root it.
I unlocked the bootloader and installed TWRP.
The procedure says I need to install the Magisk apk and then reboot into TWRP and install the Magisk zip.
When I launch the recovery and look for the zip to install (that I previously I copied on sdcard when I first booted the phone) I just see a bunch of folders with random names (encrypted I guess). Moreover I can't find the zip file where I was supposed to find it.
Am I missing something?
Thanks
Click to expand...
Click to collapse
All you missed is a bit of reading my friend. To put it in a nutshell, actual versions of TWRP around here don't decrypt data. Yet. Now you should be able to access the content of a properly formatted (ExFAT or FAT 32) sd card.
Cheers.
Thanks for the reply. I actually upgraded latest TWRP and wiped from recovery. This somehow permanently removed the encryption.
Yes, it stays pending *almost* forever.
Play Store is already updated to latest version.
DDeleted said:
Yes, it stays pending *almost* forever.
Play Store is already updated to latest version.
Click to expand...
Click to collapse
You cannot download from. Playstore??

Asus Zenfone 4: Oreo released

To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.

Categories

Resources