Pixel (Sailfish) and O-Preview

TeamWin / Team-Win-Recovery-Project

Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/

http://twrp.me

1.95k stars 742 forks source link

Pixel (Sailfish) and O-Preview #920

Open Ttumbler opened 7 years ago

Ttumbler commented 7 years ago

Pixel Sailfish Android O-Preview

Using the RamDisk method (fastboot boot ...) results in a black screen. However adb comes up and I can install the zip over the command line.

I do : cd /tmp mkdir twrp-install -- out of adb adb push twrp-pixel-installer-sailfish-3.1.0-0RC2.zip /tmp/twrp-install --in adb cd /tmp/twrp-install unzip chmod 777 twrp-installer.sh

This works and when I reboot into recovery I can now see the teamwin logo but it stops.

Now the USB device fails though and Windows says it is unrecognised. So there is no ADB and no UI interaction.

jwgcarlson commented 7 years ago

I also ran into a black screen after the initial fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img. But after formatting userdata (adb shell mke2fs -t ext4 /dev/block/sda35) and waiting a couple seconds for /data to mount, the GUI comes up and I can finish installing the zip in the normal way.

This mostly seems to work. I can reboot into recovery, /data is automatically decrypted, and the GUI seems fully functional. Unfortunately, I get no adb shell access, which is a big bummer for me. Using the GUI terminal, I can see that adbd is running. And on my computer I can see the Pixel as a USB device, but it's not exposing an adb interface (i.e. class/subclass/protocol = 255/66/1).

P.S. This is with the OPP1.170223.012 preview build.

Ttumbler commented 7 years ago

Thanks. I can confirm that works. formatting userdata is required for the bootloader install to complete. This should be added to the install notes.

When booting to recovery, as you say there is no ADB access but also my device has the /data/apps and /sdcard folders encrypted. If I have a PIN on the device I am not being asked for it. Removing the PIN in security settings does not remove any encryption so that doesn't help.

At the moment I'm still stuck with having to fastboot boot the img and use ADB from there to manually mount the system directory and write into it. I'm trying to install an app in /system/priv-app/. It copies in but is not seen when the device boots to system. i can see the app in priv-app through TWRP recovery but not when browsing the folders during a normal boot to system. Any ideas on that?

Also using OPP1.170223.012

jwgcarlson commented 7 years ago

I managed to get adb in recovery by tweaking init.rc. The process went like this:

fastboot boot the bootable TWRP image, which gives adb shell access.
adb pull the boot partition to a local boot image.
Unpack the boot image (e.g. using mkboot).
Edit init.rc and repack boot image.
Flash the new boot image and reboot into recovery.

I made two changes to init.rc relevant to adb. I don't know which one was actually the critical one, and I'm too lazy to find out. The changes were

Add write /sys/class/android_usb/android0/f_ffs/aliases adb in the on fs section, before mount functionfs adb
Remove the on property:ro.debuggable=1 trigger and instead start adb explicitly by adding a section
```
on post-fs
    setprop service.adb.root 1
```

jwgcarlson commented 7 years ago

Regarding installing to /system/priv-app, you're in for a surprise. The system partition is protected by dm-verity, and on the Pixel it uses error correction to "undo" any small changes you make to the filesystem. You'll need to wait for something like SuperSU or Magisk to provide tools for making a system overlay.

Or, maybe you could just install to /data/app instead?

lalcd commented 7 years ago

Any good news on DP2? I Tried but failed :-(

jwgcarlson commented 7 years ago

The exact same procedure has worked for me with both DP2 and DP3.

If you can't afford to format userdata, you might be able to use e2fsck and tune2fs to get past the black/flickering screen:

stratman commented 6 years ago

My problem is, that while I totally understand the steps that Ttumbler has described, they seem to me to assume the phone is already rooted. My failing to complete those tasks (ro mount) is the end of my road at the moment.

What have I missed?

Ttumbler commented 6 years ago

Things have moved on.With ODP8.1 TWRP and Magisk work to access the bootloader and root the device.I can also install in priv-app now using jrummy root file explorer. Trick is to make sure the permissions of the APK and owner of the file are set to the same as other apps (664 and root).Follow the instructions on TWRP to get your bootloader unlocked. Get Magisk 15 and copy the zip onto your SD. Then in TWRP recovery mode install the Magisk zip.All works for me. On 9 Jan 2018 10:55 pm, stratman notifications@github.com wrote:My problem is, that while I totally understand the steps that Ttumbler has described, they seem to me to assume the phone is already rooted. My failing to complete those tasks (ro mount) is the end of my road at the moment. What have I missed?

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

stratman commented 6 years ago

Bear with me. My bootloader is unlocked The Magisk zip is on /sdcard My recovery is not there at all - not even Factory ("No command")