Related
** This guide is depreciated, there is a new updated guide here**
If you are planning on using LineageOS 14 for this guide, you can bypass all of this except configuring location backends and battery optimization by heading to https://lineage.microg.org and downloading their ROM.
All download links as well as a link to a list of Open-Source applications to replace commonly used Play Store apps are in the third post.
*This will NOT work with MIUI Global, as the Play Store is already included in the ROM by default.*
I will be continuously updating this guide for everyone as I stumble upon more supported ROMs, more MicroG flashable zips, and other misc. edits. This is made with Android Marshmallow and Nougat in mind as it is all I have tested on, however this may work on older releases of Android with Xposed support or ROMs with Signature Spoofing. This has also only been personally tested on the XT1607 variant.
In order to sync calendars and contacts from your Google account, you must flash the Google Sync Addon by ale5000. If you want swipe gesture typing on the AOSP keyboard, you must flash Shadow53's swipelib.zip. Shadow53 also has a No-Gapps zip package that includes F-Droid, Firefox, and several other apps.
One final thing: This is not for everyone. There was a point in time I didn’t ever think I could go without the Play Store, but ever since I have I don't want to go back. There are numerous pros to switching to a Google-free android setup such as much better battery life, more privacy on your device, a world of open-source alternatives to popular applications, and more. If you have any questions, or if any of this seems daunting if you are newer to things of this nature, please do not hesitate to ask for help. I will try the best I can in my free time to help. Thank you for taking the time to read this, let’s go ahead and start.
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Click to expand...
Click to collapse
*This first post is for ROMs without native Signature Spoofing support. A list of those with native spoofing can be found in the second post as well as the guide for ROMs that include native signature spoofing.*
What You'll Need:
1. Your Phone with at least 80% battery, preferably 100%.
2. A computer to transfer files to phone
3. You must have Root Access. This can be native root or Magisk root.
4. Your ROM of choice
5. Download the correct Xposed SDK and Xposed APK for your version of Android. The Xposed SDK version may differ for your device.
6. MicroG Unofficial Installer ZIP and Google Sync Addon (optional) by ale5000 or any of Shadow53's MicroG flashable files (download links in third post)
7. Your favorite backup method if you wish to back up such as Titanium Backup, MyBackup Root/Pro, etc.
8. Third Party App Store/APK downloader such as Yalp Store if not wishing to use all open source apps
9. A working Google account
Click to expand...
Click to collapse
Alrighty, let’s finally get into the steps.
1. Make sure you have downloaded the requirements.
2. If you wish, backup the data you want. This should not erase any files stored on an SD card, but I cannot guarantee.
3. Boot into a custom recovery, I am using TWRP
4. Use the standard wipe data options
5. Flash the files in the following order:
Your ROM of choice
MicroG Unofficial installer
Xposed SDK
Custom kernel if using one
6. Just to be safe and to avoid any potential complications, now reboot the device and set up the basics. Afterwards, boot back into recovery.
7. In recovery, wipe Dalvik/ART cache only (Not really required, I always recommend it though just to be safe)
8. Go into Settings —> Security —> Turn Unknown Sources on to allow for APK installs.
9. Install the Xposed Installer APK
10. Open Xposed, grant any permissions/root permissions if it asks for any. Go to download, and search for FakeGApps. Download and install. Next go into the Modules tab of Xposed, and check the box next to the module. Reboot to activate (A soft reboot may work, but I recommend a full reboot.) Installing this allows MicroG to bind to the system and spoof the required signatures.
11. Open MicroG in the app drawer, and allow all permissions it asks for. While in here, turn on Google Device Registration
12. After allowing all permissions, go into Settings. Go to Accounts —> Add Account —> Google Account. Sign into your Google Account. This is necessary to allow certain applications that require Google Play Services to work properly.
13. After signing in, head back into MicroG, go under Google Cloud Messaging and enable.
14. In MicroG settings, head to the UnifiedNLP settings. Under the Configure location backends section, open WiFi Location Service and select Mozilla Location Service and grant any permissions asked. Under Configure address lookup backends, select Nominatim.
15. Finally, in Settings, go to Location and change the mode to High accuracy.
16. Check MicroG's Self-Check to see if everything has been set up properly, and if so, you are good to go!
Click to expand...
Click to collapse
*This post is the steps for ROMs that natively support Signature Spoofing. There is a list at the bottom of this post of those that currently support it
What you will need:
Your Phone
The ROM that supports Signature Spoofing and the kernel of your choice
MicroG unofficial installer and (optional) Google Sync Addon by ale5000 or one of Shadow53's MicroG installers
Magisk Root Manager (Optional)
About 20-30 minutes of your time
Click to expand...
Click to collapse
Steps:
1. Backup anything you want to have backed up. I recommend backup up your Contacts and Calendar events if you have those synced to Google
2. Boot into Recovery on your phone
3. Perform a standard wipe in TWRP
4. Flash the ROM
5. Flash the chosen microG zip file(s)
6. (Optional) Flash Magisk and your favorite kernel
7. (For crDroid Only)If you are flashing crDroid, you need to head over to Settings --> Miscellaneous and turn on the Signature Spoofing toggle
8. Go into Self-Check in microG, and tap the text that says "System grants signature spoofing permission", and allow microG that permission.
9. Still in MicroG, head back to the main part of the app. Open UnifiedNLP.
10. Select the pre-installed location backends.
11. Sign in to your Google account if you wish
12. You're done!
Click to expand...
Click to collapse
Moto G4 Play ROMs with Native Signature Spoofing
crDroid v3.8.1 - Android 7.1.2
ViperOS Coral - Android 7.1.2
TipsyOS - Android 7.1.2
AEX - Android 7.1.2
AICP (@ki's build) - Android 7.1.2
Glassrom Official - Android 7.1.2
MicroG Project has released an unofficial fork of LineageOS 14 that now includes signature spoofing and MicroG components. You will not need to follow anything in this guide except configuring location backends if you download their LineageOS build. There is no Play Store functionality added, although F-Droid (an open source app store) is included by default. You can add the Play Store with a zip that Shadow53 provided on their website (link in post below) More info can be found on their website
Flashable Packages and App Replacements
There are several different MicroG flashable zip files to choose from. ale5000 has one that includes MicroG, several location backends, and the Play Store. Shadow53 has MicroG and several other zip files such as an F-Droid package, the Swipe Libs for gesture typing on the AOSP keyboard, and several more.
Downloads:
MicroG Unofficial Installer - ale5000
Shadow53's Downloads for MicroG, F-Droid, and more
Now alternatives to apps you might commonly use such as Twitter, Facebook, Gmail, etc. can be a bit difficult to find at first. I stumbled upon a list that a user by the name of Datenschutz has compiled on GitHub that has a good collection of alternative open-source applications. Also, you can alternatively download APK files of certain apps such as Netflix, Messenger Lite, etc. if you don't find a suitable replacement.
Some open-source apps that are found on F-Droid I use daily are:
Flym - RSS Reader
QK SMS - SMS App
Twidere - Twitter Client
Toffeed - Facebook web-client
Newpipe - YouTube player
K9 Material - Mail app
ApkTrack - Checks for updates on APKs installed
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
ale5000 said:
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
Click to expand...
Click to collapse
I will definitely take a look into this, thank you! Any success on Nougat at all?
fireball0093 said:
I will definitely take a look into this, thank you! Any success on Nougat at all?
Click to expand...
Click to collapse
I'm using microG on Nougat and KitKat, and I can say that it works perfectly (but I patch the framework for signature spoofing instead of using Xposed).
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
n76 said:
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
Click to expand...
Click to collapse
I am currently looking into hopefully a method for Nougat, give me about a day to see if it works for me.
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
ale5000 said:
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
Click to expand...
Click to collapse
@ale5000: What ROM are you compiling from source for a Harpia (I hope that will work on a xt1607 flavor)? Got a URI I can use for repo init?
Thanks!
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
ale5000 said:
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
Click to expand...
Click to collapse
Thanks, I have been able to successfully use that patch on my personal builds of the Unlegacy ROM (Marshmallow and Nougat) for my Galaxy Nexus.
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
n76 said:
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
Click to expand...
Click to collapse
Sorry, I can't help with this.
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
gueschmid said:
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
Click to expand...
Click to collapse
Nice find, thank you!
Looking at the crDroid source code repository at https://github.com/crdroidandroid it does look like the patch for signature faking is in there. (We should probably have the page at https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing updated to include crDroid).
But I am a bit leary about trying the ROM linked to at https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141 as, despite the title of the XDA thread, it does not seem to be an official build. It looks like the official builds for the project are at https://androidfilehost.com/?w=devices&uid=23991606952610065 and are all built by "crdroidandroid" and there is no Moto G4 Play build there. The "[ROM][OFFICIAL][7.1.1] crDroid v2.1" links to a ROM built by SubhrajyotiSen on a different page so I am a bit hesitant to install it.
But this is interesting enough that I will try to build the ROM myself using the official sources from the crDroid project and see what happens.
it may be an inofficial Build, but it is mentioned on the G+ - Page of crDroid!
https://plus.google.com/communities...6/stream/d3e3f57f-b974-41f2-8740-97dbdd38056c
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
fireball0093 said:
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
Click to expand...
Click to collapse
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
n76 said:
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
Click to expand...
Click to collapse
I don't have a carrier that uses VoLTE, but I took a look in the Changelog on some posts and it seems to have support for it on crDroid
Updated the guide to include crDroid in the second post. I have been messing around with Tingle in my spare time but I cannot fully grasp the concept as I don't have much experience using tools like that. If I do succeed in the future, I'll edit that in as well.
I want to use MicroG instead of using GApps. Are there any ROMs with signature spoofing enabled for Xperia SP?
Possible ways to add signature spoofing
I was just reading about this yesterday, as I too had the intention of replacing GApps with MicroG. The usual methods require you to install a module called 'FakeGApps' in Xposed before flashing MicroG. But since there's no Xposed available for 7.1, there seem to be a few workarounds.
Here's what I found:
Guide to allow signature spoofing on any LOS14.1 device without Xposed (http://www.gabsoftware.com/tips/how-to-use-microg-on-lineageos-or-cyanogenmod-without-xposed/)
You need a PC-based tool made by @ale5000 to first patch your rom to enable signature spoofing (https://forum.xda-developers.com/android/development/tingle-fork-needle-t3438764)
I'm not sure if you have to flash MicroG files before or after patching your rom with the above mentioned tool. Anyway, here's a couple of links to MicroG posted in other devices' forums: Link 1, Link 2
Alternatively, I think we can use a Magisk-based module called NanoMod made by @Setialpha.
I haven't tried either method yet. Will try it out later today. Meanwhile, you may experiment with one of the two methods posted above at a time; I don't think its wise to try installing both at the same time. Just saying. Do share the results with us!
Have a nice day!
lex.vr7 said:
I'm not sure if you have to flash MicroG files before or after patching your rom with the above mentioned tool. Anyway, here's a couple of links to MicroG posted in other devices' forums: Link 1, Link 2
Click to expand...
Click to collapse
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).
ale5000 said:
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).
Click to expand...
Click to collapse
Whoa, thanks! I didn't come across this installer before. Guess I didn't do my research properly.
Wow I didn't see the replies till now. I actually tried tingle on RR and it worked fine and did use that flashable zip for microg.
Sadly Mozilla location is horrible compared to Google's for me here in India. Even playing around with TopNTP didn't help even though that helps usually if GPS is wonky.
ale5000 said:
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).
Click to expand...
Click to collapse
In the tingle repo please mention that you need p7zip-full I was confused for so long why it wasn't working.
__ganeshanand said:
In the tingle repo please mention that you need p7zip-full I was confused for so long why it wasn't working.
Click to expand...
Click to collapse
@__ganeshanand: I have to make a lot of changes but I didn't have time yet, I will do it surely.
I will add a possibility to configure and maybe add other backends in the installer in the future.
ale5000 said:
@__ganeshanand: I have to make a lot of changes but I didn't have time yet, I will do it surely.
I will add a possibility to configure and maybe add other backends in the installer in the future.
Click to expand...
Click to collapse
Oh cool. Looking forward to that then.
AICP now has implemented signature spoofing into their latest nightly builds
This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').
Gynoid said:
This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').
Click to expand...
Click to collapse
As a workaround if you flash a different kernel (i.e. Franco) prior to flash magisk everything working fine
the 0605 build also has the same issue. Is anyone has a solution for this trouble?
I met the same issue, and I have to downgrade to 0521 with sideload.
Unfortunately the devs at Lineage don't seem to give a sh... about Magisk - I tried to raise the problem at their Reddit page, but my post and all subsequent users replies (people having the same issues) were deleted - and, true, LineageOS release 0605 still has that same issue. So the only solution If found is to root my Oneplus5 with LineageOS SU instead, but I still had a problem with the current release of Tasker which does not detect root when LineageOS SU is used. Luckily enough, the latest Tasker beta works fine with it.
So I'll live without Magisk for the moment.
Until I get rid of Lineage
Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?
digger16309 said:
Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?
Click to expand...
Click to collapse
Unfortunately, the issue is still present in the 6/11 release, at least on my OP5 and most probably on OP5T as well. Regarding other kernels, I don't know and I will not start testing kernels - takes too much time.
Gynoid said:
Unfortunately the devs at Lineage don't seem to give a sh... about Magisk
Click to expand...
Click to collapse
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.
OK so just because it's free it should not be criticized? Is that your point? It should never make any progress? Well that's how "free" projects die. Hopefully their developers will be little more ambitious than that..
gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.
Click to expand...
Click to collapse
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.
batwingnz said:
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.
Click to expand...
Click to collapse
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:
gurningchimp said:
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:
Click to expand...
Click to collapse
Rooting it wouldn't help with that
gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
Click to expand...
Click to collapse
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?
digger16309 said:
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?
Click to expand...
Click to collapse
You're thinking of SuperSU, lineage, for whatever reason, reinvented the wheel and rolled their own implementation.
OP5 Lineage 15.1 after 2018-05-21 results still in bootloader
the problem seems to persist - the last updates will always result in the device being stuck in the bootloader after flashing. I reversed the update by flashing the cheeseburger 2018-05-21-nightly over the latest (thank god for the working TWRP!) and it boots up normally. I checked up to 2018-06-11
How do we know if this is indeed a problem with Magisk (have v 16.0 installed)? Does somebody need more informations regarding the OP5 (cheeseburger) installs? Can I help in some way to resolve this problem (testing? log files?)
any hope for a resolve? The device works fine but I would like to be able to update regulary at least for security reasons (patched bugs)
I installed LOS15.1 and I see it now. Was this also the case in previous versions, 13 and 14? I remember having to turn on root manually in LOS, then Cyanogenmod and flashing SU. But I think the developer of the custom 14.1 ROM I was using took it out of his ROM so I forgot all about it. Breaking Magisk is lame. I can manage without it, but I prefer the systemless Xposed option it provides.
Did anyone try this with the LOS 20180618 build?
IMHO I don't see anything in the June 18 build changelog that would make me think it's gonna work any better than the previous builds. And on the Magisk side, there hasn't been any new release or beta for a while. So ...
Did anybody find a solution? Would upgrading Magisk 16.0 to 16.4 beta be worth a shot? How about deinstalling Magisk (via the deinstall-zip? or the deinstall option in the manager?) - would this enable the LOS update (as of today 2018-06-18-nightly)? And if yes, would it be safe to reinstall Magisk afterwards or is this door permamently closed?
I would give it a try myself but do not have a backup phone in case of bricking it and I need it for work... a report about a successful strategy would help a lot!
I flashed LineageOS 15.1-20180618-NIGHTLY-cheeseburger and Gapps Nano yesterday. After the reboot I installed the latest Magisk Manager.apk and flashed the latest sdk 27. I am now running LineageOS 15.1 with Magisk v16.0.
I didn't know about any problems there were before because this was the first time I flashed Lineage (had xXx - NoLimits). But I can't see any issues by now. It's working fine. I downloaded Youtube Vanced, Watchdogs Bootanimation and Xposed Framework (only gravitybox atm) which are all working.
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
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.