yashsingh1/xdaforums huggingface dataset:
[LineageOS News & Discussion] __sterby__:
Hello!

Usually I mainly consult this forum to get unofficial builds of LineageOS or look for support when occasionly something goes wrong. Some time ago I wondered, why it has to be so annoying to install LineageOS (or most of the other custom ROMs). There have been several attempts to create a graphical installer for LineageOS (most famously this one) and some installers for specific ROMs like calyxos. But support for devices is rather limited and hard to extend.

So I decided to give it a try myself and create a new attempt to build a graphical installer for alternative Android ROMs.

Repository: https://github.com/openandroidinstaller-dev/openandroidinstaller

View attachment 5743119

Features:​

- Graphical installer with instructions.

- onefile executable.

- adb, fastboot, heimdall and some drivers included.

- Works on Linux (mainly tested on Ubuntu 20.04), MacOS (not on ARM, M1, M2) and windows (you might need to install some drivers manually).

- some checks if the selected LineageOS image and recovery works for your device.

- Installation steps are based on config files to add support for new devices.

- written in python

Supported devices:​

- Currently, the alpha version mainly supports Google, Samsung, Fairphone and Sony devices, but should be fairly easy to extend to other devices.

Alpha version release download:​

Releases · openandroidinstaller-dev/openandroidinstaller

Makes installing alternative Android distributions nice and easy. - openandroidinstaller-dev/openandroidinstaller

github.com

How can you help?​

All kinds of feedback are useful! Let me know what you think in this thread.

If you have a unused device that supports LineageOS, perhaps you could try out this tool and report your results in this thread! I bought a bunch of different android devices, but more testing on all kinds of devices is needed and very welcome! Also testing the tool on different platforms (windows, macos, etc.) would be super helpful.

Note that:

- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.

- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.

- Read the repository's README for further details!

- This installer is not associated with official LineageOS.
[LineageOS News & Discussion] SigmundDroid:
Getting a new phone this week, will give it a shot :cowboy:
[LineageOS News & Discussion] __sterby__:
Thanks a lot! I'm looking forward to your feedback! 🤩

What phone are you getting? I might be able to help you with support :)
[LineageOS News & Discussion] SigmundDroid:
FP3. Was hoping it'll arrive today... alas, didn't come, so probably I can check not before the weekend.
[LineageOS News & Discussion] __sterby__:
Great! I'll make sure, that there is support for the FairPhone 3 on the weekend, but note, that it hasn't been tested yet, since I don't have a FairPhone 3. So I'm super happy about any feedback I can get ☺️

If you have questions, let me know!
[LineageOS News & Discussion] __sterby__:
Devices that should work out of the box now:

Vendor	Device Name	CodeName	Models	Status
Samsung	Galaxy A3 2017	a3y17lte	SM-A320FL	tested
Samsung	Galaxy A5 2016	a5xelte	SM-A510F	tested
Samsung	Galaxy S7	herolte	SM-G930F	tested
Samsung	Galaxy S9	starlte	under development
Google	Pixel 3a	sargo	sargo	tested
Sony	Xperia Z	yuga	C6603	tested
Sony	Xperia Z3	z3	under development
Fairphone	Fairphone 2	FP2	under development
Fairphone	Fairphone 3	FP3	under development
Motorola	moto g7 power	ocean	under development

In general, it should be pretty easy to use the tool for all kinds of Samsung, Pixel, Sony Xperia, Fairphone and Motorola devices. Let me know if you need help with your devices.
[LineageOS News & Discussion] SigmundDroid:
View attachment 5753929

OK, it works with FP3! Awesome! Actually, that might become a nice little helper for flashing LOS!

Ran into some problems:

Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)

First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)

Had to unlock with fastboot flashing unlock

That can be a big problem for beginners if you face it the first time

A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer

Overall very good approach! Well, except for the lack of feedback (errors/progress from console). Is there any logging?

PS: Used it on Debian Bullseye with KDE.

PSPS: Perhaps an overview of the steps would fit in there as well (so one can see past, current and future steps)?
[LineageOS News & Discussion] __sterby__:
Awesome! Thanks for giving it a try! :)

Very good point! :)

In the next release it will point to the official page. I wasn't aware that this page is not at all related to LOS and not so well perceived in the community as some of the devs pointed out to me. The check is done, to find out if there is an official release of LOS and then recommend the download. There might be a better way to guide users to find an appropriate image for their device, but that was simple.

That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough and stopped after part 1. This should be easy to address by updating the config. It will be fixed in the next release.

That's very true! I'm trying to figure out, what kind of feedback is appropriate to keep people informed, but not scare them. A progress bar for flashing is in the making. Optimally, the installer can also show images of what should be going on on the phone. But that will mostly rely on community contributions for phones I don't own.

Thanks a lot for the detailed feedback! I will try to address most of them in the next release, especially more information and feedback for the user.

PS: Are you using the FP3 as your daily driver now, or would you be open to test the installer again in a few weeks or so?

PPS: I'm thinking about moving away from LOS recovery all together and only support TWRP since it allows for much more automation. What are your thought on that?
[LineageOS News & Discussion] SigmundDroid:
Would that link do it?

https://download.lineageos.org/FP3

:ROFLMAO: Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...

Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.

Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).

Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).

So, yes, keep it coming :cool: Your idea is awesome (and saves me some time as well).

Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...

Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
[LineageOS News & Discussion] __sterby__:
Yes :) And probably also to the relevant TWRP page soon.

No, other phones also require this step. Since the fairphone 2 doesn't require it (as far as I know the bootloader is already unlocked), I assumed that could be similar for the Fairphone 3.

Thanks for the suggestion, I'm working on an "advanced output mode" that lets you see all the terminal input and output.

yeah, I'm thinking about how to integrate this in a useful way. A bit more overview would be nice.

Perfect! Thanks a lot, I'm already working on a new release and hopefully there will be much more automation and more user information (and a fully working config for the fairphone 3). I keep you updated! :)

So far, it works kind of okay with TWRP I would say, but I'm having weird issues on the Google Pixel with it and wasn't able to find anyone who might know anything about it. Using twrp commands in the adb shell seems to be not so common...

Either way, I would try to get away with just booting into TWRP, wiping and flashing from there. This is an approach that seems to work fine with A/B-partitioned phones as far as I can tell.

It's not on the short-term agenda. But definitely something I'm thinking about. I should probably put a proper roadmap on github 😅
[LineageOS News & Discussion] __sterby__:
Soooo, now there is a new alpha Release 🥳

Release Alpha release v.0.2.1 · openandroidinstaller-dev/openandroidinstaller

This is an alpha release of the OpenAndroidInstaller. Linux, MacOS and Windows are supported, but the testing is mainly done on under Ubuntu 20.04. Note, that currently there is no support for ARM-...

github.com

This time mainly visual improvements and more automation. This is mainly achieved by switching recovery support completely to TWRP (currently only booted, only flashed on samsung devices).

There is now an option to get advanced output, printing commands run and terminal output in the tool. This is still early stage and needs a fair amount of improvements, but gives some more hints about whats going on.

Logs are written in the same directory you run the tool in.

...and support for quite some new devices! :cowboy:

@SigmundDroid : Now the support for the Fairphoen 3 should be fixed and TWRP should work A/B devices (tested with google pixel 3a). Give it a try, if you want! :)

I would be grateful about any feedback! Let me know how it works for you!
[LineageOS News & Discussion] SigmundDroid:
Just tried the 2nd version:

+ Nice, comes with log now, good! (y)

- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).

View attachment 5766215

The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)

PS: Shall I drop you the log somewhere?
[LineageOS News & Discussion] __sterby__:
Great! Thanks a lot!

Thanks! Did you also try the "advanced output" feature?

That's a very good catch, I noticed an issue there. I followed this official tutorial from Fairphone: https://support.fairphone.com/hc/en-us/articles/360048646311-Manage-the-bootloader-of-your-FP3-FP3-

And they used `fastboot oem unlock`, which I noticed now doesn't even exist. I fixed it now.

Ah, right now, I just boot to TWRP recovery, not flash it for A/B devices, since I was not sure how to best do it for now (without potentially destroying stuff). For Samsung devices it will be flashed.

Do you think this is an issue in general? I might try to add it as a feature for power users, that can also handle the risk a bit better. What do you think?

For now, it's fine and I guess I know whats the issue.

I'm planning another release next week, probably mostly a bugfixing and user-interface release. I will post it here again :)
[LineageOS News & Discussion] __sterby__:
Hey there!

Today I released the Version v.0.3.0-alpha of the OpenAndroidInstaller with many improvements and newly supported devices! 🥳

View attachment 5773803View attachment 5773805View attachment 5773809

The release includes 11 new devices (now 27 officially supported devices):

Motorola moto g7 power (ocean)

Motorola moto g5 (cedric)

Samsung Galaxy Note 9 (crownlte)

Samsung Galaxy Note 10 (d1)

oneplus 6

oneplus 6T

oneplus 7

oneplus 7 Pro

oneplus 7T

oneplus 7T Pro

OnePlus Nord N200

Give it a try, if you want! :cowboy:

I would be grateful about any feedback! Let me know how it works for you!
[LineageOS News & Discussion] SigmundDroid:
:cowboy: Clean shot, eh!

No, really, worked like a charm! No hickups, nothing, just awesome! Thanks! :love:

PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP 🤪
[LineageOS News & Discussion] __sterby__:
Great! Thanks a lot for testing again!

Looks like the thing is slowly moving to a more stable state. Maybe moving to beta next year :D

PS: Good point! In the next release I will try to make it clearer. At least you could not use the LOS recovery :LOL:
[LineageOS News & Discussion] SigmundDroid:
Yeah, perhaps some bold print of the file templates for unteachable people like me :D Nah, just kidding...

In any case, thanks so far and Merry XMAS 🎅
[LineageOS News & Discussion] __sterby__:
Thanks a lot! Merry Christmas to you as well! :)
[LineageOS News & Discussion] __sterby__:
Hey everyone!

I did some work in the last weeks and now the OpenAndroidInstaller is available in alpha version 0.3.1, with improved user experience and newly supported devices. 🎁

New features:

new images to guide in the process

steps indicator header

remove step-progressbar and move the header to different column container to keep it attached to the top

pop-up box to explain custom recovery and OS images.

dialog to help finding the android or firmware version

5 New devices (now 32 officially supported devices):

Sony Xperia 10 (kirin)

Sony Xperia 10 Plus (mermaid)

Sony Xperia XA2 (pioneer)

Sony Xperia XZ3 (akatsuki)

Sony Xperia XZ2 (akari)

If you're interested in trying out alternative ROMs on your device, now is the perfect time to give OpenAndroidInstaller a try. Over the holiday season, you might to play with OpenAndroidInstaller on your old or new devices and see what it can do.

Thank you for supporting open source software and giving OpenAndroidInstaller a chance. Happy holidays and happy installing! 🎅

PS: There is a brand new, shareable website now! 🥳 https://openandroidinstaller.org/ 🥳

View attachment 5790375View attachment 5790377View attachment 5790379
[LineageOS News & Discussion] __sterby__:
Hey you all! I have been quiet for while here, but the work continued!

Now I'm happy to release the first beta release of the OpenAndroidInstaller.

The major new feature is the option to install addons like GApps, MicroG or F-droid with the Installer. Also there are now 52 officially supported devices and more to come!

If you want to try it, I'm happy about all kind of feedback (positive and negative). Have a great day and happy flashing! :)

Release: https://github.com/openandroidinstaller-dev/openandroidinstaller/releases/tag/v0.4.0-beta

Download: https://openandroidinstaller.org/download.html

View attachment 5838197

View attachment 5838195
[LineageOS News & Discussion] SigmundDroid:
Awesome! Actually, I did want flash a FP3 soon/this weekend anyway, so this will be handy, thanks :)
[LineageOS News & Discussion] __sterby__:
Thats great! 🤩 I hope everything works fine and as usual, I really appreciate your feedback!

Are you planing to install addons like Gapps, MicroG or F-Droid? (Actually any flashable zip should work, but I only tested with those three) :cowboy:
[LineageOS News & Discussion] SigmundDroid:
Oh, ran into a minor problem:

Win

https://www.virustotal.com/gui/file/a0d15842c36b5716cdac49f54e482498f181be0f229461a377c9f1341f1ee2bc

Linux

https://www.virustotal.com/gui/file/0bd26f4baed0f848b613e5ee951a7df31df1914d2857ab4c54ed36e5935894d0

Usuallly I wouldn't give a damn about some obscure scanners (usually false positives anyway) but google showing up for me is a new thing... :unsure:
[LineageOS News & Discussion] __sterby__:
Thank you for pointing that out! As far as I can tell, these are all false positives. I have never thought about it! :oops:

That's actually quite an annoying issue and it seems like there is no real way to solve this. So far basically all versions of the OpenAndroidInstaller are affected and show up as different viruses or trojans 😬

The back story (after a bit of research):

The Installer is bundled and compiled python code made into an executable file. This is done with pyinstaller (https://pyinstaller.org/). As it turns out, false positive issues are known and people encounter them regularly.

- https://stackoverflow.com/questions...pyinstaller-now-seen-as-a-trojan-horse-by-avg

- https://github.com/pyinstaller/pyinstaller/blob/develop/.github/ISSUE_TEMPLATE/antivirus.md

There seem to be no real solutions for this issue. Maybe I manage to do this: https://python.plainenglish.io/pyinstaller-exe-false-positive-trojan-virus-resolved-b33842bd3184 but it might be hard to setup in my current build system...

I'm also working on a way to distribute the application as AppImage and as flatpak which in my quick tests now seems to not trigger any of the virus scanners. That might solve the issue for linux systems. For windows I have no idea, other than contacting the virus scanner vendors.

I'll keep investigating :)
[LineageOS News & Discussion] SigmundDroid:
Thanks for the quick feedback!

Yea, thought so:

:ROFLMAO:

I drop files into VT quite often ever since I had a chinese phone, some apps from it had way over 30 hits :D And, yes, these false positves are very annoying indeed but by now my personal limit is 5 where I start bothering - just this time "google" surprised me...

Hmm, I have done my stuff now but perhaps, time allowing, I can give your new installer another go tonight.

Oh, I thought it to be appimage already but computer says no :D

$ file openandroidinstaller
openandroidinstaller: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9230f3fa19123436d7e9b46b02c11f1e492895c1, for GNU/Linux 2.6.32, stripped
[Tilt, TyTN II, MDA Vario III General] ou2mame:
just updated to 6.1, hard reset, everything stock. this happened before the update too. basically, i hit the power button and it turns off, and 2 seconds later it turns back on, and will only stay off after it times out based on the power management settings. anyone know where to start looking?
[Tilt, TyTN II, MDA Vario III General] scotchua:
Most likely it is a some piece of software that is causing the device to turn back on, have you tried performing a hard reset, and not installing anything to make sure that it's something in the rom?
[Tilt, TyTN II, MDA Vario III General] ou2mame:
yup. just did a hard reset with the 6.1 update, and its still the same. do you know of any registry entries i can edit to make it so it just doesn't wake up without the power button, no matter what software is calling it to?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 61zone:
I am currently using Project Elixir A13 version. Magisk installed and root access is there but I can't put any files in data/obb folder. Tried most of the steps and apps suggested by various articles and still fails. Any 3rd party root accessible file manager redirects to Googe Files app and stops working. Some doesn't work at all. I've transferred files via PC and it only worked once and now stopped working.

Any suggestions would be really appreciated.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Shadowk1ller:
Hello!

Flash the magisk module "NoStorageRestrict" from DanGLES3.

I don't know where i get it, but in some telegram rom group... Cherish maybe... Don't know.

Cumps.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Have you tried the AOSP Files Systemapp? On some ROMs this systemapp in hidden from App Drawer.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 61zone:
No Magisk module available for that on github. Will look into Telegram.
[P3600 ROM Development] boooms:
Good morning to all, I have a program that allows the operation of a unit through odbII - serial, so use with a handheld HP5550 that has taken the serial, I wish I use with my HTC P3600 but I can not use the adapter USB to serial, can you help me please?

I have written with WINCE driver and use the ARM is right?

Sorry for my bad English
[Android Head-Units] _BYS2_:
Got an Android head unit with no physical buttons (has 1 tiny reset hole only). I was playing around with developer settings and enabled Simulate Secondary Displays with 4K option. Unfortunately this lead to the simulated display overlay taking over the entire screen with no way to get rid of it as the touchscreen is not unresponsive over the overlay. As a note, USB debugging mode was not enabled on the headunit prior to this happening.

I've hooked up a USB keyboard and have managed to get to the app drawer but can't seem to find a way to scroll through and select the "settings" app. Pressing 'TAB' or the arrow keys don't seem to be able to cycle through the app drawer.

If anyone could help with any of the 3 solutions, I would be grateful:

How to navigate through app drawer to get to "settings" app on android via USB keyboard?

How to bring up the android search bar with the keyboard only (that way I can search for "settings")

How to boot up android headunit in safe mode (tried it on my mobile phone and was able to disable simulated display once in safe mode). However my headunit has no physical buttons.

Thanks
[Android Head-Units] rigattoni:
You should use a USB mouse.
[Android Head-Units] _BYS2_:
Thanks for your reply. Ive already tried that but unfortunately the mouse clicks on don't register on the overlay. Hence I can see the move moving around but cannot interact with the actual icons.
[Android Head-Units] _BYS2_:
Thanks for your reply. Ive already tried that but unfortunately the mouse clicks on don't register on the overlay. Hence I can see the mouse moving around but cannot interact with the actual icons.
[Android Head-Units] Skenny noodles:
Hey did you find an solution? I‘ve got the same problem..
[Android Head-Units] Skenny noodles:
If someone reading this and needs it, i just took my Roccat gaming keyboard and navigated with my Tab and enter to the settings.

Just plug the USB in 1 of the 2 cables and ur got to go.
[Galaxy S 5 Q&A, Help & Troubleshooting] Furry👍:
hello everyone, i have a problem with my s5, after custom romming it it wont boot to the stock because it stays on the samsung flickering logo, any idea on why? its using a cheap battery
[Galaxy S 5 Q&A, Help & Troubleshooting] giggi10:
I'm experiencing the same issue on my not rooted G900F (Italy) and I'm stuck, waiting for any advice.

Not sure if it was due to a custom firmware though, since I stopped using it many years ago...

I also tried hard reset and any wipe options available.

Thanks in advance.
[Android Q&A, Help & Troubleshooting] AtillaHun:
Hey there,

So I want to root my Samsung Galaxy A52 phone. I know that I need to install TWRP first, and for that I need to unlock the bootloader. Since unlocking the bootloader causes a factory reset, firstly I need to backup all of my data. I want to ask if it's sufficient to backup from Smart Switch, or is there another way that I should do it? Thank you for your answers.
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @AtillaHun

Welcome to XDA. I hope you'll always get the support you require.

However, prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A but pending what your device exactly is I can also moved the thread to

https://xdaforums.com/f/samsung-galaxy-a52-4g.12131/

or

https://xdaforums.com/f/samsung-galaxy-a52-5g.12133/

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator