TWRP Flame [Official]

Search This thread

b8842dc0

Senior Member
Nov 11, 2015
180
61
sha256sum looks good:

[email protected]:~/Downloads$ sha256sum twrp-3.5.0-0-test4-flame.img
853d28e385be9f10ab1eeac2411daa04ac8b2d4b29483a0e92ed4fa1925d6246 twrp-3.5.0-0-test4-flame.img

I just tried updating my fastboot and adb. Went from 30.0.5-6877874 to 31.0.3-7562133. That didn't help. Still get the same problem.

While I was in fastboot mode, I took note of some of the details on that screen, in case this reveals any useful information:

Product revision: flame MP1.0(NA)
Bootloader version: c2f2-0.2-5799621
Secure boot: PRODUCTION
NOS production: yes
Device state: unlocked
 

me-69

Member
Jan 26, 2019
14
4
My Pixel 4 is stuck in a bootloop after starting twrp-3.5.0-0-test4-flame.img
After I once wrecked my phone running lineage-18.1 in slot b, I did this test:

- Installed stock ROM flame-rq3a.211001.001 (latest A11) to both slots
- Rebooted to bootloader
- fastboot flash boot --slot=all lineage-18.1-20211121-recovery-flame.img
- Rebooted to lineage recovery (active slot b)
- adb sideload lineage-18.1-20211121-nightly-flame-signed.zip (to slot a)
- Rebooted to lineage recovery (active slot a)
- adb sideload open_gapps-arm64-11.0-nano-20211124.zip (to slot a)
- Factory reset / format data
- Boot lineage until "welcome".

- Rebooted to bootloader
- fastboot boot twrp-3.5.0-0-test4-flame.img
TWRP starts. In TWRP, I did nothing but "Boot to system".

No system boots after that.
Slot a -> endless lineage boot animation
Slot b -> stuck with the google logo at the very beginning
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,242
My Pixel 4 is stuck in a bootloop after starting twrp-3.5.0-0-test4-flame.img
After I once wrecked my phone running lineage-18.1 in slot b, I did this test:

- Installed stock ROM flame-rq3a.211001.001 (latest A11) to both slots
- Rebooted to bootloader
- fastboot flash boot --slot=all lineage-18.1-20211121-recovery-flame.img
- Rebooted to lineage recovery (active slot b)
- adb sideload lineage-18.1-20211121-nightly-flame-signed.zip (to slot a)
- Rebooted to lineage recovery (active slot a)
- adb sideload open_gapps-arm64-11.0-nano-20211124.zip (to slot a)
- Factory reset / format data
- Boot lineage until "welcome".

- Rebooted to bootloader
- fastboot boot twrp-3.5.0-0-test4-flame.img
TWRP starts. In TWRP, I did nothing but "Boot to system".

No system boots after that.
Slot a -> endless lineage boot animation
Slot b -> stuck with the google logo at the very beginning
Hi, I put a newer version in the OP that boots properly. TWRP 3.6 official is imminent release for all devices soon.
 
  • Like
Reactions: bleh815

me-69

Member
Jan 26, 2019
14
4
Hi, I put a newer version in the OP that boots properly. TWRP 3.6 official is imminent release for all devices soon.

Thanks a lot! Now the phone starts again after using TWRP.

Unfortunately I can't restore the backup I made just before my phone crashed:
extractTarFork() process ended with ERROR: 255
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,242
It looks like you wiped your FBE keys with a full wipe, so you cannot restore your backup unfortunately.
 

me-69

Member
Jan 26, 2019
14
4
Don't know... This is my daily driver, so I already began reinstalling everything by hand now. I was able to extract some settings from the nandroid backup using titanium backup pro -- far away from a complete restore, but obviously the user date isn't completely encrypted also. Anyways, I'll have to stop testing for now...
 

mbcct

New member
Dec 7, 2021
1
0
FAIL TO INSTALL TWRP on AOSP 11 PIXEL 4 (FLAME)

I'm trying to install TWRP 3.6.0 on an AOSP build that I have built from the tag (android-11.0.0_r46).

I build aosp_flame_userdebug from AOSP and I flash the images on my Google Pixel 4:
- adb reboot bootloader
- fastboot flashall -w

Device reboot and everything seems to be running fine running fine.

Then I try to install TWRP:
- adb reboot bootloader
- fastboot boot twrp-3.6.0_11-0-flame.img

My device start to boot the TWRP image but it gets stuck in the splash screen of TWRP.

Using adb shell dmesg, I see a lot of error like this:
init: Control message: Could not find '[email protected]::IKeymasterDevice/default' for ctl.interface_start from pid: 549 (/system/bin/hwservicemanager)

Any idea why I'm not able to boot in TWRP?
Using the same procedure on a factory image of android 11, everything woks find and I can install TWRP without any problem.
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,242
FAIL TO INSTALL TWRP on AOSP 11 PIXEL 4 (FLAME)

I'm trying to install TWRP 3.6.0 on an AOSP build that I have built from the tag (android-11.0.0_r46).

I build aosp_flame_userdebug from AOSP and I flash the images on my Google Pixel 4:
- adb reboot bootloader
- fastboot flashall -w

Device reboot and everything seems to be running fine running fine.

Then I try to install TWRP:
- adb reboot bootloader
- fastboot boot twrp-3.6.0_11-0-flame.img

My device start to boot the TWRP image but it gets stuck in the splash screen of TWRP.

Using adb shell dmesg, I see a lot of error like this:
init: Control message: Could not find '[email protected]::IKeymasterDevice/default' for ctl.interface_start from pid: 549 (/system/bin/hwservicemanager)

Any idea why I'm not able to boot in TWRP?
Using the same procedure on a factory image of android 11, everything woks find and I can install TWRP without any problem.
Can you pull logcat and recovery.log via adb for debugging?
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,242

Feser31

Member
Mar 4, 2021
7
0
Hi gays, After installation twrp 3.6.1, I can not boot into the system writes: no valid slot to boot
 

Top Liked Posts