Related
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.
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/AICP/kernel_htc_msm8994
Download:
ROM https://www.mediafire.com/folder/gvfujacrh306y/crDroid_10
Version 6.12 is Claymore style version, 6.16 is my style, maybe more performance on cost of battery.
Known issues:
None, tell me
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2020-11-23
Last Updated 2021-05-13
The download link of suggested twrp is here.
tombbb said:
The download link of suggested twrp is here.
Click to expand...
Click to collapse
Its already included in flashing instructions
I clean installed your ROM on my M9, and it's nice!! Thank you!
May I ask will there be build 6.1.3 for m9?
tombbb said:
May I ask will there be build 6.1.3 for m9?
Click to expand...
Click to collapse
I think yes , i will build lastest release and then iam aiminng for Crdroid 7. But for now i have to wait to get my Notebook fixed...
Hi, I try the rom and it's great, all works but signal operator. My broadband comapny is Fastweb (Italy) and the sim is ok, not broken (tested on another HTC One M9). What can it be? Any suggestion?
Thanks in advance
Update (15 Feb 2021)
weird is when I run the phone it ask me for the SIM passoword, so it seems that it seeing by the system but, if I try make a call it say: cellular broadband network not available
Marko Indaco said:
Hi, I try the rom and it's great, all works but signal operator. My broadband comapny is Fastweb (Italy) and the sim is ok, not broken (tested on another HTC One M9). What can it be? Any suggestion?
Thanks in advance
Update (15 Feb 2021)
weird is when I run the phone it ask me for the SIM passoword, so it seems that it seeing by the system but, if I try make a call it say: cellular broadband network not available
Click to expand...
Click to collapse
Ah bro when you want sigal go to APN write something save it , and then it work , its a bug in generell
platinumthis said:
Ah bro when you want sigal go to APN write something save it , and then it work , its a bug in generell
Click to expand...
Click to collapse
I already try it without success. I'll try again in a few hours but I'm feeling that dont works. I wonder what could be. I mean, I use ViperOneM9 on another HTC OneM9 and it's always works fine. No need to set APN or whatever. Even after flash/dirty flash, changing roms and then reisntall ViperOne... the signal always works perfect in this case.
Thank you for reply anyway
Changelog
* Updated to lastest Crdroid and Lineage base
* Tweaked some Performance
* ViperFX Works Out of the Box
Such a good news ! Thank you !
Is dirty flash from 6.12 to 6.16 suggested ?
It has to work when you flash
tombbb said:
Such a good news ! Thank you !
Is dirty flash from 6.12 to 6.16 suggested ?
Click to expand...
Click to collapse
Indeed
platinumthis said:
Indeed
Click to expand...
Click to collapse
I upgraded to 6.16, it is great and stable.
platinumthis said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/AICP/kernel_htc_msm8994
Download:
ROM https://www.mediafire.com/file/gcpqv6fou03pag9/crDroidAndroid-10.0-20210512-hima-v6.18.zip/file
Known issues:
None, tell me
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2020-11-23
Last Updated 2021-05-13
Click to expand...
Click to collapse
Hello, i want revert back version 6.16. It is possible?
6.18 is doing random restarts.
Sure its possible, i wil invetigate and will make a new one when i have time, lets say 10 Days
platinumthis said:
Sure its possible, i wil invetigate and will make a new one when i have time, lets say 10 Days
Click to expand...
Click to collapse
Or use only 6.16 and get there security updates. This version was really crazy in battery life. I remember also some little graphics glitches, mostly with recents, but in overall BEST custom rom for this device.
tombbb said:
I upgraded to 6.16, it is great and stable.
Click to expand...
Click to collapse
Hi Do you have v6.16 of this ROM? If yes, could you please share with us? Thanks
Arsenik013 said:
Hi Do you have v6.16 of this ROM? If yes, could you please share with us? Thanks
Click to expand...
Click to collapse
I once checked last time someone asked, but I don't have it anymore...
I don't see any bad of 7.12, maybe you try sometime?
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/Claymore1297/android_kernel_htc_msm8994
Download:
ROM crdroid.net
ViperFX Profile for Speaker
Unzip_me_not_flashabel
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
ViperFX is included and fully suporrted,
just disabel AudioFX or turn on legacy mode.
I dont recommand both together couse (loud bugs)
For those peopel who download over phone i suggest to turn Desktop Mode ON in Browser settings to be abel to Download directly.
Known issues:
Only FM not working, if found something
share log and we will see
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2021-05-11
Last Updated 2021-11-18
Thank you for the great work!
The gapp link is for android 10. Is it good to go on android 11?
Oh, yeah i replaced them. 10 from opengapps not work doe SDK. Nikgapps should work but remember when flash new rom also to flash Nikgapps again , in recovery it will say it will backup and install again but in the end it can lead to bootloop so after a New Build flash Nikgapps again or it will not start. i just looked at Opengapps they dont have 11 there. Or when you want to ungoogel go to /data/app and find vendig or venedig apk and delete it from Recovery in Advanced settings. So it should start without need to flash of Nikgapps
Does not boot for me, even on a clean flash, just reboots with a "TSENS reset" error
Edit : After flashing it like 10 times for whatever reason it booted up just fine, will use it some time and then give you my thoughts
Edit1: After trying to install gapps, the phone crashed on boot with the same error, like 5 reinstalls later, still doesnt work, maybe it could be because my phone is hot, i think TSENS means Temperature SENSor, ill let it cool off a bit.
Edit2: After cooling down the phone shows a different error "KP: EDAC cache: UE instance:cpu7 block L2 'A57 L2 Uncorrectable Error'
This was a very cool rom for the 30 minutes that it worked, i wish i could use it, hopefully you fix these issues.
I wiped everything, installed ROM, but always reboot after logo screen.
firmware 4.16.709.3
twrp 3.4.0.0
Seems very interesting, i tryed before upload and it worked fine by me , but i will now clean flash it and try by my self. I already have the newest build, build and will check these dont forget to thx Claymore to make this possibel
In this rom i have disabled some cores and set some Voltages to enlarge battery and normal performance.
Also i replaced the Camera app to OpenCamera couse this is just a better app for photos and sharpines, also 4k is supported in OpenCamera.
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
tombbb said:
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
Click to expand...
Click to collapse
What youre mean with no luck ?
Was it booting before Gapps ?
@tombbb
platinumthis said:
What youre mean with no luck ?
Click to expand...
Click to collapse
I mean the phone doesn't boot into system, keeping reboot.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
no, I tried only flash Rom, same reboot loop.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
yeah for me too, it did boot one time but after that it never booted again, with gapps or without.
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Click to expand...
Click to collapse
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
tombbb said:
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
Click to expand...
Click to collapse
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
Click to expand...
Click to collapse
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
pinckston said:
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
Click to expand...
Click to collapse
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
tombbb said:
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
Click to expand...
Click to collapse
Did you tried to format /data and then install without gapps ? will this work ?
platinumthis said:
Did you tried to format /data and then install without gapps ? will this work ?
Click to expand...
Click to collapse
I always format data, wipe data,system,cache, install rom, gapp, magisk. But I will try again, maybe flash new build.
What I don't understand is why lineage ROM works?
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
crDroid Recovery (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Format Data
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
Update installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
NOTE: If all the flashing process succeeds the terminal output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error which is also fine.
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/hotdogg-dev
Download:
ROM https://crdroid.net/hotdogg
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_hotdogg.txt
Known issues:
* You tell me
NOTE: Default camera and gallery are from OxygenOS to have all features and cameras working. Video section of the camera will force close the app, you can take videos but doing a long press on camera shutter button.
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Reserved
Thank You for adding this rom. Been a long time since I've ran crDroid. Really looking forward to it.
so i have looked, but what do you mean with having "crDroid REcovery installed on both slots?"
so in fastboot i would set current slot a.. flash recovery, then set slot b.. flash recovery?
been out of the flashing thing since the LG v20 so this has changed a bit.
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Northern Lights said:
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Click to expand...
Click to collapse
Under Display setting if you scroll all the way down you can turn on tap to wake
Superxer said:
Under Display setting if you scroll all the way down you can turn on tap to wake
Click to expand...
Click to collapse
Thank you very much that did it..
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
TitaniumCoder477 said:
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Click to expand...
Click to collapse
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Found my first issues. Cannot install Magisk modules through the Magisk app, and TWRP decryption doesn't seem to work. I'm not sure if the issues are related, but the Magisk issue seems related to the kernel and it's ability to process different file formats. Interesting enough, Substratum module installed automatically fine and Systemless hosts also works fine, but modules from the repo fall with a simple "Installation Failed" message. Tried turning off passcode but that didn't allow TWRP to see any folders inside /sdcard still so couldn't try installing modules in TWRP how I normally would either.
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
thats_the_guy said:
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Click to expand...
Click to collapse
I was looking for a method that didn't involve TWRP since I too came across the same issues you encountered. I actually just finished rooting crDroid a few minutes ago. Here were my steps:
Grab a copy of payload-dumper-go (I used payload-dumper-go_1.2.0_linux_amd64.tar.gz)
Make it executable and install golang if you haven't already
Unzip crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip
Type: ./payload-dumper-go crDroidAndroid-11.0-20210927-hotdogg-v7.10/payload.bin
Copy the boot.img file from new folder to your phone
Also copy Magisk-v23.0.apk to your phone and install it
Open the Magisk app and and tap Magisk > Install
Choose Select and Patch a File (should be the only option you can choose at the moment)
Browse to and choose the boot.img file
Once patched, copy the resulting magisk patched .img file back to your computer
Restart your phone into fastboot mode
Then flash with: fastboot flash boot /path/to/your/magisk_patched.img file
You may also want to flash the other boot; for example, in my case boot_a was flashed, so I then typed: sudo ./fastboot flash boot_b ~/Downloads/magisk_patched-23000_dCYIE.img
Then restart your phone!
These are the steps I performed, gleaned from the Magisk github's install.html#magisk-in-recovery page and also @gwolfu at https://forum.xda-developers.com/t/...droid-v7-10-13-sep-2021.4292267/post-85192599
Northern Lights said:
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
Click to expand...
Click to collapse
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
TitaniumCoder477 said:
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
Click to expand...
Click to collapse
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Northern Lights said:
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Click to expand...
Click to collapse
Well, I've had a few calls both on and off speaker phone with no issues. Very clear.
What are the fastboot commands to flash crDroid recovery to both A/B slots?
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
fastboot flash recovery_a <drag_recovery_img_here>
fastboot flash recovery_b <drag_recovery_img_here>
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
Nevermind, I see you asked about recovery and it's been answered!
So far so good, it's breath of fresh air to wipe away all the TMobile bloat. Is wireguard support and Dolby audio (OnePlus 7 pro build uses) planned features? Thank you for this build
This Dolby Atmos magisk module with audio modification library magisk module fixes the low volume issue.
GitHub - reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
Contribute to reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module development by creating an account on GitHub.
github.com
Does anyone have L1 with this rom?
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Information
This ROM uses source built kernel, kernel modules, and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions
Follow https://wiki.lineageos.org/devices/lynx/install for how to install
Downloads
Official Builds
Optional GApps: MindTheGapps
Reporting Bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/*
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
Face Unlock, because Google doesn't provide an AOSP option.
Contributors
mikeioannina
nicknitewolf
The LineageOS team
Source Code: https://github.com/LineageOS
Great
Great. Thanks. Just got my Pixel 7a today.
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
Does the Play Store icon exist?
The GApps package may just install Play Services and the Play Store, from which you can install all optional Google apps.
Such packages avoid installing these apps as system apps, since you wouldn't be able to uninstall them without root.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
You have to reboot to recovery again for it to install on the correct slot
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
You can install Aurora Store and login there with your Google account.
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
sumdewd01 said:
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Click to expand...
Click to collapse
Wishmasterflo said:
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
Click to expand...
Click to collapse
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
mxz55 said:
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
Click to expand...
Click to collapse
No promises but we are waiting for June ASB
nicknitewolf said:
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Click to expand...
Click to collapse
This fixed it, thanks. I would like to mention that there are sone UI inconsistencies when it comes to the status bar, there's padding on one side and not the other, and when you go into the notification drawer (I think that's what it's called, swiping down from the status bar) the time and the date are not aligned by a little bit vertically. It's a small problem but still somewhat noticeable.
nicknitewolf said:
No promises but we are waiting for June ASB
Click to expand...
Click to collapse
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
mxz55 said:
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
Click to expand...
Click to collapse
Yes and yes. I am already part of the LineageOS team... Current builds are signed with test keys but official builds are signed with separate keys, hence a full wipe is required. You could try the zip attached but I doubt it works (since I don't really wanna test it).
nicknitewolf said:
Reboot into fastboot (With the device powered off, hold Volume Down + Power)
Flash
Click to expand...
Click to collapse
Just wanna say it should be "Reboot into bootloader", as the bootloader type of fastboot is required to flash some of the images: the dtbo, vendor_boot and vendor_kernel_boot partitions can't be read by pure fastboot (what's usually called fastbootD) mode and will throw this sort of error:
Warning: skip copying .. name .. image avb footer (.. name .. partition size: 0, .. name .. image size: .. ).
Sending '.. name ..' (... KB) OKAY [ 0.404s]
Writing '.. name ..' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
So anyone that got confused should just use `adb reboot bootloader` instead of reboot fastboot
I've flashed the ROM and so far it looks & feels really smooth, thanks!
Currently using GrapheneOS. Will flash LOS once they release a user build with release keys.