• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Free-Droid - One-Click Rom Installation Assistant

Search This thread

roboraver

Member
Oct 3, 2007
17
0
Sorry but do you think I can run this app on a HTC One M8 (UK) and can install a ROM that changes the language ? (Need European languages so have a Stock ROM)
 

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
Sorry but do you think I can run this app on a HTC One M8 (UK) and can install a ROM that changes the language ? (Need European languages so have a Stock ROM)
Please read the first post (description). Free-Droid is not working with HTC devices. If there is any way to make it work, this is probably not going to happen anytime soon.
 

tstuart

Member
Dec 30, 2012
6
4
Free-Droid SM-G900F

Trying to use this on a Vodacom branded Samsung Galaxy S5 SM-G900F
The phone is rooted already.
When I try to use this it detects the phone, but just says preparing please wait. Nothing ever actually happens.
 
  • Like
Reactions: imska

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
Just pushed an update with lots of bug fixes.
Using the universaladbdriver by clicking "still not detected?" does not provoke frequent crashes any more.
Lowered some http timeouts in favor of more connection retries in case of connection problems. This should make scanning for roms way faster and finding aospextended roms more reliable. Download of the latter one is fixed. Also fixed potential bug after first systest flash.

I could not test the update on windows. Please report if the windows version crashes early.

Unfortunately, I still wasn't able to understand the "unable to find bin/heimdall.exe" (or similar) bug on windows.
 
  • Like
Reactions: tstuart

tstuart

Member
Dec 30, 2012
6
4
I allowed it to update and same issue. It just sits at the screen.
I've tried monitoring the size of the free-droid folder and it's not increasing at all. Just sits at 1.45GB.
 

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
I allowed it to update and same issue. It just sits at the screen.
I've tried monitoring the size of the free-droid folder and it's not increasing at all. Just sits at 1.45GB.
At which step does it hang? Does it pass the initial (preparing/setup) screen? Do you get to see the Start button?
If really nothing happens, the folder should be more like 180mb, not 1,4gb. What it taking up that space in there?
 
  • Like
Reactions: tstuart

tstuart

Member
Dec 30, 2012
6
4
It's after clicking start. The green bar across the bottom had downloading above it. Goes all the way to the right and then just sits.
I'll try a fresh download of free Droid today.
 

tstuart

Member
Dec 30, 2012
6
4
This might be a known buf I am working on. Sometimes Free-Droid is having trouble downloading a ROM. Do you get am error message?

No errors. I've now deleted old copies and downloaded fresh from website.
It opened, found my phone, etc all without issue.
Folder size was approx 180MB at this point.

I then put the x stating I have backups and click start. It shows Downloading goes across entire screen and now just sits.
Folder size is now 580MB

Here is the log file incase it helps. It's stopped adding information about 10 mins before I posted this
2019-12-13 10:00:52 -0700 - Setup successful.
2019-12-13 10:13:10 -0700 - Device connection update: android
2019-12-13 10:13:16 -0700 - new device: SM-G900F (codename: klte) (running custom rom)
2019-12-13 10:23:14 -0700 - IOError: Net::HTTPOK#read_body called twice
2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http/response.rb:198:in `read_body'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:252:in `block in download'

2019-12-13 10:23:14 -0700 - org/jruby/RubyIO.java:1160:in `open'

2019-12-13 10:23:14 -0700 - org/jruby/RubyKernel.java:321:in `open'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/open-uri.rb:37:in `open'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:251:in `block in download'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1513:in `block in transport_request'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http/response.rb:165:in `reading_body'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1512:in `transport_request'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1474:in `request'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:235:in `block in download'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:914:in `start'

2019-12-13 10:23:14 -0700 - uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:609:in `start'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:230:in `block in download'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:2170:in `retry_on_http_connection_problem'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:229:in `download'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:1067:in `block in dl_lineageos'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:2170:in `retry_on_http_connection_problem'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:1026:in `dl_lineageos'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:182:in `block in get'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:2170:in `retry_on_http_connection_problem'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/get.rb:162:in `get'

2019-12-13 10:23:14 -0700 - uri:classloader:/shoes-app/res/manager.rb:199:in `block in get_files'
 
  • Like
Reactions: imska

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
New update released with a lot of bug fixes.
(Unfortunately, some users still get "bin/heimdall.exe not found" errors and I haven't found out why yet. Possibly antivirus raising a false positive? Any help investigating is welcome.)
 

tstuart

Member
Dec 30, 2012
6
4
Updated today and tried it out. I'm getting past downloading now and it appears to start working. But it's now getting stuck at "Getting back to TWRP". The phone was sitting in TWRP but nothing else happens, just sits here.

Here is the log so far:

2019-12-16 08:45:21 -0700 - Setup successful: Free-Droid 0.7.12 on windows
2019-12-16 08:57:23 -0700 - Device connection update: android
2019-12-16 08:57:29 -0700 - new device: SM-G900F (codename: klte) (running custom rom)
2019-12-16 09:00:38 -0700 - Starting new flashing procedure.
2019-12-16 09:00:39 -0700 - Call to flash_conductor with device state: android
2019-12-16 09:00:39 -0700 - Progress is: {:unlock=>false, :twrp=>false, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 09:00:39 -0700 - Checking progress...
2019-12-16 09:00:39 -0700 - No bootloader unlock needed on Samsung devices.
2019-12-16 09:00:39 -0700 - Detected custom rom. Assuming TWRP already installed.
2019-12-16 09:00:41 -0700 - Progress is: {:unlock=>true, :twrp=>true, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 09:00:47 -0700 - Device connection update: disconnected
2019-12-16 10:03:51 -0700 - Device connection update: heimdall
2019-12-16 10:03:51 -0700 - Call to flash_conductor with device state: heimdall
2019-12-16 10:03:51 -0700 - Progress is: {:unlock=>true, :twrp=>true, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 10:03:51 -0700 - Checking progress...
2019-12-16 10:03:51 -0700 - Progress is: {:unlock=>true, :twrp=>true, :update_twrp=>false, :format_data=>false, :rest=>false, :flashme_pre=>false, :rom=>false, :root=>false, :nanodroid=>false, :patcher=>false, :flashme_post=>false}
2019-12-16 10:04:32 -0700 - Device connection update: disconnected
 
  • Like
Reactions: imska

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
Thanks for the report. With a few answers, this is a very helpful one!
Was the phone sitting in twrp from the beginning?
What is odd to me is that it looks like it rebooted into download mode instead of recovery/twrp. And this is where it actually stayed. So Free-Droid might be wrongly detecting that the device is in download mode.
Did you tick "force reflash twrp first" in expert settings?
 

tstuart

Member
Dec 30, 2012
6
4
To start the phone was just at it's normal home screen. I started the process and free-droid triggered the reboot into TWRP.
When looking at the phone it was sitting in TWRP, not download mode. I did reboot into download mode myself later about 20 mins after deciding it was frozen, but that didn't wake the process up at all.
I did not have any additional settings checked in Settings or Expert. Just the defaults.
 
  • Like
Reactions: imska

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
OK, that's more consistent with what the logs say. But I should have looked more closely at the times: the reboot to twrp must have happened as planned but Free-Droid did not detect the connected twrp for one hour as it seems.
Did Free-Droid install/flash that twrp or did you do it yourself before using Free-Droid? It is possible that the installed twrp version is buggy on ADB connection over USB. If so, you could try to tick the option to "force reflash twrp" in expert settings and let Free-Droid install the latest official twrp release for your phone.
Please let me know if that helped solve the problem.

Anyway, I should make Free-Droid able to handle a situation, where waiting any longer is not going to help. Maybe some user interaction is a good idea at a point like that.
 

imska

Senior Member
Aug 7, 2015
202
71
free-droid.com
It would be very helpful if someone getting the bug "cannot run program 'bin/heimdall.exe' (in directory ...): CreateProcess error=2, The system cannot find the file specified" in the log file could tell me if an antivirus did something like putting the heimdall.exe into quarantine. I would also need to know if the file is actually present in the bin folder of Free-Droid and if it can be accessed or run.
Any help is greatly appreciated.
 

Sands207

Senior Member
Oct 13, 2014
1,279
670
Portland,Maine
I have a MOTO G6 Play and it is an a only device, could i help you test to add support for treble devices? i can take and post logs and locats if needed and I'm familiar with ROM building and testing and debugging. Let me know if i can help
 

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    Code:
    I am not responsible for any damage resulting from the use of the Free-Droid software.

    Introduction
    Free-Droid is an application designed to help you install custom roms on your Android device. It is supposed to make the process of finding, downloading and installing a rom (with addons like Magisk, F-Droid and microG) as easy as possible. The primary audience is all the folks who do not really know anything about Android, TWRP or roms, but still would like to run a free, open-source and non-bloated Android on their devices. Using a free after-market rom like LineageOS should not be restricted to the few people with enough technical know-how to do the complex installation procedure all by themselves.
    Free-Droid is free and open-source and is available for Windows, Mac and Linux. As of now, it should be working fine with Samsung, OnePlus, NVidia, Sony and Motorola devices and with all other devices that already have TWRP installed.

    Download
    Download from the official website.

    Images
    screenshot-start.png

    screenshot-settings.png

    screenshot-expert.png

    screenshot-help.png

    screenshot-working.png


    What it does
    • help you activate USB debugging
    • help you install drivers
    • help you unlock the bootloader
    • download and install TWRP
    • update TWRP if a newer version is available
    • download and install a rom
    • download and install F-Droid and MicroG
    • download and install Magisk (legacy method, off by default)

    Features and explanations
    Please visit the Gitlab page of the project for more details!

    Compatibility
    Free-Droid is supposed to work on as many devices as possible. Supported brands as of now are:
    • Samsung
    • Motorola
    • Oneplus
    • NVidia
    • Sony
    • Every device that already has TWRP installed: launch Free-Droid, boot your device into TWRP and connect it with USB to your computer
    For the support status of a specific device, you can enter its model name here to check the compatibility.
    The Free-Droid application itself will tell upon device connection if it is compatible. If it says that your device is not supported, you can be sure that it will not work. As of now, Free-Droid will display device untested for most devices, because I will only mark a device as supported if a few people tested it and confirmed it is actually working fine.

    Changelog
    For a changelog please just have a look at the commits on gitlab.

    Beta
    Although Free-Droid already runs very well, I was not able to test it on a lot of computers and with many different devices. Therefore, consider Free-Droid to be beta software for now.
    Besides, there are a few things that still need to be implemented. What is not working yet:
    • project treble roms
    • devices that need special treatment like storage repartitioning
    Finally, in order to lead Free-Droid out of the beta phase of development, a lot of testing needs to be done. This way, Free-Droid will know more reliably which devices can be expected to be workable without issues and which ones it should deny to work on.

    Further development plans
    • add support for more brands that can be easily unlocked
    • handle project treble GSI roms
    • add a button to abort a running installation procedure
    • create packages for 32 bit computers
    • add MoKee rom
    • add /e/ rom
    • add possibility to install openGapps instead of microG ?
    • add possibility to select an additional zip to flash after the rom ?
    • fix crash on windows if changing folder on rom selection dialog
    • add a way to backup and restore using TWRP ?
    • add more documentation to the gitlab page ?
    A note about Magisk installation
    Installing magisk is getting more and more difficult. The installation method employed by Free-Droid is now discouraged and called a legacy installation method, because it can cause trouble and break the ability of the system to boot. For that reason, the installation of Magisk is turned off by default now in Free-Droid and a warning is issued to the user when turning it on.
    You can still try to install Magisk with Free-Droid during the normal installation procedure. But if your system does not boot afterwards, you will have to try again without Magisk. On some devices, you might need to know how to manually boot into recovery in order to retry the installation (device-specific hardware key combination).
    Free-Droid now also provides an easy way to try and install Magisk later on. The same ("legacy") installation method is used, but you can try the installation after the first boot of your newly installed system. I've seen a case where this would work while installing Magisk before the first boot would not work. This assumes that TWRP is connected or at least still installed.

    I need you
    Please test Free-Droid on your computer and with your device.
    In case of issues: use the button in Free-Droid to pack a bug report and either send it with an email or create an issue on the gitlab issue tracker.
    If you have a device of a supported brand for which Free-Droid does not find a rom by itself, please leave me a message with a link to a working rom (and/or TWRP image). If you can confirm that the rom is stable and fully working, I will add it to the Free-Droid unofficial archive and it will become available in Free-Droid.
    If you know about a faulty official release of TWRP or a rom, please also leave me a message. Example: the latest few official releases of TWRP for i9305 (Samsung Galaxy S3 LTE) are faulty and fail when trying to install a rom with sideload. Free-Droid uses a specific version of TWRP in that case and can automatically handle cases like that in general. I just need to know which devices need a workaround.

    Thanks To/Credits

    XDA:DevDB Information
    Free-Droid, Tool/Utility for all devices (see above for details)

    Contributors
    imska
    Source Code: https://gitlab.com/free-droid/free-droid


    Version Information
    Status:
    Beta

    Created 2019-07-01
    Last Updated 2021-04-09
    3
    This is beatiful! I wasted probably 2 hours this morning to get a android 9 on my old s5 since i need it for a project, i'm not a complete newby, i rooted and changed rom many time in the last 8 years but i do it every once in a while, so i always have to check for tutorials again and there is alwasy some step that don't go as planned, as today the rom was not installing, was almost ready to give up to not lose more time, saw this, was almost sure this would gone wrong somewhere as all automated stuff while after a couple of clics and 5/10m my s5 was ready with android 9 on it. THIS IS JUST BEATIFUL and great, hope it gain the visibility it deserve!
    Really GREAT job!
    2
    2
    download for linux coming soon ?
    2
    0.8.2
    • The data partition is now formatted by default instead of just wiped (can be switched off in the expert options, though it means the data partition would not be touched at all). This somehow helped make the installation of Lineage 18.1 work on pioneer.