Project Treble For Xperia XBased on Sony Open DevicesThanks to Pavel's KernelI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
请中文用户遵守XDA规则,使用双语留言
If Your Camera doesn't work, see #141 please
Required files:
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
[New SODP Kernel version]
V20190812:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190811:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
[Pavel's Kernel versions]
V20190702:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190503:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190501:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
[Old SODP Kernel versions]
V20190429:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v7_loire.zip
V20190210:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_loire.zip
[OEM-File]
DownloadLink
[TWRP-Q]
DownloadLink
How to go Treble?
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Wipe Data and Cache, then flash Treble-X-sjll-XXX.zip in Twrp .
Notice:If you failed when flashing Treble-X-sjll-XXX.zip in Twrp or can't boot into desktop. Please do follwing command:
Code:
fastboot flash boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Optional step If treble file without system
Fourth: Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Google Camera Guide:
1.Gcam must work with Google play services.
2. Suzu doesn't support raw Format Raw10, we should set raw Format to Raw Sensor .
3.We should set Viewfinder Format to YUV_420_888
4.Please enable: Buffer Fix to Fix viewfinder lags.
5. Suzu only support Init SlowMo at 120 FPS
Recommend Gcam Version:
ARNOVA8G2 Link
Gcam_6.1.021_Advanced_V1.7beta3.190707.0105.apk
Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk
Update and known BUG:
20190812:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back, suzu will be cold as ice.
3. F2FS support for cache(Qnovo) and userdata partitions.
20190811:
Update:
1. Go back to SODP kernel.
2. Performance and stability improve.
3. A lot of Fixes of SODP.
20190716:
Update:
1. New twrp-Q uploaded.
V20190702:
Fixes:
1. Cancel OverClock.
2.New CAF imported in kernel.
3.Forcecryptable canceled. If you upgrade from old version, you need to format userdata and use new TWRP-Q.
Bugs:
Need feedback.
V20190503:
Fixes:
1. New PowerHAL.
Bugs:
Need feedback.
V20190501:
Fixes:
1. Use Pavel's kernel source codes.
2. Quick Charge 3.0 works fine.
Bugs:
Need feedback.
V20190210:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-02-10
Last Updated 2019-08-12
Hi! And it is possible to flash system.img via TWRP?
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
no, I tried
Is it A Only or A/B type?
sebasrock156 said:
Is it A Only or A/B type?
Click to expand...
Click to collapse
A only.
[email protected] said:
Hi! And it is possible to flash system.img via TWRP?
Click to expand...
Click to collapse
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
Use the twrp provided by me, it can flash these partition with an img file.
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Thelooks14 said:
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
Click to expand...
Click to collapse
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
You can flash a GSI to get better experience. Thanks for your feedback!
Sjll said:
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
Click to expand...
Click to collapse
Where I can download GSI?
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
can you still enter recovery mode now?
I could only enter recovery with TWRP 3.2.3.2!
So I jused Sjll's recovery vor initial installation and then changed to 3.2.3.2
But I am not sure, if the Treble updates will work with this TWRP...
I used your guide to install another treble ROM
Thanks
One question:
I can root without any problem, but if I reboot the phone the data partition gets encrypted, ¿what can I do to solve this?
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
sessions04 said:
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
Click to expand...
Click to collapse
These are bugs of SODP. only waitting for their fix.
where to get boot.img?I can't flash zip
There is a Link in the first post, next to
"[Tested]
V20190210 Link... "
You find the "twrp-Q.img" there.
Related
Latest TWRP changelog :
New features of 3.2.3-0:
Changelog)
Download Link - 64 bits version (non-treble)
twrp-3.2.3-0-64bits.img
Download Link - Treble version (64bits too)
twrp-3.2.3-0-treble.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.2.3-0 Moto G5, Tool/Utility for the Moto G5
Contributors
ZJRDroid
Source Code: Local manifests
Version Information
Status: Stable
Stable Release Date: 2019-01-18
Created 2019-01-18
Last Updated 2019-01-18
Thanks for the updated TWRP! Works like a charm
Are there any circumstances which would make it necessary to use the non-treble version?
image not signed or corrupted moto g 5 cedric. is this for cedric?
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
update3: after requering the password he pressed back and then formatted the phone, phone booted into the stock rom, and the twrp is gone.
update4: tried install viperos cedric android 9.0.0 gave error 7 I don't know what to do twrp is working, he tried this https://www.youtube.com/watch?v=VCqROwIGLLE and now stock rom is gone. we are loosing hope ;-;
update 5: tried using the twrp provided by this guy https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737/page11 but nothing. still error 7 even doing the procedure above ^^
update 6: Forget everything you read, upthere^^^^ he downloaded the rom for a different phone XD
so anone tested any treble roms from the project forum on our phones with this twrp?
luigge said:
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
Click to expand...
Click to collapse
What did he do exactly to avoid the password screen?
so...does this fix some of the issues present in the previous treble recovery? such as the camera not working? flashlight not working? crashes? can i use it as a daily driver?
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
alright so here's a question: the lineage treble build to flash before the img is down, so where can i find a treble-ised rom to flash before the actual image?
fenerbuuh said:
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
Click to expand...
Click to collapse
how'd you get the MIUI10 sGSI working on your phone? mine keeps rebooting into twrp
Links for both versions are down. Can you re-upload, please?
actuallynxthing said:
Links for both versions are down. Can you re-upload, please?
Click to expand...
Click to collapse
here
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
---------- Post added at 04:58 AM ---------- Previous post was at 04:14 AM ----------
eljoantonyn said:
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
Click to expand...
Click to collapse
Spoke too soon !
Got it working.
Now I need to see why it says "wrong password" while trying to decrypt.
Link fallen
Would you people kindly stop deleting your files from android file host, sick of broken links
Cloudane said:
Would you people kindly stop deleting your files from android file host, sick of broken links
Click to expand...
Click to collapse
I would use the 64bit twrp in the link below
It's not treble but then there's no stable treble roms for this device anyway (which is probably why this twrp is not maintained)
The following 64bit twrp will work with all 64bit custom roms
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
He.Art said:
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
Click to expand...
Click to collapse
If you want an never version use Jarl's TWRP - it works perfectly fine except if you encrypt backups (not the same as backing up encrypted data)
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
So this is not my work some developers had done unofficial build of lineageos 18.1 Android 11 based rom at oneplus nord 2 community I am just tested and sharing it at here.
All credit goes to SakilMondal from nord 2 telegram channel.
Bugs:
1)autobrighness is not working.
2)alert slider is not working.
3)NFC not working.
Prerequisites:
1) Working TWRP
2) You must be on latest OOS A15 or Elixir custom rom.
Steps:
1)If you are on custom rom elixir os download lineageos 18.1 and gapps and place them in pendrive
If you are on oxygenos A15 place both files in internal storage.
2)Now boot your device in to TWRP by using advance reboot if you are on stock oos use adb command
adb reboot recovery.
3)when we booted in to TWRP now connect USB OTG and go to mount and checkmark usb storage,after click to select storage and select usb storage.(skip otg process for oxygen os A15 users)
4)Now click install and select lineageos zip flash then falsh gapps now click reboot and select bootloader.
5)when phone boots to bootloader connect to pc and go to folder where we placed A15 stock boot emmc open command prompt there and type following commands.
fastboot devices
fastboot flash boot boot.emmc.win
For EU user inhave given boot as boot.img so cmd command will be as below
fastboot flash boot boot.img
fastboot -w
fastboot reboot
Phone will boot it May stuck at 1+ logo but don't worry it will boot to lineageos 18.1 within 10min so wait atleast for 10min.
Downloads:
Download LineageOS 18.1:
lineage-18.1-20211228-UNOFFICIAL-denniz.zip
drive.google.com
Gapps:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Download Indian boot img (emmc.win.format):
{Mod edit: Link removed}
fastboot flash boot boot.emmc.win
Download boot img for EU:
{Mod edit: Link removed}
cmd command:
fastboot flash boot boot.img
Cmd command to erase data:
fastboot -w
Google camera stable app:
https://1-dontsharethislink.celsoazevedo.com/file/filesc/MGC_8.1.101_A9_GV1x_MGC.apk
If you are still want some video instructions here is a guide.
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Ok
jerryhou85 said:
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Click to expand...
Click to collapse
I will do
What do you guys prefer? Lineage or Elixir?
Eastw1ng said:
What do you guys prefer? Lineage or Elixir?
Click to expand...
Click to collapse
LineageOS but elixir is love because of android 12
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Fi
vince30 said:
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Fingerprint is working vibrations are also OK for me but after some days when u rebooted it cause that vibration bug
vince30 said:
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Stable and bug-free enough for official would be nice.
Give him some time, i find its already good enough for a daily driver on my Nord 2
Thanks for this great build @pankspoo
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Fixed:
Device vibration bug seems to be fixed.
Auto brightness seems to work.
Update more bugs:
- Fingerprint not working.(perist image intact).
- Ringtone doesn't change after changing in sound settings.
- Slider still broken.
- Changing background startscreen/lockscreen with own photo will crash.
vince30 said:
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Device vibration bug seems to be fixed.
Alert slider still broken.
Click to expand...
Click to collapse
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
pankspoo said:
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
Click to expand...
Click to collapse
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
vince30 said:
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
Click to expand...
Click to collapse
U can use vanilla build if your don'ts want gapps inbuilt. If your not able to here sound then disable A2DP developer setting and Reboot your phone and see
vince30 said:
LOS 18.1 is still preffered no GApps just clean LOS.
Click to expand...
Click to collapse
How do you clean GAPPS from LOS?
exis_tenz said:
How do you clean GAPPS from LOS?
Click to expand...
Click to collapse
18.1 is without GApps included.
To remove them from LOS 19 you can use adb:
adb shell pm uninstall --user 0 package_name
Wifi Is not detecting
Pls Help
I am stucked
Turboisonfire said:
Wifi Is not detecting
Pls Help
I am stucked
Click to expand...
Click to collapse
We already got latest android 13 roms please use them
Android Open Source Project android-11.0.0_r46Disclaimer:* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Instruction:
Unlock boot loader
Connect the device to your computer in Fastboot mode (by pressing volume up while inserting the USB cable)
Download and extract the vendor image provided by Sony
Flash the vendor image provided by Sony
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.img
Download and extract AOSP image android-11.0.0_r46.zip
Flash the boot, recovery, system, vendor and userdata images
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
DONE!
If you have any problem with this recovery image, then download and flash the latest TWRP recovery release.
What's working:
Wifi
Hotspot
Bluetooth
GPS
4G/3G/2G
Camera
Fingerprint sensor (work without press the button)
BUGS:
TWRP recovery goes into bootloop, so start twrp again you need to flash the userdata.img (factory reset) via fastboot. There is this twrp recovery here on xda link.
Screen lag
After each start / restart the screen must be turned off and on again get to the homescreen
Credits:
Sony Xperia Developer World
Source code:
GitHub
Info:
ROM OS Version: Android 11
ROM Release: android-11.0.0_r46
ROM Kernel: Linux 4.14
Based On: AOSP
Status: Testing
Created 2022-02-14
Last Updated 2022-02-17
Reserved
bugs?
nathankaunang said:
bugs?
Click to expand...
Click to collapse
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
D_Riccardo said:
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
Click to expand...
Click to collapse
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
JimKatsanos said:
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
Click to expand...
Click to collapse
The screen lags slightly, the camera work perfect and for now I did not see any signal drops
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
hihiman1 said:
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
Click to expand...
Click to collapse
Thank you, I have also encountered that problem of the screen at startup. The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
D_Riccardo said:
...The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
Click to expand...
Click to collapse
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
hihiman1 said:
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
Click to expand...
Click to collapse
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
D_Riccardo said:
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
Click to expand...
Click to collapse
Yes now it works - please add the link to SW_binaries also in the 1st post
Wouldn't it be said to install the rom on the g8343?
Ramfisrd said:
Wouldn't it be said to install the rom on the g8343?
Click to expand...
Click to collapse
I would not risk to install to g8343, it could work as not
Tested on my Mi Pad 5 Pro 12.4"(dagu) using elish's ROM.
Step to install:
1. Download FastbootEnhance.
2. Download ArrowOS ROM (Xiaomi/elish), and unzip it. There should be a payload.bin inside.
As elish (Mi Pad 5 Pro) and dagu (Mi Pad 5 Pro 12.4") uses the same SoC, it should be fine. But still, unverified if further problems occurs.
3. Either backup the boot and vendor_boot, or download a stock firmware and extract from it.
小米社区
web.vip.miui.com
4. Under fastbootd (fastboot boot fastboot), use FastbootEnhance to flash the payload.bin.
5. Re-enter to fastbootd, use
Code:
fastboot flash boot boot_stock.img
to flash the boot img back to the vendor one.
6. fastboot reboot, and then unplug the cable.
Then, fastboot reboot. And the ArrowOS should boot.
Current issue:
camera not working
NOTE:
not sure if
fastboot --disable-verity --disable-verification flash vbmeta_ab vbmeta.img
is needed
What do you think are the major changes now with the ArrowOS?
CauAguiar said:
What do you think are the major changes now with the ArrowOS?
Click to expand...
Click to collapse
I just found that the UI and overall experience is better than LineageOS.
And also the Pad is on the official support list of ArrowOS.
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
spacezmonkey said:
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
Click to expand...
Click to collapse
Same for me. Tried TrebleApp, using
Code:
am start -n me.phh.treble.app/.TopLevelSettingsActivity
to call at adb shell, but still not working.
does this work for enuma as well?
Does the Xiaomi Pen work on this Rom?
niveZz said:
does this work for enuma as well?
Click to expand...
Click to collapse
I am also very much interested using this on my: Mi Pad 5 Pro 5G "Enuma".
@All If this doens´t work on "Enuma" - can this be adapted?
@kokomicat
Really interested in this. Any news? Also I dont quiete understand, "no system sounds" means no notification sounds etc. or no sound at all like from youtube spotify etc...?
Thx
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
I Tried the steps, No Errors, but after Last fastbook reboot it just Boots to normal MIUI?
Any Tips?
siamese007 said:
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
Click to expand...
Click to collapse
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
spacezmonkey said:
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
Click to expand...
Click to collapse
It means this ROM is modified to suit elish device. So you need to use some apps to modify the system settings manually to fix the audio effects that are not compatible with the stock firmware.
I am using A13 Arrow GSI ROM. Everything works fine after disabling all the audio effect features of the ROM system. Except Xiaomi peripherals are not compatible.
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
spacezmonkey said:
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
Click to expand...
Click to collapse
You may try to flash the new Stock ROM that is compatible with the custom ROM. It seems the firmware you installed has sound conflicts with the installed firmware. Try the stable version of the firmware. The dev versions are still under development.
If the sound issues persist, I think you may wanna try the new custom ROM.