Related
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!
According to Project Treble lead Iliyan Malchev,
Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work.
Click to expand...
Click to collapse
Now that there's an Oreo beta for the Essential Phone that supports Treble, perhaps this can be used to further development on the device.
/u/foremi on Reddit confirmed that simply flashing a Pixel 2 system and boot image to the device is not enough, as it fails to boot, so the question is what constitutes a generic AOSP build?
I don't have Linux installed right now or I'd build it myself, but I suspect that building it with the simple target device of "generic" might be what Malchev is referring to.
If any devs would like to test this theory or give their input as to how they think this actually works I think it'd be incredibly useful for not just Essential phone development, but Android development as a whole.
EDIT: @phhusson confirms that the target device should be aosp_arm64_ab
FWIW "generic AOSP build" is really what it says it is.
I have access to the "Google certification generic AOSP build" (that's weirdly not public, I don't know why), so I gave it a try. (Edit: So if the ROM was Treble-certified, it would work)
I get the Android bootanimation, but that's all (I have to say that's still a big step forward compared to other Android versions
Looking at the logs, I see a loop of crash because of: /vendor/bin/hw/[email protected]
Which I guess is the HAL for the accessories, but that doesn't seem to be the reason for the crash
The reason of the crash, seem to be this:
11-15 12:59:04.491 5331 5331 F MediaProfiles: frameworks/av/media/libmedia/MediaProfiles.cpp:329 CHECK(quality != -1) failed.
in CAF, frameworks/av/media/libmedia/MediaProfiles.cpp we see vendor-specific (i.e. not in AOSP) quality attributes, like "vga"
And it is defined by Essential's framework (in vendor/etc/media_profiles_V1_0.xml)
Considering there are media_profiles xml files, I'd guess that _V1_0 is supposed to only contain AOSP-capable qualities
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Edit3: the generated fingerprint is too long to build, needs to do make BUILD_NUMBER=4412360
Edit4: To make the situation more clear:
- NO, current ROM is NOT Treble capable
- BUT, almost everything is available for that. Every HAL is using "hwbinder" which is the basis, and most work needed for Treble
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
phhusson said:
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Click to expand...
Click to collapse
I was gonna link to the aosp_arm64 make file but it said it was specifically for the emulator so I wasn't sure, that's good to know though.
phhusson said:
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
Click to expand...
Click to collapse
Thanks for this, I suspected such but couldn't find a clear answer from Google on the matter so I suggested trying the boot.img as well just in case.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2. I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
For what it's worth I only have a LG V20 right now which currently doesn't support Treble, so I'm pretty useless as far as testing anything goes, but if this is figured out it'll greatly influence what device I go with when I eventually upgrade.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2.
Click to expand...
Click to collapse
Yup. I feel like Treble deserves its own "device" section in XDA
I'm afraid I'm working on something that other people already did on other devices...
I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
Click to expand...
Click to collapse
That's my guess as well.
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
MishaalRahman said:
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
Click to expand...
Click to collapse
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
PhantomGamers said:
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
Click to expand...
Click to collapse
Google Pixel/Pixel 2 will do, yes?
MishaalRahman said:
Google Pixel/Pixel 2 will do, yes?
Click to expand...
Click to collapse
Yeah they should be fine
PhantomGamers said:
Yeah they should be fine
Click to expand...
Click to collapse
Alright, I'll find you some testers
MishaalRahman said:
Alright, I'll find you some testers
Click to expand...
Click to collapse
Here's the system image if you find anyone, it's a straight fresh build of aosp branch 8.0.0r34
If it doesn't work it's possible that I messed the build up, but it should be fine.
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
PhantomGamers said:
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
Click to expand...
Click to collapse
Hero you go
TheDethEgineer said:
Hero you go
Click to expand...
Click to collapse
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
PhantomGamers said:
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
Click to expand...
Click to collapse
That's true only for new devices, not for devices upgrading for nougat to oreo.
I wasn't aware there was an AMA yesterday... Too bad we could have asked.
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
How about flashing the system image directly from a Pixel 2 XL?
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
PhantomGamers said:
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
Click to expand...
Click to collapse
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
MishaalRahman said:
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
Click to expand...
Click to collapse
I believe it should work as normal
fastboot flash system system.img
EDIT: Apparently with the A/B partitions you'd do fastboot flash system_b system_other.img to flash the b partition, but the aosp build didn't include a system_other.img so I'm assuming perhaps it's not necessary
So far I still can't find anyone willing to flash this on their Pixel haha. People are really hesitant to flash stuff on the Pixel it seems. Times are not like they used to be =\
I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
https://github.com/ShqipLewis/Xiaomi_Kernel_OpenSource/tree/andromeda-p-oss
https://github.com/ShqipLewis/device_xiaomi_andromeda
https://github.com/ShqipLewis/vendor_xiaomi_andromeda
https://github.com/Inkypen79/device_xiaomi_andromeda
If anyone wants to build a custom rom possibly lineage i have found the trees hopefully this does help, lineage is the easiest so yeah
Current lead Dev is @Inkypen, if anyone else has any idea or wants to contribute here is the group chat
https://t.me/mimix3_5G
How I can help with this?
ZigmaInvader said:
How I can help with this?
Click to expand...
Click to collapse
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Quantumkk123 said:
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Click to expand...
Click to collapse
there also another difference is processor
Sorry guys I can't lie I think it's a complete mess I will be building a device tree for this device I just need A LOT of time and then I will try building some ROMs for this device reason why it will take so long is because I am learning myself and this will be the first time I am doing it hope it goes successfully for me
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Inkypen said:
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Click to expand...
Click to collapse
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Quantumkk123 said:
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Click to expand...
Click to collapse
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Inkypen said:
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Click to expand...
Click to collapse
Oh aha that's fine man , didn't realise this was android 10 good job man
Quantumkk123 said:
Oh aha that's fine man , didn't realise this was android 10 good job man
Click to expand...
Click to collapse
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Inkypen said:
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Click to expand...
Click to collapse
Lmao I realized when it said 16.0 aha that's fine tho still a lot more progress than me
I keep getting this error when trying to flash...the suggestion was to update twrp but 3.3.1-0 is the only one we have available ....
E: String resource 'zip_compatible_err' not found.
Using default value
Zip Treble compatibility error!
Invalid zip file format!
Any suggestions?
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Quantumkk123 said:
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Click to expand...
Click to collapse
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
ptlsajan said:
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
Click to expand...
Click to collapse
Sure there's a group chat where more info is posted there...updates etc https://t.me/mimix3_5G
I also have a mi mix 3 5g on the way, will be happy to test once i get it, thx alot for you work!
So far I have built a working version of Orange Fox recovery. Still waiting for my device to arrive, then some real work can start
https://www.androidfilehost.com/?fid=4349826312261670861
I should be getting my Mix 3 5G this week, the parcel is allegedly with my local post office already. I'd love to help out to get LineageOS working on it. I have minimum experience having flashed custom ROMs onto my current phone (Mi Max helium) as well as that of my Mrs (Mi 6 sagit), but I'd love to get more involved if possible. I don't need it to be my daily driver immediately, so I just need enough confidence in what we'll be doing here so as not to turn it into an expensive, cute brick The chassis being ceramic, it's already half way there right off the bat, but let's not get any closer please
Please generate LineageOS android 10 from Mi Mix Andromeda
ZigmaInvader said:
Please generate LineageOS android 10 from Mi Mix Andromeda
Click to expand...
Click to collapse
Join the telegram chat if you want any requests
Has anyone created a lineage rom for the A33? Can't find it.
To be clear, for me this forum is like a maze, i was previously searching for a rom for the galaxy S7 and could not find it anywhere but then a forum member sent me a link to an unofficial build which i installed and it works perfectly, so i really dont care about unofficial builds, i will take anything over the preinstalled google spyware, if you know where to find a lineageos build for the A33 please share it!!
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
ShaDisNX255 said:
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
Click to expand...
Click to collapse
I did not expect lineageos to be available for a very new phone, this is the only phone i can get for free from my provider that's why i asked.
As recovery i could use TWRP, or not?
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Librem5OS said:
As recovery i could use TWRP, or not?
Click to expand...
Click to collapse
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
Librem5OS said:
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Click to expand...
Click to collapse
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
Librem5OS said:
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
Click to expand...
Click to collapse
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
ShaDisNX255 said:
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
Click to expand...
Click to collapse
I am from the EU so i dont have a US phone.
Im not an expert so this whole information is a little more detailed than what i usualy deal with, had to read it twice lol. How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
I also never heared about OneUI, does it or does RayOS (your work) have google services in it or is it google free? I don't necessarly need lineage as my os, anything without google spyware will do the job.
-Thank you for the reply.
Librem5OS said:
How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
Click to expand...
Click to collapse
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
Librem5OS said:
I also never heared about OneUI
Click to expand...
Click to collapse
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
Librem5OS said:
does RayOS (your work) have google services in it or is it google free?
Click to expand...
Click to collapse
I leave the Google apps on, I use them so I don't remove them.
Librem5OS said:
I don't necessarly need lineage as my os, anything without google spyware will do the job.
Click to expand...
Click to collapse
Well then when you look for GSI, search for the term vanilla.
ShaDisNX255 said:
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
I leave the Google apps on, I use them so I don't remove them.
Well then when you look for GSI, search for the term vanilla.
Click to expand...
Click to collapse
Thank you now i know what ill have to look for!
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
This seems to be the generic build you where talking about?
I was just a little confused if i should visit phhs github or xda.
After all his XDA thread says: You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST
So i did that and this is where it takes me https://github.com/phhusson/treble_experimentations/releases/tag/v414
However all the files extensions are .xz i have no idea what that means.
When i flashed lineage it said img.tar if i remember correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whats the difference between the two red marked? one says secure img the other only img?
As they say vanilla these must be the ones without google?
Or should i download these instead? If yes which one? I have no clue what the names stand for. Noticed one says ARM and the other doesnt. However what is the difference between those and what is the difference between all arm versions and all non arm versions?
Librem5OS said:
However all the files extensions are .xz i have no idea what that means.
Click to expand...
Click to collapse
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Librem5OS said:
I was just a little confused if i should visit phhs github or xda.
Click to expand...
Click to collapse
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Librem5OS said:
When i flashed lineage it said img.tar if i remember correctly.
Click to expand...
Click to collapse
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
ShaDisNX255 said:
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
Click to expand...
Click to collapse
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
Librem5OS said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
Click to expand...
Click to collapse
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
Librem5OS said:
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Click to expand...
Click to collapse
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
Librem5OS said:
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
Click to expand...
Click to collapse
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Librem5OS said:
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Click to expand...
Click to collapse
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Librem5OS said:
Is the GSI all in one or are further steps required?
Click to expand...
Click to collapse
Usually GSI have all the same steps. Flashing the system and wiping data
ShaDisNX255 said:
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Usually GSI have all the same steps. Flashing the system and wiping data
Click to expand...
Click to collapse
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right? I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Librem5OS said:
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
Click to expand...
Click to collapse
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
Librem5OS said:
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right?
Click to expand...
Click to collapse
This is correct
Librem5OS said:
I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Click to expand...
Click to collapse
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Librem5OS said:
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Click to expand...
Click to collapse
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
ShaDisNX255 said:
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
This is correct
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
Click to expand...
Click to collapse
My bad you are right the twrp for the "arr" shows the first release back in 2017 so that cant be the new 5g version...
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Either way in theory the GSI for android version 12 should/could be compatible with the A33 since it is as you said a generic build, but even if that would work i obviously need a custom recovery in order to flash the system on the device, kinda surprised me you mentioned telegram, i never used it as im not really into social media. I tought if there is a custom recovery my best bet would be XDA forums.
If there is no custom recovery i guess ill have to wait for a official twrp release, or an unofficial one on XDA.
Librem5OS said:
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
Click to expand...
Click to collapse
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Librem5OS said:
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Click to expand...
Click to collapse
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Librem5OS said:
i obviously need a custom recovery in order to flash the system on the device
Click to expand...
Click to collapse
Correct
Librem5OS said:
kinda surprised me you mentioned telegram, i never used it as im not really into social media.
Click to expand...
Click to collapse
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
Librem5OS said:
I tought if there is a custom recovery my best bet would be XDA forums.
Click to expand...
Click to collapse
That's what we all say of course lol
ShaDisNX255 said:
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Correct
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
That's what we all say of course lol
Click to expand...
Click to collapse
Im having a problem with my old Huawai SCL-L01, this phone is slow and bad (only 1gb ram).
Atleast even when the devices is trash i wanted to install linage on it to atleast have privacy, as long as it's still working why not use it?
So the problem is i have usb debugging and oem unlock both activated, i installed adb fastboot / platformtools on my pc (which i downloaded here https://developer.android.com/studio/releases/platform-tools), i connected the phone to the pc and allowed data transfer over usb debugging by confirming the request which appears on the phone, i entered adb reboot bootloader into cmd.exe on the pc and the phone rebooted into bootloader, i then typed adb flash lineageos_rom.img
As a result instead of flashing the img, the cmd output "waiting for any device".
I dont know what is going wrong, what am i doing false in the process?
I was following the instructions here https://forum.xda-developers.com/t/index-list-of-roms-for-y6-2018.3854167/
Librem5OS said:
then typed adb flash lineageos_rom.img
Click to expand...
Click to collapse
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
ShaDisNX255 said:
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
Click to expand...
Click to collapse
I used: fastboot flash system recovery.img
Librem5OS said:
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
View attachment 5678691
Click to expand...
Click to collapse
Great to meet someone who also uses pagexray.fouanalytics.com
Yeah sourceforge is not trustworthy at all...
I always get confused by sourceforge.net and curseforge.com
One of them is owned by twitch or overwolf which are owned by amazon = bigtech.
Anyways, looking at forum.xda-developers.com makes me worry...
I believe you can use any LineageOS GSI, but you'd need to flash it in a custom recovery such as TWRP while retaining the stock kernel in /boot.