Database Develop

[Official] crDroid 9.0 TISSOT 05-11-19 Security patch

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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Feature list https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Rom folder + screenshot -> https://drive.google.com/open?id=1GYVVJ2GVC-MCN-dL84x8Z2uPkhcUd3cY
Instructions :
Backup all before flash!!
Check if you have unlocked bootloader and updated firmware if not download and flash it with twrp and reboot recovery before start flash
https://drive.google.com/open?id=1FfYb6hWviggupkQRBNfE-ah85MSl-1aB
First of all you need to flash or boot @Giovix92 TWRP (I recommend)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
or official twrp
Boot into twrp and factory reset
Flash the rom zip
Flash twrp installer (skip if you use twrp survive option)
Reboot recovery
Flash opengapps nano or pico
If you want to root, flash Magisk
Reboot to System.
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES :
You tell me
Some QS theme maybe have color problem but default QS works. Source bug,I can't fix for now
A very special thanks to @Giovix92 and my telegram friends https://t.me/XiaomiMiA1Italia and who tested this rom.
Source
https://github.com/crdroidandroid
https://github.com/LineageOS/android_device_xiaomi_msm8953-common/tree/lineage-16.0
https://github.com/LineageOS/android_device_xiaomi_tissot
https://github.com/LineageOS/android_kernel_xiaomi_msm8953
https://github.com/RevengeOS-Devices/android_vendor_xiaomi_tissot
https://github.com/LineageOS/android_device_xiaomi_msm8953-common/tree/lineage-16.0
https://github.com/LineageOS/android_device_xiaomi_tissot
https://github.com/LineageOS/android_kernel_xiaomi_msm8953
https://github.com/RevengeOS-Devices/android_vendor_xiaomi_tissot
XDA:DevDB Information
[Official] crDroid 9.0 TISSOT, ROM for the Xiaomi Mi A1
Contributors
samuele94, Giovix92, https://t.me/XiaomiMiA1Italia users for support!
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 firwmare (check my profile)
Based On: LOS
Version Information
Status: Stable
Created 2019-10-23
Last Updated 2019-11-28

Goodjob!

Hope 6.0 for 10

Nickinfinity said:
Goodjob!
Click to expand...
Click to collapse
Thanks,I'll keep it updated!
manchirua said:
Hope 6.0 for 10
Click to expand...
Click to collapse
Yes but for now I wait stable public trees for us,for now I keep android 9 updated and I try to build 6.0 soon!
until the situation of android 10 remains "beta" I will stay on android 9 for stability.
android 10 is a great working in progress, right now I don't feel the need to go to 10 but I'll work on it willingly! The development of tissot needs people who keep it alive!

Awesome, unless q stabalises pie will do dont rush for q, btw why not take official maintainership, its abandoned afaik.

Good, thanks bro

Sohil876 said:
Awesome, unless q stabalises pie will do dont rush for q, btw why not take official maintainership, its abandoned afaik.
Click to expand...
Click to collapse
You're right but I'm learning. I only claim to continue building this rom for my only smartphone because I want to keep an updated rom 9.0. For now the tag isn't essential for me but I'll see what I can do!

Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.

samuele94 said:
Thanks,I'll keep it updated!
Yes but for now I wait stable public trees for us,for now I keep android 9 updated and I try to build 6.0 soon!
until the situation of android 10 remains "beta" I will stay on android 9 for stability.
android 10 is a great working in progress, right now I don't feel the need to go to 10 but I'll work on it willingly! The development of tissot needs people who keep it alive!
Click to expand...
Click to collapse
Yeah, thank you
BTW, i can use MindTheGapps?

manchirua said:
Yeah, thank you
BTW, i can use MindTheGapps?
Click to expand...
Click to collapse
Not tested but why not? you can try,rom works fine with opengapps but i think you can change type of gapps. I like opengapps nano (or pico) but MindTheGapps for arm64 and android 9 should work properly

Mendibil said:
Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.
Click to expand...
Click to collapse
Last i tried all gapps build before 6 oct worked fine so download older than 6 oct release, its not los problem.

Great rom, Working flawlessly.
Btw any solution for green slow-motion recording?

Mendibil said:
Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.
Click to expand...
Click to collapse
Yes you can use latest opengapps nano or pico 9.0 arm64 but if you have problem you can download older version here https://sourceforge.net/projects/opengapps/files/arm64/ gapps are nightly, I don't know if it have bugs/problems
Stealtherthreat said:
Great rom, Working flawlessly.
Btw any solution for green slow-motion recording?
Click to expand...
Click to collapse
Try a good GCam and see if it fix, I don't use this feature sorry
Added on my Gdrive folder changelog about this build. I'll update file after new build,when new build? when I can see difference to previous build!

Hi to all! Rom is now official,check here!
https://crdroid.net/tissot Add Telegram group https://t.me/crDroidA1
Tested today opengapps nano 25/10/19 works perfect and encryption works too

Messed up
Not sure what happened but everything is messed up after trying to flash the new ROM.
not able to run twrp properly,
Not able to install gaps
I keep getting a message that some partition is not there and...
Looking for a new handset...

teoasv said:
Not sure what happened but everything is messed up after trying to flash the new ROM.
not able to run twrp properly,
Not able to install gaps
I keep getting a message that some partition is not there and...
Looking for a new handset...
Click to expand...
Click to collapse
Steps? Twrp used? Here works fine,tested by me and other people. Without info I can't help you

samuele94 said:
Steps? Twrp used? Here works fine,tested by me and other people. Without info I can't help you
Click to expand...
Click to collapse
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data

teoasv said:
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data
Click to expand...
Click to collapse
You shouldnt flash img from fastboot only boot that, fastboot boot twrp then flash installer.zip file of twrp from the hotbooted twrp, then do reboot to recovery.

Sohil876 said:
You shouldnt flash img from fastboot only boot that, fastboot boot twrp then flash installer.zip file of twrp from the hotbooted twrp, then do reboot to recovery.
Click to expand...
Click to collapse
Sorry I don't get what you are saying. I did this:
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If your asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp-2.8.x.x-xxx.img
└ Here modify twrp.img with the name of your TWRP recovery .img file.
Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot

teoasv said:
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data
Click to expand...
Click to collapse
Previous version? It's the first version!
Your firmware is up to date? you need to update it and hotboot again twrp,flash installer reboot recovery and follow op step.
No you need to fastboot boot latesttwrp.img boot not flash,for flash you need twrp installer

[Q][BONITO] Descendant X - android ver. 10r32

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct ​
Android OS version: 10.0.0_r32
Security patch level: March​
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11

Cool cool some more love coming in

Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.

crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.

johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning

crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:

johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.

crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.

stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/

What version do I have to download for a 3a xl device ?

Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?

Hasn't been updated in like 2 months if I am reading it right

[ROM][UNOFFICIAL][10.0][CPH1859/CPH1861] Pixel Experience and Plus [AOSP][06/06/2020]

{
"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"
}
Pixel Experience and Plus for Realme 1
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device.
What's working:
1. Boots
2. RIL(Calls,SMS,Data)
3. Wi-Fi
4. Bluetooth
5. Camera
6. Audio
7. Sensors
8. Flash
9. Brightness
10. GPS
11. Gcam (Dont download from Play Store, it wont work)
12. Hotspot
13. USB Tethering
14. DT2W
15. Face Unlock
Known issues:
1. Selinux is permissive.
2. Video codec issues in all Chromium based browser. Check 4th post for fix.
3. VoLTE.
Before Flashing:
1. Take a backup of your data.
2. Clean flash is recommended as of now.
3. Flash the shared TWRP only.
4. Always download latest build.
5. TWRP downloads (alternative one) and flashing instructions can be found in this git link.
6. Always read 2nd and 3rd posts.
Installation Instructions:
1. Clean Flash is recommended, Install TWRP and enter into it.
2. Wipe Dalvik, Cache, System, Data, Internal Storage.
3. Reboot to TWRP.
4. Flash Pixel Experience or Pixel Experience Plus ROM (Gapps are included).
5. Flash Magisk (v20.3 is recommended and is optional).
6. Wipe Cache and Dalvik after flashing.
7. Reboot to system and first boot will take time.
8. Done, you are in Pixel Experience or Pixel Experience Plus ROM and njoy.
Note:
1. In our testing only few versions of Magisk are working. So use the shared one only.
2. Working magisk versions:
Original - 20.1 and 20.3
Phh based - 20.3
3. Dont update magisk (you can update app though).
4. Use the shared TWRP only and dont use others (testings are based on the shared TWRP).
5. ROM is now stable for daily use, enjoy.
Downloads:
Pixel Experience (discontinued)
Pixel Experience Plus​
Pixel Experience: 10
Pixel Experience Plus: 10+
Security Patch Level: August 2020
Build Author: Naveen56
ROM Source Code: https://github.com/PixelExperience
Device Tree: https://github.com/CPH1859/Pixel_Experience_and_Plus
Kernel Source Code: https://github.com/CPH1859/android_kernel_oppo_mt6771
Information
[STABLE][ROM][10.0]Pixel Experience 10 and 10+, ROMs for Realme 1 [CPH1859/61]
Contributors:
1. Invincible-Venom
2. Naveen56
3. Phhusson
4. SamarV-121
5. vishalk17
Credits:
1. mmoreyrav
2. GSI Community
Testers:
1. venombiceps
2. Vijay996
3. MpS005
4. eldraco19
5. ahmadfahim0123
6. Mohit619
Thanks to:
1. Realme and Oppo,
2. Google and Android,
3. Lineage OS, Pixel Experience and other open source ROM developers,
4. XDA Developers.
ROM OS Version: Android 10
ROM Kernel: Linux 4.4.159
ROM Firmware Required: C.49 (Latest Version)
Based On: AOSP
Version Information:
Status: Stable
Release Date: 12-07-2020
Created: 12-07-2020
Last Updated: 16-08-2020

CHANGELOG:
Code:
16/08/2020
1. August Patch
2. Added OnePlus Screen Recorder
3. Added Face Unlock
4. Kernel up-streamed to 4.4.159
5. All changes of PE+ for the month of August.
Code:
13/07/2020
1. Fixed offline charging animation
2. July Patch.
Code:
06/06/2020
1. Initial Release.

Get into this link for some workarounds to the issues you are facing in all Realme 1 ROMs.
Pixel Experience is discontinued and PE+ will be continued. If you are still interested then you can use tress to update it monthly.

Thanks @Naveen56 for the support! Also add some screenshots

Any information regarding JIO VOLTE
I know that Volte might not be possible ever in realme 1. But JIOCALL app is also not working in any of the custom rom. I really want to use this rom , but the only thing stopping me is that my sms/calls will not work. Can you please share any info if you have to make jiocall app work..
---------- Post added at 08:15 AM ---------- Previous post was at 08:10 AM ----------
Somehow i got jiocall app working, and the sim was also registered and status was connected. But i am still not getting any calls/sms. And if i try to call, it says "use your default dialer, your device is already volte"."JioCall App should only be used to make rich calls". This means i can only call to the person who is using jiocall app.

Awesome work!

issues , fedbaack and question
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt

Zainullahk said:
sometimes some apps crash like whatsapp And is there OTA updates? and if there isnt
Click to expand...
Click to collapse
Are you using 15th August build?

MpS005 said:
Are you using 15th August build?
Click to expand...
Click to collapse
yes is there ota?

Zainullahk said:
yes is there ota?
Click to expand...
Click to collapse
15th build is the latest build for Pixel Experience. Did you try clean flashing rom again?
And OTA doesn't work in any rom as of now. Even if you get OTA in any rom (Bliss), then do not install it.

Can I update Google play patch?

zainullahk1 said:
Can I update Google play patch?
Click to expand...
Click to collapse
Yes, you can do Google Play System (Security) updates

Urgent!!!!
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!

Zainullahk said:
i clicked reset in pixel expierince and now i cant boot into my os it keeps booting into twrp i tried re flashing didnt work i tried this https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200 it says conv disabled how do i enable conv!!
Click to expand...
Click to collapse
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.

Just wanted to say how awesome this is.
Hey, I used the rom and it worked as intended and it was an awesome experience. Gotta say, you guys know your stuff. I am in love with the pixel experience plus as the bundle makes it very easy to flash and it works almost flawlessly(except for, of course VoLTE, @MpS005 user - https://forum.xda-developers.com/member.php?u=9393824 told me that the source for cellular network is closed in mediatek chips so it is really hard to activate VoLTE) but I love the ROM anyways and I must commend your hard work. Just want to say keep it up and I'll be waiting for when you guys crack the VoLTE problem. I am so in love with pixel experience that my next phone sure is going to be a pixel.

Naveen56 said:
Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
sir me too got stuck in such kind of situation i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my hear....please share me the links
Click to expand...
Click to collapse

i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links

Naveen56 said:
Get into twrp format data and wipe system, data, cache, dalvik, internal. Flash stock rom. Then you can flash anything (i mean ROM).
Never use reset from settings. It causes infinite loops.
Click to expand...
Click to collapse
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help

vishalv.vv469 said:
i just had flashed pixul ui 3.5 for real me 1 and i clicked on advance reboot and their selected boot into recovery and now when ever i try to turn on my device it keep on booting into recovery mode even if in twrp i select boot into system but it again loop into recovery please help me i love this rom for real me 1 but it just broke my heart...please share me the links
Click to expand...
Click to collapse
I feel sorry for that. You need to flash stock ROM through twrp. Then boot into stock ROM. And from here you can proceed to flash custom ROM. Anyway I don't recommend flashing this ROM now as it has no VoLTE and is outdated. Try other ROM that have VoLTE.

vishalv.vv469 said:
as a devloper you have to add this as a marked,this error as a priority for those who is flashing this rom now m getting twrp looping i even tried toflash other custom rom using recovery but that doesnt help me out seems now i have to flash ozip file please help
Click to expand...
Click to collapse
Yes, you have to flash Ozip and please check the twrp you flashed has this feature of flashing ozip and also leave some 3GB storage in the memory card as ozip has to be decrypted to zip.

[ROM][UNOFFICIAL] LineageOS 18.0 for HTC One M8 / M8 Dual SIM

{
"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 11 (R), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
​
Device tree source code: LineageOS/android_device_htc_m8
Kernel source code: LineageOS/android_kernel_htc_msm8974
Working:
WiFi
Bluetooth
ANT+
Camera (including video recording)
FM Radio
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Broken / not yet supported:
MHL
NFC
Compatibility:
Single SIM variants:​Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr).​Dual SIM variants:​Builds are compatible with all M8 Dual SIM variants (m8dug and m8dwg).​In both cases, all builds are based off the HTC's Android 6.0.1 firmware and kernel with binaries from Android 6.0 GPe.
Downloads:
Single SIM variants:​
lineage-18.0-20201109-UNOFFICIAL-m8.zip
Dual SIM variants:​
lineage-18.0-20201109-UNOFFICIAL-m8d.zip
Installation:
Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
Wipe /system, /data and /cache
Install LineageOS zip package
[*]Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Credits & collaborations
This work is due to efforts from everyone involved in M8 development. The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Single SIM variants:​
Official wiki link
Dual SIM variants:​
Official wiki link

Please note that M8 GPe partition layout is no longer supported. The device must first be converted to Sense firmware, otherwise installation will fail.

Can not find Gapps for m8.
---------- Post added at 10:51 PM ---------- Previous post was at 10:28 PM ----------
BitGapps will this work? Any other option?
https://bitgapps.cf/
https://bitgapps.cf/arm/R/

Initial expression everything working. Nice job
Gapps Link: https://bitgapps.cf/arm/R/

had a few teething troubles, first the clicky bootloop (speaker popping) on the lineage animation, then an "entering recovery" loop (my twrp had disappeared (probably because I was using an out of date one), got back to fastboot and flashed twrp-3.4.0-1-m8.img and all is well until booting lineage, then powering off and entering recovery, at which point it's gone again and it just reboots normally. Reverting to a fresh 17.1 and the recovery remains intact.
works nicely with the Gapps above,
sadly my banking apps don't, Is this because it's signed with public keys?
Out of all the ROMS i've tried, only your variant of 17.1 worked correctly

In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid

fela4 said:
In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid
Click to expand...
Click to collapse
Same here. Furthermore, now I cannot install fastboot drivers and reinstall twrp recovery. Any solution? Can't even install gapps.

adem_7 said:
Same here. Furthermore, now I cannot install fastboot drivers and reinstall TWRP recovery. Any solution? Can't even install gapps.
Click to expand...
Click to collapse
The GApps at https://bitgapps.cf/arm/R work fine
You should be able to boot TWRP using fastboot
download the TWRP image and open a terminal in that directory
I use Linux so this came in handy
Code:
sudo $(which fastboot) boot twrpxxx.img
**replace twrpxxx with your TWRP image file name
Your device should boot TWRP and you can flash your zips

Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.

cexcells said:
Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.
Click to expand...
Click to collapse
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.

Dynamo_anik said:
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.
Click to expand...
Click to collapse
I also had the issue of a bootloop every time immediately after getting to the home screen.

cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
i did clean installation and i didn't face any issue.

Dynamo_anik said:
i did clean installation and i didn't face any issue.
Click to expand...
Click to collapse
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.

cexcells said:
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.
Click to expand...
Click to collapse
Use bitgapps
https://bitgapps.cf/arm/R/
there is no google account setting up at the starting.

Flashing this rom on my M8 worked perfectly fine.
Thanks a lot for your work!

took the plunge
cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
Followed your 3 step install and all great so far.
Skipped setting lock screen during set up as a precaution, is it OK to set one up?
Installing apps from an OTG USB is going great

Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?

text1 said:
Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?
Click to expand...
Click to collapse
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot

ainaz said:
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot
Click to expand...
Click to collapse
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452

Martoost said:
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452
Click to expand...
Click to collapse
Adb driver is not enough for that, you also have to install the HTC mobile driver. If it's still the same try changing the USB cable

[DISCONTINUED][ROM][OFFICIAL][gta4xlwifi][10] LineageOS 17.1 for Galaxy Tab S6 Lite (Wi-Fi)

{
"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 10, 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
Instructions:
Follow the instructions on the wiki https://wiki.lineageos.org/devices/gta4xlwifi
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Warning: 17.1 is now discontinued, use 18.1 instead
Builds: https://download.lineageos.org/gta4xlwifi
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS

reserved

reserved

Congrats @Linux4 , you're "official" Lineage maintainer for GT4XLWIFI now.

any plans the lte edition, it really is sad people dont make anything for this version I don't actually care for the lte I just happened to have bought it second hand. EDIT: nevermind just saw the actual version

Works great for me!
For anyone interested: Netflix and Nanolx microG patcher do not work out-of-the-box.
Edit: Netflix does work after using MagiskHide Props and selecting the Galaxy Tab S5e Fingerprint, clearing the Playstore Cache and activating Magisk Hide for Netflix.

Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?

SvenHee said:
Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?
Click to expand...
Click to collapse
No, I'm sorry, you can't dirty flash official over unofficial, there are two reasons for this:
1. It's signed with other keys (lineage ones)
2. It has FBE enabled like my unofficial 18.1 has, while unoffcial 17.1 had FBE disabled

Ok, thanks for the quick reply. Will clean flash

OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?

bose301s said:
OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?
Click to expand...
Click to collapse
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time

mu1989 said:
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time
Click to expand...
Click to collapse
I tried the slightly smaller step down GAPPS and it worked fine, must be something with that package or something.

Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.

I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?

SvenHee said:
I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?
Click to expand...
Click to collapse
Please just stick to lineage recovery,
I'm almost sure all of these are being caused by TWRP.
Probably the reboot to twrp thing was even caused by TWRP messing with FBE again ... Did it show "Android Rescue Party Trigger" maybe ?

Linux4 said:
Please just stick to lineage recovery,
Click to expand...
Click to collapse
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.

SvenHee said:
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.
Click to expand...
Click to collapse
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too

Linux4 said:
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too
Click to expand...
Click to collapse
I had the same problem with an installation with Heimdall. After that I have installed the version 1230 without problem

dgo65 said:
Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.
Click to expand...
Click to collapse
At the end I found the solution. After the "Preparing for installation" process I had to follow this procedure.
Fix Missing OEM Unlock Toggle on Samsung Galaxy Devices (Guide)
Are you facing the missing OEM unlock issue on your Samsung Galaxy device? That's because your phone has entered the Prenormal RMM/KG state. However, if you'd like to bypass it, then you can follow…
www.thecustomdroid.com
Before to follow with the installation.
Only if anybody as the same problem.

Any ideas how to enable MIDI over USB in this ROM?