yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Accessories] nickokio:
Hmm allrite too bad

Maybe someone else who can reply?

I decided to crash last weekend in Winterberg, test my helmet en break my old el cheapo phone holder. Now looking for a replacement.
[Touch Diamond, MDA Compact IV Accessories] nickokio:
Well wanted to tell yall that ive bought the small version and that is fits perfectly on my mtb and suits the diamond well (even with 2000mah battery)
[Touch Diamond, MDA Compact IV Accessories] alex jb:
great

hey thats great news. thnks 4 letting us know.

can you post a pic too?
[Touch Diamond, MDA Compact IV Accessories] nickokio:
Pictures Holder

Yeah offcourz, it looks great :)

Here are some pics, taken with iPhone 3GS
[Touch Diamond, MDA Compact IV Accessories] mc4ren:
Hi guys... how do you manage the Diamond to last the entire MTB run? I use the great GPSCycleComputer with map downloading (HSDPA) and I run out of battery in about 1,5 hours.

I was thinking in buying a high capacity battery (I've seen 2400 mAh) but they wouldn't fit in a standard holder because they are thicker. So, by now I'm wearing it in my back pocket.
[Touch Diamond, MDA Compact IV Accessories] phil-smith.tk:
I'm currently using a Herbert Richter mount... So I can move between car and bike with the same phone holder.

Plus I can keep the car and bike mount when I change my phone! :D

Very, very good German quality products!

Just as shame they don't do a waterproof holder... so I can only use my holder in good weather.

If they did one, I'd buy it straight away! :cool:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
To install TWRP, you need LZMA support kernel.

My custom kernel is here

https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Taobaibai:
Why is there a custom kernel needed?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Because stock kernel doesn't support LZMA ramdisk.

It's needed to install TWRP.

https://xdaforums.com/showpost.php?p=83255125&postcount=207
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DB126:
Better to boot vs install until build is proven. Yep, a bit annoying but keeps options open while allowing fluid OTA updates if that's your preference. In boot scenario custom kernel should not be needed.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Archangel:
This is big news and so awesome!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Nice!! Congrats on getting it built and posted! Thank you for the mention ;)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Theodor0504:
The kernel gived me a bootloop
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Witch FW version you use?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Archangel:
Has anyone used this to create a back up and then restore it properly without problems?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bursug:
https://xdaforums.com/pixel-4a/development/kernel-holydragon-kernel-t4155283

This kernel is good or no?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
My apologies if this has been asked/answered before, but could someone ELI5 on why it's so difficult to get custom recoveries running on Pixel devices?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] cmstlist:
The short answer is - recovery is no longer its own independent partition. Instead it's embedded into boot.img which also contains the kernel for the OS itself.

Recovery used to be its own partition because OS updates looked like this:

- OS downloads new OTA file

- OS boots into recovery

- Recovery installs the OTA

- Reboots back to OS

Now on "A/B" devices OS updates look like this:

- OS boots from "partition A".

- OS downloads new OTA file.

- OS installs OTA on "partition B" which it's not currently booting from.

- OS switches the active partition to B and reboots from that.

No recovery needed anymore. So it's no longer a partition of its own. Which is great for Google but harder for Android do-it-yourselfers.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
The only A/B phone I've ever worked on was my Dad's Mi A1, but that had TWRP running just fine.

I remember reading a few things about Project Treble back then, is that related to this?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
I used his kernel as a reference, and I added LZMA ramdisk support.

So, his kernel isn't fit TWRP install.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] 12paq:
Did you use LZMA compression because the partition where the ram disk is has very little room like the pixel 3A? The pixel 3A did not have enough room in the partition so TWRP was stripped down of features and compressed with LZMA to get it small enough to fit. I believe, but could be wrong, LZMA was used because it yielded the smallest image.

Does the Pixel 4A have the same space issues as the Pixel 3A?

I'm only asking because on the Pixel 3A TWRP never became functional enough to use much because of lack of partition space to reside even after uniquely compressed with LZMA. If the pixel 4A has more space maybe LZMA compression and a specific kernel that requires lcma might not be necessary?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] jhill110:
I've never had an a/b phone before and am thinking of getting this one.

A couple of questions :

What is sunfish

Does anyone regret getting this phone

Is it a pain in the azz to deal with a/b
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Sorry, I don't know it's needed LZMA compression.

I used pixel4 TWRP made by [MENTION=2638973]bigbiff[/MENTION] as a reference, and I used LZMA compression as he did.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] daemonspudguy:
Sure thing.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] daemonspudguy:
It works!!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nor-ric:
Could you please point me to that mod?

Thanks
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
Could you please point me to that mod?

There were a bunch of things I looked into, and I did get this working, but it was a while ago so my final notes are not in order. But I plan on returning to this again soon and work out exactly what I did and incorporate it in my daily driver.

But hopefully the below info will help figure out what I did.

From what I remember, I had to use Android Image Kitchen to decompile this TWRP image, then make some modifications to the recovery.fstab and twrp.flags file (in the \ramdisk\system\etc folder (attached), then recompile back into an image and install it.

NOTE: I made this mod to the original version of TWRP posted for A10 in the OP, so I don't know if this will work with any newer version posted in the OP.

For some reason I copied the below notes from one of the below links because I think they were relevant to this mod:

•Restoring works only with -> Settings -> Use rm -rf instead of formatting

Apr 9, 2021 see if that param in the flags file will do this for just this partition <----- My personal note

•Backup Internal Storage -> to Internal Storage

•does not show backup size / wrong size

(Settings - Disable free space check before backup)

Apr 9, 2021 I think this wont fix the wrong size, but will allow backup to destination it thinks is too small <---- My personal note

•Progress bar does not work (or does it just not go to 100% because backup size wrong?) <----- My personal note

•Internal Storage not proper unmounted when unmounting data

*** Apr 9, 2021 is this something I need to be concerned about <---- My personal note

•TWRP shows errors in log (E:Unhandled flag 'bind')

•TWRP shows errors in log when successfully mounted (Failed to mount '/sdcard0')

•does not work with busybox v1.22 bionic (TWRP default)

•does not work with toybox

Here are some links that might be related to this mod that I jotted down as I was researching this issue:

https://xdaforums.com/t/app-10095-t...ll-backup-internal-storage-bull-v1-6.3831217/

https://xdaforums.com/t/recovery-twrp-fix-o-backup-internal-storage-o-backup-option.3941108/

android_device_xiaomi_beryllium/recovery.fstab at android-9.0 · TeamWin/android_device_xiaomi_beryllium

For building TWRP for Pocophone F1 ONLY. Contribute to TeamWin/android_device_xiaomi_beryllium development by creating an account on GitHub.

github.com

https://xdaforums.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/

GitHub - kdrag0n/tipatch: A patcher for TWRP to backup internal storage/emulated SD card contents (photos, downloads, videos, etc).

A patcher for TWRP to backup internal storage/emulated SD card contents (photos, downloads, videos, etc). - kdrag0n/tipatch

github.com
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
It's nice(y)

Thank you testing it.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
There is also a "rename folder" trick you can do to include the internal memory into a TWRP backup:

https://xdaforums.com/t/tutorial-create-internal-storage-backup-in-twrp.3389172/
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Zaxx32:
TWRP for A11!?! :cry:

Now I'll NEVER get around to trying A12! Would muuch rather be able to play with ROMs & Tweaks!!

Mikamura, you sir are a gentleman and a scholar. (...and there not many more of us left!!) :giggle:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] alecxs:
Basically all it needs is one single entry in fstab. It is a bind mount of /sdcard into any other mount point (like /storage) that makes TWRP think it is regular partition (which is not, it is /data/media/0 part of userdata partition)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] amphi66:
So lots of options throughout this thread .. .. is there a step-by-step summary for those of us new to Sunfish?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] alecxs:
This is for @nikamura to look at
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zman519:
Test5 fails to backup on los18.1 "CreateTarFork() process ended with ERROR: 255"
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Sorry for taking so long on getting around to upload a requested log.

I had a boot failure on stock July ROM (with Magisk and some associated mods). It caught me off guard (is there any other way....), so I gave the TWRP a go. I used the "live boot"method ie (after renaming the image file)

fastboot boot twrp.img

I did not flash it permanently, and the error of the user above makes me feel confident that that is not why it failed.

It failed to backup, with error 255. I *think* they were possibly before I un-encrypted, but could of been either way for either one or both or none.

What I was able to do was, un-encrypt, connect via ADB, and then pull all my data onto my windows PC. Which would of been a god-send last time, as the failure to boot meant I lost a few photos.

I hope the logs help.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
nikamura Oh... two more things.

1. I was backing up to a usb flash drive

2. Because I flashed it via adb over a USB cable, when it rebooted, I had to quickly plug in the flash drive for it to be recognized. I am pretty sure on previous devices with TWRP, I could plug the flash drive after it had booted.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
As I previously mentioned in this thread, if you have parallel apps installed or logged into multiple gmail accounts on your device, a error 255 will occur.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zman519:
Thank you for pointing that out, I do remember reading that.

I was/am logged into two gmails with Fairmail. I'll log out of one of them and try the backup again.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
I only have a single account in my phone, and I checked the above folders to be sure, and the 999 folder was not present. I still got a 255 error.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
There was a bug in the A10 version of this in which when you boot into TWRP recovery, it did not read the date/time correctly from the device.

So, when you tried to do a backup with "auto name" enabled, the date/time it used was in 1970. So, it made it hard to know which backups were done when because it always defaulted to 1970.

Can someone check to see if this date/time bug still exists in the newer 3.5.x builds of this TWRP?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] zman519:
Removed one of the gmail accounts and still got the same 255 error.

I checked all the folders and do not have any 999 folders.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
I am on Stock A10 and using the (OP) posted "sunfish_twrp201017-test5.img" for it.

However, the version of TWRP in that image is 3.4.0.0

Any chance a newer TWRP 3.5.2.11 version can be created for A10?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I'm on LOS18.1 08-12-2021 & Lineage recovery 08-12-2021. I've no custom kernel. I've no GApps. Magisk was not installed during this test.

I used "fastboot boot test5.img" and booted successfully to TWRP.

However, I also got the 255 error.

I don't have the 999 folders. I attached a screenshot showing the "multiple users" setting is off.

I've attached the recovery.log, in case it helps @nikamura in any way.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheSayaMan:
It's possible but unlikely that some parallel apps could go in folders other than 999. There are no parallel apps installed on your device? Parallel apps would also be referred to as clone apps which are apps that clone another. Basically you could clone any app with a cloner and log into two different accounts. This would cause problems. If this is not the case than it would need to be addressed with the dev for a fix.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
Pardon my neophyte's ignorance.

I did not clone any apps, as I wouldn't know how to do it. If it's of any use,

the only account I have in "Settings->Accounts" is for Signal Messenger.

I also noticed that my recovery.log attachment is gone. I hope I didn't break a rule by attaching that. :) I thought it would be useful for nikamura.

Thanks for all the time you've taken trying to help us in this thread.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
I built and test TWRP for stock ROM A10 and A11 version.

I didn't test it on custom ROMs.

I would like to test it on latest version, but my pixel4a dosen't have enough storage changing firmware from stock ROM to custom ROM.

Can anyone test TWRP test6 build?

https://drive.google.com/file/d/1mB73pX_0UQQA4PNPvqBBWqSZ6TixZfho/view?usp=sharing
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Slim2none4u:
Booted. Installed. Took a backup. Did not try to restore. Seems to work fine though.

Kernel - Blu_spark r117

Magisk v23

LSPosed v153
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
This might sound like a newbie question, but are these new builds of TWRP OS independent?

Meaning can I use the above test6 build on my A10 Pixel 4a?

Or do I have to wait until a build is made specifically for Pixel 4a Sunfish FM QD4A.200805.003?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
1. TWRP is not an OS.

2. If you look at post #1 of this topic, you'll see:

"Android11 FW

test6"

This is to let us know that test 6 is for Android11.

3. In that same, first post, you'll see a link to:

"Andriod10 FW https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing

It's tested both FW version QD4A.200805.001 and QD4A.200805.003."

This is from last year, though. You'll have to read the early posts in this topic to find out if it was working well.

Hope this helps.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
Thanks for the info. That is what I thought, but when nikamura said in a recent post "I built and test TWRP for stock ROM A10 and A11 version." it seemed to suggest that he might have "recently" rebuilt the A10 version (because his post was from the other day).

But when I checked, the A10 file in the OP didn't look like it was updated, so that made me think maybe the latest build he did recently post might work on A10 (if TWRP was not OS dependent), hence my question for clarification.

So, the end result is that I will need to wait for an A10 version to be built using the newer 3.5.2-11 version of TWRP.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I'm on LineageOS 18 09.16.2021. I have LOS recovery 09.16.2021. There's no GApps, Magisk, or custom kernel.

I used "fastboot boot twrp6.img" to start TWRP.

It booted fine. The backup started this time. There was no error 255. :)

However, the backup failed. It created 5 files. "data.f2fs.win000, data.f2fs.win001, data.f2fs.win002, data.f2fs.win003, data.f2fs.win004" are their filenames.

I don't know if it's OK to post from the recovery.log file. These lines are at the bottom:

I:createTarFork() process ended with RC=0

* Generating digest...

I:SHA2 Digest: 559c094062948f2be7dc9090f7a8ad45b4cc8c8a3c67437cfbdc2dcc76a92f47 data.f2fs.win000

I:digest_filename: /data/media/0/TWRP/BACKUPS/0C251JEC201764/1970-09-30--06-59-08_lineage_sunfish-userdebug_11_RQ3A210905001/data.f2fs.win000.sha2

* Digest Error!

Backup Failed. Cleaning Backup Folder.

As you can see, the createTarFork() didn't return an error with test6. However, I don't get any details for the generic "Digest Error!"

Thanks for your continued time on this. I imagine custom ROMs are a nuisance.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
I’m sorry if I caused a misunderstanding.

I'm building TWRP for A11 version now.

I'll build TWRP for A10 new version, if I have time.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Thank you for testing.

Do you check Backup Option "Skip Digest～"?

Could you upload the recovery.log?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
I attached the previous "recovery.log" to my prior message.

I booted with "fastboot boot twrp.img"

The setting: Settings->"Skip Digest generation during backup" was not checked. I checked it.

I started a backup and it completed successfully.

Unfortunately, this phone has become my daily-driver. I didn't dare test a restore. :)

I attached the recovery.log file from this, successful backup.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Sorry, I missed previous "recovery.log"

Thank you for testing.

I don't know why "Digest Error" has occurred.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mangokm40:
No!!! Please don't apologize to us. We appreciate your work on this. Thank you very much.

To be clear, you missed nothing. My English was poor. I meant, I attached the recovery.log with the error to the message about the error AFTER you asked me to do it. I thought it would make it easier to distinguish from the new recover.log file. I'm sorry I created a confusion about the timing.

You did nothing wrong.

If I get a few hours, I will test a restore. It's just that I need to have everything ready, in case I have to reinstall from scratch. :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] psc-m3:
Well, I did a Backup running "lineage-18.1-20210930-nightly-sunfish" and tried to update to "lineage-18.1-20211007-nightly-sunfish" this didn't worked so I tried to restore my TWRP Backup.

The Restore completes, but the Phone hangs in a bootloop. The lineageOS animation shows up shortly and the it reboots. After some time the (I think) LOS-Recovery shows up and says something like "Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset" - which indeed works. At least I get a naked lineageOS without any data.

Unfortunately I can not get any log messages while it hangs in the boot loop. adb logcat does not connect at that stage and "/proc/last_kmsg" or so is not available on my phone. Only restoring "data" results in the same bootloop. In my experience with TWRP nothing like that happened to me.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] EngineerMind:
When you boot into TWRP, does anyone else notice that the time at the top center is wrong - and when you enable the backupname to include the date/time - it has an invalid date of 1970?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] psc-m3:
true, but this is not limited to TWRP it seems to me. If you do a "date" via adb shell in the LOS-Recovery it also shows 1970. TWRP seems to have a fix for that:

But it seems this value is not used.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Zaxx32:
If it's fixed issue without requiring a custom kernal, I'll rollback to Android 11, no problem!!

TWRP 3.6 arrives with Android 11 support and faster install process​

BY RAJESH PANDEYPUBLISHED 2 DAYS AGO

12

It's also easier to use with A/B partitions!

If anyone has tried, it (Ahem, OP...), how did it go? What'd you think of it?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] momojuro:
Hello @nikamura,

Feel free to checkout Pixel 4 TWRP's Github repository. I am sure it is gonna be helpful as the devices have some stuff in common.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
I rebuilt TWRP 3.6 version based on Pixel4.

But, I don't test it enough.

fastboot boot OK

install recovery ramdisk OK

flash zip OK

backup/restore it's not tested yet

My PC is broken, I can't test backup/restore.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Theodor0504:
Installed succesfully on my pixel 4a. I am running HDK and lineageos. Backup works. Date and time does not works. Everytime I try to install something I get the same error... Can't Mount system_root (device or resource busy)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Theodor0504:
September FW
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Chaprnks:
could you send me a download link, I'd be more than happy to help you test it :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] nikamura:
Download link

https://drive.google.com/file/d/16aTC8w0YUYBS_lqcA3KL0kz5mq7NsxxG/view?usp=sharing

Please test it.

You are a lifesaver.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] old.splatterhand:
I have tested the 3.6_10 build on my 2nd P4a with broken screen and it seems to work fine so far:

Installation worked

Flashing img files worked (tested with boot.img)

Installing TWRP.img to ramdisk worked

Flashing zip files worked (tested with magisk.zip)

Backup worked

Restoring backup worked

Notes:

Time/Date does not work. Could not set timezone correctly, date of the backup folder started with the year 1971

Backup is huge, more than 28 GB on my phone!

After restoring backup and the boot to system, it booted back to TWRP one time (while it was already in Android OS) after the second boot, it stayed in Android OS.

No option to wipe system in "Advanced Wipe" menu

For the short time i used this Twrp build it seems almost everything except Date/Time works!

Thanks a lot for this @nikamura
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] DiamondJohn:
Regarding the backup size.From previous devices, I can navigate/browse the TWRP backup using 7Zip. And thus, check what the heck is making up all the size?

Regarding the "No option to wipe system". purely conjecture, but wiping system as far as i see, has no point, as when a system image is flashed, it would replace and thus wipe the system. So I can see why TWRP would remove the feature. Especially since wiping the system without flashing a new one would only serve to soft brick a device.

Many years ago ROM ZIp's contained individual system files, but that is no longer the case. Its all or nothing these days.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] old.splatterhand:
I have not used Twrp quite a long time, so i was only surprised that the wipe option is missing.

For the time/date problem, i found the solution, and it is not a Twrp fault. But it's too late here, time for bed now.

Tomorrow we will go back to this.