vassiliszacharis said:

Thanks can you explain further the process of installing custom ROM via fastboot? I am used to installing custom ROMs by copy them to an SD card

adb reboot bootloader
fastboot flash boot magisk_patched_boot.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash boot magisk_patched_boot.img
fastboot flash system rom_img_you_want_to_install(extract from zip file)
fastboot -w
fastboot format cache
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot

adb reboot bootloader
fastboot flash boot boot.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash boot boot.img
fastboot flash system rom_img_you_want_to_install(extract from zip file)
fastboot -w
fastboot format cache
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot

zenowaren said:

I followed the guide below. It is for ZA5G0100TR. I am not sure if it will work for your device too.

First of all Have platform-tools installed for adb / fastboot

Here it is important to select the rom file which is suitable for your device.

I am not responsible for bricked devices.

- I presume you unlocked bootloader. Otherwise -> Unlocking Bootloader
- If you want root -> Steps 2-3 (You must get boot.img and vbmeta.img from your stock rom version which is already runnig your device) you might find your stock rom from here

Warning, all user data, apps etc. will be deleted.

If you want root just use pached_boot.img;

Code:

adb reboot bootloader
fastboot flash boot magisk_patched_boot.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash boot magisk_patched_boot.img
fastboot flash system rom_img_you_want_to_install(extract from zip file)
fastboot -w
fastboot format cache
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot

If you dont want root just use stock boot.img and vbmeta.img from your device stock rom;

Code:

adb reboot bootloader
fastboot flash boot boot.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash boot boot.img
fastboot flash system rom_img_you_want_to_install(extract from zip file)
fastboot -w
fastboot format cache
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot

Click to expand...

Cheers mate I tried all the same again. I think I will go to stock ROM, tough luck

vassiliszacharis said:

I think I will go to stock ROM,

AFAIK, I need to do in any case when a custom rom flash was unsuccessful

BTW:
is your device in this list ?

Lenovo and Motorola

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

rw_on_xda said:

AFAIK, I need to do in any case when a custom rom flash was unsuccessful

BTW:
is your device in this list ?

Lenovo and Motorola

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

Click to expand...

My device is Lenovo tablet X606-F. Some have already managed to install it. Some other like me, unfortunately not. It might be TWRP fault. My device is not on that particular list mate.

vassiliszacharis said:

My device is Lenovo tablet X606-F. Some have already managed to install it. Some other like me, unfortunately not. It might be TWRP fault. My device is not on that particular list mate.

Then you should search for an HowTo-flash for your device.

I'm currently unsure if you got what I said before, so again:
On my SM-T510 I need to *first* flash stock with bootloader unlock, etc if a custom rom flash failed.

over and over again flashing a custom rom under TWRP (no idea if so too via fastboot) when one flash failed won't lead to an successful custom rom flash

vassiliszacharis said:

My device is Lenovo tablet X606-F. Some have already managed to install it. Some other like me, unfortunately not. It might be TWRP fault. My device is not on that particular list mate.

Sorry I logged into xda after 2 months. Try Telegram for your device group or contact Developer named Eternityson on Telegram, he is very helpful and he is Developer for CAOS11 and Other GSI ROMS like A11 CrDroidv316 R-Mod. He can definitely tell you how to boot his GSI on Lenovo Tab or further directions. I flashed for Shamshung device SM-M215G using TWRP after unlocking bootloader, you have to check in Developer Optons if the Unlock Bootloader option is greyed out, if not greyed out you cannot flash any TWRP or ROM or GSI as it will reboot to Stock Recovery or maybe bootloader. To make Unlock Bootloader option greyed out, after you have unlocked bootloader connect to internet for 10 seconds and the Unlock Bootloader option will be greyed out automatically, after that flashing anything is possible, this is for Shamshung but check for Lenovo, the steps could be a bit different to unlock bootloader properly.

vassiliszacharis said:

Thank you mates I installed again stock ROM then installed lineage android 12, no luck with CAOS though...

Treble Info - Apps on Google Play

Helps you check Project Treble, A/B and Architecture for GSI installation

play.google.com

rw_on_xda said:

have you checked the correct caos rom variant with this app ?

Treble Info - Apps on Google Play

Helps you check Project Treble, A/B and Architecture for GSI installation

play.google.com

- you need to unzip the caos*.xz, e.g. "xz -dkv caos-*.xz" (on a linux box)
- copy the unzipped file to an sdcard on your device
- reboot into TWRP
- format DATA (and /or System ???)
- flash the caos rom to System

that's what I did on my SM-T510.

I guess if you could flash lineage you should be able to flash caos too
and currently you don't need to install stock with your TWRP installed.
just go though the above steps.

sure if the caos flash fails you need to flash stock again to get the device in a clean state

P.S.
currently I'm unsure what the differences between lineage and caos are, but I guess they aren't much ...

Click to expand...

I have tested both CAOS 11 & CrDroid11 R-Mod , both are made by same dev Eternityson, I found CrDroid11 better than CAOS11, but thats just my opinion. User can try both for a week and compare.

vassiliszacharis said:

Is CAOS ROM still on Android 11 or have already been updated to let's say android 12 or Android 13?

yes its on A11 till now.

OldNoobOne said:

Hi Eternityson, Can you post Caos11 OR CrDroid 11 - R-Mod with latest Security Patch? Its great Gsi-Rom you have made . Waiting for your reply.

I guess you'll need to wait somewhat longer, cause (see first page) cit.:
"CAOS 11 (Custom AOSP OS) is a project which based on @phhusson's Treble GSI AOSP 11..."

and the last looks like this:

Releases · phhusson/treble_experimentations

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

Terrorigel97 said:

this rom is asking for an passwort to boot why?

my wild guess (cause your lack of enough info's):
- cause bootloader is unlocked (but it boots after some seconds or after pressing power button)
OR
- cause you didn't wipe data (see 1st page)

Gueron said:

Hi Eremitein,

I am quite frustrated at the moment, and I dont know how to solve this..
I really like your GSI rom developments, and appreciate the work you have done, thanks.
But only on "paper" since I cant seem to flash any of them.

I have a Samsung A10e with unlocked bootloader and dm-verity canceled.
I use heimdall to flash.
I have successfully flashed AndyYans Lineage (17 and 18) and Of2pks Aosp (Android 10 and 11).
In all cases I extract the download file using xz on linux.

But whichever of your ROM builds (Caos, Crdroid, LiR), Android 10 or 11, various dates, Heimdall
gives me an error after 3% flash...
ERROR: Failed to confirm end of file transfer sequence
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

I have tried with magisk patched stock boot, recovery, and also flashing with twrp. Twrp will
flash but wont boot, goes to bootloader instead.

Searching for Heimdall answers on internet have not helped. I wonder whether there is some
difference in the xz compression you use or Rom signature.

I would appreciate any insight you could give me.. thanks !!

Click to expand...

Today I tried decompressing xz file using peazip on windows. Same result. Also tried flashing with Pbrp, same result as twrp...

Gueron said:

Today I tried decompressing xz file using peazip on windows. Same result. Also tried flashing with Pbrp, same result as twrp...

Finally success... So still no luck with Heimdall flash, but twrp completed. I had tried dirty flashing crdroid and lir with the expectation to keep my lineage data. So in the end I could boot once I had wiped data. Now I am trying to recover my seedvault saved data with Caos... Is the data storage compatible with other aosp roms ? I was hoping to try this - https://forum.xda-developers.com/t/...al-cve-august-2021-arm32-64-vndklite.4281231/

Gueron said:

Finally success... So still no luck with Heimdall flash, but twrp completed. I had tried dirty flashing crdroid and lir with the expectation to keep my lineage data. So in the end I could boot once I had wiped data. Now I am trying to recover my seedvault saved data with Caos... Is the data storage compatible with other aosp roms ? I was hoping to try this - https://forum.xda-developers.com/t/...al-cve-august-2021-arm32-64-vndklite.4281231/

Hi Gueron, This A11 GSI ROM is the BEST till date (as far as my device Galaxy M21 2021 Edition is concerned).
For the last 1.5 Years I have been trying out almost each and every GSI ROM on github-phh-gsi-list right from A11 upto A13, nothing beats This CrDroid R-Mod A11 by Eremitein a.k.a Eternityson. 32 Hours of Battery Backup...smooth & stable. Best So far. I didn't like the Andoid Versions above A11. Eremitein is from Ukraine so its a war zone right now, I wish him good luck and thanks for his GSI-ROM.