yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] 7ig3rsh4rk:
I don't use Carbon but on LineageOS 17.1 (Android 10) I could flash Magisk 20.4 without problems. An update of the manager app to v23 was possible but not magisk itself.

With LineageOS 18 (Android 11) it seems it is necessary to make some modifications before flashing Magisk:

https://xdaforums.com/t/official-lineageos-18-1-for-xperia-z3-compact.4308517/post-85400443
[Xperia Z3 Compact Original Android Development] hrsh45:
thanks very much :)

it works
[Xperia Z3 Compact Original Android Development] hrsh45:
is there any way to use Volume Up as Volume Up ONLY,

Volume Down as Volume Down ONLY?

i just want to change the volume, but instead it skips/ restarts the track, its so annoying.

i think its Android 10's problem but not this rom's, if i remember correctly Lineage was like that too.

i tried to search for solution but couldn't find much.

i'll ask here in case there's solution only applied to Carbon
[Xperia Z3 Compact Original Android Development] Myself5:
Settings -> Carbonfibers -> Gestures -> Skip music track.

Disable the feature you enabled there.

If its not enabled, theres a third party service doing that to you (the musicplayer being a main suspect here, afaik poweramp has that feature).

Either way its always disabled by default so it's gotta be something you activated :P
[Xperia Z3 Compact Original Android Development] hrsh45:
thanks very much for your reply :) however i couldn't find such option under Gestures nor other subsettings :/

i only use the default app Vanilla Music, and seems their Settings doesn't have such option :/

(i'm on Carbon 8.0 20210727)

its quite newly flashed & doesn't have much 3rd party software [besides microG, brave (browser) & adaway]

i'll flash it on another z3c later this week & see if the problem still persist.
[Xperia Z3 Compact Original Android Development] Myself5:
CR8 has the option in CF -> Buttons, my bad. Thought you were already running CR9.
[Xperia Z3 Compact Original Android Development] hrsh45:
thanks, although i couldn't find it in Buttons in CR8.

don't worry, i'll flash CR9 later instead.

and thanks very much for bringing CR9 to Z3C :D
[Xperia Z3 Compact Original Android Development] Myself5:
"Screen off playback control" right in that screenshot ;) If it's off though then my best bet is still on some third party app to cause it.
[Xperia Z3 Compact Original Android Development] hrsh45:
thanks sooo much :)
[Xperia Z3 Compact Original Android Development] Preacher_at:
Does anybody use CR9.0 on Z3C?

I upgraded, had infinite bootloop first, but could fix that by flashing Android 11 GAPPs in TWRP.

But since then, camera stopped working. Already did full wipe and start over, but except loosing old CR camera app, didn't change something.

Open Camera just lock up with black screen, most camera apps report camera used by other app.

Anyone similar issues? Better try Lineage 18.1?
[Xperia Z3 Compact Original Android Development] PriToX:
Anyone knows what root solution works for this rom? I have tried magisk and supersu and nothing seems to actually work ;/
[Xperia Z3 Compact Original Android Development] hrsh45:
im still on CR8, not sure abt CR9.

older version of Magisk works for me.

see post #107
[Xperia Z3 Compact Original Android Development] PriToX:
I belive i tried this, and it failed. However i did try the "sony modded" magisk i found in either of the threads, dont remeber which and that one worked. It was also possible to update both magisk and the app using the magisk app.
[Xperia Z3 Compact Original Android Development] Finsnevis:
Install latest canary apk.Patch the boot image with magisk and flash the patched boot image with twrp.Works with latest carbon weekly and lineage weekly.Flashing magisk 23 never installed for me.
[Xperia Z3 Compact Original Android Development] Finsnevis:
@Myself5 Thanks for latest 130122 release all good and root with patching boot.img,😇
[Xperia Z3 Compact Original Android Development] Finsnevis:
Thankyou for latest A11 with January 2022 security patch
[Xperia Z3 Compact Original Android Development] kla960:
Hi, is version 9.0 usable or does it have any bugs?
[Xperia Z3 Compact Original Android Development] Finsnevis:
No bugs for me latest 0902 release.Nice rom everything perfect as far as I could see.Am currently using the z3 crDroid A11 on this but keep twrp backup of carbon 9.0 to easily restore.
[Xperia Z3 Compact Original Android Development] Finsnevis:
Am using latest build 2402 with february security patch and perfect no bugs
[Xperia Z3 Compact Original Android Development] Dabronik:
Hi, does anyone know why SMS notifications are delayed?
[Xperia Z3 Compact Original Android Development] greg46:
Hi, is the latest 9.0 build usable for a daily driver? Or should we stick to latest 8.0 release
[Xperia Z3 Compact Original Android Development] Myself5:
Latest CR9 build is Daily driver ready :)
[Xperia Z3 Compact Original Android Development] greg46:
Thank you. Also is this compatible with microG?
[Xperia Z3 Compact Original Android Development] Myself5:
It is, indeed.
[Xperia Z3 Compact Original Android Development] arthurbolotov:
Hello. Do you know how to solve this problem? If you do, please tell me how to fix this error. I have been struggling with this for weeks and nothing works. I have tried many things, but all the time there is an error with this permission
[Xperia Z3 Compact Original Android Development] arthurbolotov:
So you just gave up the gapps? I always gave them up, too. Well, nowadays it's very difficult without them, many applications do not work. And microg often does not work with the right applications. I have exactly the same problem with them, well, I have many times installed without problems gapps well the last time I removed them I forgot to log out of the account. And now I installed the gapps again and they don't work now, maybe the problem is in the account that was saved in db? (database sqlite)
[Windows Mobile Development and Hacking General] irfan2288:
I had downloaded this photo from some forum but can't remember from where. As you can see, its a good theme with some nice colour contrast. Maybe its the screen capture program that gives this picture a nice resolution and it may look differently on the device. But still I would like to try it out.

Not sure whether this is the right place to ask for. Moderators, please move it to the appropriate location if needed. Any help would be highly obliged.
[Android Q&A, Help & Troubleshooting] daniel-ayers:
During what circumstances can a mediatek phone get bricked while flashing?
[Nexus 5 Original Android Development] z3DD3r:
TWRP HH for Nexus 5​

About:

Disclaimer:

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

You can find the source code for TWRP on GitHub. If you would like to contribute to TWRP, please visit Gerrit Code Review.

Features:

HH.S version with stock partitions map. S means stock.

HH.R version with repartition support. R means repartition.

Working decryption on custom roms

. Tested on LOS 16.0, LOS 17.1, LOS 18.1, but should work on all Androids since Nougat.

exFAT and NTFS support (read and write) for USB OTG

Requirements:

You need to have an

unlocked bootloader

to install and use TWRP!

Known bugs:

Everything looks good so far

Downloads:

https://sourceforge.net/projects/hammerhead-twrp/files/beta/

Credits:

TeamWin

@Clamor

@steadfasterX

And all the contributors out there in the community

Contributors:

@z3DD3r

Source Code:

Device tree: https://github.com/z3DD3r/twrp_android_device_lge_hammerhead

Version Information:

Satus: Stable

TWRP version: 3.7.0_9

HH Project versions: HH.S.17 and HH.R.17

Created: 2020-02-08

Last Updated: 2022-02-06
[Nexus 5 Original Android Development] z3DD3r:
Repartition (HH.R versions)

ALWAYS DO THE BACKUPS!!!

No one is responsible for your actions!

Repartition may potentially brick your device, although risk is reduced to minimum.​

Features:

Increases /system partition to ~1444Mb

Decreases /cache partition to ~255Mb

Doesn't provide /vendor partition

Doesn't touch /data partition

Requirements:

Not modified partitions by any other solutions

How to increase /system partition and change partitions map:

- Flash the HH.R version of TWRP and launch it

- Open terminal (TWRP -> Advanced -> Terminal)

- Type hh_repart -m

- Wait until your phone reboots

- Install your rom

How to revert back to stock /system size and stock partitions map:

- Launch HH.R version of TWRP

- Open terminal (TWRP -> Advanced -> Terminal)

- Type hh_repart -r

- Wait until your phone reboots

- Flash official TWRP or HH.S version of TWRP! Don't ignore this step!

- Install your rom

How to dump partitions map:

- Launch HH.R version of TWRP

- Open terminal (TWRP -> Advanced -> Terminal)

- Type hh_repart -d

- Wait until process finishes

- Look at /sdcard/partitions.log file
[Nexus 5 Original Android Development] z3DD3r:
Some technical notes about the decryption and Android Q support.

Right now the only possible way to decrypt data on our devices is to use system's vold. This logic was added to TWRP some time ago but one required change wasn't in the tree. This change is here: https://gerrit.twrp.me/c/android_bootable_recovery/+/1919. Without this patch system's vold will fail on hammerhead. I don't know why but services in the sbin can't handle decryption. Also using the system's vold means that ROM should be installed to decrypt data. Without installed ROM decryption is not possible!

About SAR and Android Q. Work on SAR support in TWRP is still in progress but some patches are already available on gerrit. These patches are required to properly detect SAR and mount partitions. Also since Android Q one more service should be run before trying to decrypt data. This service is apexd. Android Q runs apexd on early-init stage to provide required runtime libraries. U can see how it launched at https://android.googlesource.com/pl...fs/tags/android-10.0.0_r29/rootdir/init.rc#37. Only after that step all other services like qseecomd, hwservicemanager, servicemanager and keymaster can be run from system or vendor.

The last point is prebuilt vdc. Prebuilt vdc_pie which is shipped with TWRP fails to run because of linker error. I don't remember exactly what was the error but i guess that something is removed in libc. To fix that problem i've built vcd_ten binary with Android Q sources and placed it into device tree for hammerhead as a temporary solution. The source code of that binary is identical to vdc_pie which located at https://github.com/TeamWin/android_...b/android-9.0/crypto/vold_decrypt/vdc_pie.cpp

This is just a quick notes about what was done.

Patched bootable_recovery is located at https://github.com/z3DD3r/twrp_android_bootable_recovery/tree/android-9.0

Device tree for Q located at https://github.com/z3DD3r/twrp_android_device_lge_hammerhead/tree/q-sar

I hope this will be helpful for TWRP Team!

PS: Changes i've made should be improved. Don't treat them as production ready and/or stable!

FYI [MENTION=912474]Dees_Troy[/MENTION]
[Nexus 5 Original Android Development] VnnAmed:
Hi, thank you very much for this solution.

hh_repart -d - worked but I couldn't read the log file before rebooting, maybe it's obvious

hh_repart -m - worked without any issues

I have also successfully flashed Lineage 17.1 from your other thread, gapps and Magisk.
[Nexus 5 Original Android Development] z3DD3r:
New versions are up (HH.S.3 and HH.R.3)

Added exFAT and NTFS support (read and write) for USB OTG

Kernel image is compressed with XZ LZMA2 compression algorithm (smaller size of the recovery image)
[Nexus 5 Original Android Development] z3DD3r:
New versions are up (HH.S.4 and HH.R.4)

Fixed mounting issues of the system partition

Fixed device overheating while in recovery

I highly suggest everyone update to this version!
[Nexus 5 Original Android Development] dahawthorne:
I have a question, certainly not in any way a complaint.

I have been running HH4 for a few days. Last night I made a TWRP backup of my LineageOS 17.1, which I installed on 20th without Gapps to see how it works without Google - quite well, in fact, with the help of APK Updater.

This morning I stupidly applied the 22nd update with Gapps - I was on autopilot and forgot that this device had no Google.

No problem, I thought, I'll just restore last night's backup. So I did a total wipe and format ("yes"), but no backup will restore. I just get the LOS line-&-circle animation for ages. I've tried earlier backups, and even standard unmodified TWRP, all with the same result. No backup will restore.

It's not a big deal - I can start with a totally new installation - but I'd like to know if anyone has taken a backup and successfully restored it. Or am I just lucky...? :) If I can't restore, then it sort of defeats the point of TWRP, no?

Edit: Seriously, 85 people have downloaded HH4. Has not a single one of you tried a restore of a backup?

Edit: Tumbleweed... :)

Edit: Do I take it that nobody has tried to restore a backup? If you haven't, and my experience is normal, then we're risking a two-hour fresh install in case of update problems rather than a two-minute restore.
[Nexus 5 Original Android Development] z3DD3r:
Have u tried to restore backup of other ROMS? I guess it is not TWRP's problem...
[Nexus 5 Original Android Development] sant514:
With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 14.1 with encyption = ok

With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 17.1 with encyption = ok
[Nexus 5 Original Android Development] z3DD3r:
Can u tell me which build of LOS 17.1 have u used for these tests?
[Nexus 5 Original Android Development] sant514:
Los 17.1 28-02-2020
[Nexus 5 Original Android Development] z3DD3r:
Thanks! U just confirmed that LOS 17.1 could not be restored due to selinux denials. Some days ago i've updated sepolicies and now everything works.

[MENTION=6161558]dahawthorne[/MENTION], FYI
[Nexus 5 Original Android Development] dahawthorne:
Excellent news - thank you.

And also a relief to find that I wasn't just being an idiot... :)
[Nexus 5 Original Android Development] smsmasters:
I see "E:Unable to decrypt FBE device" when flashing in TWRP.

Should I just disregard this message?
[Nexus 5 Original Android Development] z3DD3r:
Just ignore it.

Our device doesn't support FBE (file based encryption). So this error doesn't affect our device at all.
[Nexus 5 Original Android Development] dahawthorne:
Since I was the one to mention my problem with restoring a TWRP image, I think I should report that, as z3DD3r stated above, TWRP HH 4 does indeed work fine in making and restoring backups. I took a backup yesterday and restored it this morning; no wipe, just a straight recovery, and it all went through in less than two minutes.

Thanks for all your work, z3DD3r. It's great to have bleeding-edge software on such an old device.
[Nexus 5 Original Android Development] TomiLynch:
Hello [MENTION=7268092]z3DD3r[/MENTION] , I've been working on a ship for the last couple of months, so missed some things.

I'm using the first original twrp-3.3.1-HH-hammerhead version you shared in the telegram group, but now I found this thread with newer versions.

Just wanted to double check if it's okay to update straight from that original HH version (ALREADY REPARTED) to the lates HH.R.4 without any problems.

And just out of curiosity, cause I'm not planning on reverting to stock partitions. Why is it so important to flash official or HH.S version after reverting?

What is the difference between stock and HH.S.4 then?

Thanks for putting your time and efforts in to keeping this device alive!
[Nexus 5 Original Android Development] z3DD3r:
twrp-3.3.1-HH-hammerhead and TWRP HH.R uses the same script for repartition. So, yes, it is okay to flash HH.R over the twrp-3.3.1-HH-hammerhead.

Because TWRP includes size of system partition. This size should match the size of system partition on device. Otherwise bad things can happen...
[Nexus 5 Original Android Development] blairfancy:
Hi [MENTION=7268092]z3DD3r[/MENTION]

Did you build a 2GO version of TWRP?
[Nexus 5 Original Android Development] z3DD3r:
Some time ago. But i've removed it and don't support it anymore...
[Nexus 5 Original Android Development] arunaksh:
error message

it gives me an error saying hh_repart -m not found..any way i can fix this
[Nexus 5 Original Android Development] bharatshaan:
Hi Guys,

I'm new to this. So do I need install R=Recovery to increase partition size install LOS17.1 and GApps and then revert back to stock size and install S-Recovery?

Or can I install R-Recovery, increase partition and install LOS and GApps and use my phone?
[Nexus 5 Original Android Development] z3DD3r:
Install .R, increase partition, install LOS + GApps and use your phone. No need to revert back to stock...
[Nexus 5 Original Android Development] bharatshaan:
Thank you. :)
[Nexus 5 Original Android Development] Elder007:
Hi guys, I need help! I installed android 9, and I'm experiencing slow issues. So I would like to go back to rom stock 6.0.1, I follow these steps below.

1. Flash twrp-3.3.1-HH-hammerhead.img

2. Open terminal (TWRP -> Advanced -> Terminal)

3. Type hh_repar -m

4. Wait until your phone reboots.

How to revert everything:

1. Open terminal (TWRP -> Advanced -> Terminal)

2. Type hh_repart -r

3. Wait until your phone reboots.

4. Install original TWRP (3.3.1-0 at the current moment)

My question is: After reverting the partition using the commands in the "hh_repart -r" terminal and after installing the official twrp. Can I install rom stock 6.0.1 using recovery or the Toolkit? please resolve this doubt. ?
[Nexus 5 Original Android Development] TomiLynch:
Try avoiding toolkits. Doing things manually is always safer (and makes you learn a thing or two).

If you want to go back to stock you could flash the factory image with fastboot. There is a guide on going back to stock here in xda (https://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)

If you want twrp you can flash it again after that also through fastboot.
[Nexus 5 Original Android Development] Elder007:
Hi friend, I saw your message now. I used the toolkit and it worked. Thank you!
[Nexus 5 Original Android Development] Elder007:
Good afternoon guys. Does anyone know why these errors? I can't install anything.

I'm using

Rom LOS 17.1

TWRP 3.3.1-HHR4

https://ibb.co/w7Zkd8f
[Nexus 5 Original Android Development] z3DD3r:
Check that "Zip signature verification" option is disabled in TWRP's settings.
[Nexus 5 Original Android Development] Elder007:
Thank you so much! now it's working. :D
[Nexus 5 Original Android Development] Robexuk:
Works very well probably the easiest way to repartition your hh.
[Nexus 5 Original Android Development] z3DD3r:
New versions are up (HH.S.5 and HH.R.5)

Merged latest changes from TWRP team

Updated prebuilt kernel with sdFAT driver for FAT filesystems
[Nexus 5 Original Android Development] z3DD3r:
It included. Check that u using right version of TWRP (HH.R version). If u trying to build it yourself then use android-9.0-repart or q-sar-repart branches.

Thanks! These new changes were included after .5 version was released. I know what is wrong in commit you've pointed. I'll fix it in my fork of TWRP.

[MENTION=5363856]DroidFreak32[/MENTION],

Temporary fix is here: https://github.com/z3DD3r/twrp_andr...mmit/a2fe98c039c8485b6275b3ecd5d470fb09a91e5c
[Nexus 5 Original Android Development] z3DD3r:
New versions are up (HH.S.6 and HH.R.6)

Merged latest changes from TWRP team

Dropped prebuilt kernel of favor of building kernel from source code

PS: I've stopped hammerhead support. So this is the last version of TWRP HH from my side...
[Nexus 5 Original Android Development] akshakhil:
repartition

THANK U VERY FOR KEEPING NEXUS 5 ALIVE

Hi I am a nexus 5 user. i have installed lineage OS 17.1 with BitGApps(ARM) from it official site. twrp repart thread worked, but couldn't install ROM with same version of twrp so i revet back to twrp 3.4.0.0 and installed LOS 17.1 with BitGApps. i have tried AOSiP, crDROIDV6.8 AND crDROIDV6.9 to installed but none of them worked. anyhow thank you for the repartitoin thread. it really worked.
[Nexus 5 Original Android Development] FirePower36v:
Hello, I've repartitioned my nexus 5 with Clamor TWRP various months ago, now if I want to change from the Clamor one to this one, can I do that without making a disaster with the partitions?

Thanks!
[Nexus 5 Original Android Development] lona79:
Hi,

I tried to install twrp-3.4.0-HH.R.7 version, but when twrp reboot, is lock in first page.

Then, I tried to install twrp-3.4.0-0-hammerhead, and it work, but in Wipe/Advanced if I select "System" and "Repair or Change File System" all data is 0 MB.

Someone can help me?
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Hello,

What do you mean with "lock on the first page"? Is TWRP frozen? You can't access the terminal?
[Nexus 5 Original Android Development] lona79:
Exact.

It frozen on first page.

I can't access on twrp menu.
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Ah now I get it.

What happens when you boot up the TWRP image that does work and wipe all of your partitions?

(assuming you took a backup and don't have any important files stored on your device)

Is your internal storage accessible after doing so?
[Nexus 5 Original Android Development] lona79:
I don't tried.

Must I wipe also "Data" and "Inetrnal Storage" partitions?

There aren't important files, I use this phone like a gps device for MTB or Hiking.
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Yes, those two partitions too.
[Nexus 5 Original Android Development] lona79:
This is the result:
[Nexus 5 Original Android Development] Mr.FREE_Bird:
Alright, my tips didn't work.

I would advice you to completely restore the Stock ROM of your Nexus 5 with Google's factory images. This will make sure you can start over with a fresh and working system and it's partitions.

Here's a link for the latest factory image from Google for the Nexus 5: https://dl.google.com/dl/android/aosp/hammerhead-m4b30z-factory-625c027b.zip

And this is a link to a guide that explains how to restore your Nexus 5 with Google's factory images: https://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

After restoring your device you can attempt to repartition your device again by following the instructions provided in this thread.

Good luck ??
[Nexus 5 Original Android Development] lona79:
I tried to flash the factory image with "Tool All In One" but:

View attachment 5134803
[Nexus 5 Original Android Development] lona79:
I tried also with the guide that you have linked, but:

View attachment 5134817

Is there a method to create a partition table?
[Nexus 5 Original Android Development] Mr.FREE_Bird:
I would never advice to use such all in one tools, they are outdated and can cause issues.

I specifically linked the Google's factory image and a guide that explains how to restore your device because I know that it should work.

Just trying out things will cause issues.

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

You could try to follow the instructions of this thread that explain how you can revert to the stock partitions but I'm not sure if that will work.
[Nexus 5 Original Android Development] lona79:
My problem is that when I install HH.R version of TWRP, this lock of boot screen:
[Nexus 5 Original Android Development] Mr.FREE_Bird:
I'm sorry to tell you that I don't have any other tips or tricks anymore... I never ran into such issues.

But maybe this thread will be helpful: https://xdaforums.com/google-nexus-5/orig-development/repartition-nexus-5-repartition-t3844395

You could try to follow it's instructions to revert to the stock partition sizes. It may work or not, hopefully it does.