TWRP 3.2 on android 8.1 - Google Pixel XL Questions & Answers

Does TWRP 3.2.0-0 work on 8.1?

kingbri said:
Does TWRP 3.2.0-0 work on 8.1?
Click to expand...
Click to collapse
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.

Pain-N-Panic said:
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.
Click to expand...
Click to collapse
Can you use a password with this?

Pain-N-Panic said:
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.
Click to expand...
Click to collapse
How did you do it. I'm on Pixel , 128 GB, Oreo 8.1 (nov) but TWRP doesn't allow to attain the disk
I booted the 3.2.0-0.img, flashed the zip file but no way.

henk-jan said:
How did you do it. I'm on Pixel , 128 GB, Oreo 8.1 (nov) but TWRP doesn't allow to attain the disk
I booted the 3.2.0-0.img, flashed the zip file but no way.
Click to expand...
Click to collapse
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me

kingbri said:
Can you use a password with this?
Click to expand...
Click to collapse
Not sure. I intentionally did not set a password prior to using it just in case twrp wasn't compatible with a password like the previous version.
---------- Post added at 09:00 PM ---------- Previous post was at 08:52 PM ----------
These are the steps I took to get twrp 3.2 working (without using a pin/password):
Clean flash 8.1 image
Boot into phone, setup device withOUT pin
Boot to bootloader
Fastboot boot twrp 3.2
Flash 3.2 installer zip
Reboot recovery
Flash 14.5 magisk beta
Flash 14.5 magisk a 2nd time
Reboot system.

kingbri said:
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me
Click to expand...
Click to collapse
Thanks. I don't like a factory reset (till now I managed a dirty flash) because of the many apps I use
I don't have ElementalX at the moment installed, that's why I used ( ). I'm waiting for a update, probably when 8.1 is no longer beta.

henk-jan said:
Thanks. I don't like a factory reset (till now I managed a dirty flash) because of the many apps I use
I don't have ElementalX at the moment installed, that's why I used ( ). I'm waiting for a update, probably when 8.1 is no longer beta.
Click to expand...
Click to collapse
You'll only get away with dirty flashing for so long. I did the same as you for a while and ended up with a corrupted data partition. I was forced to do a factory reset and lost all data on my phone. Literally had to start from scratch.
Now, I clean flash (full wipe) every time. I make a backup of all of my apps with titanium backup. I adb pull my titanium folder, DCIM folder (photos) and my twrp folder (nandroid backup) to my PC. After I clean flash I use adb to push them back to my SD card. Reinstall titanium from the play store and restore all apps from my backup folder.

Pain-N-Panic said:
You'll only get away with dirty flashing for so long. I did the same as you for a while and ended up with a corrupted data partition. I was forced to do a factory reset and lost all data on my phone. Literally had to start from scratch.
Now, I clean flash (full wipe) every time. I make a backup of all of my apps with titanium backup. I adb pull my titanium folder, DCIM folder (photos) and my twrp folder (nandroid backup) to my PC. After I clean flash I use adb to push them back to my SD card. Reinstall titanium from the play store and restore all apps from my backup folder.
Click to expand...
Click to collapse
Twrp would probably update it once 8.1 releases

kingbri said:
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me
Click to expand...
Click to collapse
No it didnt fix the encryption...

Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?

no, I don't think so, wait for twrp to update

Doenerbude said:
Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?
Click to expand...
Click to collapse
I am assuming you have things to flash, like root? Put the files on a USB and use the adapter to plug it into the phone. Hit cancel interpretation at the password screen and then you can select storage for the USB and flash the zips from there.

kingbri said:
Can you use a password with this?
Click to expand...
Click to collapse
No its still encrypted

before dirty flash 8.1, remove all patten/fingerprint, then flash 8.1, install twrp
flash all zips you need
re-enable your patten/fingerprint, just leave twrp there, till next update.

Doenerbude said:
Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?
Click to expand...
Click to collapse
The key is to NOT set a password at all...

Can we not use twrp 3.1.1-1 on Android 8.1?

It worked with both -removing any pin/passwort/pattern or in case you don't want to do this putting the files on an USB-C Stick, fastboot boot twrp.img and mount the USB-OTG

Just got everything working on 8.1, but TWRP does ask for a password instead of a pattern unlock. I got around this by the following method:
in fastboot:
fastboot boot twrp-3.2.0-0-marlin.img
since my phone is encrypted with a pattern, I had to "cancel" out of the prompt and sideload install everything, starting with TWRP 3.2:
adb sideload twrp-pixel-installer-marlin-3.2.0-0.zip
then rebooted into recovery:
adb reboot recovery
since unlocking encryption still didn't work, I sideloaded Magisk first:
adb sideload Magisk-v14.5(1456).zip
and then SuperSU:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
rebooted to system, everything works as it should. passes safetynet check.

cowrecked said:
since unlocking encryption still didn't work, I sideloaded Magisk first:
adb sideload Magisk-v14.5(1456).zip
and then SuperSU:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Click to expand...
Click to collapse
Why are you flashing both? New to Magisk so perhaps I am missing something.

Related

March 2016 Updates Bug

My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?
I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/
Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
no issues here on 19J. modified boot image here
bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.
SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Bump
Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out
How is the new update in terms of making the phone better?
gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.

Can't decrypt my phone after installing oos nougats beta 8

After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.

Stuck rooting

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.

How to flash official nougat without wiping internal storage?

Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.

How to Root Using SuperSU and TWRP on Oreo OPR6 Official Release

After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!
Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.
Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you
Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.
I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.
I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.
Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it

Categories

Resources