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

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

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.

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.

[Addison]MultiROM v33 [No Kexec Workaround]

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for MotoZ Play. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting.
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.ays.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app (wait until I compile it) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-addison.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (MULTIROM-TWRP-3.1.1-Addison-unnoficial.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
[*]Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.[/INDENT]
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - add ROM to boot
List ROMs - list installed ROMs and manage them
Inject boot.img file - When you download for example kernel, which is distributed as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - we'll, settings.
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
Code:
[HIDE]
<remote name="multirom"
fetch="https://github.com/Tasssadar" />
<project name="multirom-dev/multirom" path="system/extras/multirom" remote="github" revision="master" />
<project name="multirom-dev/Team-Win-Recovery-Project" path="bootable/recovery" remote="github" revision="android-7.1-mrom" />
<project name="multirom-dev/libbootimg" path="system/extras/libbootimg" remote="github" revision="master" />
[/HIDE]
Kernel: https://github.com/Alberto97/android_kernel_motorola_msm8953/commits/twrp-7.1
Device: https://github.com/XPerience-AOSP-Lollipop/android_device_motorola_addison/tree/android-7.1-MROM
XDA:DevDB Information
[Addison]MultiROM v33 [No Kexec Workaround], Tool/Utility for the Moto Z Play
Contributors
TeamMex
Version Information
Status: Stable
Created 2017-05-20
Last Updated 2017-05-20

Reserved
Downloads:
TWRP_Multirom.img
multirom-20170520-v33-UNOFFICIAL-addison.zip
multirom_uninstaller.zip
MultiROMMGR Adapted for Addison

Reserved
FAQ and other notes
Device encryption
Encryption Fully working
SD CARD
Fully working
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentially make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very satisfying to work on code for device I don't have - I invested hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that:
https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM

CREDITS:
 @nkk71 (For kexec workaround) 
 @Tasssadar for MultiROM 
 @Alberto97 For TWRP kernel and Encrypt fixes taked from his TWRP repo.
Screenshots

Try to test but, mod twrp stuck on initial logo ( flashed via , twrp , flashify and fastboot )
Download it three time.
Please you can upload to another host?
Thanks sorry for my bad English.
Inviato dal mio XT1635-02 utilizzando Tapatalk

lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen....
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption

Alx31 said:
lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen..
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption
Click to expand...
Click to collapse
For me it's working fine
Sent from my Moto Z Play using XDA Labs

TeamMex said:
For me it's working fine
Sent from my Moto Z Play using XDA Labs
Click to expand...
Click to collapse
I mean is a upload problem..try to change host
Inviato dal mio XT1635-02 utilizzando Tapatalk

I'm getting, "Failed to create system.img" error for both SD card and internal storage.

Great work!
Waiting for Android O for the device.?
Can you tell if development of Android O for the device(Z Play) is started or not?
Thanks!

VR25 said:
I'm getting, "Failed to create system.img" error for both SD card and internal storage.
Click to expand...
Click to collapse
Me as well

Mrawesome13 said:
Me as well
Click to expand...
Click to collapse
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.

TeamMex said:
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.
Click to expand...
Click to collapse
I've decrypted my data, now recovery gets stuck at the splash screen. The standard TWRP works though. Tried MULTIROM TWRP 3 times -- Auto installation from the MultiROM app and manual from flashify & standard TWRP. I forgot to get a log. Will do it if I have time to try that again.

I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!

Hey, i did that. But it isnt working.. still same message

Anybody who can confirm that MultiROM v33 is working on moto z play under 7.1.1 stock rom with stock kernel?
Thanks!

wokawoka said:
I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!
Click to expand...
Click to collapse
yes but him was reverted the encription support.
I will try to update multirom in some day's.

Thank you for your reply @TeamMex!
I'm actually using in this right moment your TWRP 3.1.1 multirom and these are my findings:
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
I'm running a rooted stock moto z play 7.1.1 rom as my primary rom and I've installed MultiROMMGR and reinstalled TWRP from there as well.
Do you by chance have any suggestion about these issues?
Any new version that corrects bugs is of course very welcome. Thank you very much again for your work!

wokawoka said:
Thank you for your reply @TeamMex!
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
Click to expand...
Click to collapse
- Alright, so I was able to resolve the encryption password problem, as iit was my fault and not twrp multirom's: I just had to change again the security settings of the phone to enable the ask for pin code on boot.
- I circumvented the 64GB SDXC problem by using a 32GB SD card (still, it would be great to use a bigger sd card)
- Unfortunately, I'm still not able to use the multirom function: I'm running a moto z play stock 7.1.1 encrypted and rooted system, and as no alternative kernels exits for 7.1.1 at the moment. Is there a possibility in this conditions to get multirom working? I still receive the "E:Failed to create system.img" error when I try to install a secondary rom.
I'm not sure, but it feels like this moto z play multirom port is not actively mantained, which is a real pity because the phone is great and has all the characteristics to be the center of an active community of enthusiasts (in the same way some nexus or Samsung phones do) since it has quite unique features like good specs and an incredible battery life, the mod expandibility and an hardware qwerty keyboard that is going to be released very soon, and it also recently became very affordable.
Having a working multirom would help immensely and push the development of custom roms and alternative OSs (like for example sailfish https://talk.maemo.org/showthread.php?p=1538755#post1538755 ).
I would try to help or to take care of it myself but unfortunately I don't have the specific skills needed. I would be eventually up to give my contribution with some money (actually I'm thinking about creating a bountysource for it).
Is there by chance someone else that could bring on the port and release a stable working version?
If not, do you guys think that the it would be possible to adapt the twrp multirom released for the Moto Z (non-play version): https://forum.xda-developers.com/moto-z/development/mod-multirom-v33b-moto-z-t3513868 ? I can imagine that they have to be very similar.
Thanks again

any update on this?

[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)

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

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.

[oneplus3/t][Official] Droidian (Debian Bookworm) for OnePlus 3/T

Code:
/*
* 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.
*/
{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.This is accomplished by using well-known technologies such as libhybris and Halium.## What works
WIFI
Audio
Video Playback
USB-OTG
Cellular Data
Calls/SMS
Bluetooth
Wireguard
Flashlight
GPU (Works well in WayDroid, partially in Droidian)
See full list here
## What doesn't work
Camera
VoWifi
You tell us
Old UNOFFICIAL installation steps
Spoiler
This steps and UNOFFICIAL build of droidian have been abandonned and is deprecated, you're on your own there ! We recommand to follow official steps below
## Required Files
ADB commands and stuff
TWPR Treble : https://mega.nz/folder/UgdQRYSD#8s-_u2HJQZDEqNnFOnejxQ
You'll find it in : Recovery_(System-As-Root_Compatible) > twrp-op3treble-3.3.1-1.img
Latest firmware for your phone (at the writing time: 9.0.6) : https://github.com/nvertigo/firmware-3t/tree/master/archive (like version oxygenos-9.0.6-no-alipay-firmware-3.zip or oxygenos-9.0.6-firmware-3.zip if using a OP3)
WARNING ! Firmware are device-specific, be careful to take a OP3 or OP3T depending on your device !
LineageOS Treble: https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7
You only need the file LineageOS Treble
droidian-api28-arm64.zip : https://github.com/droidian-images/droidian/releases
NOTE: As we are flashing LineageOS 16 (android 9), pay attention to use and flash Droidian API28 (which is the version for Android 9)
Please do not use generic halium anymore, @Bettehem made a special version combining both files for OnePlus 3/T here : https://gitlab.com/Bettehem/op3-halium-waydroid Please prefer this version
Below, generic halium files that this tutorial does not recommend
halium-boot.img : https://mirrors.lolinet.com/firmware/halium/oneplus3/halium-boot.img
halium-ramdisk.zip : https://mirrors.lolinet.com/firmware/halium/GSI/tools/halium-ramdisk.zip
GSI patch by @Bettehem : https://gitlab.com/Bettehem/op3-gsi-fix-droidian
You can have alpha version from CI/CD artifact : https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
## Installation
First treblize your phone with the instructions from here: https://github.com/OP3-Halium/Documentation#treblelizing-your-op3t--firmware--twrp
Basically, all you have to do is :
Flash the special TWRP Treble previously downloaded
Boot it up and go to "Advanced" -> "Terminal", Type treblize and run
Reboot to recovery
Click to expand...
Click to collapse
Then follow the instructions here: https://github.com/OP3-Halium/Documentation#installing-using-erfan-gsi
Basically after you've treblized your device and installed the latest firmware, the install steps are as follows:
Flash the custom LineageOS Treble,so you get the /vendor partition populated.
Reboot to check that everything works. If so, reboot back in to recovery.
Go to advanced wipe and wipe everything except /vendor.
Reboot back into recovery.
Flash the droidian .zip (adb sideload droidian-api28.zip)
Deprecated steps
Flash halium-boot.img
⚠ This shouldn't be done with adb sideload, instead use those two lines :
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Flash halium-ramdisk.zip.
Now just flash @Bettehem's halium-boot.img
Flash @Bettehem's op3-gsi-fix-droidian.zip
⚠ Do NOT flash the regular op3-gsi-fix.zip which is for ubports and not this project ⚠
### Out of storageA note from @Bettehem 's GSI fix :
It was made possible to move the user's home dir to the phone's userdata partition, so you can utilize the full 64/128GB storage on the device. By default when you install Droidian, the user's home dir is on the 8GB system image, and that's not very much space for both the OS and your home dir
So after installing and booting the device, you can perform the first time setup if you want or skip it for now. Then open a terminal and run the command move-home
Click to expand...
Click to collapse
OnePlus3 is officially supported by Droidian now, here's the updated step by step install :
## Required Files
Download the latest recovery flashable zip droidian-OFFICIAL-phosh-phone-oneplus_oneplus3-api28-arm64_XXXX.zip: https://github.com/droidian-images/droidian/releases
## InstallationThe step-by-step installation comes from this guide : https://github.com/Droidian-oneplus3/device-page#requirements
Treblize your device:
Instructions here: https://forum.xda-developers.com/t/treble-unofficial-lineageos-16-0-treble-for-oneplus-3-3t.3830455/
After you have installed the custom twrp and you have a /vendor partition, install the custom LineageOS 16 build from the guide.
With LineageOS 16 installed, reboot and verify that everything works. Then reboot back into TWRP.
In TWRP, go Wipe -> Advanced Wipe -> Select everything except Vendor and USB-OTG, then Swipe to Wipe.
Reboot into recovery
Flash the droidian .zip using the recovery's install menu or adb sideload
Reboot
Congrats, you're all done, just restart your phone and enjoy using Droidian
## Troubleshoots
It had been reported some failing with the sideload function to flash parts of this tutorial.
If you enconter those problems, we recommend you to push the files to the device using adb push /path/to/your/file /tmp/ and then use TWRP's own install method
## Notes:
### First bootThe first boot can take up to 30 seconds. If you see the green droidian's logo on boot, don't worry for the following black screen, just your phone doing its stuff. Once you're os finally booted and ready to use, you'll have the screen showing time and icons.
### Default passwordThe default password is 1234.
### Wrong UI scaleSome applications aren't designed to fit well on to tiny mobile screens, so if you encounter a problem where buttons/text doesn't properly fit on the screen, do the following:
1. Open the application which doesn't fit well on your screen
2. Open the Mobile Settings application and navigate to the Compositor menu
3. Turn on the toggle for the application which doesn't scale well
Now every time you open the application, it should get scaled down to fit your screen.
### Status
Droidian GSIs are experimental! Bugs and missing features are expected.
OnePlus 3 isn't officially supported by Droidian
OnePlus3 is offically supported since 19/06/2023
@Bettehem's patch is a WIP
### SSH accessConnect your phone to your computer and type ssh [email protected]<OP3-WIFI-IP>, the password is 1234
### ApplicationsYou can find a list of mobile-friendly Linux applications at LinuxPhoneApps
# Credits
Thanks the Droidian team and the Mobian team for bringing Debian on mobile https://droidian.org | https://mobian-project.org
Thanks to the HaliumProject for all the hard work they do making this whole possible https://halium.org
Thanks to everyone contributing on https://github.com/OP3-Halium for those comprehensive tutorials
Thanks to simonsmh, dianlujitao, chenxingyu, for working and building the LOS Treble (Source Code: https://github.com/OP3Treble )
A huge and special thanks to @Bettehem (Telegram, Gitlab, XDA) for developing the patch and did help me to have it up and running on my phone
Thanks to you for giving a try to this and following this tutorial

# Troubleshooting## WiFi not connectingDroidian detects two wifi cards, and only one seems to work at a time.
If Droidian is trying to connect using the wrong card, you can easily change it by running the command nmtui, then select "Activate a connection" and then select the WiFi network you want to connect to.
## Mobile data not workingIn settings go to mobile network and press the "Unlock" button. Then close the settings app and open again, because the UI doesn't get updated automatically.
You should now be able to manage your mobile connection from here. To get correct Acces Point Name (APN) settings for your carrier, look here: https://apn.how
After you have set up the APN settings, then just toggle the "Mobile Data" setting off and back on again. If mobile data still doesn't work, you may want to restart the ofono service by running this command: sudo systemctl restart ofono.service. Then reopen settings and toggle the "Mobile Data" setting off and on again.
## Changing audio deviceThere's a known issue with changing the audio device inside the Settings app. You can use something like pavucontrol, ncpamixer or even just run pactl/pacmd commands directly.
You need to change the sinks port from the primary_output sink for it to work. Changing the port from the deep_buffer sink doesn't work.
# Random screenshots

I'm working on getting this installed. Can't seem to get past bootloader (oneplus icon).
Attempting to build on my system and see if that helps.

@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"

RoiArthurB said:
@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"
Click to expand...
Click to collapse
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.

undrwater said:
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.
Click to expand...
Click to collapse
The problem may come from the firmware link I did put before. It wasn't for 3T, so I just updated it and it would prevent similar errors
Please tell me when you'll retry and if now it works well

Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available, and the few I've tried fail with:
E: No hybris-mobian image found
Click to expand...
Click to collapse
/vendor is populated, lineage is flashed and booted halium boot image dd'ed.

undrwater said:
Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available
Click to expand...
Click to collapse
Hey, the good version is Droidian API 28 ('cause you're using a base Android 9) ARM64 (which is the Snapdragon in OP3/T)

My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted

the-blind-bandit said:
My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted
Click to expand...
Click to collapse
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device

Bettehem said:
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device
Click to expand...
Click to collapse
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored

the-blind-bandit said:
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored
Click to expand...
Click to collapse
Yeah I like Droidian quite a lot. I have been using it as my daily driver for some time now. Only camera doesn't work but hopefully I'll solve that issue at some point in the near future

I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?

prosch said:
I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?
Click to expand...
Click to collapse
Hi, this tutorial recommand using Bettehem's halium-boot file.
If you did checked the Github's documentation, you should have saw a note part for flashing the halium-boot.zip ( https://github.com/OP3-Halium/Documentation#note ) describing 3 differents methods to do it. Did you follow them all or how did you do it ? It may be recommended to use the old technic :
Flash halium-boot.img ⚠ This shouldn't be done with adb sideload, instead use those two lines :
Code:
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Click to expand...
Click to collapse

I used fastboot and the TWRP push method, no difference. I used all the files linked in this tutorial and all of those in the github documentation. After flashing, when rebootIng, TWRP complains that there is noch OS installed... Lineage Installation is no problem. I just tried the ubports installer to install Ubuntu Touch. This stops while pushing the files... Installing OxygenOS works... kinda strange
Update: It's working now. I also had to do "format data / factory reset" after step 2 and repair the fs of cache, system and data to ext4 after rebooting. Using the files from the OP3-Halium-Documentation Droidian is now loading.

I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?

marmistrz said:
I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?
Click to expand...
Click to collapse
You shouldn't be installing ubports_GSI_installer if you want Droidian. UBports is Ubuntu Touch.
To get Droidian running, follow the instructions on this page or https://github.com/OP3-Halium/Documentation#installing-droidian
For Droidian, you shouldn't be using ubports or droidian-devtools, as neither of those are used in this installation.
droidian-devtools is optionally used with very old droidian images and is not at all needed in the newer ones so don't use it.

Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?

sfoslino said:
Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?
Click to expand...
Click to collapse
Hi, I'm not sure why it does that but I'll try to investigate

Bettehem said:
Hi, I'm not sure why it does that but I'll try to investigate
Click to expand...
Click to collapse
If I remember right it could sleep if I disable wifi. I tried to work around with a script running 'onsuspend' but had no luck, always a probleme because the wifi adapter was shown twice in phosh settings.

Database Info

welcome