[Official] crDroid 9.0 TISSOT 05-11-19 Security patch - Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De

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

Related

[ROM][OFFICIAL][voyager][10] LineageOS 17.1

{
"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 :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/voyager
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
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:
XDA:DevDB Information
[ROM][OFFICIAL][voyager][10] LineageOS 17.1, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-04-21
Last Updated 2020-04-21
[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
cecja said:
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Ask me again on irc; I don't like guessing on forums.
cecja said:
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
magullo said:
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
Click to expand...
Click to collapse
Same to you, if you join irc I may be able to help.
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
hamirali said:
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
Click to expand...
Click to collapse
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
LuK1337 said:
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
Click to expand...
Click to collapse
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
hamirali said:
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
Click to expand...
Click to collapse
I guess just to be safe, yes.
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Done!
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
hamirali said:
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
Click to expand...
Click to collapse
Wait for newer one.
LuK1337 said:
Wait for newer one.
Click to expand...
Click to collapse
When will a new one come?
EmmJottAah said:
When will a new one come?
Click to expand...
Click to collapse
This year.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Perfect:good:
LuK1337 said:
This year.
Click to expand...
Click to collapse
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
hamirali said:
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
Click to expand...
Click to collapse
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Nooooooooooooo!!!!!!!!!!!!!!!!! .... (waits impatiently)
LuK1337 said:
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
Click to expand...
Click to collapse
Reporting an issue: H4493 Voyager updated to the latest version lineage-17.1-20200529-nightly-voyager.
Cannot seem to make any calls - No service - requests to turn off airplane mode to make calls. However, the airplane mode is infact already off.
Also, strangely enough (for me at least) I can receive calls and sms.
I (maybe stupidly) thought it might be installation error, so I flashed the latest version from recovery - reinstalled everything.
No luck.
Should I not be able to sort it out, I will have to revert back to my previous version. What would you advise?

[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

[ROM][lavender][Android 11] crDroid v7.0 [20.11.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"
}
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:
Click Here (To be Updated)
Flashing Instructions:
Pre-installation:
OrangeFox Recovery(Download from here)
Bitgapps(Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Reboot to recovery
Flash Required Firmware (First-time only)
Wipe System/Vendor/Data/Cache if you are coming from Android 10/9 Roms
Format Data Partition
Flash crdroid zip + Gapps
Reboot and profit!
Update installation:
Boot to recovery
Flash crDroid zip
Flash gapps and reboot to system
Enjoy
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Click Here
Download:
ROM https://crdroid.net/lavender
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/11.0/changelog_lavender.txt
Known issues:
LiveDisplay and Night Light [ Will be Fixed on next update]
Maybe more?
Visit official website @ crDroid.net
crDroid Community Telegram
XDA:DevDB Information
[ROM][lavender][Android 11] crDroid v7.0, ROM for the Xiaomi Redmi Note 7
Contributors
letsmakecakes
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI 11.0.1 Android 10 Firmware
Version Information
Status: Beta
Created 2020-11-19
Last Updated 2020-11-19
Reserved
This is initial Beta Build . There maybe bugs more than mentioned. Please report as you find one .
Reserved
Will there be more Android 10 update?
Is SELINUX Permissive or Enforced?? Do banking apps work without root or not? For example Revolut - can it be installed without Magisk from Google play?
i can't download it
download fails before the end of it
About bugs, I can add a lagging curtain(or statusbar, sorry i dont know how its called on English ). If i turn off blur it become better, but some lags steal here
silmium said:
i can't download it
download fails before the end of it
Click to expand...
Click to collapse
Its a server problem . I tried also with a file downloader, but stoped after 50mb
LE: now download is working perfect
letsmakecakes said:
This is initial Beta Build . There maybe bugs more than mentioned. Please report as you find one .
Click to expand...
Click to collapse
Some animations like scrolling the status bar and opening some applications look a bit laggy.
Besides I'm having several problems with certain google apps (YT and Maps crash, Chrome goes very slow and keeps stucking)
Ok, another bug: if u have password and not the system keyboard, after reboting u cant to enter password cause there is no any keyboard
i finally could download it
but with FIRMWARE Global_V12.0.2.0.QFGEUXM
error 1
i opened the zip file to change updater script and it's working
Flash Required Firmware (First-time only)
Which is the required firmware? Miui 12?
I have right now the Android 9 lineage rom. Can I install this rom from that one of should I install something before?
ruchimes said:
Flash Required Firmware (First-time only)
Which is the required firmware? Miui 12?
I have right now the Android 9 lineage rom. Can I install this rom from that one of should I install something before?
Click to expand...
Click to collapse
if you have a Android 9 rom i guess you have an old firmware too (one for android 9)
so you should flash firmware for android 10 (no fw is labeled android 11 yet)
i guess (i did not try) firmware V11.0.1.0.QFGMIXM should work (just like for crdroid v6.11)
https://xiaomifirmwareupdater.com/firmware/lavender/stable/V11.0.1.0.QFGMIXM/
or you can flash the lastest V12.0.1.0.QFGMIXM like i did but you need to edit the updater file to install the rom
flash also the last recovery !
https://orangefox.download/device/lavender
or
https://dl.twrp.me/lavender/
it's all write down in the first post.....
Flashing Instructions:
Pre-installation:
OrangeFox Recovery(Download from here)
Bitgapps(Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Reboot to recovery
Flash Required Firmware (First-time only)
Wipe System/Vendor/Data/Cache if you are coming from Android 10/9 Roms
Format Data Partition
Flash crdroid zip + Gapps
Reboot and profit!
ROM Firmware Required: MIUI 11.0.1 Android 10 Firmware
silmium said:
if you have a Android 9 rom i guess you have an old firmware too (one for android 9)
so you should flash firmware for android 10 (no fw is labeled android 11 yet)
i guess (i did not try) firmware V11.0.1.0.QFGMIXM should work (just like for crdroid v6.11)
https://xiaomifirmwareupdater.com/firmware/lavender/stable/V11.0.1.0.QFGMIXM/
or you can flash the lastest V12.0.1.0.QFGMIXM like i did but you need to edit the updater file to install the rom
flash also the last recovery !
https://orangefox.download/device/lavender
or
https://dl.twrp.me/lavender/
it's all write down in the first post.....
Flashing Instructions:
Pre-installation:
OrangeFox Recovery(Download from here)
Bitgapps(Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Reboot to recovery
Flash Required Firmware (First-time only)
Wipe System/Vendor/Data/Cache if you are coming from Android 10/9 Roms
Format Data Partition
Flash crdroid zip + Gapps
Reboot and profit!
ROM Firmware Required: MIUI 11.0.1 Android 10 Firmware
Click to expand...
Click to collapse
Thanks men, I didn't read the rom firmware required sentence in the bottom.
So, I can download V12.0.1.0.QFGMIXM, but how do I have to change the updater file? What do I need to put in there?
Also another doubt, the xiaomi.eu latest rom would work and provide the required firmware to later install this crdroid? Or should I better install the chinese one?
One more doubt (maybe not the last): do I have to do all the installs from recovery? Or the firmware is better to do it from the compute with XiaoMiFlash?
Thanks a lot
The required firmware is MIUI 11 not 12
letsmakecakes said:
The required firmware is MIUI 11 not 12
Click to expand...
Click to collapse
Can I install xiaomi.eu rom? Or better with global o china?
ruchimes said:
So, I can download V12.0.1.0.QFGMIXM, but how do I have to change the updater file? What do I need to put in there?
Click to expand...
Click to collapse
stick to v11 as it supposed to be :good:
ruchimes said:
Also another doubt, the xiaomi.eu latest rom would work and provide the required firmware to later install this crdroid? Or should I better install the chinese one?
Click to expand...
Click to collapse
eu global chinese fw are the same (except language i guess) i never saw any difference
go for the global firmware cause...it is "global"
ruchimes said:
One more doubt (maybe not the last): do I have to do all the installs from recovery? Or the firmware is better to do it from the compute with XiaoMiFlash?
Click to expand...
Click to collapse
you should ! easier faster less trouble
you never know what could go wrong when you do it with comp (drivers link or else)
but xiaomiflash should"flash xiaomi"s phone (if not what is the point ??)
you have to wipe everything to make a clean install
i don't know if your flash tool dirty flash or clean everything first
with recovery you format the partition or wipe it all and you know you are good to go for a clean intall
ruchimes said:
Can I install xiaomi.eu rom? Or better with global o china?
Click to expand...
Click to collapse
same thing !
so yes !
letsmakecakes said:
This is initial Beta Build . There maybe bugs more than mentioned. Please report as you find one .
Click to expand...
Click to collapse
Also, Wi-Fi tethering seems not working neither in 2.4 GHz nor in 5 GHz
after install storage can't decrypt in recovery
silmium said:
Flashing Instructions:
Pre-installation:
OrangeFox Recovery(Download from here)
Bitgapps(Download from here)
First time installation:
Backup your data to PC, OTG flash drive
Reboot to recovery
Flash Required Firmware (First-time only)
Wipe System/Vendor/Data/Cache if you are coming from Android 10/9 Roms
Format Data Partition
Flash crdroid zip + Gapps
Reboot and profit!
ROM Firmware Required: MIUI 11.0.1 Android 10 Firmware
Click to expand...
Click to collapse
On Android 10 Orangefox v.11 always decrypted the storage with my pin.
After a full clear installation of Android 11, I am unable to decrypt the DATA storage with my PIN (generated when the system first started).
The system is always unlocked with a pin code. But in recovery mode, decryption failed (with this pin code "Password failed, please try again!")
cos10 said:
after install storage can't decrypt in recovery
Click to expand...
Click to collapse
Did you format the data? Because that usually happens when you haven't formatted the data.
chippey5 said:
Did you format the data? Because that usually happens when you haven't formatted the data.
Click to expand...
Click to collapse
Yes. I wiped Dalvik / ART Cache, Cache, System, Vendor, Data.
After this in "Menu" tab /Manage Partition/Data & red button "Format Data"
Maybe need first "Change FS" ext4 to ext4 & then "Format Data"(i will try in new build)?

[Discontinued][ROM][11.0][Official] crDroid 7.4 TISSOT 07-03-2021

{
"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:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.2 or newer for root - (Download from here)
First time installation:
Download twrpboot.img & twrp.zip in your pc (link above) and extract zip file
Hotboot twrp from your pc with command fastboot boot boot-recovery.img
Wipe system wipe data wipe dalvik cache
Copy downloaded rom fom pc to your phone and start the installation
After installing flash twrp.zip and reboot to recovery again
Install gapps & magisk (optional) and then reboot your phone
Profit! (Enjoy your rom)
Update installation:
You can choose to update via seamless ota or use recovery mode method (here i will cover how to update via recovery mode)
Reboot to recovery from phone
Flash Rom.zip & Twrp.zip and reboot to recovery
Flash Gapps & magisk (optional) & reboot your phone
Profit! (Enjoy your rom)
Sources:
ROM: https://github.com/crdroidandroid
Device tree: DT
Common Device Tree: CDT
Vendor Tree: VDT
Kernel: kernel
Download:
ROM Mi A1 Tissot
Changelog:
Current Rom Changelog
Here
Changes From Previous Crdroid Build
Here
Known issues:
Freezes on Certain Apps
Visit official website @ crDroid.net
crDroid Tissot Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Working:
Camera/Video/Mic
Fingerprint
GPS
IMS (VoLTE)
RIL
Video playback
Wi-Fi
NightLight
CTS
DRM
FM
Encryption
WFD
Broken:
(Nothing Except Random Freezes)
Note: The ROM Does Not Include Gapps Feel Free to flash any gapps of your likings Open Gapps Beta are Recommended
Screenshots
Credits Section
I am not alone to bring it up to you guys alone there are many many and many people who helped me to achive this
and i would like to mention them
First I would like to thanks
@abhinavagrd_1129 even tho me and him started bringing up trees differently he was always there to guide me
& i would like to tell you that his Aosp Beta 3 Rom Inspired me to try to bringup trees
@SagarMakhar he is the one who fixed my noobish mistake i made everytime (also helped me to fix ril in the previous version)
@shivatejapeddi thanks to him VNDK29 issues were solved
@Lostark13 pointing and hinting me out for diffrent smaller things
Vince Device Devs (i picked there fixes thanks alot guys )
@jomadeto thanks alot for giving me a chance to handle this rom for our device i picked many stuff from him to retain original stuffs from him
my mates in tissot maintainer TG group
also my testers @hatethisusername,@NishatAhmed,@sauru660,@bhatia1583 this guys are my pro testers & because of them i have achived this stability in this rom
if i miss anyone from the list do let me know
FAQ's
1)Magisk Latest Beta is working?
a)Yes Full magisk is functional as well as you can use magisk hide without issues
2)Like previous Builds does this rom will update weekly?
a)No unless i find it important to do so i will update it bi-weekly or monthly
3)Chrome is freezing randomly?
a)it is because of DRM is crashing, because you are using root, to use it properly with root use latest magisk beta 21.x & hide magisk from settings & then reboot after it should be fixed
4)Random Freezes?
a)On all Android eleven based roms there are freezes issues abhinav managed to minimised them alot his kernel sources are not public but his Lineage OS Boot Image Works Just Fine In crDroid I am linking link for it use it and it should get fine
Download
instructions to Flash
Go to twrp
select Install Image Option
Navigate to Downloaded Bootimage Directory
flash this Boot Image
Flash (Twrp Installer Zip & Magisk Again)
Reboot
Note: (Install this Image In Either Lineage os Or Crdroid Or Other Lineage Based Roms only)
5)OTA updates are not booting up?
a)Gapps (Nik gapps & others may not able to restore gms after OTA update) i suggest to reinstall gapps from recovery that will solve the issue
6)Having low I/O Speeds?
a)Flash this Module it will disable Fuse But will increase I/O speeds drastically
Download (Flash from magisk) Credits to @jabiyeff21 for creating this module
Note: Encryption users do not flash this it will break encryption & you may not able to boot
More FAQ's will be added later if you have any querys reply to this specific post and i will answer your queries
Peru..?
I love you @murtaza1326
Sent from my Mi A1 using Tapatalk
murtaza1326 said:
Changes From Previous Crdroid Build
New Trees Based On Lineage os 17.1 (More stable then before)
Click to expand...
Click to collapse
Lineage 17.1? Android 11 or back to 10?
sag said:
Lineage 17.1? Android 11 or back to 10?
Click to expand...
Click to collapse
i redid everything from start
i started again from lineage os 17.1 trees (stuff to compile this rom) rom is still android eleven don't worry
Updated everything i could from now onwards kindly see all of my top 3 Owner post
thank you
Hi @murtaza1326 and congratulations for your new work !
I have installed this rom, following your instructions in OP but seems there is some problems.
When I restart in recovery, twrp is gone and there is only lineage recovery.
I know that this behaviour is due to our device that have A/B partition, so, when I flash a rom I do this step:
- go in the twrp (if I don't have that I do fastboot boot twrp....img)
- wipe system, data and cache
- installing rom
- installing twrp
- reboot in recovery
- installing rom
- installing twrp
- install gapps (optional)
- reboot
Ok, this get me a full rom functionally, very well.
Now, I want to root my device, so I boot into recovery and I flash Magisk v21.1 (or v21.00), when I reboot it come to fastboot loader and I can restore all only reload twrp by fastboot boot twrp....img, ecc....
Why I cant' install Magisk ?!
truevision said:
Hi @murtaza1326 and congratulations for your new work !
I have installed this rom, following your instructions in OP but seems there is some problems.
When I restart in recovery, twrp is gone and there is only lineage recovery.
I know that this behaviour is due to our device that have A/B partition, so, when I flash a rom I do this step:
- go in the twrp (if I don't have that I do fastboot boot twrp....img)
- wipe system, data and cache
- installing rom
- installing twrp
- reboot in recovery
- installing rom
- installing twrp
- install gapps (optional)
- reboot
Ok, this get me a full rom functionally, very well.
Now, I want to root my device, so I boot into recovery and I flash Magisk v21.1 (or v21.00), when I reboot it come to fastboot loader and I can restore all only reload twrp by fastboot boot twrp....img, ecc....
Why I cant' install Magisk ?!
Click to expand...
Click to collapse
my steps are correct and because of this behaviour i mentioned multiple times do not install twrp permanently
just use lineage os recovery & when you flash magisk from it
then it will be fine (if it says signature verification failed just select install anyway & it will install it)
again i repeat do not install permanent twrp zip if you want latest magisk to work
murtaza1326 said:
my steps are correct and because of this behaviour i mentioned multiple times do not install twrp permanently
just use lineage os recovery & when you flash magisk from it
then it will be fine (if it says signature verification failed just select install anyway & it will install it)
again i repeat do not install permanent twrp zip if you want latest magisk to work
Click to expand...
Click to collapse
mmm, is a behaviuor of rom based on Android 11 ?
I'm on crDroid 6.10 and many versions before, and twrp works always good, I installed Magisk 21.1 without problems.
twrp give me many usefull stuff, like backup and restore and is difficult to leave it...
And if I use a old version of Magisk, you think resolve it ?
truevision said:
mmm, is a behaviuor of rom based on Android 11 ?
I'm on crDroid 6.10 and many versions before, and twrp works always good, I installed Magisk 21.1 without problems.
twrp give me many usefull stuff, like backup and restore and is difficult to leave it...
And if I use a old version of Magisk, you think resolve it ?
Click to expand...
Click to collapse
yes kind if it is eleven behaviour
truevision said:
mmm, is a behaviuor of rom based on Android 11 ?
I'm on crDroid 6.10 and many versions before, and twrp works always good, I installed Magisk 21.1 without problems.
twrp give me many usefull stuff, like backup and restore and is difficult to leave it...
And if I use a old version of Magisk, you think resolve it ?
Click to expand...
Click to collapse
then magisk r is fine
also you can always hotboot & restore your stuff whenever you want so i don't see any issue there
When flashing through OTA Lineage recovery will be installed ? Because I have TWRP installed, but want to overwrite it on next update and use latest Magisk ,,
Hey, does this have an automatic call recording option for India?
Please let me know.
agm2112 said:
When flashing through OTA Lineage recovery will be installed ? Because I have TWRP installed, but want to overwrite it on next update and use latest Magisk ,,
Click to expand...
Click to collapse
it will if you don't reflash twrp over it again
shaikhatik0786 said:
Hey, does this have an automatic call recording option for India?
Please let me know.
Click to expand...
Click to collapse
no auto call recording but it has call recording feature
New Build is Up Link in OP post
Note:Clean Flash is Mandatory (Must clean flash this update because of new changes you might get issues)
murtaza1326 said:
New Build is Up Link in OP post
Note:Clean Flash is Mandatory (Must clean flash this update because of new changes you might get issues)
Click to expand...
Click to collapse
good job, thank
has bad wifi signal at low levels before the original image.
kloklo50 said:
has bad wifi signal at low levels before the original image.
Click to expand...
Click to collapse
explain it a bit?

[ROM][13.0][OnePlus8T] PixelExperience [AOSP/UNOFFICIAL] - JUNE 24, 2023

YOU MUST HAVE STOCK OOS13 INSTALLED ON BOTH SLOTS TO AVOID TOUCH SCREEN ISSUES. IF YOU ARE ON A11 or A12, THEN UPDATE TO A13. IF YOU ARE ON A13 then you are good to flash this already. Use copy partions if you want to make sure firmware is on both slots.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
YOU MUST BE ON STOCK ANDROID 13 ON BOTH SLOTS FOR IT TO WORK PROPERLY. IF NOT, THEN UPDATE TO A13.
THANKS TO THE ENTIRE PE TEAM FOR HAVING THEIR SOURCE AVAILABLE FOR USE!!!
What's working?
You tell me
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
DOWNLOAD ROM & RECOVERY FILES HERE
Put recovery files in same folder as your fastboot or platform tools folder.
Install instructions also located here.​
Android OS version: 13.0​
Security patch level: June 2023​
Device Source code: https://github.com/PixelExperience-Devices​
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250​
Source code: https://github.com/PixelExperience​
ROM Developers: jhenrique09, Broly
Maintainer: TheSayaMan
XDADevDB Information
PixelExperience A13 ROM for OnePlus 8t Kebeb
REBOOT TO BOOTLOADER
fastboot -w​fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash recovery recovery.img
Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
adb sideload PixelExperience-Plus-kebab-WEEKLY-13.0-20230624-UNOFFICIAL.zip
REBOOT TO SYSTEM TO SETUP. IF YOU WANT ROOT, THEN BOOT BACK TO RECOVERY AND ADB SIDELOAD MAGISK
adb sideload magisk.apk or rename magisk.apk to magisk.zip and adb sideload magisk.zip
IF YOU ARE ALREADY ON PREVIOUS UPDATE, YOU CAN DIRTY FLASH NEW UPDATE. REBOOT TO BOOTLOADER.
IN RECOVERY, SIMPLY ADB SIDELOAD NEW UPDATE.
UPDATES ARE INSTALLED TO INACTIVE SLOT IN CASE OF INSTALL ISSUE, YOU CAN REVERT BACK TO PREVIOUS BOOTABLE SLOT.
Oos12 or oos13 based ?
i try flash on oos13.
diegots said:
Oos12 or oos13 based ?
Click to expand...
Click to collapse
I have tested on 13. No idea if it will work on 12. It definitely will not work on 11.
vallobrescia said:
i try flash on oos13.
Click to expand...
Click to collapse
It will work fine
TheSayaMan said:
It will work fine
Click to expand...
Click to collapse
which recovery did you use? is the twrp from the official site ok?
Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)
SaigoW said:
Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)
Click to expand...
Click to collapse
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.
vallobrescia said:
which recovery did you use? is the twrp from the official site ok?
Click to expand...
Click to collapse
Yes twrp is fine or if your on another custom rom, you can use that one as well. I will post a recovery for this when I can.
TheSayaMan said:
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.
Click to expand...
Click to collapse
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ
logan_007 said:
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ
Click to expand...
Click to collapse
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.
does this one work better or the one on the official site?
TheSayaMan said:
Sì twrp va bene o se sei su un'altra rom personalizzata, puoi usare anche quella. Pubblicherò un recupero per questo quando posso.
Click to expand...
Click to collapse
Good job, I'll run this thread right.
TheSayaMan said:
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.
Click to expand...
Click to collapse
I use Pixel Experience recovery to flash the rom.
I flashed in the official Oxygen OS 13 version,It booted fine and everything works fine.
and then unlocked the OEM, extracted the Pixel Experience 13 recovery and then flash into this Pixel Experience recovery.
Also follow the tutorials to flash the rom
(https://wiki.pixelexperience.org/devices/kebab/install/)
After the first boot devices,the screen touch is not working.
{
"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"
}
Then I followed your instructions and the screen touch did not work either.
-----
I use the same way flash, PE ROM 12 is everything works, and I have used it for half a year.
Also I can't use twrp,I can't use twrp since android 11, even though I flashed in the latest version, it can't decrypt my data correctly and can't identify my data correctly. Maybe it's just a problem with my phone.
So I can't flash the PE rom via twrp either
just now I went to test the latest version of LineageOS android 13, also following the official tutorial to use LineageOS recovery to swipe in, and found the same problem, normal boot up, the result is the same as PE rom is on the new user guide page, the screen touch does not work.
---
I haven't seen too many people report this kind of problem, I think there may be some strange problems with my phone. TAT
vallobrescia said:
does this one work better or the one on the official site?
Click to expand...
Click to collapse
The official hasn't updated the security patch yet.
Thread updated with recovery install instructions.
Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?
M_Power01 said:
Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?
Click to expand...
Click to collapse
It's a known problem. I switched to Nova Launcher and then disabled that.
No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.
Dior DNA said:
No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.
Click to expand...
Click to collapse
Although this is Android 13. It's based on Android 12 so you must have a12 on both slots for it to work properly. Sorry for the confusion. I have updated the instructions, sorry.

Categories

Resources