[RECOVERY][TWRP][dragon][3.6.2] -> 2022-06-01

Search This thread

_benedict_

Senior Member
Try to run following command in adb shell ..
"fwtool vbnv write dev_boot_fastboot_full_cap 1"

In case twrp recovery or system have been already erased you might get stuck ..
They have never been erased because the tablet is still running factory Android and bootloader is still locked.


So how should I proceed from there? Sorry it's been a long time and I forgot the procedure.
 

followmsi

Senior Member
Oct 10, 2013
4,215
13,079
They have never been erased because the tablet is still running factory Android and bootloader is still locked.


So how should I proceed from there? Sorry it's been a long time and I forgot the procedure.

In this case you need to unlock bootloader first .. and follow normal procedure to install custom ROM.

The "fwtool vbnv write dev_boot_fastboot_full_cap 1" command helps on unlocked bootloader with 'unsupported command' issue.
 

followmsi

Senior Member
Oct 10, 2013
4,215
13,079
I dl'd and flashed. Didn't work to me. When I booted to recovery, it booted up to system.
Will try again, but I have to update ADB/Fastboot drivers.

To prevent any cables or any fastboot drivers ..

Just install the new version from your current TWRP ..
Install the twrp.img as "Image" onto your recovery partition .. afterwards you directly reboot into recovery and enjoy the new version.

Of course, you need to have a working TWRP version to install an Image.
Without any TWRP version installed you have to go for cable and fastboot drivers first.

Cheers
 
  • Like
Reactions: Alxoom33

Alxoom33

Senior Member
May 18, 2011
5,098
1,818
New York
www.sack-ip.com
To prevent any cables or any fastboot drivers ..

Just install the new version from your current TWRP ..
Install the twrp.img as "Image" onto your recovery partition .. afterwards you directly reboot into recovery and enjoy the new version.

Of course, you need to have a working TWRP version to install an Image.
Without any TWRP version installed you have to go for cable and fastboot drivers first.

Cheers
Yeah, that's the dig! TWRP and Fastboot were not working for me. Tried updating adb and Fastboot by instlling the latest SDK Tools for Windows 10.1, tried a bunch of cables, all work on my Taimen. So not sure what else to try?? Can I fastboot from a Chromebook?

I solved the immediate problem by using Flashify to flash the new LOS 19 update, gapps and Magisk. Also was able to flash TWRP. Everything working now. Except Fastboot :)
 
Last edited:
  • Like
Reactions: followmsi and ipdev

bernardomarx

Member
Dec 31, 2021
11
2
In this case you need to unlock bootloader first .. and follow normal procedure to install custom ROM.

The "fwtool vbnv write dev_boot_fastboot_full_cap 1" command helps on unlocked bootloader with 'unsupported command' issue.

Any other way to set that flag from a context other than adb/recovery?

See also:
 

szescxz

Member
Sep 1, 2019
15
3
For some reason I cannot flash OpenGApps with 3.6.1. Script finished without error but no GApps was actually installed. I think this might be related to system partition not being correctly mounted, as I noticed the following in OpenGApps' log:
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.
Tested with last official build of LineageOS 15.1. Downgraded TWRP to 3.6.0 and everything works as expected.
 
Last edited:

laffin_boy

Member
Dec 15, 2021
33
6
(This is not necessarily a TWRP issue but if I have any options left it's almost certainly going to involve TWRP so...)

The system & vendor partitions on my Pixel C seems to have been erased as I learned (the hard way) how to use TWRP (3.6.1).
--The device is unlocked.
-- adb & fastboot still work
-- the data partition was reformatted so TWRP doesn't ask for passwords
-- I can still get to the bootloader screen and recovery.
-- I have TWRP installed but it can't see my USB-OTG drive now - although it used to be able to - so I can't install anything from TWRP.
-- I tried to sideload LOS 15.1 but it failed with these errors in TWRP:

Code:
]Failed to mount '/system (invalid argument)
updating partition details...
Failed to mount '/vendor (invalid argument)
Failed to mount '/system (invalid argument)
...done
Full LinuxSE support is present.
MTP Enabled
Failed to mount '/system (invalid argument)
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Unmounting system'
Warning: no file contents
Target: google/ryu/dragon:8.1.0/OPM8.190605/5749003:user/release-keys
could not detect file system for dev/blockplatform/700b0600.sdhci/by-name/APP at /system: invalid argument
failed to unmount /system: no such volume
script aborted (no error message)
updater process ended with error:  7

Then I tried to install factory 8.1 image from fastboot. It failed with the following console errors:

Code:
H:\Android\ADB>flash-all
Sending 'bootloader' (16384 KB)                    OKAY [  0.515s]
Writing 'bootloader'                               (bootloader) writing flash
OKAY [ 90.105s]
Finished. Total time: 90.636s
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.139.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'partition-size:system'                   OKAY [  0.016s]
Snapshot cancel                                    FAILED (remote: 'unknown command')
fastboot: error: Command failed

What can I do to get ANYTHING installed on this device?
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
1,929
1
3,551
Google Nexus 10
Nexus 7 (2013)
(This is not necessarily a TWRP issue but if I have any options left it's almost certainly going to involve TWRP so...)

The system & vendor partitions on my Pixel C seems to have been erased as I learned (the hard way) how to use TWRP (3.6.1).
--The device is unlocked.
-- adb & fastboot still work
-- the data partition was reformatted so TWRP doesn't ask for passwords
-- I can still get to the bootloader screen and recovery.
-- I have TWRP installed but it can't see my USB-OTG drive now - although it used to be able to - so I can't install anything from TWRP.
-- I tried to sideload LOS 15.1 but it failed with these errors in TWRP:

Code:
]Failed to mount '/system (invalid argument)
updating partition details...
Failed to mount '/vendor (invalid argument)
Failed to mount '/system (invalid argument)
...done
Full LinuxSE support is present.
MTP Enabled
Failed to mount '/system (invalid argument)
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Unmounting system'
Warning: no file contents
Target: google/ryu/dragon:8.1.0/OPM8.190605/5749003:user/release-keys
could not detect file system for dev/blockplatform/700b0600.sdhci/by-name/APP at /system: invalid argument
failed to unmount /system: no such volume
script aborted (no error message)
updater process ended with error:  7

Then I tried to install factory 8.1 image from fastboot. It failed with the following console errors:

Code:
H:\Android\ADB>flash-all
Sending 'bootloader' (16384 KB)                    OKAY [  0.515s]
Writing 'bootloader'                               (bootloader) writing flash
OKAY [ 90.105s]
Finished. Total time: 90.636s
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.139.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'partition-size:system'                   OKAY [  0.016s]
Snapshot cancel                                    FAILED (remote: 'unknown command')
fastboot: error: Command failed

What can I do to get ANYTHING installed on this device?

I have sideload issues on mine as well.
Not sure why. I haven't had time to look into it.

For now I just push the rom and Gapps to the sideload directory and then use the regular install option in TWRP to install it.
The /sideload/ directory is a temporary directory when booted into TWRP. Once you reboot it will be gone and empty the next time you boot into TWRP.​

Example.
Code:
[[email protected] cr]$ adb push crDroidAndroid-12.1-20220326-dragon-v8.3.zip /sideload/
crDroidAndroid-12.1-20220326-dragon-v8.3.zip: 1 file pushed, 0 skipped. 8.9 MB/s (783255506 bytes in 84.285s)
[[email protected] cr]$ adb push /ip/opengapps/20220311/open_gapps-arm64-12L-nano-20220311-UNOFFICIAL_MOD.zip /sideload/
/ip/opengapps/20220311/open_gapps-arm64-12L-nano-20220311-UNOFFICIAL_MOD.zip: 1 file pushed, 0 skipped. 9.8 MB/s (233310248 bytes in 22.781s)
[[email protected] cr]$

--

About the stock flash-all script not working.
It is not uncommon for older devices.
Updates to the fastboot command are not always backward compatible.

Instead you have to flash the images manually.

The bootloader is in the main zip file.
Probably do not need to flash it again since it is the current and already installed.

Unzip image-ryu-opm8.190605.005.zip to get the boot, cache, recovery, system and vendor images.

Erase and format cache and userdata.
fastboot -w should work.
If not, use fastboot erase and format.
fastboot erase cache then fastboot format cache


Flash the images to their corresponding partition.
fastboot flash system system.img


Good luck.

Cheers. :cowboy:
 

EnginEAR

Senior Member
Mar 19, 2008
290
85
Tel Aviv

ipdev

Recognized Contributor
Feb 14, 2016
1,929
1
3,551
Google Nexus 10
Nexus 7 (2013)
Will there eventually (not asking for an ETA) be a twrp-X.Y.Z_12-0-dragon.img version?
Highly doubtful. 🙂
The last factory release for ryu (dragon) was Android 8.1.0 (OPM8.190605.005, Jun 2019).

---

TWRP is built based on device rom build.
Normally omni or (cm)Lineage.
The recovery part is replaced by TWRP so when recovery is built, it builds TWRP instead.

The major changes in Android (AOSP) can not be supported by older devices.
Dynamic Partitions for example.​
The major changes in Android start with Android 9/10.
Devices based on Android 9 and lower, build using the TWRP 9 branch.

That is why A12 fixes are included in the TWRP 9 branch.

Android 9 and Android 11 Branches
  • A12 keymaster keyblob structure file update (for no pin encryption) - zhenyolka & Quallenauge
  • Fixes
    • Override bootctrl for flashing images - CaptainThrowback
Android 9 Branch
  • Keymaster 3 dump functions - koron393

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
 

EnginEAR

Senior Member
Mar 19, 2008
290
85
Tel Aviv
Highly doubtful. 🙂
The last factory release for ryu (dragon) was Android 8.1.0 (OPM8.190605.005, Jun 2019).

---

TWRP is built based on device rom build.
Normally omni or (cm)Lineage.
The recovery part is replaced by TWRP so when recovery is built, it builds TWRP instead.

The major changes in Android (AOSP) can not be supported by older devices.
Dynamic Partitions for example.​
The major changes in Android start with Android 9/10.
Devices based on Android 9 and lower, build using the TWRP 9 branch.

That is why A12 fixes are included in the TWRP 9 branch.

Android 9 and Android 11 Branches​
  • A12 keymaster keyblob structure file update (for no pin encryption) - zhenyolka & Quallenauge
  • Fixes
    • Override bootctrl for flashing images - CaptainThrowback
Android 9 Branch​
  • Keymaster 3 dump functions - koron393

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
Actually confuses... If it's built based on device ROM build and (CM)Lineage is Android 12L - why wouldn't it be "Android 12 branch"? Sorry if question is stupid. I did read, but might have understood something wrong.
 
  • Like
Reactions: ipdev

ipdev

Recognized Contributor
Feb 14, 2016
1,929
1
3,551
Google Nexus 10
Nexus 7 (2013)
Actually confuses... If it's built based on device ROM build and (CM)Lineage is Android 12L - why wouldn't it be "Android 12 branch"? Sorry if question is stupid. I did read, but might have understood something wrong.
All questions are stupid. 🙂

We are all stupid about something.
It is the reason we ask a question. 🙃
The more I learn, the more I ask questions.
The more answers I understand, normally leads me to more of what I do not know. 😜

I failed at answering your original question.
Sorry. I am not sure how to explain it better. 🙁

The only thing I can think to add is about backwards compatibility.

Backporting Android 12(12L) to work with older devices..
Older devices are not updated to current device changes.
Instead the current changes are altered to work with the older device.​

Maybe followmsi or someone else can also help answer your question. 🙃

Cheers. :cowboy:
 
  • Like
Reactions: followmsi

followmsi

Senior Member
Oct 10, 2013
4,215
13,079
Actually confuses... If it's built based on device ROM build and (CM)Lineage is Android 12L - why wouldn't it be "Android 12 branch"? Sorry if question is stupid. I did read, but might have understood something wrong.

Like ipdev said .. newer devices require to handle stuff differently as older devices.
The reason why TWRP team maintains different branches.

Even we would use TWRP 12 branch for Pixel C .. TWRP will not work better .. maybe worse.

On gdrive inside the TWRP folder there is a test version to fix sideloading .. but breaking MTP. ( twrp-3.6.2_9-1-dragon_followmsi.img )

Cheers
 
  • Like
Reactions: ipdev and EnginEAR

EnginEAR

Senior Member
Mar 19, 2008
290
85
Tel Aviv
Like ipdev said .. newer devices require to handle stuff differently as older devices.
The reason why TWRP team maintains different branches.

Even we would use TWRP 12 branch for Pixel C .. TWRP will not work better .. maybe worse.

On gdrive inside the TWRP folder there is a test version to fix sideloading .. but breaking MTP. ( twrp-3.6.2_9-1-dragon_followmsi.img )

Cheers
I've been using it since you put it on Google Drive :)
 
  • Like
Reactions: followmsi and ipdev

Top Liked Posts

  • There are no posts matching your filters.
  • 34
    April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !

    https://twrp.me/google/googlepixelc.html

    twrp-3.6.2_9-0-dragon.img

    I would like to continue this thread for publishing test builds and other troubleshooting.
    Once the changes are stable and tested I will merge them into TeamWin github for the next official build.

    Known issues:
    - FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.

    Changes:
    Official 3.6.2
    (2022-06-01)
    - New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html

    Official 3.6.1 (2022-03-10)
    - New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html

    Official 3.6.0 (2021-11-28)
    - New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html

    Official 3.5.2 (2021-04-07)
    - New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html

    Official 3.5.1 (2021-03-17)
    - New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html

    Official 3.5.0 (2020-12-31)
    - New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html

    Official 3.4.0-0 (2020-06-22)
    - New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html

    Official 3.3.1-2 (2020-03-01)
    - Script updates to improve encryption -> Thanks to updateing from Team Mokee !

    Official 3.3.1-1 (2020-01-27)
    - Script updates for Android 10
    - Added more languages
    - Fixed build issues
    - New Kernel

    Official 3.3.1-0 (2019-05-19)
    - New official version

    Official 3.3.0-0 (2019-04-10)
    - New official version

    Official 3.2.3-0 (2018-07-29)
    - New official version
    * Fix automatic installing of OTA zips on encrypted devices
    * Remove SuperSU from TWRP
    * Support both md5 and md5sum file extensions when doing MD5 checking for zip files

    Official 3.2.2-0 (2018-06-30)
    - New official version
    * DRM changes

    Official 3.2.1-0 (2017-12-18)
    - New official version

    Official 3.2.0-0 (2017-11-29)
    - New official version

    Official 3.1.1-1 (2017-09-15)
    - Including all changes for Oreo and for better en/decryption from unofficial V1 and V2

    Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
    - New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.

    Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
    - Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)

    Official 3.1.1-0 (2017-05-17)
    - Upgrade to 3.1.1-0

    Unofficial 3.1.1-0 (2017-05-14)
    - Latest TWRP changes (3.1.1)
    - Latest kernel sources (2017-05-12)
    - Latest LineageOS changes (Android 7.1.2)

    Official 3.1.0-0 (2017-04-01)
    - Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.

    3.1.0-2
    - Custom installer script problems should be fixed now.

    3.1.0-1
    - Removed all the FBE changes - will take longer to get it running on dragon :)
    - Added NTFS-3G support for NTFS R/W -> USB-OTG
    - Used new kernel binary with changed F2FS config

    3.1.0-0
    - @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
    - Added some more config changes for FBE.

    3.0.3-4
    - Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.

    3.0.3-3
    - Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
    - fstab modification (usb-otg -> auto)

    3.0.3-2
    - F2FS enabled
    - tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)

    3.0.3-1
    - Based on Android 7.1.1 AOSP -> android-7.1.1_r14
    - Based on TWRP branch for Android 7.1
    - tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)

    v23
    - Based on Android 7 AOSP -> android-7.0.0_r3
    - Based on TWRP branch for Android 7
    - tegra-3.18 kernel -> v160907

    v22
    - Based on Android 7 AOSP -> android-7.0.0_r1
    - Based on TWRP branch for Android 7
    - chromeos-3.18 kernel -> v160823
    - Maybe not fully working as v21 due to new sources.

    v21
    - Added BRIGHTNESS PATH ... Thx to @ggow

    v20
    - Added Battery PATH ... Thx to @ggow

    v19
    - "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now :)
    - New versioning

    v18
    - MTP is working in recovery now !
    - Added dragon keyboard layout files

    v17
    - "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
    - chromeos-3.18 kernel -> v160618

    v16
    - ADB shell was not working in recovery - fixed now !
    - chromeos-3.18 kernel -> v160617


    fwtool
    The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
    The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
    If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
    For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96


    Installation:
    Please install the new version from your current TWRP.
    Pls make a "reboot to recovery" once you have installed the new version.
    Of course you can install it via fastboot too.


    Sources:
    https://github.com/TeamWin/android_device_google_dragon
    https://github.com/omnirom/android_bootable_recovery


    DOWNLOAD:
    https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw


    Have fun!


    XDA:DevDB Information
    [TWRP][dragon], Tool/Utility for the Google Pixel C

    Contributors
    followmsi

    Version Information
    Status:
    Stable
    Current Stable Version: 3.3.1-2
    Stable Release Date: 2017-04-01

    Created 2016-06-17
    Last Updated 2020-03-01
    11
    April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !

    https://twrp.me/devices/googlepixelc.html

    twrp-3.1.0-0-dragon.img

    Changes:
    Official 3.1.0-0
    - Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.

    I would like to continue this thread for publishing test builds and other troubleshooting.
    Once the changes are stable and tested I will merge them into TeamWin github for the next official build.

    Enjoy :)
    11
    New TWRP build arrived .. twrp-3.3.1-2-dragon.img

    To improve encryption .. Thanks to updateing from Team Mokee !

    TWRP website has some server replication issues in the moment.
    The new build is not available on European download server .. just on American server for the moment.

    Changes:
    Official 3.3.1-2 (2020-03-01)
    - Script updates to improve encryption -> https://gerrit.twrp.me/c/android_device_google_dragon/+/1991

    Sources:
    https://github.com/TeamWin/android_device_google_dragon

    Enjoy :p
    11
    Made a quick build to test latest 3.4.0 sources .. https://github.com/TeamWin/android_bootable_recovery/commits/android-9.0

    TWRP team added permissions.xml for the TWRP app.
    This should prevent boot problems for devices running Android 10 .. in case you have agreed to install TWRP app from recovery.

    twrp-3.4.0-test-dragon.img

    Happy testing :p
    11
    Finally ..
    New official version .. twrp-3.3.1-1-dragon.img

    Changes:
    Official 3.3.1-1 (2020-01-27)
    - Script updates for Android 10
    - Added more languages
    - Fixed build issues
    - New Kernel

    Sources:
    https://github.com/TeamWin/android_device_google_dragon

    Enjoy :p