[RECOVERY][TWRP][dragon]

[_benedict_]

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]

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.

 

[_benedict_]

Thank you followmsi and sorry it was such a silly question :/

edit: it worked

 

[followmsi]

New TWRP version arrived .. twrp-3.6.0_9-0-dragon.img

The TWRP Team released version 3.6.0 !

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

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

Enjoy

 

[Alxoom33]

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.

 

[followmsi]

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

 

[Alxoom33]

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

 

[bernardomarx]

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:

Can't flash anything to Pixel C with `fastboot flash`, and fwtool is nowhere to be found

This is driving me nuts. I am trying (without success) to install LineageOS on my Pixel C. As a first step, I am trying to install TWRP. I have enabled Developer Mode, and the bootloader is unlocked. However, attempting to flash TWRP (or...

forum.xda-developers.com

 

[followmsi]

New TWRP version arrived .. twrp-3.6.1_9-0-dragon.img

The TWRP Team released version 3.6.1 !

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

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

Enjoy

 

[szescxz]

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.

 

[laffin_boy]

(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:

]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:

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?

 

[ipdev]

(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:

]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:

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.

[[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.

 

[laffin_boy]

"Good luck"

I used your 2nd method - individual partition flashing (w/o doing recovery - thought I could save TWRP - nope) - and it WORKED!!! I now have a working OS again.

Thank you very much for your clear explanations and for rescuing this frazzled newbie!

 

[followmsi]

New TWRP version arrived .. twrp-3.6.2_9-0-dragon.img

The TWRP Team released version 3.6.2 !

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

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

Enjoy

 

[EnginEAR]

New TWRP version arrived .. twrp-3.6.2_9-0-dragon.img

The TWRP Team released version 3.6.2 !

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

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

Enjoy

Will there eventually (not asking for an ETA) be a twrp-X.Y.Z_12-0-dragon.img version?

 

[ipdev]

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.

 

[EnginEAR]

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.

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.

 

[ipdev]

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.

 

[followmsi]

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

 

[EnginEAR]

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