crDroid Android is a free firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
crDroid is based on the LineageOS & Android Open Source Project with extra contributions from many people within the Android community.
All the source code for crDroid is available in the crDroid GitHub repo
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware (tested over 61.2.A.0.410)
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-BQ52 (Global version)
Current build has no Gapps built-in so it's up to you either to stay Gapps-less or flash Gapps version you want (I would recommend NikGapps personally)
Make sure you have gone through the installation guide once before proceed!
Installation:
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
Bash:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
Bash:
fastboot --set-active=a
fastboot flash dtbo_a <dtbo>.img
fastboot flash vendor_boot_a <vendor_boot>.img
fastboot flash boot_a <boot>.img
Now reboot into recovery to verify the installation:
Bash:
fastboot reboot recovery
Installing ROM from recovery
Download the crDroid installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the crDroid package
On the device, select "Apply Update", then "Apply from ADB" to begin sideload
On the PC, sideload the package using:
Bash:
adb sideload filename.zip
Return to the main menu
(Optionally) If you want to install any add-ons (Gapps, Magisk..), click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from ADB", then "adb sideload filename.zip" those packages in sequence.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://sourceforge.net/projects/xperia5iii/files/crdroid13/
Device Trees & Kernel Source:
https://github.com/faust93/android_device_sony_sm8350-common
https://github.com/faust93/android_device_sony_pdx214
https://github.com/xperiaossdev/kernel_sony_sagami
Build Information
Device: Xperia 5 III (pdx214)
Build Type: Unofficial
ROM OS Version: 13
Kernel Version: 5.4.219-Krispy-v1.2
Kudos:
@Sakuu
@clfbbn
Changelog
2023-04-27:
- crDroid v9.4
- kernel side tuning and optimisations
2023-04-15:
- crDroid sources repo sync
- performance optimizations
- HW assistant button gestures fix: single, long, double click works and can be re-assigned
Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?
Gray47Maxx said:
Geez, our first custom ROM! Thank you very much for your efforts :^)
Any list of what's working and not working?
Click to expand...
Click to collapse
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..
faust93 said:
My daily driver for about a week now. Haven't found any problems so far. Seems everything to be working. But for sure we need more testing..
Click to expand...
Click to collapse
Neat! Based on stock, I guess?
Gray47Maxx said:
Neat! Based on stock, I guess?
Click to expand...
Click to collapse
Well, it's not GSI if that's what you meant. Closed source proprietary blobs are taken from stock ROM, otherwise just fully-fledged build from crDroid sources.
faust93 said:
Well, it's not GSI if that's what you meant.
Click to expand...
Click to collapse
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting
Gray47Maxx said:
Not exactly. There's an initiative called SODP which provides all the necessities and binaries to build anything you want. Alas, usually it's not stable enough, especially on newer devices with hard configurations (like with our periscope camera).
Anyway, gonna test crDroid today and report anything I'd find interesting or worth noting
Click to expand...
Click to collapse
Aah, I see. It's my first SONY device so I'm not aware about all the nuances yet No, it's not SODP based build.
thanks very nice rom
Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.
Just installed this. Feels like I've been waiting ages for a custom ROM, and now here it is!
So far it seems too good to be true, not a single issue yet.
Sakuu said:
Good work, btw might want to do a rebuild with the newest Krispy version, major speedups on the 1 III that's running Krispy-v1.2.1 plus some battery life improvement, maybe I'll do 5 III builds too, if I get any testers that is.
Click to expand...
Click to collapse
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60
bhow11 said:
Will test later today. Curious to see if refresh rate can be locked @ 120hz. The GSI builds I tried on A11 and A12 were stuck at 60
Click to expand...
Click to collapse
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though
Sakuu said:
Of course you can lock that dunno if he added the stuff for the refresh rate qs tile though
Click to expand...
Click to collapse
Just a prop edit?
bhow11 said:
Just a prop edit?
Click to expand...
Click to collapse
Not even that, i think you can turn it on from the settings, but qs tile is more convenient
All good thus far
Will google wallet work with this ROM?
dima_vy said:
Will google wallet work with this ROM?
Click to expand...
Click to collapse
For me it works. Magisk Delta does the trick.
After using it for a few days, it is very stable and smooth, the battery performance is also great, thank you for your efforts
Cannot get Photo Pro and other sony app running after install sony framework in Magisk delta. Any one else has the same issue?
Related
Hello !
Currently i'm working in Le 2 kernel and device tree. My purpose is to make meaningful changes and additions so other ROMs can implement them.
Confirmed working with LOS, Carbon, LegendROM (latest releases)
This thread is all about the kernel. Currently the kernel features
sdcardfs support
cpu-input boost
power efficient work-queues
improvements to touchscreen driver, preparing support for dt2w
adj tree
low memory killer improvements
powersuspend driver
nvidia patches for energy efficiency
memory bus improvements
Adreno memory pools
and other small improvements in battery management and scheduler
Download: https://drive.google.com/open?id=0B4AOvCehd4v3OXBEX3dMSkdxQ3c
Source: https://github.com/mthomos/android_kernel_leeco_msm8976
To enable sdcardfs support just add this line in build.prop
Code:
ro.sys.sdcardfs=true
To be clear from the beginning: I will not answer to any feature requests and i respond to bug reports without logs. I hope to understand this
Cheers !
XDA:DevDB Information
Diades Kernel, Kernel for the LeEco Le 2
Contributors
marios199546
Kernel Special Features:
Version Information
Status: Testing
Created 2017-09-05
Last Updated 2017-09-07
What's the decryption key?
Good luck :good::good:
For which ROM?
Nice one.
Gonna try and report!
Its asking for decryption key!
OP updated with new link
Work on rom based in eui or only aosp rom ?
Sent from my Le X522 using XDA-Developers Legacy app
fmehdi said:
Work on rom based in eui or only aosp rom ?
Click to expand...
Click to collapse
Doesnt work on eui base
Only custom roms
What does sdcardfs mean?
bonsai.14 said:
What does sdcardfs mean?
Click to expand...
Click to collapse
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
billybobjoe512 said:
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
Click to expand...
Click to collapse
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Njishi said:
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Click to expand...
Click to collapse
So where would I flash these .img files? Or do I have to do something else before flashing
billybobjoe512 said:
So where would I flash these .img files? Or do I have to do something else before flashing
Click to expand...
Click to collapse
What else you can do? Like going for a walk is recommended!?
You just have to boot into recovery. And then flash them like the way i said.
Or else you can use this app.
https://youtu.be/6IMvOCUy2Wc
You can also flash .img via fastboot with this command : fastboot flash boot <file_name.img>
Also if you have magisk installed you have to flash again the magisk install every time you install a new kernel.
I am a bit of a noob so I'm probably doing a ton of things wrong here
So how long does it take to start up the device after flashing the kernel? I flashed to boot partition and I waited for about 10 minutes and I got impatient so I restarted and tried to take a logcat but it just said waiting for device so I just restored a backup that I had made
Did I mess up somewhere or do I need to have a logcat for this
Phone don't boot bro I waite d 20 min
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
marios199546 said:
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
Click to expand...
Click to collapse
Phone not booting. Stuck at Spash screen. Cant take logs (waiting for device).
Code:
[B][COLOR="Red"]Your warranty is now void.[/COLOR][/B]
I am not responsible for bricked devices, dead SD cards. Please
do some research if you have any concerns about features included in this method
before apply it!
I also do not provide any warranty! The result of a failure could include voiding of warranty and hardware damage.
Be careful! Many of these commands have a high probability of resulting in a brick if mistyped.
What you’ll need
Backup your personal data. It is good idea backup your system with twrp too
Divice Lg V20 H990
Unlocked bootloader and rooted Device ([url]https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296[/URL])
ADB (in Linux , windows)
twrp 3.2.1 recovery
New method(07-05-2018)
Here you have an only one zip rom. Flash via twrp, reboot and wait. Please be patient, you have to wait +-18mins.
Works
NFC
gps
call
sms
wifi
Bluetooth
Hotspot
Camera focus and good resolution
STEPs
Download: https://drive.google.com/drive/folders/1zZHGjigoPZq2VNjWAn-Lg4azlTst4UzW
flash
reboot
wait
Old Method
ISSUES
Bluetooth
Hotspot
Camera poor resolution
Other that you find
STEPs
Download Official Lianogeos 14 ROM and save in SDCARD (lineage-14.1-20180405-nighttly-h910-signed.zip)
Download neocore.zip kernel and save in SDCARD ([url]https://forum.xda-developers.com/v20/development/kernel-t3726416[/URL])
Save firmware wifi files (fw_bcm*) from your device (/system/etc/firmware) in your computer
Save configuration file (bcmdhd.cal) from your device (/system/etc/wifi) in your computer
Modify zip of rom to H990:
Open(not uncompress) with some zip program
go to META-INF/com/google
open and edit update-script: replace 910 by 990
save and close
Reboot into Twrp recovery, wipe system, data, cache
flash lineageos
Reboot into Twr
if twrp ask abot password, click cancel, go wipe and format data
flash neocore.zip
Reboot into Twrp
Push wireless firmware into your device (connect your device to pc):
virify your device is ready
Code:
adb devices
into via adb
Code:
adb shell
mount sytem partition
Code:
mount /dev/block/sda14 /mnt
push
Code:
exit
adb push fw_bcmdhd.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_mfg.bin /mnt/system/etc/firmware
adb push fw_bcmdhd_apsta.bin /mnt/system/etc/firmware
adb push bcmdhd.cal /mnt/system/etc/wifi
Reboot into SYSTEM
Enjoy!
Does this work on a H990DS
faeterov said:
Does this work on a H990DS
Click to expand...
Click to collapse
I dont have h990ds but i tried installing SuperV20 custom rom (h990ds Stock-rom based) and that works in h990, MAYBE my solution works in h990ds
You should package the zip folder and is there a result for us to use old nightly ?
I have tried with 20180419 version and this worked fine
Hi,
Possible to package the whole zip ?
@x86cpu
The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps
XolYnrac said:
The main point here is that could be posible compile lineageos for h990 only we have to be careful to configure kernel like neocore respect to mode to handle modem and using the correct firmware for gps
Click to expand...
Click to collapse
I'm trying build it
joaovictorsouza said:
I'm trying build it
Click to expand...
Click to collapse
Let me know to test
H990ds ???
Is there any H990ds developpement guys ???
So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.
Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416
thirdzcee said:
Kernel compiled its in my neocore page, you guys could give it a test. Remeber have a back up, its the only build i have not personally tested cause im not on Lineage
https://forum.xda-developers.com/v20/development/kernel-t3726416
Click to expand...
Click to collapse
The lineage patches should work fine. the kernel I use for TWRP is stock based (which needs either Lineage's patches or manually adjusting twrp's config to stop the overflow), until recently it was 99% stock.
I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.
thirdzcee said:
So i heard you guys using my kernel for this but have issues with 2nd screen overflow, ill give a try to build one with the lineage patches to prevent overflowing of screen contents in the second screen.
Click to expand...
Click to collapse
Hi, to me it isnot a disvantage, i consider that like a advantage because meaning we can manipulate the second screen. The task is that in the GUI layer add some area in the upper place, that would give us podinility to put anything in that area more than simple shortcut.
I am speculating because i dont know android architecture.
The other task is identify how neocore handle the modem and introduce that in lineageos kernel.
Yesterday i compiled lineageos based on a installation like this thread. When i installed that i only had problem with modem, wifi worked fine
iDefalt said:
I still find it suss we haven't had any definitive response from someone who has flashed this to say whether or not it's working. No screenshots, anything.
Click to expand...
Click to collapse
I coul give you a screenshot runnig lineageos on my h990.
@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG
jl10101 said:
@XolYnrac
Have you tried using the ported Google Camera to see if the camera resolution / quality issues are resolved?
https://www.celsoazevedo.com/files/android/google-camera/
You could probably try a LOS compatible one, or something by cstark or BSG
Click to expand...
Click to collapse
I will try that but I have tried with that https://forum.xda-developers.com/lg-v30/themes/cstark27-google-camera-mod-wide-angle-t3747263 the resolution is good but the focus isnt work
I'll test in H990DS. I'm building again LineageOS with the H910 binaries.
Here my own compilation of lineageos for h990 with neocore kernel.
In the screenshot we can see the complity screen but I cant see the upper left corner in the cellphone because in this part are the camera and sensors
Using a GSI on your shiny new A2 Lite? How have your experiences been? Which GSIs have you been using? Have some GSIs work better than others for the A2 Lite? If so, which?
I want this to be a thread for talking about people's experiences with using Project Treble's Generic System Images in the Xiaomi Mi A2 Lite.
Just to tide us over until there are proper, less "generic", ROMs being developed for this phone.
Tried the Pixel Experience 9.0 GSI, worked fine and all, but camera is not working, been wanting to try another one in the next few days.
Using latest PixelExperience P as daily driver, everything works fine (except Wifi-Hotspot). Got a semi-working Gcam port now, stock camera worked though it had few features. Mi a1 camera port magisk module works, too. All in all I have the feeling that our phone is well-suited for GSI flashing. So if you'd like too, go ahead and try some GSIs. Bricking should be rather hard, but in case of bootloop, just flash stock ROM through Xiaomi Flash tool (worked for me).
opal06 said:
Using latest PixelExperience P as daily driver, everything works fine (except Wifi-Hotspot).
Click to expand...
Click to collapse
How is the battery ?
I'm using hotspot almost everyday, guess I'll wait for another rom
Tayloro said:
How is the battery ?
I'm using hotspot almost everyday, guess I'll wait for another rom
Click to expand...
Click to collapse
Battery life is good, with normal usage (some browsing, some gaming and texting, few short calls and some videos) I get through the day with 50% battery left. I am using Googles AI battery optimization as well as Greenify Magisk module. Can't post screen shots from settings because those stats are wrong/not working correctly. I'm using BetterBatteryStats instead, which normally shows me average usage of ranging from 2.5 to 3 % per hour.
Edit: Wifi-hotspot not working seems to be a common bug for all GSIs based on phh's work (so, basically all). Probably, we'll have to wait for a custom ROM specifically made for A2 lite. I hope to see some soon!
My experience with gsi:
I tried the following roms. (now with links)
1) Pixel Experience Oreo: https://download.pixelexperience.org/treble_gsi/
- smooth
- everything works except hotspot
- nice rom but not enough customizations for me
- no rounded corners -> you will loose some info on both sides of statusbar
2) Beno-Rom: https://basketbuild.com/uploads/devs/yshalsager/GSI/Benzo/arm64-ab/benzorom-9-unofficial-20180920-ab-arm64.img.xz
- soo smooth
- everything works incl. hotspot except camera and flashlight -> it´s a pity becouse it´s a great rom!
- rounded corners and notch are recognized -> no lost info anywhere
- some other adjustments for gsi treble
- enough customizations especially for pie
3) Havoc 2.0 Pie: https://sourceforge.net/projects/havoc-os/files/arm64ab/
- booting only with twrp as boot kernel! Everything works except wifi (like on every rom, when booting from twrp)
- laggy (like every rom that boots with twrp as kernel)
-> we need a new twrp! Then we can enjoy havoc.
- tons of customizations, no problem with rounded corners.
4) AEX 5.5 - 5.8: https://androidfilehost.com/?w=files&flid=271118&sort_by=date&sort_dir=DESC
- fc ui -> interacting with phone nearly impossible. 2x pwr gesture opens camera and it works.
- Normally my favorite rom, especially becouse it offers rounded corners and the ajustment -> but there´s somthing wrong with that roms
-> it someone gets it running pleas pm me!
5) AEX 6 Pie: https://androidfilehost.com/?w=files&flid=271118&sort_by=date&sort_dir=DESC
- Everything works - even hotspot seems to work -> forgot to put in sim, but hotspot started...
- same sources and developer as AEX 5.x but this one works - strange....
- smooth and stable, but nearly no customizations right now
6) RR Oreo: https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64ab/
- everything works
- smooth
- safetynet works after flashing universal safetynet fix
7) CrDroid Oreo: https://androidfilehost.com/?fid=5862345805528041177
- smooth and stable
- everything works, but safetynet not fixable -> flashing universal safetynetfix fixes device not certified but but still basic integrity false...
- even though safetynet not working, playstore and everything works normal
- my daily driver right now!
8) Arrow OS Pie: https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/
- everything exact like on Havoc Pie (3) - only less customizations
-> boots only laggy with twrp as kernel
Chears!
Voodoojonny said:
My experience with gsi:
I tried the following roms.
1) Pixel Experience Pie:
- smooth
- everything works except hotspot
- nice rom but not enough customizations for me
- no rounded corners -> you will loose some info on both sides of statusbar
2) Beno-Rom
- soo smooth
- everything works incl. hotspot except camera and flashlight -> it´s a pity becouse it´s a great rom!
- rounded corners and notch are recognized -> no lost info anywhere
- some other adjustments for gsi treble
- enough customizations especially for pie
3) Havoc 2.0 Pie
- not booting at all -> tried all kernels - no dm veryfy, no encryption, disabled encryption in vendor - idk.
4) AEX 5.5 - 5.8
- fc ui -> interacting with phone nearly impossible. 2x pwr gesture opens camera and it works.
- Normally my favorite rom, especially becouse it offers rounded corners and the ajustment -> but there´s somthing wrong with that roms
-> it someone gets it running pleas pm me!
5) AEX 6 Pie
- Everything works - even hotspot seems to work -> forgot to put in sim, but hotspot started...
- same sources and developer as AEX 5.x but this one works - strange....
- smooth and stable, but nearly no customizations right now
6) RR Oreo
- everything works
- smooth
- safetynet works after flashing universal safetynet fix
7) CrDroid Oreo
- smooth and stable
- everything works, but safetynet not fixable -> flashing universal safetynetfix fixes device not certified but but still basic integrity false...
- even though safetynet not working, playstore and everything works normal
- my daily driver right now!
Can someone share the original build.prop? There are entries about the notch and rounded corners. Perhaps some roms will respond to these entries.
Chears!
Click to expand...
Click to collapse
do you install all this rom by twrp unofficial?
Voodoojonny said:
Can someone share the original build.prop?
Click to expand...
Click to collapse
https://github.com/TadiT7/xiaomi_da...ODLMIFF-release-keys/system/system/build.prop
notthesun said:
do you install all this rom by twrp unofficial?
Click to expand...
Click to collapse
Only via fastboot! Changing to decrypt breaks wifi!
cpu004 said:
https://github.com/TadiT7/xiaomi_da...ODLMIFF-release-keys/system/system/build.prop
Click to expand...
Click to collapse
I did some testing with build.prop.
-> all data about notch and rounded corners are in the additional.prop
-> in original build.prop system.prop and additional.prop from /vendor are being importet. Importing them in Lineage´s build.prop leads to bootloop...
to roll back to stock is enough flash the stock system.img with fastboot?
Thanks!
Paolo
ilpolpi65 said:
to roll back to stock is enough flash the stock system.img with fastboot?
Thanks!
Paolo
Click to expand...
Click to collapse
Normally yes!
Voodoojonny said:
My experience with gsi:
I tried the following roms.
1) Pixel Experience Pie:
- smooth
- everything works except hotspot
- nice rom but not enough customizations for me
- no rounded corners -> you will loose some info on both sides of statusbar
2) Beno-Rom
- soo smooth
- everything works incl. hotspot except camera and flashlight -> it´s a pity becouse it´s a great rom!
- rounded corners and notch are recognized -> no lost info anywhere
- some other adjustments for gsi treble
- enough customizations especially for pie
3) Havoc 2.0 Pie
- not booting at all -> tried all kernels - no dm veryfy, no encryption, disabled encryption in vendor - idk.
4) AEX 5.5 - 5.8
- fc ui -> interacting with phone nearly impossible. 2x pwr gesture opens camera and it works.
- Normally my favorite rom, especially becouse it offers rounded corners and the ajustment -> but there´s somthing wrong with that roms
-> it someone gets it running pleas pm me!
5) AEX 6 Pie
- Everything works - even hotspot seems to work -> forgot to put in sim, but hotspot started...
- same sources and developer as AEX 5.x but this one works - strange....
- smooth and stable, but nearly no customizations right now
6) RR Oreo
- everything works
- smooth
- safetynet works after flashing universal safetynet fix
7) CrDroid Oreo
- smooth and stable
- everything works, but safetynet not fixable -> flashing universal safetynetfix fixes device not certified but but still basic integrity false...
- even though safetynet not working, playstore and everything works normal
- my daily driver right now!
Can someone share the original build.prop? There are entries about the notch and rounded corners. Perhaps some roms will respond to these entries.
Chears!
Click to expand...
Click to collapse
Hi,
I was using redmi note 3 pro before with latest RR rom. I'm kinda fan of RR.
Recently i bought mi A2 lite. And I'm new with this treble thing. And I want to use RR on this device. My phone is new and didn't do any tweaks yet. Not even unlock bootloader.
My humble request to u brother, can u guide me through for the first time how can I flash RR on it. after that I can mange further updates and other things.
Good wishes for u. And Thanks in advance.
GOD bless.
hasanzahir said:
Hi,
I was using redmi note 3 pro before with latest RR rom. I'm kinda fan of RR.
Recently i bought mi A2 lite. And I'm new with this treble thing. And I want to use RR on this device. My phone is new and didn't do any tweaks yet. Not even unlock bootloader.
My humble request to u brother, can u guide me through for the first time how can I flash RR on it. after that I can mange further updates and other things.
Good wishes for u. And Thanks in advance.
GOD bless.
Click to expand...
Click to collapse
Ok, let´s start:
Some words before starting:
RR treble runs perfectly. Good bb, everything works, incl. camera, wifi hotspot, etc.
But: becouse of the rounded corners of the display, some info of the statusbar gets lost - especially if you reduce ui-size -> I´m trying to find a solution!
Omni doen´t have this problems, but it has no gapps included and installing gapps without twrp is a pain in the ass!
-> finally I did it using twrp and after that reflashing stock recovery and format data with stock...
Treble Roms runs smoother and more stable with the july build. If you updated to august stock I would suggest to reflash 9.6.4.0 via miflash!
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
Before starting, you shold root your kernel with this guide: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
1.) Download latest AB arm 64 gsi build: https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64ab/system-180818-arm64-ab-gapps-su.img/download I would always use the gappsed version - twrp still not running for daisy...
2.) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/showthread.php?t=2588979
3.) copy system-180818-arm64-ab-gapps-su.img to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> fastboot opens and connect your phone to your pc
6.) type in your command prompt fastboot oem unlock - Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!
7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- -> fastboot
8.) Type in your command prompt fastboot flash system system.img
Important: If you havn´t rooted your device via magisk before doing this, you have to follow the next steps too! if you are already rooted: fastboot reboot Violla
9.) Don´t reboot stay in fastboot and download a prerooted kernel from here: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952, copy the patched kernel into fastboot folder and type: fastboot boot patched_boot.img
10.) Now it boots up and tells you that your data is encrypted and can´t be read. At this point you can put in whatever you want. Then you get the message reset phone! Say yes!
11.) Your phone will boot up and erase data! While it´s doing this, press vol-, then your phone will boot after that into fastboot
12.) fastboot boot patched_boot.img. Now it should boot up normal and after setting up google you should reinstall magisk via magisk manager!
Violla - Now you have RR on your Mi A2 Lite!
Voodoojonny said:
Ok, let´s start:
Some words before starting:
RR treble runs perfectly. Good bb, everything works, incl. camera, wifi hotspot, etc.
But: becouse of the rounded corners of the display, some info of the statusbar gets lost - especially if you reduce ui-size -> I´m trying to find a solution!
Omni doen´t have this problems, but it has no gapps included and installing gapps without twrp is a pain in the ass!
-> finally I did it using twrp and after that reflashing stock recovery and format data with stock...
Treble Roms runs smoother and more stable with the july build. If you updated to august stock I would suggest to reflash 9.6.4.0 via miflash!
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
1.) Download latest AB arm 64 gsi build: https://sourceforge.net/projects/re.../system-180818-arm64-ab-gapps-su.img/download I would always use the gappsed version - twrp still not running for daisy...
2.) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/showthread.php?t=2588979
3.) copy system-180818-arm64-ab-gapps-su.img to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> fastboot opens and connect your phone to your pc
6.) type in your command prompt fastboot oem unlock - Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!
7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- -> fastboot
8.) Type in your command prompt fastboot flash system system.img
Violla - Now you have RR on your Mi A2 Lite!
Click to expand...
Click to collapse
You are so kind and generous brother. I'm trying now. Will keep u posted.
Thanks for ur time bro.
Update: @Voodoojonny brother, I did what u told me to do. after flash RR system image and reboot it bootlooped. like, it shows Android One screen for 3/4 min and then reboot again. any solution brother?
Thanks in advance
hasanzahir said:
You are so kind and generous brother. I'm trying now. Will keep u posted.
Thanks for ur time bro.
Update: @Voodoojonny brother, I did what u told me to do. after flash RR system image and reboot it bootlooped. like, it shows Android One screen for 3/4 min and then reboot again. any solution brother?
Thanks in advance
Click to expand...
Click to collapse
Oh sorry, I forgot something. I hope I didn´t brought you into trouble!
To boot into a gsi treble rom, you need a prerooted kernel! https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You shold boot from a patched kernel and install root via magisk as discribed in the link above!
Sorry, I just forgot this point, idk why!
I edited the guide above! Please follow steps 9-12!
Voodoojonny said:
Oh sorry, I forgot something. I hope I didn´t brought you into trouble!
To boot into a gsi treble rom, you need a prerooted kernel! https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You shold boot from a patched kernel and install root via magisk as discribed in the link above!
Sorry, I just forgot this point, idk why!
I edited the guide above! Please follow steps 9-12!
Click to expand...
Click to collapse
Thanks for ur reply brother. after doing so it shows a screen where it ask me to give password to start android. then I turned off my device and it start by itself and stuck on android one screen. trying to find way to do it right.
Update: I put password 1234 and it start and tell me reset phone. I click reset and keep vol- button and it boot up in fastboot. then I command fastboot boot patched_boot.img again and its boot up then dycripted my phone then reboot again and everything is fine now.
Thank U brother for ur kind help. GOD bless u.
Ok, I finally able to flash RR oreo on my A2 lite. Thanks to @Voodoojonny for his time and effort on me to achieve that. Here is my experience on this ROM.
Bootup fine. Everything works so far. Some annoyance though.
1. Rom can't recognise notch. So u will miss some information on status bar and can't customise that much. Because maximum items will coverup by notch.
2. In rom camera quality is very poor and almost no option there. I tried some other cameras from magisk but none is working. (Can anyone suggest me any good camera mod please?)
3. Notification light doesn't work while charging.
4. Can't remove the google widget from home screen which is kinda annoying. (Can anyone suggest me how to get rid off that please?)
5. Headphone not working. Can't recognise any headphone/earphone.
NB: 1. can anyone tell me how to update this rom since I don't have TWRP installed. Should I download the rom zip to pc and flash via fastboot or do I need to do anything more.
2. If I want to check any other GSI roms how is the procedure? Do I need to go back stock rom again and start from beginning or can I just flash via fastboot? Should I need to flash patched boot.img everytime? If that so then which version?
Thanks in advance. Peace.
hasanzahir said:
Ok, I finally able to flash RR oreo on my A2 lite. Thanks to @Voodoojonny for his time and effort on me to achieve that. Here is my experience on this ROM.
Bootup fine. Everything works so far. Some annoyance though.
1. Rom can't recognise notch. So u will miss some information on status bar and can't customise that much. Because maximum items will coverup by notch.
2. In rom camera quality is very poor and almost no option there. I tried some other cameras from magisk but none is working. (Can anyone suggest me any good camera mod please?)
3. Notification light doesn't work while charging.
4. Can't remove the google widget from home screen which is kinda annoying. (Can anyone suggest me how to get rid off that please?)
5. Headphone not working. Can't recognise any headphone/earphone.
NB: 1. can anyone tell me how to update this rom since I don't have TWRP installed. Should I download the rom zip to pc and flash via fastboot or do I need to do anything more.
2. If I want to check any other GSI roms how is the procedure? Do I need to go back stock rom again and start from beginning or can I just flash via fastboot? Should I need to flash patched boot.img everytime? If that so then which version?
Thanks in advance. Peace.
Click to expand...
Click to collapse
1. So far no solution! I`ve put the time to the left side of the statusbar so I don´t miss too much!
2. Install magisk module mi a2 camera and give the permissions manually via apps section. You will have a fully working camera with all options - everything is working!
3. I guess that´s not that big problem
4. use another launcher - evie is great!
5. that seems to be the biggest problem!
If there is a newer version of rr you can flash it via fastboot using fastboot flash system [imagename].img Boot.img is always the same. No need to reflash it!
For round corners try:
adb shell settings put secure sysui_rounded_size 26.0
adb shell settings put secure sysui_rounded_content_padding 8.0
Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 15.1 for the ZTE Blade S6 aka P839f30.
This is the first beta release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable nano).
Please check this prop!
Click to expand...
Click to collapse
Changelog:
16.10.2019 - 2nd stable release:
los security patch level 05.10.
merge upstream kernel from oppo devices
kernel version 3.10.108
30.08.2019 - 1st stable release:
los security patch level 05.08.
use sdcard fs now
updated fs drivers
updated wifi driver
fix line-out, you can use it now
use deep-buffer for audio playback
23.12.2018 - 2nd beta release:
los security patch level 05.12.
cpu min freq. 200MHz, min cpu 0
correct modem and wcnss symlinks.
11.12.2018 - first beta release:
los security patch level 05.11.
standard features working.
Click to expand...
Click to collapse
Downloads
second stable release - 16.10.2019:
Google Drive or here.
first stable release - 30.08.2019:
Google Drive or here.
second beta release - 23.12.2018:
Google Drive or here.
first beta release - 11.12.2018:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: There is no weather provider available to download for los-15.1 - what to do now?
A: Search for it here on xda or see this post or use this download link.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
XDA:DevDB Information
Unofficial LineageOS 15.1 [OPM7.181205.001] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS 15.1
Version Information
Status: Stable
Current Stable Version: OPM7.181205.001
Stable Release Date: 2019-08-30
Current Beta Version: OPM7.181205.001
Beta Release Date: 2018-12-23
Created 2018-12-11
Last Updated 2019-10-16
The end of the year is coming and some will have a christmas feast before. So this is a small christmas gift for you - LineageOS 15.1 aka Oreo for our phone. Have fun with it.
In my opinion it is better than nougat.
Thanks!!!
Tested and no issues found
Great Rom:good:
Files error
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
Check if your build.prop has "ro.sys.sdcardfs=false" or check with terminal or adb shell:
Code:
getprop ro.sys.sdcardfs
it has to be false.
I have read about some problems with that and found it not to be working at the moment, so I disabled it.
d.alvick said:
There is an issue with files or smth. Some apps can't get the files (all permissions are given)
Click to expand...
Click to collapse
It´s true, with other file manager different from the stock (Root explorer / ES Explorer) I cann't see the files in storage.
lightwars said:
Check if your build.prop has "ro.sys.sdcardfs=false"
Click to expand...
Click to collapse
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
d.alvick said:
I've added this key, everything is fine with that now, sdcard is visible for all apps. Also there is a well-known (?) bug with audio/video streaming from web. Playback can't be resumed if I pause it (HD YouTube videos or SoundCloud, for example)
Click to expand...
Click to collapse
Great that it could be resolved so fast. I will check, why the prop got not in or overwritten. For the second thing: I didn't know that, this is an android oreo thing?
lightwars said:
this is an android oreo thing?
Click to expand...
Click to collapse
Very similar error was in old LineageOS or miui builds for our device or in both of them, I don't quite remember. Tried it again just now, playback is fine... Maybe it depends on device's mood or smth with charging, but I can't repeat it
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
d.alvick said:
There are a few more bugs in build.prop. Our SoC is Snapdragon 615 (MSM8939), but you wrote MSM8916 (actually, this is Sd 410). This may not be very good due to the different architecture of these SoCs. Apps, such as the Xposed Framework, identify the phone as armeabi-v7 (32-bit), and in fact it is armeabi-v8 (64-bit). This can affect performance, so I will try to change these keys if there are no reasons why I should leave everything as it is
Click to expand...
Click to collapse
These are no bugs! There wont be an impact in performance. Go and look for a device tree which defines msm8939... The platforms msm8ôô916 and msm8939 aren't that different. Even qualcomm defines the values like this, have a look at the CAF. Some vendors habe a common device tree for both platforms, for example asus.
And the last thing the Hardware is 64bit, but the Software is 32bit,changing to armeabi-v8 will not make the Software be 64bit.
Works great so far. Thank you
PS: could unbrick my phone
Update in the OP. new beta release.
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
d.alvick said:
2nd beta is fine.
I've been using your LOS ROM's for a while, and there is a question I want to ask. Why do Gapps consume waaay too much battery? 15.1 with Gapps has really the least working time I've ever seen (about 3-4 hours screen-on), 14.1 is better a little (4-6 hours), so I have to charge phone twice a day. On MIUI9 and stock everything wasn't that bad. Now I'm trying 15.1 with no Gapps, and it seems a lot better, 2 hours screen-on and I still have about 60%. Internet is always on. I think Gapps do the thing, but why does working time vary from MIUI9 to 14.1 to 15.1? Or is my battery becoming dead?
Click to expand...
Click to collapse
I try to answer your question, but I haven't any insight views or infos, should I could be barely wrong... Over time GApps have gotten more permissions ands task and also more GApps have been published. I think at first there was the syncing of contacts, calendar and sorts of thinks, than the geolocation services. Now we have backups or storage expansion through GApps and also tracking of your fitness, reading out sensor data of your phone. And maybe other sorts of thing, which should make your experience with a smartphone better, but also consums energy.
To emphasizes your feelings about GApps I attach a screenshot of my phone, you can see how often the google service triggers and alarm or wakeup in a span of some hours, roughly speaken every minute.
I stumbled across LKT, which should give you more screen on time. I have used it, but found mixed results. I also think that the battery optimization of 15.1 needs some time, but I could be also wrong.
At the moment I use the naptime app to get more usage, I'm afraid to say this will only help your device last longer, when not used in my opinion.
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
MouZ124 said:
Hello, I need Help for my Blade S6 (AS version).
LineageOS 15.1 from this thread I do not work, i had a Boot-Loop by the Logo of Lineage ...
The Device will not start again, its only Start in TWRP!
I have tried to go back to CM12 who works before. No chance to get out of this problem ....
I have try to flash the stock-rom with is modifide for TWRP but the result is the same
Coud some one help me to save my phone to get out of the TWRP mode, please?
Click to expand...
Click to collapse
Hi,
have you run the factory reset command from within the android settings menu?
So the device only boots the recovery, even if you select to start the system within TWRP, right?
In the TWRP terminal or from the adb shell with su permission you can try to reset all flags in the misc partition like so:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
You can also back the partition beforehand to be sure, nothing breaks.
Hello lightwars,
thank you for your answer
lightwars said:
have you run the factory reset command from within the android settings menu?
Click to expand...
Click to collapse
No, the Device starts automatically into TWRP after Lineage OS 15.1 has the Boot-Loop
lightwars said:
So the device only boots the recovery, even if you select to start the system within TWRP, right?
Click to expand...
Click to collapse
Yes, i can select Reboot - System, then i see the ZTE-Logo with vibration and then start the TWRP short after this Logo...
If i tipped this Command in the TWRP terminal it shows an Error:
Code:
dd: can't open '/sys/block/bootdevice/by-name/misc' : No such file or directory
I try to go back to the old Partition-Layout and try to flash CM12.1, stock-rom B15 (modifide for TWRP), LineageOS 15... nothing works
I try TWRP 3.0.2 and TWRP 3.2.3
I try to flash CM12.1 with other Kernels with is Modified for CM12.1 from the other thread but it fails too...
What else could I do?
Screen if i install a zip
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
MouZ124 said:
Wenn ich sys/block im File Manager öffne und mir ansehe sind nur loop0 - loop7, ram0 - ram15, zram0, mmcblk0, mmcblk0pmb, mmcblk1 dateien vorhanden
Click to expand...
Click to collapse
Sorry, my bad. It is not in sys, it is dev so this is the correct command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
You could mention Treble support means "since XZ1" (unless hacks)
Hoping to carry this on here, since I own the 1 not the 5 In order to de-google my life, I've decided that I am ready for GSI!
A few notes from my flashing weekend;
Following these instructions, from an unlocked Xperia 1 running stock rom, worked for the following;
ExpressLuke's Havoc 3.0
LineageOS 17.x
Interesting thing. These both install to system in 3 parts (when watching the flash to system.
Any other that I tried (installing in 2 parts) did not seem to work.. but then I am new at this. It's entirely possible that some of these failed because I didn't re-flash stock first.
I was also using a patched boot / kernel with a specific magisk version, which might have played a part. Failed are also (obviously) Pie.
Failed flashes were;
PPH Treble AOSP 9
Havoc 2.9 Official
So far, I've been blown away with Havoc. Of the tons of things I've run in the last 24, I've seen the following issues;
1) Call volume on handset doesn't seem to do anything. (Bluetooth works fine)
2) I had one reboot last evening. Since then solid as a rock.
3) Selection of notification sound for fastmail app didn't take right away
I haven't worked up the courage to try setting up twrp yet, so no recovery. I may give magisk a shot later tonight. I need to back this stuff up somehow!
Thanks to @Miustone for replying and making things easier, and @thatguy222 for the info he provided in the Xperia 5 thread!
charlatan01 said:
Hoping to carry this on here, since I own the 1 not the 5 In order to de-google my life, I've decided that I am ready for GSI!
A few notes from my flashing weekend;
Following these instructions, from an unlocked Xperia 1 running stock rom, worked for the following;
ExpressLuke's Havoc 3.0
LineageOS 17.x
Interesting thing. These both install to system in 3 parts (when watching the flash to system.
Any other that I tried (installing in 2 parts) did not seem to work.. but then I am new at this. It's entirely possible that some of these failed because I didn't re-flash stock first.
I was also using a patched boot / kernel with a specific magisk version, which might have played a part. Failed are also (obviously) Pie.
Failed flashes were;
PPH Treble AOSP 9
Havoc 2.9 Official
So far, I've been blown away with Havoc. Of the tons of things I've run in the last 24, I've seen the following issues;
1) Call volume on handset doesn't seem to do anything. (Bluetooth works fine)
2) I had one reboot last evening. Since then solid as a rock.
3) Selection of notification sound for fastmail app didn't take right away
I haven't worked up the courage to try setting up twrp yet, so no recovery. I may give magisk a shot later tonight. I need to back this stuff up somehow!
Thanks to @Miustone for replying and making things easier, and @thatguy222 for the info he provided in the Xperia 5 thread!
Click to expand...
Click to collapse
Thanks for Your great Feedback! Glad i was able to help out Think i will add some stuff to the Guides soon. Wonder if i get Contributer Status now :silly:
Miustone said:
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Check with the manufacturer of the Android device for explicit flashing instructions. Use the following steps as a general guideline:
1. Ensure that the Device has the following:
Treblized
A method for unlocking devices (so they can be flashed using fastboot)
A method for disabling verify boot (for example, vboot 1.0 or AVB)
An unlocked state to make it flashable via fastboot (To ensure that you have the latest version of fastboot, build it from the Android source tree.)
2. Disable verify boot.
3. Erase the current system partition, then flash the GSI to the system partition.
4. Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions).
5. Reboot the device.
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Open up the Zip File and place the 2 Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC
Disable verify boot (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Erase and flash the GSI to the system partition:
Code:
fastboot erase system
fastboot flash system system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Click to expand...
Click to collapse
Please, try to install gcam in lineageos 17!
What happen with drm keys when you flash other roms? I love sound settings of sony ui and settings of display.
I haven't been confident in the gcam build for the 1, but I'm quite pleased with open camera thus far.
The only DRM issue I'm aware of is widevine level dropping. I'm perfectly happy with my unlocked 1.
charlatan01 said:
I haven't been confident in the gcam build for the 1, but I'm quite pleased with open camera thus far.
The only DRM issue I'm aware of is widevine level dropping. I'm perfectly happy with my unlocked 1.
Click to expand...
Click to collapse
Did you notice any degradation in photo / video quality on stock ROM with the bootloader unlocked?
I'm considering unlocking my X1, but I want to know if the consequences are as bad as they used to be a few years ago with the Z2 and Z3.
MeltdownSpectre said:
Did you notice any degradation in photo / video quality on stock ROM with the bootloader unlocked?
I'm considering unlocking my X1, but I want to know if the consequences are as bad as they used to be a few years ago with the Z2 and Z3.
Click to expand...
Click to collapse
As soon as I unlocked I went to a custom ROM, so I didn't test on stock. Sorry. I think there are some people in the ROM section that said pics looked good. They definitely confirmed there was no green or blue tint like there was with those other devices
Just finished flashing, thank you so much with the tutorial. At the -w step, it didn't seem to find the /userdata, and I tried to skip the part and just reboot. After what seems like a bootloop, it automatically rebooted to "Android Recovery" which I assume is a part of the gsi? It prompted me to wipe data and I did, and it booted!
So, a Generic System Image is just a generic version of Android? Essentially then, I could flash other ROMS - some of whom are listed in this thread (Havoc etc) and get a brand new experience? It doesn't say so here in the thread, but I'm guessing I need to unlock my bootloader - correct?
Chima2 said:
So, a Generic System Image is just a generic version of Android? Essentially then, I could flash other ROMS - some of whom are listed in this thread (Havoc etc) and get a brand new experience? It doesn't say so here in the thread, but I'm guessing I need to unlock my bootloader - correct?
Click to expand...
Click to collapse
Yes
does sd card still work?
Just curious, does auto brightness work out of the box for Xperia 1? Using havoc 3.5 on xz2, and autobrightness is the main thing not working for me.
Updated the Thread. No need for the vbmeta Image with Havoc 3.5 (Official GSI with GApps)! Means a more secure Device somehow...
I'm building Overlays for the Xperia 1 & 5 if anyone is willed to grab me the FrameworksResCommon.apk overlay from your device in /vendor/overlay
I need to decompile it, so You can do it anyways if You are willed to. I also need the build fingerprint from the build prop. It should say anything like:
ro.vendor.build.fingerprint=Sony......
The next step for GSIs on our Xperias! I will also look into a GCam Mod for our Devices! Installing Ubuntu 20.04 now...
Beetle84 said:
Just curious, does auto brightness work out of the box for Xperia 1? Using havoc 3.5 on xz2, and autobrightness is the main thing not working for me.
Click to expand...
Click to collapse
Yes bro never had an issue with that.
Thread updated with new Instructions. Added the flashing to A/B without changing the Slot. Added also the flashing of SONYs AOSP Vendors to A/B. Enjoy
PS: Did that as preparation for the MARS_SOM BETA2. Got stunning results with that SOM and PHH AOSP 10... Check it out <3
Can we use also Havoc OS 3.6 then bro and does it have bugs ?
Pandemic said:
Can we use also Havoc OS 3.6 then bro and does it have bugs ?
Click to expand...
Click to collapse
Works just fine like the latest PHH AOSP Versions with passing SafetyNet. I recommend using My latest Guide here to use it. Things that don't Work yet are:
-VoLTE
-Always on Display
-Camera Button
-HDR 4K native Video Playback in Apps
I recommend using Open Camera with CameraAPI2 enabled in the settings since we don't have GCam. Otherwise it's fine to use...
Miustone said:
Works just fine like the latest PHH AOSP Versions with passing SafetyNet. I recommend using My latest Guide here to use it. Things that don't Work yet are:
-VoLTE
-Always on Display
-Camera Button
-HDR 4K native Video Playback in Apps
I recommend using Open Camera with CameraAPI2 enabled in the settings since we don't have GCam. Otherwise it's fine to use...
Click to expand...
Click to collapse
@Miustone do you have telegram btw ? Sorry for OT