yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] rfresh:
Wow, really great to see this phone is under development

Can I use this image?

/lineage-21-td/lineage-21.0-20240424-UNOFFICIAL-a64_bvN.img.xz
[Upgrading, Modifying and Unlocking] nuttydoc:
It shall work like any other a64 image. Only thing I am not sure about is 4G VOLTE. AFAIK IMS apk needed for 4G VOLTE doesn't work with newer GSI versions like android 14. I haven't tried lineage 21.
[Upgrading, Modifying and Unlocking] seawildflower:
I'll test the volte this week
[Upgrading, Modifying and Unlocking] rfresh:
My phone is on the way and can't wait to try this fantastic tutorial.
[Upgrading, Modifying and Unlocking] rainland666:
anyone tried latest android 14 ROM yet ?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] nuttydoc:
Yes. 4G VOLTE doesn't work. It can be used if only 2g/3g network is required.
[Upgrading, Modifying and Unlocking] rainland666:
Thanks, so can I make a phone call and receive SMS as a regular phone ?

How about GPS and wifi?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] nuttydoc:
Depends on your network provider. Phone call/sms shall work if there is 2g/3g network. Phone call on 4G network will not work. SMS on 4G may work will little tweaking of settings. There shall be no problem with GPS and wifi. Voice over wifi will not work.
[Upgrading, Modifying and Unlocking] rainland666:
I would like to use it on US Mobile which is on t-mobile network, any chance we can get phone call on 4G work ?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] seawildflower:
strange problem for me.

After flashing lineage 21 I am stuck in boot loop. When i boot into boot loader and select recovery, I am stuck with with a droid tipped over and words displaying "no command"

I cleared cache with "fastboot erase cache" and rebooted back to recovery. I still get no command with droid on the screen.

---

RECOVERY "NO COMMAND" FIXED

If you try to boot into recovery and you get "no command", hold the power button, and tap vol-up until recovery screen appears. be careful not to press the ptt button or it will not work.

---

When I try to reflash the rom, it fails and i get an error, "partition table does not exist"

UPDATE

currently floowing this revert to stock guide, will update soon. if someone could advise what went wrong here that would be great!

Cat S22 Flip - revert to Stock

Not sure if this is the correct place for this, as there isn't a dedicated Cat S22 forum. Instructions on restoring stock on the Cat S22. Note, you perform this at your own risk, there is a chance of bricking your phone if you do something...

xdaforums.com

UPDATE 2

The guide above will successfully bring you back to stock, but for those following this guide and have deleted "product" partition you will receive an error when attempting to flash product.img. do this,

enter fastbootd if not already

fastboot reboot fastboot

fastboot create-logical-partition product 100000

now you can flash product.img
[Upgrading, Modifying and Unlocking] rainland666:
Appreciate your support of this ROM, I would like to try out android 14 and see if it could be a daily use

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] seawildflower:
I am having issues after reverting back to stock and trying to update to v30 again.
[Upgrading, Modifying and Unlocking] nuttydoc:
Once you revert back to stock, it should work like stock without issues. Try clean install, starting with "fastboot -w" followed by reflashing all partitions.

Go to fastboot mode(not fastbootd)

adb reboot bootloader

and do below

fastboot -w
fastboot erase cache

fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash modem modem.img
fastboot flash dsp adspso.img
fastboot flash dtbo dtbo.img

Now boot into fastbootd (not fastboot) and flash remaining images:

fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
[Upgrading, Modifying and Unlocking] seawildflower:
fastboot -w

/usr/lib/android-sdk/platform-tools/make_f2fs failed with status 1

fastboot: error: cannot generate image for user data
[Upgrading, Modifying and Unlocking] nuttydoc:
Make sure you are in bootloader mode and not in fastbootd mode.
[Upgrading, Modifying and Unlocking] seawildflower:
I am in bootloader and not fastbootd
[Upgrading, Modifying and Unlocking] seawildflower:
Is there anything else I can do to generate image for user data?
[Upgrading, Modifying and Unlocking] nuttydoc:
This error is unusual, never faced it before. Instead of fastboot -w, just do "fastboot erase userdata" and continue with rest.

EDIT: btw, which fastboot version you are using, is it windows or linux?
[Upgrading, Modifying and Unlocking] seawildflower:
I tried running fastboot -w in fastbootd. heres what happened.

Erasing 'userdata' OKAY

Erase successful, but not automatically formatting

filesystem raw type not supported

Erasing 'cache'

(Same as above)
[Upgrading, Modifying and Unlocking] seawildflower:
Linux,

COMMAND

fastboot erase useradata

********** Did you mean to fastboot format this ext4 partition?

Erasing 'userdata' OKAY

Finished
[Upgrading, Modifying and Unlocking] nuttydoc:
We are just looking for clean install of stock rom. "fastboot -w" actually erase userdata/cache and formats the partition. I don't know why it is failing in your case. But we should be fine with erasing cache and userdata.
[Upgrading, Modifying and Unlocking] seawildflower:
I have finished flashing all the image files you have listed previously. I will reboot and attempt v30 update?
[Upgrading, Modifying and Unlocking] seawildflower:
When trying to update through Android the update downloads but will not reboot. Giving an error "verification problem"
[Upgrading, Modifying and Unlocking] seawildflower:
Is it possible to flash v30 images the same way we just did it for v29?
[Upgrading, Modifying and Unlocking] nuttydoc:
Stock v30 is partial upgrade, so all files are not there. However someone has produced lite version of v30, and shared in cat s22 telegram group. You can grab and install it directly. https://t.me/cats22flip/2002 (direct message link), https://t.me/cats22flip (channel link)

EDIT: If you are planning to install GSI there is no need to install additional apps in that link, as all that will be replaced by GSI anyway.

EDIT2: If you are going to install GSI, I can share v30 partitions other than system ( I don't have that one).
[Upgrading, Modifying and Unlocking] seawildflower:
Yes if you don't mind sharing any additional files that would be greatly appreciated. I will be installing GSI and hopefully continuing on to making lte work
[Upgrading, Modifying and Unlocking] debloateverything456:
Went ahead and ordered one, will get it in a week. Could be a great device for anyone like me who wants to cut the time that they waste on their phone while still running some messaging apps like Signal. De-googled ROM on it will also help with this.
[Upgrading, Modifying and Unlocking] seawildflower:
You should look at SimpleX as a replacement for signal. It is all around a better solution for secure messages,

I have successfully installed v30 light rom. hands down it is the best solution for stock. I will be leaving this phone as it is for now and wait to install Android 14 whenever I receive my second device.

Nuttydoc thank you for your help today! did you happen to attempt the volte solution I provided?
[Upgrading, Modifying and Unlocking] debloateverything456:
Looks great and has all of the features that Signal does. Main one I was looking for is calling, as a lot of other alternatives don't have that. As always, the problem is getting other people to use it.
[Upgrading, Modifying and Unlocking] rfresh:
My device is arrived, I would like to wait to see if I can flash any android 14 ROMs?
[Upgrading, Modifying and Unlocking] seawildflower:
As soon as I've attempted Android 14 on my second device I'll let you know immediately how it went. I think the main question that we're trying to figure out is if we can get volte working. I don't know why Pixel IMS won't solve this problem as they have recently found a workaround for the March 2024 update that had broken it.

I'm currently using pixel IMS to use volt on Android 11 and it works great. This device isn't currently rooted but there is a workaround using a root alternative. I have posted a Reddit link describing how to install pixel IMS on your device on the first or second page of this forum.
[Upgrading, Modifying and Unlocking] rfresh:
After adb reboot bootloader

I sent below command

C:\Users\vilu>fastboot flashing unlock

< waiting for any device >

Does that mean I am still not in fastboot mode? or I am missing any driver?
[Upgrading, Modifying and Unlocking] seawildflower:
And there's a lot of more information that's needed to figure out where your problem lies. Firstly, is the phone currently in the bootloader or is it in fastbootd

mode? Also I don't think that that command look looks correct to me to begin with. But I could be wrong I'm not in front of my computer and I'm not an Android developer per se. I also use Linux which seems to be more hassle-free then windows for this type of work. Nutty doc will likely jump in, but you can answer my above questions and maybe able to guide you through the process.
[Upgrading, Modifying and Unlocking] rfresh:
I got my phone today, and after bootup, I enabled developer mode -> enabled OEM unlock

Boot into fastboot mode by adb reboot bootloader

Which command should I use to unlock the bootloader? do I need to enter another fastboot mode?

Thanks

PS. I am on windows 10
[Upgrading, Modifying and Unlocking] rfresh:
USB debug mode is enabled, otherwise, adb reboot bootloader won't work
[Upgrading, Modifying and Unlocking] rfresh:
I have just managed to unlock my bootloader,

Apparently you need to take care of the android question mark driver from device manager and select - browse driver from pc -> Android adb bootloader.

Try :

fastboot devices

Now you can see your device serial number
[Upgrading, Modifying and Unlocking] rainland666:
anyone successfully boot into lineage os21 ? after flash .img, I got boot loop, and not able to boot into android OS

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] rfresh:
@nuttydoc, can help look at why I am getting boot loop afte

r install this lineage OS 21?
[Upgrading, Modifying and Unlocking] seawildflower:
Did you clear the cache and reset the device in recovery mode before first boot?
[Upgrading, Modifying and Unlocking] rfresh:
Before first boot? I don't remember, I am reverting back to v30 and do it over again with clear cache an reset to factory default,

I will provide another update.
[Upgrading, Modifying and Unlocking] seawildflower:
there are recovery steps available to reflash stock, its hard to tell what could have went wrong, common mistakes are running certain fastboot commands in the bootloader when they should have been fastbootd
[Upgrading, Modifying and Unlocking] rainland666:
I completed went back to stock v29, but when I do OTA to v30, I got failed update due to verification error, how should I relock bootloader ? is this the problem ?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] seawildflower:
Once you complete the flashing the rom while you are still in recovery mode you will see clear cache as well as reset to factory, you have to do that, but ill be able to provide better steps once I have attempted it myself. Besides its pointless to install lineage 21 until volte is known to work anyway
[Upgrading, Modifying and Unlocking] seawildflower:
You have to read the past few pages on this forum I had the exact same problem whenever I tried to flash version 30. Nutty doc provided a solution and a stock version 30 ROM that you'll have to flash manually, over the air updates aren't going to work for whatever reason. If you read the last few posts you'll find the solution to your problem and the files you need to fix it. Click on the telegram link that has a super light version of version 30. You will see nutty doc had posted the command steps to flash individual partitions from that telegram download. As long as you don't delete the bootloader you will have the ability to recover without issue.

The unlocked bootloader is not your problem
[Upgrading, Modifying and Unlocking] rfresh:
Really appreciate your kind help, let me give it a try now...
[Upgrading, Modifying and Unlocking] seawildflower:
But if you are patient ill have a complete walk through with all information, files and tutorials compiled for this device
[Upgrading, Modifying and Unlocking] rfresh:
I had tried the previous post to flash back to v30. it was successful.

But, when I try to boot into fastbootd, deletion of product partition was successful, but when I flash GSI rom, it complained about size again,

D:\Downloads\lineage-21.0-20240424-UNOFFICIAL-a64_bvS.img>fastboot flash system lineage-21.0-20240424-UNOFFICIAL-a64_bvS.img

Resizing 'system' FAILED (remote: 'Not enough space to resize partition')

fastboot: error: Command failed
[Upgrading, Modifying and Unlocking] seawildflower:
This is above my knowledge. I would "suggest" to delete scratch partition. But do not do that, wait for nuttydoc
[Upgrading, Modifying and Unlocking] nuttydoc:
With stock rom there should not be scratch partition. Stock rom have system/vendor and product. GSI rom has system/ vendor and scratch. To check current status use "fastboot getvar all"

I am attaching all v30 stock partition, (not lite). You can flash all this as per revert to stock thread.

First erase userdata and cache after that use bootloader to flash all except system/product/vendor, followed by fastbootd to flash system/product/vendor. At last clean cache/factory reset in recovery before reboot to system.

EDIT: you can replace system with GSI image, in that case erase product partition if that exists.

EDIT2: you may need to erase super partition, if you have flashed v30 lite rom, and you are getting size issue, but after that you will need to recreate vendor/system/product for stock/ vendor/system for GSI. I have not used v30 lite rom so not absolutely sure about this.

EDIT3: there is no harm in deleting scratch before flashing GSI as suggested in previous post, it is worth trying, it should be recreated automatically, this is what happens when we flash GSI first time.
[Upgrading, Modifying and Unlocking] seawildflower:
God bless nuttydoc
[Upgrading, Modifying and Unlocking] nuttydoc:
WARNING: Do NOT try to re-lock bootloader, after that you will not be able to flash anything, in other words recovery from brick shall become almost impossible.

Unlocked bootloader just gives warning at boot, no other effect.

EDIT: I have uploaded modified lineage 18 GSI in first post, with "su" binary removed. This will allow magisk install by flashing patched boot image.
[Upgrading, Modifying and Unlocking] rfresh:
I am going to try delete scratch partition first and how I am going to do that ?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] rfresh:
@nuttydoc, appreciate your help, but I think you are missing product.img file? can I use the one from v29 ?
[Upgrading, Modifying and Unlocking] nuttydoc:
Yes indeed. I am running GSI, therefore there is no product partition in my phone. Someone running v30 with root access can copy that. Product partition in v29 and v30 is different, however I think it may work, someone need to try.

If you are planning to install GSI product partition is not needed.
[Upgrading, Modifying and Unlocking] rfresh:
I booted up my OS to v30 with all your files and product.img from v29, after that, follow guide to flash GSI again and I am still getting below error:

D:\Downloads\CAT S22\lineage-21.0-20240424-UNOFFICIAL-a64_bvS.img>fastboot flash system lineage-21.0-20240424-UNOFFICIAL-a64_bvS.img

Resizing 'system' FAILED (remote: 'Not enough space to resize partition')

fastboot: error: Command failed
[Upgrading, Modifying and Unlocking] nuttydoc:
Have you deleted product partition to free-up space ?
[Upgrading, Modifying and Unlocking] rfresh:
Yes, I did
[Upgrading, Modifying and Unlocking] nuttydoc:
Delete all product/scratch/vendor/system. After this recreate vendor and flash v30 stock vendor, recreate system and flash GSI image. If you get error again post your partition layout "fastboot getvar all"
[Upgrading, Modifying and Unlocking] nuttydoc:
Your output is from bootloader, post one from fastbootd. There is no product/vendor is this output.

EDIT: you need to flash system from fastbootd not from bootloader.
[Upgrading, Modifying and Unlocking] rfresh:
I flashed GSI image from fastbootd

Here is the output from fastbootd:

(bootloader) treble-enabled:true

(bootloader) first-api-level:29

(bootloader) dynamic-partition:true

(bootloader) system-fingerprint:Cat/S22FLIP/S22FLIP:11/RKQ1.210416.002/LTE_S02113.11_N_S22Flip_0.030.03:user/release-keys

(bootloader) super-partition-name:super

(bootloader) hw-revision:0

(bootloader) off-mode-charge:0

(bootloader) battery-voltage:4302

(bootloader) is-userspace:yes

(bootloader) partition-type:recovery:raw

(bootloader) partition-type:userdata:raw

(bootloader) partition-type:mdtp:raw

(bootloader) partition-type:cache:raw

(bootloader) partition-type:misc:raw

(bootloader) partition-type:mmcblk0:raw

(bootloader) partition-type:boot:raw

(bootloader) partition-type:super:raw

(bootloader) partition-type:system:raw

(bootloader) partition-type:vendor:raw

(bootloader) secure:yes

(bootloader) battery-soc-ok:yes

(bootloader) serialno:S226001221032491

(bootloader) slot-count:0

(bootloader) cpu-abi:armeabi-v7a

(bootloader) variant:NA

(bootloader) has-slot:recovery:no

(bootloader) has-slot:userdata:no

(bootloader) has-slot:ssd:no

(bootloader) has-slot:mdtp:no

(bootloader) has-slot:cache:no

(bootloader) has-slot:misc:no

(bootloader) has-slot:mmcblk0:no

(bootloader) has-slot:boot:no

(bootloader) has-slot:super:no

(bootloader) has-slot:system:no

(bootloader) has-slot:vendor:no

(bootloader) product:S22FLIP

(bootloader) is-logical:recovery:no

(bootloader) is-logical:userdata:no

(bootloader) is-logical:mdtp:no

(bootloader) is-logical:cache:no

(bootloader) is-logical:misc:no

(bootloader) is-logical:mmcblk0:no

(bootloader) is-logical:boot:no

(bootloader) is-logical:super:no

(bootloader) is-logical:system:yes

(bootloader) is-logical:vendor:yes

(bootloader) vendor-fingerprint:Cat/S22FLIP/S22FLIP:11/RKQ1.210416.002/LTE_S02113.11_N_S22Flip_0.030.03:user/release-keys

(bootloader) version-vndk:30

(bootloader) unlocked:yes

(bootloader) current-slot:

(bootloader) version-os:11

(bootloader) version-baseband:

(bootloader) max-download-size:0x10000000

(bootloader) partition-size:recovery:0x4000000

(bootloader) partition-size:userdata:0x2D15FBE00

(bootloader) partition-size:mdtp:0x2000000

(bootloader) partition-size:misc:0x100000

(bootloader) partition-size:boot:0x4000000

(bootloader) partition-size:super:0xA0000000

(bootloader) partition-size:system:0x38565000

(bootloader) partition-size:vendor:0x13E8C000

(bootloader) security-patch-level:2022-06-05

(bootloader) version-bootloader:unknown

(bootloader) version:0.4

all:

Finished. Total time: 0.306s
[Upgrading, Modifying and Unlocking] nuttydoc:
I compared this with my device, only size of vendor and system are different. Size of vendor partition in your device appears larger. My suggestion is to delete vendor, system --> recreate both, first flash system with GSI followed by flashing vendor with stock vendor.
[Upgrading, Modifying and Unlocking] rfresh:
I deleted vendor and system, reflashed GSI system and vendor from stock, flashed successfully and now my phone still boot looping...

here is the GSI image that I flashed:

lineage-21.0-20240424-UNOFFICIAL-a64_bvS.img
[Upgrading, Modifying and Unlocking] nuttydoc:
reboot to fastbootd --> go to recovery --> factory reset and clear cache --> reboot
[Upgrading, Modifying and Unlocking] rfresh:
Yes, I did it, let me try it again
[Upgrading, Modifying and Unlocking] nuttydoc:
If this still doesn't work, I can only think of some of the downloaded image may be corrupt ( mostly GSI as you were able to boot v30 stock). Also I haven't used this LOS 21 image before, so you can try LOS 18. I won't be able to reply during next few hours, as it is late night in my tz.
[Upgrading, Modifying and Unlocking] rfresh:
I am able to boot into LOS 18 with your image file from the first post, very nice, have not insert my SIM card yet, but I still would like to try out LOS 21 if possible to use the latest android OS.

Thanks a lot.
[Upgrading, Modifying and Unlocking] seawildflower:
Curiously when I tried to flash lineage 21 I also received a boot loop. I'm curious to know why this would be the case. I don't remember what rendition of lineage 21 GSI I used though, what do you think nutty doc?
[Upgrading, Modifying and Unlocking] seawildflower:
Actually I wonder what would happen if you flashed lineage 21 after lineage 18 has been flashed. I don't know if that would make a difference or not. I also wonder if flashing to lineage 19 would be successful. As to me I believe that I will be able to get LTE working without issue but I don't see the point of trying to get it to work if the GSI itself is not receiving future updates. As without current updates or LTE the phone is essentially useless
[Upgrading, Modifying and Unlocking] rfresh:
these Los 21 ROM are TD-Based ROMs, and I don't know what is the difference between Los 21 TD -based vs non TD-Based ones, any other LOS21 GSI rom we could try out ?

Sent from SM-S918U1 using ReLabs
[Upgrading, Modifying and Unlocking] seawildflower:
I don't believe that's the issue but nutty doc could jump in, the TD means treble and any device that can run GSI is treble compatible. One of the core differences between older treble devices in newer travel devices is a only and a b GSI ROMs. Maybe this is the issue for this device. I still haven't received my second device, I'll be more able to answer these questions once I can experiment on the second device,. But currently I'm running version 30 super slim and is working great, but I really want to be able to receive regular security updates and I can't say how long this version of Android 11 will be useful as time goes on with app compatibility and whatnot. You seem Keen to experiment, maybe you can try to find a GSI ROM that is lineage 20 and can attempt to flash it for us and help us diagnose these issues. I don't know nutty doc personally so I don't know his availability or is commitment to this project so basically it's the four of us that's active on this forum to try to solve this problem for ourselves. That is kind of where we are at. But I promise that as soon as I receive my device I will do all my own suggestions in anyone else's to try to make this work. I truly love this device and it's really the only device of its kind on the market, not really on the market anymore, so let's all work together and try to make it work. It is quite a niche and if we can provide solid documentation towards the device I think that there will be a lot more people involved once we get past the security in lte's hurdle, I'm sure we'll have more experience developers than us to help us in this development once we've
[Upgrading, Modifying and Unlocking] seawildflower:
Done the legwork to make this relevant