{
"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, 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 :
https://wiki.lineageos.org/devices/discovery
Downloads :
https://download.lineageos.org/discovery
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
[ protip: 20191010+ 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=4349826312261769960 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. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
banbenggengxin
Hello, I started to use this ROM for my H4233 on October 1st. At present, I mainly use the WeChat camera and there will be problems. Seeing that the download address has been updated to the 20201011 version, can I post a change log on this page after the version is updated? Thanks for the above from Google Translate
你好 我10月1日左右开始给我的H4233 使用该ROM 目前主要是使用微信相机会有问题，看到下载地址已经更新到了20201011版本能否在版本更新后在该页面 发布一个更新日志呢 ，谢谢
Hi, someone did install the rom? Any benefits compare to the 17.1
so i installed it, but it shows me LOS 17.1 and not 18.1.. whats the point??
ok, forget it, it was the problem of the internal recovery of LOS. It shows the sideload, but it has strange effects, or no effect. With TWRP it works. But now i try E os
there are no opengapps available for android 11, what gapps to get (similar to opengapps micro) please?
found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?
maxis123 said:
found nikgapps .
but theres another problem
after wiping everything from recovery, installing gapps - it boots in OS everything is okay, then I install magisk (21.00) from recovery but I cant boot anymore, I get bootloop?
Any ideas please?
Click to expand...
Click to collapse
yeah you need a modded version for 11. Theres a modded magisk floating around the oneplus 7 pro forums somehwere
sorry for double post but heres the magisk link
[ROM][Android 12L][OP7Pro] crDroid v8.12 [19.12.2022]
Does anyone have the magisk download links from the third post? They're not showing up on the new website.
forum.xda-developers.com
should be second post
I upgraded my phone H3223 from Android 9 to this version. Using TWRP. Before update I applied Sony AOSP 11 https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-14-nile/
I used NIKgapp.
NikGapps - Browse /Releases/NikGapps-R at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
I didn't wipe my data , after installing this version and NIKgapp , I rebooted and I have version lineage_discovery-userdebug 11 RQ1A.201205.008 eng.luk.20201212.191949 dev-keys
All existing apps are working after update.
Camera is working , only problem that I have is microphone . Randomly mic is so low or does not work for some applications. I have to reboot to fix this and this problem happens everyday.
Also up and down audio volume keys sometime donot work .
I noticed after upgrade to this Android version I have a program called AudioFX . I turn it off and on but the problem with microphone happens .
Hi!
I installed LOS 18.1 on my sony XA2 ultra H4213, but i have the following problems that i could not solve, even after deleting the cache:
- no sound for media (videos, music, telegram ...) the rest of the sound works well (buzzer, call ...)
- and all videos stuck.
Do somebody has an idea?
Thanks!
I reflashed android pie and the sound / videos work well again, but i can not install LOS now
no possibility to get to recovery mode and no fastboot drivers for the H4213. I even forgot how could I install it in the past... maby the recovery mode was working.
HowTo upgrade from 17.1 (make sure your computer has working "adb" (setup instructions can be found here):
1. Download the latest Lineage build and Lineage recovery from here. Optional, if you need Google apps, it can be obtained from here.
2. Run "adb reboot sideload"
3. Run "adb sideload /path/to/zip" (inserting the path to your LineageOS package).
4. If you need Google apps: Advanced -> Reboot to Recovery -> [when the device reboots] -> Apply Update -> Apply from ADB, then sideload gapps "adb sideload /path/to/zip". Reboot.
5. Start your device with new installed LineageOS, set the minimal startup settings. Open developer options (to unlock it: "Settings" -> "About phone" -> tap 7 times on "Build number") and enable ADB interface ("Settings" -> "System" -> "Developer options" -> "Android debugging").
6. Download Magisk from here, and install it "adb install Magisk.apk" (replace Magisk.apk with the appropriate filename).
7. Copy Lineage recovery file to your device (for example, to the Download folder).
8. Open Magisk app on the device and tap "Install" button in the Magisk card. Choose “Select and Patch a File” in method, and select the Lineage recovery file you copied previous step.
9. The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img
10. Copy the patched image to your PC with ADB "adb pull /sdcard/Download/magisk_patched_[random_strings].img"
11. Power off device. With the device powered off, hold "Volume Up" and connect the USB cable - the notification light should turn blue (you are in the 'fastboot mode').
12. Flash patched image "fastboot flash boot /path/to/magisk_patched.img". Reboot.
13. Open Magisk app and enable 'MagiskHide'.
14. ...
15. You have root and Google's SafetyNet passes.
What is your--
LineageOS version: lineage-18.1-20210401-nightly-discovery-
LineageOS Download url:https://download.lineageos.org/discovery/changes/#!
Gapps version: NikGapps-basic-arm64-11-20210404-signed
Did you--
wipe: fresh install
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer:no
a non-stock kernel: no
other modifications: no
Navigation with gesture is bugged, has dead touch on the edges of the screen
An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.
Just upgraded from 17.1. Looks fine, everything working to this moment. Good job man, thanks for the hard work!
LuK1337, update the #2It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...
Vlackrs said:
An other bug, my phone need to reboot to charge it, cuz otherwise it won't. In battery menu say can't be charged right now.
Click to expand...
Click to collapse
Hm. Exact same problem here :/
Dear developer
Does GPS navigation and positioning do not work?
Is there a way to improve it?
AndreyAleks said:
LuK1337, update the #2It's mandatory to remove simlock.ta file. Earlier, Newflasher did ignore (didn't flash) that file automatically. As for now - it doesn't. I just flashed my phone by your guide and now I have phone, which doesn't see simcards
I can't even imagine what to do now ...
Click to expand...
Click to collapse
False alarm. The simlock.ta is ignored just as earlier (details here). I've flashed whole stock firmware and simcards are working.
Related
{
"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 8.1 (Oreo), 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.
What's not working :
IMS
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/discovery
Root addon : https://download.lineageos.org/extras
Google Apps : 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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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][discovery][8.1] LineageOS 15.1, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-11-06
Last Updated 2019-05-10
How to flash latest firmware
[ protip: Currently Lineage builds depend on latest 8.0 firmware (50.1.A.13.123), they will not boot up on 50.2.A.0.* or newer ]
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:
- kernel_X-FLASH-ALL-18AE_0x00.hash
- kernel_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. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
Do we download arm or arm64 for su and gapps?
Aklenz07 said:
Do we download arm or arm64 for su and gapps?
Click to expand...
Click to collapse
arm64.
this device will be upgrad to pie?.
By the way tnx for hard work.
Echo MsK said:
this device will be upgrad to pie?.
By the way tnx for hard work.
Click to expand...
Click to collapse
I could release 16.0 builds too but I'm being lazy for time being.
LuK1337 said:
I could release 16.0 builds too but I'm being lazy for time being.
Click to expand...
Click to collapse
plz take your time enjoy your life and then spend sometimes here your valuable time.
We can wait for awesome dev.:highfive:
I installed the ROM and had everything work but it won't read my SD card. If I go into recovery I can view my SD card and files but when I am on the phone it can't read it
HaxUrMom69 said:
I installed the ROM and had everything work but it won't read my SD card. If I go into recovery I can view my SD card and files but when I am on the phone it can't read it
Click to expand...
Click to collapse
Pull a kernel log (adb shell dmesg after adb root).
[ actually I think i know what it's caused by, add me on hangouts/discord whenever it's not 4am in my timezone ]
If someone wants to be helpful, let me know if flashing this kernel https://kremowka.xyz/files/b767d5e5d4817b0530914d929f7611d315afd233.img ( fastboot flash boot b767d5e5d4817b0530914d929f7611d315afd233.img ; fastboot reboot ) fixes external sdcard ^.^
Once I get a confirmation that it actually fixes the issue I'll merge changes in repos and next official build will have working ext SD.
[ someone else already confirmed it works thus I merged required change ]
LuK1337 said:
If someone wants to be helpful, let me know if flashing this kernel https://kremowka.xyz/files/b767d5e5d4817b0530914d929f7611d315afd233.img ( fastboot flash boot b767d5e5d4817b0530914d929f7611d315afd233.img ; fastboot reboot ) fixes external sdcard ^.^
Once I get a confirmation that it actually fixes the issue I'll merge changes in repos and next official build will have working ext SD.
[ someone else already confirmed it works thus I merged required change ]
Click to expand...
Click to collapse
Can it be flashed from internal storage or do I need a working SD card to flash i
Edit: sorry Im retarded I flashed it and now it reads my SD card. Thank you for this fix . I was still trying to figure out how to pull a log for you
HaxUrMom69 said:
Can it be flashed from internal storage or do I need a working SD card to flash i
Edit: sorry Im retarded I flashed it and now it reads my SD card. Thank you for this fix . I was still trying to figure out how to pull a log for you
Click to expand...
Click to collapse
I don't need a log anymore. I literally just fixed it.
LuK1337 said:
I don't need a log anymore. I literally just fixed it.
Click to expand...
Click to collapse
I know... I was trying to say you were fast. You got a fix before I could give a log
Windows 8 mobile? LOL I'll wait for the external storage fix, possibly linage 16 release. Hopefully we can format as internal since the stock Sony ROM can't.
Ricktor said:
Windows 8 mobile? LOL I'll wait for the external storage fix, possibly linage 16 release. Hopefully we can format as internal since the stock Sony ROM can't.
Click to expand...
Click to collapse
You can flash the boot image located a few posts before for the external storage fix, I'm sure it will come officially in the next build.
Now that today's build is out I disabled downloading of kernel image from page #1 so that less smart people won't think they need to flash it on newer builds.
Any news about the dual sim support?
Kirrr said:
Any news about the dual sim support?
Click to expand...
Click to collapse
I don't have a dual sim device therefore I can't fix it myself. Feel free to fix it and submit patches onto our gerrit~!
LuK1337 said:
I don't have a dual sim device therefore I can't fix it myself. Feel free to fix it and submit patches onto our gerrit~!
Click to expand...
Click to collapse
I'm not a developer so I can not do that. Can this brick my H4213 if I try to flash it?
Kirrr said:
I'm not a developer so I can not do that. Can this brick my H4213 if I try to flash it?
Click to expand...
Click to collapse
No, but dual sim feature won't work properly. You can keep using it as a single sim device tho.
{
"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 9 (Pie), 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 : https://download.lineageos.org/discovery
Root addon : https://download.lineageos.org/extras
Google Apps : 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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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][discovery][9] LineageOS 16.0, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-03-01
Last Updated 2020-02-28
How to flash latest firmware
[ protip: 20191010+ 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=4349826312261769960 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. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
Flashed this morning and it works beautifully. Fast, sweet pie. Thanks @LuK1337!
newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.
WangYcca said:
newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.
Click to expand...
Click to collapse
Yes.
great work thanks you i have flash the rom 1/3/19 and test now all items so is fast and stable whith root magisk work su work my only problems is 2 now i dont know how to install in phone twrp and second big problem is how to hide in start phone the black boot logo of sony unlocking bootloader screen ,( if iknow any body please tell me how to fix this thanks a lot ) . thanks again for great work guys save my phone respect.
sorry for my bad english
install os in my xperia xa2 ultra 4213
the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.
WangYcca said:
the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.
Click to expand...
Click to collapse
Who'd have thought that something meant to be used with 15.1 won't work with 16.0.
I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong
GhostCow said:
I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong
Click to expand...
Click to collapse
Join my irc channel?
(see my signature)
Anyone else getting bad screen freeze? Like the touches dont read right?
Scruffdog1978 said:
Anyone else getting bad screen freeze? Like the touches dont read right?
Click to expand...
Click to collapse
In my case, while an app is launching, the screen will freeze about a second. Once it is launched, it runs smoothly.
Many thanks for your outstanding contribution. I have flashed build 02.03.2019, gapps nano, rooted with magisk 18.1 and it is working pretty much good exept few things. Every time after instaling any magisk module phone is going to bootloop right after restarting, volume up and power 2,3 times fix the restart. Fingerprint reader stop working and it's menu disapper sometimes from settings/securitym,restart helps. Button recent sometimes does not show recent apps, restart helps. Chrome FC after attemt to instal any apk downloaded. No downloaded galery app is allowed to delete any picture from storage. Radio FM is working really well, much better than stock one.
Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?
jnappert said:
Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?
Click to expand...
Click to collapse
You probably have mismatched firmware between A and B if that's a thing. Follow #2.
LuK1337 said:
You probably have mismatched firmware between A and B if that's a thing. Follow #2.
Click to expand...
Click to collapse
But is there a way to flash the update in twrp or the lineage recovery?
Aklenz07 said:
But is there a way to flash the update in twrp or the lineage recovery?
Click to expand...
Click to collapse
What update?
LuK1337 said:
What update?
Click to expand...
Click to collapse
The ROM update?
Aklenz07 said:
The ROM update?
Click to expand...
Click to collapse
Why would you do that?
LuK1337 said:
Why would you do that?
Click to expand...
Click to collapse
Because I get a bootloop if I do the normal way and I don't have time to do #2 to get it 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"
}
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 : https://download.lineageos.org/discovery
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][discovery][10] LineageOS 17.1, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-10-23
Last Updated 2020-04-01
[ protip: 20191010+ 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=4349826312261769960 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. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
Where do I get gapps for 10? Opengapps only says something about a patched rom because blah blah webview whenever I click on "10" but doesn't actually let me download anything
Answer: https://forum.xda-developers.com/android/software/arm64-bitgapps-q-10-0-0-t3968500
Sourceforge under "beta" folder
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
Here's the link
https://sourceforge.net/projects/opengapps/files/arm64/
---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------
Another thing I would like to mention is the "nano" packets was give me issues it would freeze when I tried typing the pin to the fingerprint part of the setup. I am running Pico now and I have had no issues?
OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!
Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)
appleknight said:
OK so far the only issue I've seen is not being able to set the dark mode to black, it just reverts back to normal dark mode, other than that no issues here! Great work man!
Update: If I try connecting to a public WiFi that requires a login, when I click "sign in to network" that function just crashes, however regular WiFi at home works great.
Also, expanded desktop crashes the settings app when you try going into it
I'll be able to send you a logcat when I get home(about 8hrs from now)
Click to expand...
Click to collapse
Don't bother sending a logcat for expanded desktop.
Great Job @LuK1337! As always, well done!
So, basically we can instal this straigth over the 50.2.A.0.400 build ?
kamyk70 said:
So, basically we can instal this straigth over the 50.2.A.0.400 build ?
Click to expand...
Click to collapse
If you have any 50.2.* on both slots then sure.
LuK1337 said:
If you have any 50.2.* on both slots then sure.
Click to expand...
Click to collapse
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?
kamyk70 said:
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?
Click to expand...
Click to collapse
It depends how you flashed it. You can do `strings /dev/block/bootdevice/by-name/modem_* | grep Daily` in TWRP. If you see both dates starting with 2019 then you probably have some kind of 50.2 on both slots.
Any word on what is supported/not working in this build? Is it safe to say this is fairly Beta and we can expect a decent amount of glitches along the way?
kamyk70 said:
Sorry for bothering, I'm just not really sure.
If I flashed recent Sony full stock 50.2 firmware with Newflasher, does it mean I am on both slots with it?
Click to expand...
Click to collapse
Yes
I'm sure I either did something wrong or I misread but I currently have no fingerprint.
Also things I noticed which are not concerns
Exposed is wonky
Pin will crash ui and then give u blank unknown pin
Not important but substratum cause lag
Only things I've notice
lonewolfbtown said:
I'm sure I either did something wrong or I misread but I currently have no fingerprint.
Also things I noticed which are not concerns
Exposed is wonky
Pin will crash ui and then give u blank unknown pin
Not important but substratum cause lag
Only things I've notice
Click to expand...
Click to collapse
Consider reading #2 post.
LuK1337 said:
Consider reading #2 post.
Click to expand...
Click to collapse
Yup I'm an idiot. I misread that post. Thanks man
Siemano.
My question is: what kind of gapps is recommended for this build?
Since it says its android 10 I thought it should be this one:
opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?
razider said:
Siemano.
My question is: what kind of gapps is recommended for this build?
Since it says its android 10 I thought it should be this one:
opengapps/files/arm64/beta/
But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28). Which one should I pick?
Click to expand...
Click to collapse
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.
And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.
(I tried to reboot TWRP after flashing rom)
LuK1337 said:
>But TWRP says I should go with valid GAPPS for 16.1.0 (SDK28).
re-boot twrp.
Click to expand...
Click to collapse
razider said:
And the gapps should be arm64. Is that true?
When I tried to to install gapps for LOS 16.1 it said I should go with "arm", I'm assuming instead of arm64.
(I tried to reboot TWRP after flashing rom)
Click to expand...
Click to collapse
Something tells me that you didn't do it.
Install lineage, boot twrp again, install gapps.
Also yes, use ARM64.
{
"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, 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 here
Downloads:
Builds: d1, d2s, d2x
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
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
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
KiwiNote+ said:
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
Click to expand...
Click to collapse
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
PortentousLad said:
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
Click to expand...
Click to collapse
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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...
forum.xda-developers.com
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Linux4 said:
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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...
forum.xda-developers.com
Click to expand...
Click to collapse
...Well that explains it I guess.
Linux4 said:
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Click to expand...
Click to collapse
yeah... the wrong one.
Linux4 said:
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Click to expand...
Click to collapse
that was me being more stupid and no I did not try to boot before.
Linux4 said:
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Click to expand...
Click to collapse
that does nothing. I'll keep trying a bit before I move one.
Thanks for your quick response anyway.
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
stenncell said:
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
Click to expand...
Click to collapse
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Linux4 said:
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Click to expand...
Click to collapse
i joined the telegram group... i will try to install again.
Linux4 said:
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Click to expand...
Click to collapse
Thanks for providing the ROM! Does it support signature spoofing?
tempe222 said:
Thanks for providing the ROM! Does it support signature spoofing?
Click to expand...
Click to collapse
I don't include out-of-tree patches, sorry
However in my S10 Series thread there's another solution for this one
Anyways, read the OP, download links are taken down temporarily as some users apparently had problems with getting it to boot
Will be up again next week hopefully (will get a device myself by that time)
Fixed builds are now up
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Donkey666 said:
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Click to expand...
Click to collapse
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Linux4 said:
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Click to expand...
Click to collapse
@Linux4
I managed to install your version, its more stable than ivans version so thank you man great job, on ivans version had microphone issues and telephoto2x did not work, this one feels very good and probably usable as a daily driver phone..
I have a question for you, is there a way to add option in settings that blocks notification&quick-access-tiles from being accessed from locked screen?
And S-pen question: is there a way to make keyboard appear when I tap whit S-pen on txt field (it puts cursor there but keyboard does not apper until I tap there with finger.)
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Donkey666 said:
View attachment 5367685
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Click to expand...
Click to collapse
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Linux4 said:
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Click to expand...
Click to collapse
Yea you are right, I did pay closer attention to S-pen behavior and you are right, it is basicaly a mouse.. And issue solved, had magnetic case and that messed up S-pen behavior..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
crDroid Recovery (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Format Data
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
Update installation:
You must have crDroid recovery installed in both slots
Boot crDroid recovery
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_crdroid_zip_here>
Install gapps (Optional)
Reboot recovery again (from advanced menu)
Plug your phone to pc and Apply update via ADB
Run adb sideload <drag_gapps_zip_here>
Reboot
NOTE: If all the flashing process succeeds the terminal output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error which is also fine.
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/hotdogg-dev
Download:
ROM https://crdroid.net/hotdogg
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/11.0/changelog_hotdogg.txt
Known issues:
* You tell me
NOTE: Default camera and gallery are from OxygenOS to have all features and cameras working. Video section of the camera will force close the app, you can take videos but doing a long press on camera shutter button.
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Reserved
Thank You for adding this rom. Been a long time since I've ran crDroid. Really looking forward to it.
so i have looked, but what do you mean with having "crDroid REcovery installed on both slots?"
so in fastboot i would set current slot a.. flash recovery, then set slot b.. flash recovery?
been out of the flashing thing since the LG v20 so this has changed a bit.
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Northern Lights said:
Good day all. I just flashed my onplus 7t McLaren to crDroid Rom. And I love it. Just a quick question. When the screen is off I have to press the power button for it to wake up. How can I do it so I tapped on the screen instead for it to come up? Thank you
Click to expand...
Click to collapse
Under Display setting if you scroll all the way down you can turn on tap to wake
Superxer said:
Under Display setting if you scroll all the way down you can turn on tap to wake
Click to expand...
Click to collapse
Thank you very much that did it..
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
TitaniumCoder477 said:
So far, super impressed with this ROM and the overall experience! I like the little "ditties" under the Welcome to crDroid at the top!
So question, the Preinstallation section says, "Magisk 20.0 or newer for root (after first boot) - (Download from here)". I have installed the Magisk APK from the Github repo, and it confirms "Ramdisk Yes" which, from what I am reading on Magisk's install page, means I need to patch the boot.img file. Magisk says, "You should be able to extract the file you need from the official firmware packages or your custom ROM zip (if using one)." I think that means I need to somehow extract this .img file from crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip. However, when I look into that zip, I'm not seeing it. Forgive me if I am just misinformed or overlooking something!
Click to expand...
Click to collapse
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Found my first issues. Cannot install Magisk modules through the Magisk app, and TWRP decryption doesn't seem to work. I'm not sure if the issues are related, but the Magisk issue seems related to the kernel and it's ability to process different file formats. Interesting enough, Substratum module installed automatically fine and Systemless hosts also works fine, but modules from the repo fall with a simple "Installation Failed" message. Tried turning off passcode but that didn't allow TWRP to see any folders inside /sdcard still so couldn't try installing modules in TWRP how I normally would either.
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
thats_the_guy said:
Super happy to see some development on hotdogg again, and one of my favorite ROMs no less. I just hope to get regular updates unlike everything else (besides Carbon 8.0, not even 9.0), but am super happy to find everything working, unlike some of the one off ROM builds on here. So far, no problem (other than not realizing Gapps weren't included and Magisk causing softbricks if installed before setup). Everything tested so far is working and has the battery life I expect from crDroid.
So the easiest way to install magisk and (I did it on this ROM) is to rename magisk.apk to magisk.zip and install that through TWRP. On this ROM, you MUST do it after setup or risk a potential soft-brick.
Click to expand...
Click to collapse
I was looking for a method that didn't involve TWRP since I too came across the same issues you encountered. I actually just finished rooting crDroid a few minutes ago. Here were my steps:
Grab a copy of payload-dumper-go (I used payload-dumper-go_1.2.0_linux_amd64.tar.gz)
Make it executable and install golang if you haven't already
Unzip crDroidAndroid-11.0-20210927-hotdogg-v7.10.zip
Type: ./payload-dumper-go crDroidAndroid-11.0-20210927-hotdogg-v7.10/payload.bin
Copy the boot.img file from new folder to your phone
Also copy Magisk-v23.0.apk to your phone and install it
Open the Magisk app and and tap Magisk > Install
Choose Select and Patch a File (should be the only option you can choose at the moment)
Browse to and choose the boot.img file
Once patched, copy the resulting magisk patched .img file back to your computer
Restart your phone into fastboot mode
Then flash with: fastboot flash boot /path/to/your/magisk_patched.img file
You may also want to flash the other boot; for example, in my case boot_a was flashed, so I then typed: sudo ./fastboot flash boot_b ~/Downloads/magisk_patched-23000_dCYIE.img
Then restart your phone!
These are the steps I performed, gleaned from the Magisk github's install.html#magisk-in-recovery page and also @gwolfu at https://forum.xda-developers.com/t/...droid-v7-10-13-sep-2021.4292267/post-85192599
Northern Lights said:
I have been using with this rom and i wanted to see if anyone had this issue, lets say you are on a call and I have the speaker on, I hear crackling noises. ?? cant figure out
Click to expand...
Click to collapse
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
TitaniumCoder477 said:
I have not experienced any issues so far. Are you talking about speaker phone when you're on a call? If so, I will try that on my next call and let you know.
Click to expand...
Click to collapse
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Northern Lights said:
Hi Titanium, yes when Im on a speaker phone. This doesnt happen always but often. Thanks
Click to expand...
Click to collapse
Well, I've had a few calls both on and off speaker phone with no issues. Very clear.
What are the fastboot commands to flash crDroid recovery to both A/B slots?
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
fastboot flash recovery_a <drag_recovery_img_here>
fastboot flash recovery_b <drag_recovery_img_here>
gnabtib8 said:
What are the fastboot commands to flash crDroid recovery to both A/B slots?
Click to expand...
Click to collapse
Nevermind, I see you asked about recovery and it's been answered!
So far so good, it's breath of fresh air to wipe away all the TMobile bloat. Is wireguard support and Dolby audio (OnePlus 7 pro build uses) planned features? Thank you for this build
This Dolby Atmos magisk module with audio modification library magisk module fixes the low volume issue.
GitHub - reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module
Contribute to reiryuki/Dolby-Atmos-OnePlus-8-Visible-Magisk-Module development by creating an account on GitHub.
github.com
Does anyone have L1 with this rom?