TWRP 3.2.3-2 for Pixel 3

[bigbiff]

Hello all, here is a test build for blueline on android-10.0. Do not flash it to boot or repack it to boot or you will not be able to boot android.

Just use fastboot boot to boot TWRP. I am hoping a kernel maintainer can enable LZMA ramdisk for testing TWRP repacking.

Please find it here: https://build.twrp.me/test/blueline/twrp-3.4.0-0-test1-blueline.img

Decryption works, backup/restore works.

Update: This has backup time/date fixed: Please find it here: https://build.twrp.me/test/blueline/twrp-3.4.0-0-test2-blueline.img

Please let me know of any issues.

 

[shaunoleary]

Hello all, here is a test build for blueline on android-10.0. Do not flash it to boot or repack it to boot or you will not be able to boot android.

......

Please let me know of any issues.

Firstly - thank you so much for your hard work on this.

I've tried both test1 and test2 builds on my blueline (running Lineageos 17.1 latest build, rooted with Magisk Canary).
Entering fastboot with

adb reboot bootloader

then loading TWRP with

fastboot boot twrp-3.4.0-0-test1-blueline.img

TWRP boots to the title screen with the TWRP logo (arrows) and TEAMWIN at the bottom, but does not progress further. I have left both builds on this boot screen for 10-20 minutes, but it does not seem to proceed further from there.

Am I doing something wrong?

Again - thanks.

 

[wangdaning]

I got in the habit of posting things on the Crosshatch forum, even though I use blueline. Both of these were able to boot on my phone, running DU 14.5 that I built. I changed flags to build Unicornblood kernel with LZMA support and it does allow the image to be installed through the twrp menu.

 

[NYCHitman1]

I got in the habit of posting things on the Crosshatch forum, even though I use blueline. Both of these were able to boot on my phone, running DU 14.5 that I built. I changed flags to build Unicornblood kernel with LZMA support and it does allow the image to be installed through the twrp menu.

Unicornblood already supports LZMA in ramdisk.

 

[bigbiff]

Firstly - thank you so much for your hard work on this.

I've tried both test1 and test2 builds on my blueline (running Lineageos 17.1 latest build, rooted with Magisk Canary).
Entering fastboot with

adb reboot bootloader

then loading TWRP with

fastboot boot twrp-3.4.0-0-test1-blueline.img

TWRP boots to the title screen with the TWRP logo (arrows) and TEAMWIN at the bottom, but does not progress further. I have left both builds on this boot screen for 10-20 minutes, but it does not seem to proceed further from there.

Am I doing something wrong?

Again - thanks.

There seems to be a few issues with apex locations but I have been working on other things at the moment. If you can post /tmp/recovery.log and logcat I can look it over for issues.

 

[wangdaning]

Unicornblood already supports LZMA in ramdisk.

I see it does. Oddly, I had made the change manually the same day you added the commit.

 

[johnpwu]

Stuck!

Hello,

Just got my replacement pixel after dropping and cracking my old one, and am struggling to get it set up with TWRP and root, in spite of having managed multiple times in the past. If anyone can help I would appreciate it tremendously!

I downloaded the linked copies of the TWRP img and zip and from fastboot performed the "fastboot boot twrp.img" command. Once booted into TWRP, I installed the zip file and attempted to reboot. Unfortunately, now I'm stuck on the fastboot screen with the following showing at the bottom: "Error reason: error boot prepare"

I'm really not sure where to go from here, as the phone won't currently boot normally.

Edit: tried getting back to stock using a factory Google image,but ran into an error (screen showed the green android and the computer acted as though the device was disconnected). Still have access to fastboot but can't boot the system.

 

[KurioHonoo]

Hello,

Just got my replacement pixel after dropping and cracking my old one, and am struggling to get it set up with TWRP and root, in spite of having managed multiple times in the past. If anyone can help I would appreciate it tremendously!

I downloaded the linked copies of the TWRP img and zip and from fastboot performed the "fastboot boot twrp.img" command. Once booted into TWRP, I installed the zip file and attempted to reboot. Unfortunately, now I'm stuck on the fastboot screen with the following showing at the bottom: "Error reason: error boot prepare"

I'm really not sure where to go from here, as the phone won't currently boot normally.

Edit: tried getting back to stock using a factory Google image,but ran into an error (screen showed the green android and the computer acted as though the device was disconnected). Still have access to fastboot but can't boot the system.

Go grab the stock boot.img from whatever build you're currently running and flash that using fastboot on both partitions.

 

[bigbiff]

Hello, this image will fix wiping data: https://build.twrp.me/test/blueline/twrp-3.4.0-0-test3-blueline.img

 

[johnpwu]

Go grab the stock boot.img from whatever build you're currently running and flash that using fastboot on both partitions.

Thanks for your reply. Unfortunately, after flashing to boot image to both slots, in fastboot I get an error "Enter reason: no valid slot to boot"

Tried grabbing the latest factory image (for 10) and going that route, but wound up with an error (see screenshot). Was left at the screen showing "fastbootd" (see second screenshot).

Device currently shows the initial (expected) bootloader unlocked message, then goes to the white Google screen briefly, before going to the fastboot screen showing "Enter reason: error booting boot.img" on rebooting, it shows "Enter reason: no valid slot to boot"

Really, really appreciate any help anyone can provide. Made sure to download the latest android sdk for up to date ADB and fastboot, also made sure I have the most up to date driver for android.

If anyone would be willing to PM me and help me out directly, I'd be happy to buy you a couple beers!

Thanks in advance!

 

[shaunoleary]

There seems to be a few issues with apex locations but I have been working on other things at the moment. If you can post /tmp/recovery.log and logcat I can look it over for issues.

Sure - here they are. And thank you for the reply. Wishing you all the best.

 

[KurioHonoo]

Thanks for your reply. Unfortunately, after flashing to boot image to both slots, in fastboot I get an error "Enter reason: no valid slot to boot"

Tried grabbing the latest factory image (for 10) and going that route, but wound up with an error (see screenshot). Was left at the screen showing "fastbootd" (see second screenshot).

Device currently shows the initial (expected) bootloader unlocked message, then goes to the white Google screen briefly, before going to the fastboot screen showing "Enter reason: error booting boot.img" on rebooting, it shows "Enter reason: no valid slot to boot"

Really, really appreciate any help anyone can provide. Made sure to download the latest android sdk for up to date ADB and fastboot, also made sure I have the most up to date driver for android.

It's also possible that you might just need to use a slightly older build of Android 10. Maybe grab something like the January release and try it with that. I think the February release and onward changed something, but I can't quite remember what it was.

If anyone would be willing to PM me and help me out directly, I'd be happy to buy you a couple beers!

Honestly, I would just try again using a different USB cable/USB port. Or if you can boot into stock recovery then you should try sideloading the OTA instead of using Fastboot.

You might also just need to download a slightly older release of Android 10. Maybe try something like the January release instead. I think the February release changed someone, but I can't quite remember what.

 

[bigbiff]

Sure - here they are. And thank you for the reply. Wishing you all the best.

While in TWRP, using adb shell can you execute

find / -name libion.so and see if it's found?

Also I would appreciate you doing this in android too.

 

[johnpwu]

Honestly, I would just try again using a different USB cable/USB port. Or if you can boot into stock recovery then you should try sideloading the OTA instead of using Fastboot.

You might also just need to download a slightly older release of Android 10. Maybe try something like the January release instead. I think the February release changed someone, but I can't quite remember what.

THANK YOU!!

Turned out to be a matter of trying a bunch of different cables.

 

[shaunoleary]

While in TWRP, using adb shell can you execute

find / -name libion.so and see if it's found?

Also I would appreciate you doing this in android too.

Done. Hope this is what you were looking for...
Cheers.

 

[bigbiff]

Done. Hope this is what you were looking for...
Cheers.

Please test http://build.twrp.me/test/blueline/twrp-3.4.0-0-test6-blueline.img and let me know if there are any issues.

 

[shaunoleary]

Please test http://build.twrp.me/test/blueline/twrp-3.4.0-0-test6-blueline.img and let me know if there are any issues.

Hi,

The test6 image boots! First time I've seen TWRP on my blueline. Well done (and again, thanks)!

When it boots, after the TWRP boot screen, it gives me a screen "Mount - Decrypt Data", and asking "Enter Password.", with a keyboard, and "Cancel" and "Select Language" buttons. Entered my android PIN and it proceeds to the main TWRP menu. Backup seems to work, as this is my daily use phone I haven't worked up the nerve to attempt a restore yet...

I've attempted an ADB sideload (tried to flash OpenGAPPS into existing system, just for the sake of something harmless to test with sideload) - adb can't see the phone for sideloading. When cancelling the sideload, TWRP gives error message "E:Unable to get child ID", and freezes with running progress bar at the bottom of the screen. I could not exit out of that screen, and had to hold down power button to get phone to reset and reboot to android.

 

[Portgas D. Ace]

...

When it boots, after the TWRP boot screen, it gives me a screen "Mount - Decrypt Data", and asking "Enter Password.", with a keyboard, and "Cancel" and "Select Language" buttons. I have no idea what the password should be.....

The required password should be your phone's default password which you use to unlock your device, e.g. after unlocking your screen.

 

[shaunoleary]

The required password should be your phone's default password which you use to unlock your device, e.g. after unlocking your screen.

Thanks - yeah, I just figured this out after posting - updated the post.

 

[bigbiff]

Hi,

The test6 image boots! First time I've seen TWRP on my blueline. Well done (and again, thanks)!

When it boots, after the TWRP boot screen, it gives me a screen "Mount - Decrypt Data", and asking "Enter Password.", with a keyboard, and "Cancel" and "Select Language" buttons. Entered my android PIN and it proceeds to the main TWRP menu. Backup seems to work, as this is my daily use phone I haven't worked up the nerve to attempt a restore yet...

I've attempted an ADB sideload (tried to flash OpenGAPPS into existing system, just for the sake of something harmless to test with sideload) - adb can't see the phone for sideloading. When cancelling the sideload, TWRP gives error message "E:Unable to get child ID", and freezes with running progress bar at the bottom of the screen. I could not exit out of that screen, and had to hold down power button to get phone to reset and reboot to android.

We are working on sideload and fastbootd which is our last 2 blocking features before we can support official 10 devices. Then we will chase android 11 encryption.