Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 Ultra (Exynos)

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 Ultra (Exynos) - Samsung Galaxy S22 Ultra

Changelog:
GitHub History

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.

Any love for s22/s22+?

Hi, this it's Really cool, But no more official releases?

NisseGurra said:
Any love for s22/s22+?
Click to expand...
Click to collapse
Soon, join the group and provide me with some files

ANyone already test it?
Does it works stable?

dantist_140 said:
ANyone already test it?
Does it works stable?
Click to expand...
Click to collapse
No Problems so far.. Installed and decrypted since 6 Days now

Daniel210191 said:
No Problems so far.. Installed and decrypted since 6 Days now
Click to expand...
Click to collapse
I cant delete any in /system/ directory via Solid Explorer or TWRP File Manager - "rm -rf ERROR 1."
What am I doing wrong ?
==============
UPD: There are no /system/ in Backup or Format tabs...
UPD2: I tryed for remount it by a cmd:
mount -o rw,remount /system_root
and have output:
'/dev/bloc/dm-0' is read-only.
Filesystem on /system - F2FS.
Total: /system/ directory is read only. I have no way to remount it to RW to make a changes...

So when making a backup what partitions do I need to check? There is a lot more partitions these days some I've never heard of before lol just got the s22 ultra as an upgrade coming from Note 9. oh how i already miss my headphone jack and sd card lmao holding on to this old note as looong as I can. But yea just a little confused note 9 had way less partitions and I know some aren't needed for backups just can't remember and don't know about these new partitions ie: Super, Prism , Etc

dr.ketan said:
Super + data should be enough. Though you can backup prism + optics
As S22 have system ro nothing going to change in system, product,etc except vendor. For that purpose you needs super backup. Prism and optics for csc related.
Click to expand...
Click to collapse
dr.ketan:
Here some my thoughts and explanation about TWRP backup and restore
Firstly brief explanation about what does partition contains.
Boot : It is Kernel
Recovery : It is Recovery
super : That contains odm,product,system and vendor partitoin all togather.
optics : CSC files (where we routinely making changes for csc features) and network settings depending on your carrier
prism : carrier related apps and other stuff . In odin when you flash CSC*_ or Home_CSC* these two optics and prism gets flashed.
data : That is all your installed app and made changes in settings
Now what to backup/restore?
boot - Helps if something messed up with magisk or waht to restore kernel after flashing custom.
recovery - usually it doesn't require but if you flash some other recovery(TWRP) and you want to restore one in backup, that helps
super : As stated above these is main system, if something you have messed up in system/vendor (usually with flashing something, or erasing something) you can restore by super.img.
optics and prism : as explained above are CSC files, Rather than restoring it, I prefer to flash HOME_CSC*.tar.md5 to make csc compartment clean. So to backup or not not much important.
data : This very sensible part. I prefer to make data backup when there is no samsung a/c or Lockscreen protection there. Also don't restore it cross version of ROM. Also some common mistakes user making is, He/She clen install ROM and then restore data partiton of previous ROM. This is worst then even dirty installing ROM, never do it. It is just false sense of satisfaction that you made a clean install. According me, data partiton backup best to be made just after complete clean install ROM and setting up device without adding any account and lockscreen protection. So when you restore this backup, you will have a device just like you recently completed clean install and save your time to setup initial wizard
Backup Application,Call logs,Contacts,SMS etc
Titanium backup was ruling for decade for these but since A11 it's not trust worthy and on A12 almost useless.
Swift Backup is now my choice (Some other like Migrate, App dash (by RD XDA dev flar2) also alternatives)
For contacts : I do prefer google sync. Just adding google ac everything will be restore on it's own, provided you are saving contacts in google. In case you want to make off line backup of contact, there is a built in utility in phone. Contact - settings - export - This will create a file. Similarly browse same file while you want to import contacts. Catch in this is your contact image will not retain size and it just backup thumbnail picture.
Only one utilility I have found that makes offline contact backup without distoring image quality is My Phone Explore client (needs on both PC and Phone). Also this utility is best for wireless file manager.
Schheduled backup - A must needed utility.
I always prefer clean installation (Factory reset withot wiping media files) and really it takes less than 30 minutes to setup everything.
If you enable schedule backup utility in your Backup app (e.g Swift backup have this) and make some profile like
1.Backup - new app at X time then it will auto backup all app that you have new installed at given time
2.Backup updated app at x time - This will make backup of any app that you have updated in store will backup at given time
3.Any app which get data changes frequently and you needs data changes like whatsapp then create a profile favorite app - add whatsapp in favorite and schedule it to make backup daily at given time.
with these your device always remain ready to clean install anytime instead of last moment backup or some urgent clean install needed.
Also Folder Sync is good utility if you needs duplicate copy of files from Internal storage with scheduled operation.
Hope this may helpful and answer lots of queries for many.
Click to expand...
Click to collapse
Passing this info along to anyone else that was confused by which partitions were needed for a basic backup

Any chance we can get the kernel to support OverlayFS so it can emulate system rw? Trying to get this module to work Magisk OverlayFS.
Thanks

Two questions:
1. Is the custom kernel required to be flashed?
I have rooted ROM and Magisk is already installed.
2. Can be TWRP installed on this phone or do I need first back to stock ROM flashing original AP* tar file?

rafal.polska.b said:
Two questions:
1. Is the custom kernel required to be flashed?
I have rooted ROM and Magisk is already installed.
2. Can be TWRP installed on this phone or do I need first back to stock ROM flashing original AP* tar file?
Click to expand...
Click to collapse
1.If you want to use TWRP fully functional, you needs to run multidisabler and that needs to have custom kernel. If you want to use TWRP and don't run multidisabler, it is fine with stock kernel too, but here TWRP have very limited functions like backup partition (except data partition) only to USB storage. SO say, yes you needs custom kernel, else it is useless to have TWRP
2. You can install straighway TWRP (must be included patched vbmeta) if you are already on stock rooted ROM + you needs to run multidisabler + needs to Format data.

dr.ketan said:
1.If you want to use TWRP fully functional, you needs to run multidisabler and that needs to have custom kernel. If you want to use TWRP and don't run multidisabler, it is fine with stock kernel too, but here TWRP have very limited functions like backup partition (except data partition) only to USB storage. SO say, yes you needs custom kernel, else it is useless to have TWRP
2. You can install straighway TWRP (must be included patched vbmeta) if you are already on stock rooted ROM + you needs to run multidisabler + needs to Format data.
Click to expand...
Click to collapse
TWRP installed, custom kernel too.
Everything went OK except Wipe -> Format Data.
It ended with "Successful" final result but generated few errors at the beginnig:
Anyway, when restarting my phhone to recovery TWRP is launched, in system everything is OK.
Now I'm waiting for dr.ketan ROM version S09.
Thanks so far for your explanations @dr.ketan

Guys I have just received a Korean 512GB S908N, the phone seems to have a Snapdragon CPU. Why is it in this Exynos thread?
Please help me understand, searching has not led to any answers so far about what the CPU really is. The internet seems to have mixed feelings.
What is happening?

babyboy3265 said:
Guys I have just received a Korean 512GB S908N, the phone seems to have a Snapdragon CPU. Why is it in this Exynos thread?
Please help me understand, searching has not led to any answers so far about what the CPU really is. The internet seems to have mixed feelings.
What is happening?
Click to expand...
Click to collapse
Install cpu-z or any app that check for cpu and check, also check for bootloader. Might be flashed to different fake software

afaneh92 said:
Install cpu-z or any app that check for cpu and check, also check for bootloader. Might be flashed to different fake software
Click to expand...
Click to collapse
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.

babyboy3265 said:
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.
Click to expand...
Click to collapse
Let me double check

babyboy3265 said:
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.
Click to expand...
Click to collapse
OK you have a snapdragon S22 Ultra, it was mistake maybe samsung changed her mind when I first searched they said exynos.

Related

[Recovery] Official TWRP for the OnePlus 3 & 3T

Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07

Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.

jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:

peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.

RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.

ext4 decrypted fine on OnePlus 3 OOS 4.0.2.

Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.

fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.

Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T

Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?

Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version

ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything

cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:

the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?

Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.

Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?

chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.

[FIXED][OFFICIAL][APP]Dualboot Patcher For Lenovo A6000/+

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am proud to present the official dual boot project for Lenovo A6000. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:I have managed to get Lenovo A6000 to the DualBootPatchers Official list, I am not the creator of the Dualboot patcher, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am 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 ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app from the download section below.
4. A rare thing you find now-a-days on XDA known by the codename: B.R.A.I.N
What does the app do ?:It patches...
Custom kernels for dual boot support
ROMs to make them boot as secondary
Gapps
Any other mod you would like to install on your secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
-Grant Root Permission
-Go to settings and select install bootui
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later, and if you weren't asked to set kernel then select set kernel also.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to "a6000-Lenovo-A6000" and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip.
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Using Bootui:
- After installing (update) bootui, and flashing the secondary ROM then go to "ROMS" section again and open secondary ROM Settings) and select Update Ramdisk, Now when you will reboot a TWRP like Screen will appear, in that select whichever ROM u wanna boot.
Note-
Clean Flashing any simple ROM from TWRP will wipe both the ROMs, so if you clean flash and want to dual boot, follow the instructions again.
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?This is simple ... . So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Instead you can use the bootUI to switch ROMs as stated above
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
FAQs
How do I uninstall the secondary ROM
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
OK, Now i Want to change my Primary ROM but want to keep the Secondary ROM
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM
I wanna change the secondary ROM
Wipe it using the 3 dot menu and Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Ok but the Update Ramdisk failed
Dont worry simply follow the further steps, i have got it thoroughly tested on the telegram group and by myself
But I have the 8GB Variant so wont flashing secondary ROM eat my Storage space?
The Answer is NO, you may not be able to flash Gapps in some cases for secondary ROM, but as long as you flash the secondary ROM in /system, your storage space wont be used
Downloads:
https://dbp.noobdev.io/downloads/Cheers ! we are officially supported
Note: You can download any version since "9.3.0.r97.g737d9dd5"
Sources:DualBootPatcher:https://github.com/chenxiaolong/DualBootPatcher
Lenovo A6000 Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/922
Known Issues:
Comment here if you face any.
Credits:
@chenxiaolong for the awesome DualBootPatcher.Other people behind the DualBootPatcherAnd Me :V
XDA:DevDB Information
[OFFICIAL][APP]Dualboot Patcher, Device Specific App for the Lenovo A6000/Plus
Contributors
[email protected]_, chenxiaolong
Source Code: https://github.com/varunhardgamer/DualBootPatcher
Version Information
Status: Stable
Created 2017-11-04
Last Updated 2017-11-04

This is more than awesome dude.

Reserved

Fine...
Something new for A6k/+

[email protected]_ said:
Reserved
Click to expand...
Click to collapse
Oops!!! Seems I posted before OP. Sorry for that.

Jitheshwar said:
Oops!!! Seems I posted before OP. Sorry for that.
Click to expand...
Click to collapse
No problem dude, you reserved for me :good:

is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4

garvit girotra said:
is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4
Click to expand...
Click to collapse
I know that and we are checking it again, looks like something got derped

EDIT-> The issues are fixed grab the latest snapshot

The fix has been added, download fhe latest snapshot and enjoy

Astala vistala baby
Varun you are the man

Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work

garrygarvit said:
Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work
Click to expand...
Click to collapse
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants

[email protected]_ said:
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants
Click to expand...
Click to collapse
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Well i find the solution i revert to the stock rom of lenovo and try dual boot patcher work in that ramdisk kernel boot ui all work i think the problem is in the .aex rom by the thanks for all help varun
---------- Post added at 09:08 AM ---------- Previous post was at 08:46 AM ----------
Well a new problem arises now after all success that now when i am not able to download any things from chrome or other browser in the internal storage it shows no sd card detected download failed by the then i checked into storage there both my internal storage and external storage dont know why this happen now i fed up of all this. Now i will be only to stock rom for some while no rooting no flashing

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Right now i am on aex 4.4 dual booting aicp

[email protected]_ said:
Right now i am on aex 4.4 dual booting aicp
Click to expand...
Click to collapse
Updating ramdisk on work for in lenovo stock rom not on aex even after the clean flash

Dual Boot
Hello Varun
Can i Dual Boot Stock Kitkat and Viper
as Both has different Android version. so difference is only of one flaashable file that is: kk to lp firmware patch .
so how to do that.

[Recovery] TWRP (vela) - Official 3.3.1-0 (final)

Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.

yotamy said:
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
Click to expand...
Click to collapse
It's working now. Thanks

I think it works
gringo80 said:
It's working now. Thanks
Click to expand...
Click to collapse
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?

yotamy said:
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
Click to expand...
Click to collapse
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !

thanks. Some QA
gringo80 said:
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
Click to expand...
Click to collapse
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam

yotamy said:
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
Click to expand...
Click to collapse
this is not a bug. you have to format data after installing twrp.
from twrp homescreen, go to :
Wipe > Format Data (on the right) > type yes from the keyboard
TWRP don't support backup/ restore from encrypted files/folders. You must decrypt by formatting data !
Reboot to system. Install and config your rom then go TWRP to make backup !
Always put your roms and zip on the External SD Card... or sideload them by adb cmd from your windows PC !

Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !

sorry. i dont understand
gringo80 said:
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
Click to expand...
Click to collapse
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?

yotamy said:
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
Click to expand...
Click to collapse
lol
it's inside the zip. go to my mediafire link. you will find everything
yes you flash it on twrp

i cannot thank you enough
thanks again

New Update (TWRP auto-decrypt)
yotamy said:
i cannot thank you enough
thanks again
Click to expand...
Click to collapse
Please update you TWRP ! (Highly recommended). Read OP carefully !
Thanks
:good:

You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp

yotamy said:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
Click to expand...
Click to collapse
Yes, the fingerprint and the lockscreen pattern.
Follow the instruction on the OP !

Are the font files related to this twrp?
There are 2 font files in the link

yotamy said:
There are 2 font files in the link
Click to expand...
Click to collapse
NO, for the roms !

Speaking of roms.....

yotamy said:
Click to expand...
Click to collapse
work in progress

now its working good
gringo80 said:
work in progress
Click to expand...
Click to collapse
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam

yotamy said:
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
Click to expand...
Click to collapse
Don't delete TWRP folder on your internal storage, to keep your TWRP settings.
3 way reboot is framework related. Sorry i don't support MIUI for now because i'm busy with GSI. Try to download "Simple Reboot" from the playstore.

[ROM][11] DarkJoker360 AOSP 11 for Huawei P8 Lite 2017

Hi,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DarkJoker360 AOSP 11 for Huawei P8 Lite 2017
*** Stable Version ***
About
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
Click to expand...
Click to collapse
Working
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures
Click to expand...
Click to collapse
Not Working
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
Update
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download
AOSP 11 and NFC fix
NikGapps
OpenGapps
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !

NOTES
* For root method read this post, for rooting with magisk read this instead.
* If you face corrupted storage issues you need to go back on emui and re-install the rom.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.

Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)

Hi . how can i "resize system" ?

piterconlai said:
Hi . how can i "resize system" ?
Click to expand...
Click to collapse
Go to twrp recovery, press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System" - press on it and done ur System has been resized.

hardcorehenry said:
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
View attachment 5194331 View attachment 5194333
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Click to expand...
Click to collapse
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?

Added to AOSP 11 accent, font and icon shape picker (like theme picker), now working on an aosp icon pack picker (aka styles) !

piterconlai said:
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Click to expand...
Click to collapse
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected again and again), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.

hardcorehenry said:
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
Click to expand...
Click to collapse
Thanks for the reply
so can you do 8 h of screen with this rom?
Have you tried if the blutooth smartwatch works by accident?
Last question :
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it

piterconlai said:
so can you do 8 h of screen with this rom?
Click to expand...
Click to collapse
Well you have to calculate yourself from data I provided or flash rom and find out.
piterconlai said:
Have you tried if the blutooth smartwatch works by accident?
Click to expand...
Click to collapse
I don’t have such device.
piterconlai said:
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
Click to expand...
Click to collapse
If you are more interested in comfort than struggle, testing and help DEV to perfect this rom don’t change anything. Going back means flash and install everything from scratch.

I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.

hardcorehenry said:
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
Click to expand...
Click to collapse
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards

Friedensfurz said:
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Click to expand...
Click to collapse
Hi,
I’ll try exactly step by step how I did it(I’m on macOS so there might be small differences). When on stock after unlocking bootloader and flashing TWRP(took from this post), you need to copy on your external sdcard or USBOTG NFC_fix.zip, gapps(optional) and fstab.hi6250b.zip or edit your own from /vendor/etc like in this post. Boot into TWRP (backup just in case your vendor partition)and either flash fstab.hi6250b.zip(easy way) or replace fstab.hi6250 in /vendor/etc with edited one via TWRP file manager(harder way). After flashing/replacing enter in TWRP into Wipe and Format Data>yes then reboot into TWRP, wipe: cache, dalvik cache and data and reboot into system. You should reboot into ugly looking stock rom. In settings>security>more you should see Encrypt phone that means storage is decrypted. Enable debug and confirm via adb and boot into TWRP. Make backup(ramdisk, kernel, data, system) enter section Wipe>Advanced Wipe and wipe Dalvik/ART Cache, Cache, Data and System. Don’t Format Data again because most probably it'll f*up Internal Storage besides internal storage is already decryptet. Reboot into bootloader. Run in terminal(macOS) or whatever is used in Windows/Linux:
fastboot devices
fastboot flash system drag and drop aosp-11_prague_20210117.img
Reboot into TWRP, resize System if needed, flash NFC_fix.zip and gapps(optional).
Wipe Cache and Dalvik, reboot and that should be all.

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
It is a know "issue", just ignore it and boot it.
It is most likely a warning.

DarkJoker360 said:
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
Click to expand...
Click to collapse
Nope it's caused by new version of official firmware for this phone, system partition on newer versions is 2GB on b388 is 3GB.

That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed working firmware 8.0.0.402[service rom] or 8.0.0.400 [the same as developer's]).

hardcorehenry said:
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed firmware 8.0.0.402[service rom]).
Click to expand...
Click to collapse
I recommend .360 firmware or .400 (the one I am using)
Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding.

Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.

Friedensfurz said:
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Click to expand...
Click to collapse
No magisk at the moment, I'm sticking with A10 untill Magisk 19.3 will work on this rom (need to pass safety net)

[Ubuntu Touch][Halium-9.0]LG Nexus 5X (WIP)

I am not responsible for bricked devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
What Is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu. This operating system is developed and maintained by UBports: An international community of passionate volunteers. This means Ubuntu Touch is 100% community driven and independent.
Ubuntu Touch - A Different Approach
Ubuntu Touch offers a completely different approach to using your smartphone or tablet than using other mainstream operating systems. The OS is built on Ubuntu, which provides us with a secure and stable base system used by millions of people across personal computers, servers, IoT devices and even the international space station.
The intuitive user interface allows you to access all of your phone's features by swiping from the edges of the screen to access your apps, tools and settings all with one hand and no on-screen buttons. It looks great and feels smooth.
How to install :1- Download this ubuntu-touch-bullhead-v02.zip2- Backup your data, boot, vendor partition (system not needed) if you want return back to your current rom3- Format data partition (format to remove any encryption setting)4- Copy ubuntu-touch-bullhead-v02.zip in internal storage of your phone5- install ubuntu-touch-bullhead-v02.zip like regular ROM6- reboot.
Password system : 1111what work :
Touch Screen
Wifi
Sound
Camera (on first boot if system tell you for permission, just reboot phone)
Ril
GPS (tested with uNav)
What not work yet:
Bluetooth
Fingerprint

Code Source :
Device Tree : https://github.com/bullhead-ubuntu-touch/device_lge_bullhead
Kernel source : https://github.com/bullhead-ubuntu-touch/kernel_lge_bullhead
Ubuntu Touch Rootfs : https://ci.ubports.com/job/xenial-hybris-android9-rootfs-arm64/

good job i will try it

Going to give it a go. Hopefully things will go well.
Which recovery would you recommend? (or can I use any?)

safdarhp said:
Going to give it a go. Hopefully things will go well.
Which recovery would you recommend? (or can I use any?)
Click to expand...
Click to collapse
TWRP latest version

Above all, thank you for your work and sharing.
Overall, the system works well and is stable.
But I've a major problem, I don't have sound and microphone during an standard phone call.
(i'm sorry for my English (french - translate))

linuxowin said:
Above all, thank you for your work and sharing.
Overall, the system works well and is stable.
But I've a major problem, I don't have sound and microphone during an standard phone call.
(i'm sorry for my English (french - translate))
Click to expand...
Click to collapse
thank you for testing, i 'm working to solve this issue. Also i have progress for fingerprint, sensor, work but when system try to save fingerprint the application crash.
Best regards

Thank you, it seems to be working well (I don't plan to use the device for calling, more for IoT and it is much better than emulating linux in android).

Love your work sooo much! Only was able to find a nexus 5x instead of 5 and was considering return it when I find your post.

walidham said:
I am not responsible for bricked devicesView attachment 5724455
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
What Is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu. This operating system is developed and maintained by UBports: An international community of passionate volunteers. This means Ubuntu Touch is 100% community driven and independent.
Ubuntu Touch - A Different Approach
Ubuntu Touch offers a completely different approach to using your smartphone or tablet than using other mainstream operating systems. The OS is built on Ubuntu, which provides us with a secure and stable base system used by millions of people across personal computers, servers, IoT devices and even the international space station.
The intuitive user interface allows you to access all of your phone's features by swiping from the edges of the screen to access your apps, tools and settings all with one hand and no on-screen buttons. It looks great and feels smooth.
How to install :1- Download this ubuntu-touch-bullhead-v02.zip2- Backup your data, boot, vendor partition (system not needed) if you want return back to your current rom3- Format data partition (format to remove any encryption setting)4- Copy ubuntu-touch-bullhead-v02.zip in internal storage of your phone5- install ubuntu-touch-bullhead-v02.zip like regular ROM6- reboot.
Password system : 1111what work :
Touch Screen
Wifi
Sound
Camera (on first boot if system tell you for permission, just reboot phone)
Ril
GPS (tested with uNav)
What not work yet:
Bluetooth
Fingerprint
View attachment 5724459
Click to expand...
Click to collapse
When I install it and reboot it doesn't go past the Google logo

By the way you need to install a Android 9 rom first (Nexus PieX for example, that's what I used) so that halium 9 would work (Link to Nexus PieX: https://forum.xda-developers.com/t/...nexus-piex-v1-0oct-bullhead-20181101.3827122/)

jihoonahn said:
When I install it and reboot it doesn't go past the Google logo
Click to expand...
Click to collapse
TimSR9624 said:
By the way you need to install a Android 9 rom first (Nexus PieX for example, that's what I used) so that halium 9 would work (Link to Nexus PieX: https://forum.xda-developers.com/t/...nexus-piex-v1-0oct-bullhead-20181101.3827122/)
Click to expand...
Click to collapse
Here

TimSR9624 said:
Here
Click to expand...
Click to collapse
Thanks! I was using a10

Hi thanks for the port. Installed fine and running well so far. It does take up space though and for the novice ROM installer there are a couple of steps required.
Download
Ubuntu Touch link as above (post1)
Android Pie as per post 12
TWRP for Bullhead
Boot to bootloader (fastboot) - Make sure the bootloader is unlocked - If not unlock the bootloader, reboot to Android, set it up and reboot to bootloader.
Flash the TWRP recovery
Boot recovery and Backup if required the stuff in post1 ( backup all your data if the device is your daily driver)
Format the data partition to EXT4 (if it is not already EXT4) in the wipe tool
Connect to PC and put the Android Pie zip to the root of the device, i.e. not in a folder
In TWRP install Android from Zip file
Reboot to Android.
Reboot to fastboot
Install TWRP
Change DATA partition to EXT4 in the advanced part of the wipe tool
Wipe CACHE
Copy the Ubuntu Touch zip file to the root of the device
Install the zip file - leave the device alone while it is doing this
When done reboot
Enjoy Ubuntu Touch on your Nexus 5X "Bullhead". This worked for me and is my experience. You do this at your own risk. The Nexus 5X is a pain for bootlooping due to a c**p design, like its predecessor, the Nexus 5.

MrT10001a said:
Hi thanks for the port. Installed fine and running well so far. It does take up space though and for the novice ROM installer there are a couple of steps required.
Download
Ubuntu Touch link as above (post1)
Android Pie as per post 12
TWRP for Bullhead
Boot to bootloader (fastboot) - Make sure the bootloader is unlocked - If not unlock the bootloader, reboot to Android, set it up and reboot to bootloader.
Flash the TWRP recovery
Boot recovery and Backup if required the stuff in post1 ( backup all your data if the device is your daily driver)
Format the data partition to EXT4 (if it is not already EXT4) in the wipe tool
Connect to PC and put the Android Pie zip to the root of the device, i.e. not in a folder
In TWRP install Android from Zip file
Reboot to Android.
Reboot to fastboot
Install TWRP
Change DATA partition to EXT4 in the advanced part of the wipe tool
Wipe CACHE
Copy the Ubuntu Touch zip file to the root of the device
Install the zip file - leave the device alone while it is doing this
When done reboot
Enjoy Ubuntu Touch on your Nexus 5X "Bullhead". This worked for me and is my experience. You do this at your own risk. The Nexus 5X is a pain for bootlooping due to a c**p design, like its predecessor, the Nexus 5.
Click to expand...
Click to collapse
here i have a problem. i have did all steps by order and always i get bootloop on start (google sign on black screen)
please help me

Ensure the data partition is formatted to EXT4. When installing Android Pie, you must reboot and allow it to boot up to the home screen. Sometimes on other ROM's once I have changed the data partition to EXT4, I reboot to TWRP recovery.

MrT10001a said:
Ensure the data partition is formatted to EXT4. When installing Android Pie, you must reboot and allow it to boot up to the home screen. Sometimes on other ROM's once I have changed the data partition to EXT4, I reboot to TWRP recovery.
Click to expand...
Click to collapse
i have tried it few times and still don't work :/
is it matter which twrp is installed, maby it needs specific version??

It shouldn't do, but I used twrp-3.5.2_9-0-bullhead.img. It is important to install Android Pie.

MrT10001a said:
It shouldn't do, but I used twrp-3.5.2_9-0-bullhead.img. It is important to install Android Pie.
Click to expand...
Click to collapse
Do you use telegram, that we can be faster in chat and that i can send a video?

I am not on social media. Start from installing Android Pie from the above download. Make sure you have fully booted in and enable developer options again, then try again.
Did you have a custom ROM on before, like LineageOS. A custom ROM sometimes will resize the partitions to non-stock and Ubuntu Touch requires stock partition sizes to install. If you have had a custom ROM installed, you will need to find out how to get the Nexus 5X back to stock partition sizes.

Database Info

welcome